Re: open translations database



Hi Christian

Gerry Ekstrom is our Swedish freelancer, his e-mail is 
"keekorok@eircom.net".  I chatted to Gerry and he is very 
interested in getting involved.  

Gerry spent a few hours looking at the overall Swedish quality 
of Gnome and found it to be very good.  At a high level, the 
main issues reported were as follows (see the attached QA report 
for details).  The report outlines suggested changes, however, 
the translators are the experts of the product, so feel free not 
to take our suggestions on board.

* A lot of applications had untranslated text.
 
* Extended characters  are sometimes displayed 
AA,AE,OE,aa,ae,oe.
 
*  Some Inconsistencies

Christian, let me know how we can help.
Aoife



> Delivered-To: gnome-i18n@gnome.org
> Date: Thu, 02 Nov 2000 15:50:12 +0100
> From: Christian Rose <menthos@menthos.com>
> X-Accept-Language: sv, en
> MIME-Version: 1.0
> To: GNOME i18n list <gnome-i18n@gnome.org>
> Subject: Re: open translations database
> Content-Transfer-Encoding: 7bit
> X-BeenThere: gnome-i18n@gnome.org
> X-Loop: gnome-i18n@gnome.org
> X-Mailman-Version: 2.0beta5
> List-Id: Internationalization (I18N) of GNOME 
<gnome-i18n.gnome.org>
> 
> Hello Aoife,
> 
> I believe most teams are interested in working together with 
people from
> Sun and it's contractors with improving the GNOME 
translations.
> Of course, I can only speak for the Swedish team, but we look 
very much
> forward to hear from Sun and the Swedish freelancer working 
for Sun (is
> there one?), possibly with a QA on existing GNOME 
translations.
> 
> 
> Christian
> 
> 
> 
> > Aoife Dunne - Sunsoft ELC wrote:
> > Gustavo, I can have our Brazilian Portuguese freelancer
> > perform a QA on GNOME translations and report his/her
> > feedback to the Brazilian Translation Team.  Let me know if
> > you are interested.
> > 
> > Bye for now
> > Aoife
> 
> 
> 
> 
################################################################
#######
> Christian Rose
> http://www.menthos.com                    	    
menthos@menthos.com
> 
################################################################
#######
> 
> _______________________________________________
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-i18n

Aoife Dunne
Program Manager
European Localisation Centre
Sun Microsystems Ireland Ltd
Hamilton House
East Point Business Park
Dublin 3
Ireland
Tel.:  	+353-1-8199-266
Fax:.	+353-1-8199-261
Email:	aoife.dunne@Ireland.Sun.COM

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
   <meta name="Generator" content="Microsoft Word 97">
   <meta name="GENERATOR" content="Mozilla/4.75 [en] (X11; U; SunOS 5.7 sun4u) [Netscape]">
   <title>SUN Quality Assurance Matrix</title>
</head>
<body>

<center><b><font size=+3>SUN Quality Assurance Document</font></b></center>

<p><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<p><b>QA CHECKLIST - To be filled in by LS</b>
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<table BORDER CELLPADDING=7 WIDTH="590" >
<tr>
<td VALIGN=TOP WIDTH="50%"><font size=-1>Product name</font></td>

<td VALIGN=TOP WIDTH="50%">&nbsp;Gnome</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="50%"><font size=-1>Platform/Product line/Version</font></td>

<td VALIGN=TOP WIDTH="50%">&nbsp;Linux</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="50%"><font size=-1>Code</font></td>

<td VALIGN=TOP WIDTH="50%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="50%"><font size=-1>Language</font></td>

<td VALIGN=TOP WIDTH="50%">&nbsp;Swedish</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="50%"><font size=-1>QA phase</font></td>

<td VALIGN=TOP WIDTH="50%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="50%"><font size=-1>Date</font></td>

<td VALIGN=TOP WIDTH="50%">&nbsp;30.10.00</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="50%"><font size=-1>List of files QAed</font></td>

<td VALIGN=TOP WIDTH="50%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="50%"><font size=-1>Completed Call-for-Work document
received?</font></td>

<td VALIGN=TOP WIDTH="50%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="50%"><font size=-1>Any outstanding queries in the
sample QAed?</font></td>

<td VALIGN=TOP WIDTH="50%">&nbsp;</td>
</tr>
</table>

<p><font size=-1><b>Important note:</b> Please note that the Linguistic
Specialist is required to fill in all applicable fields and most importantly
that a Pass/No Pass valuation is given for each applicable category as
well as for the overall assessment. Please also supply a high-level summary
assessment at the beginning of you report which should be directed to the
Project Manager. All comments apart from specific language examples and
corrections must be given in English.</font>
<p><font size=-1><b>Important note:</b> If the linguist at any stage during
the QA cycle deems the translation to be not fit for QA, the QA cycle should
be interrupted and the translation together with an initial report returned
to the vendor immediately for editing/correcting. Another day should be
earmarked for a second QA cycle. It is of greatest important that the vendor
gives priority to correcting the translation so that the second QA cycle
can take place as soon as possible.</font>
<br>&nbsp;
<br>&nbsp;
<p><b><font size=-1>SUMMARY REPORT ON THE TRANSLATION</font></b>
<br>&nbsp;
<table BORDER CELLPADDING=7 WIDTH="640" >
<tr>
<td VALIGN=TOP HEIGHT="263"><b><u><font size=-1>SUMMARY:</font></u></b>
<br>&nbsp;
<ul>
<li>
<b>The overall quality is good, however it does contain some inconsitencies
which should be fixed.</b></li>

<li>
<b>A lot of the applications have untranslated text. In this type of program,
a degree of unlocalized text can be acceptable. However, there are to many
incidences and to many places of mixed (translated and untranslated) occurences,
e g&nbsp; in&nbsp; </b>Program>Applikationer>gedit><b> were buttons and
PopUps are mixed. This needs to be rectified and looked at.</b></li>

<li>
<b>In my opinion, a more relaxed attitude could be taken to a program of
this nature. In other words, an acceptance of a less strict following of
Guidelines in e g Solaris. (E g 'd&ouml;da' = kill, is used for translation
of destroy, normally a less strong word would be used such as 'Finish',
'Close' or 'Exit', but strictly speaking, the translation is not wrong
(possible to change to 'Avsluta'). Another example is th use of 'applets'
in its english form rather then the swedish plural 'appletar', although
I personally prefer the swedish ending, it is quite common to see the english
form used in swedish computer literature.)</b></li>

<li>
<b>I would advise going through of the hole product in order to rectify
the language inconsistancy.&nbsp; I feel that some acceptance of residual
english in some areas is acceptable (e g PlugIns and Help) bearing in mind
the nature and history of the product. The fact that the product is stil
evolving also has a bearing on the issue.</b></li>

<li>
<b>Extended characters &Aring;&Auml;&Ouml;&aring;&auml;&ouml; are sometimes
displayed AA,AE,OE,aa,ae,oe. This does not look good, although perfectly
understandable, it should be rectified (Globally?).</b></li>
</ul>

<dir>
<dir>
<dir>
<dir>
<dir>
<dir>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;</dir>
</dir>
</dir>
</dir>
</dir>
</dir>
<b>SIGNATURE &amp; DATE: __Gerry Ekstrom _30.10.00______________________________________________________</b></td>
</tr>
</table>

<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<p><b>REPORT</b>
<br>&nbsp;
<table BORDER CELLPADDING=7 WIDTH="590" >
<tr>
<td VALIGN=TOP WIDTH="17%"><font size=-1>Location of error</font></td>

<td VALIGN=TOP WIDTH="17%"><font size=-1>US text</font></td>

<td VALIGN=TOP WIDTH="17%"><font size=-1>Translated text</font></td>

<td VALIGN=TOP WIDTH="17%"><font size=-1>Description of error/issue&nbsp;</font></td>

<td VALIGN=TOP WIDTH="17%"><font size=-1>Required/suggested correction&nbsp;</font></td>

<td VALIGN=TOP WIDTH="17%"><font size=-1>Comments</font></td>
</tr>

<tr>
<td>rcm (Right Cklick Mouse)</td>

<td></td>

<td></td>

<td>Untranslated</td>

<td></td>

<td>(except 'Ny')</td>
</tr>

<tr>
<td>Dialog Boxes>Headers</td>

<td></td>

<td></td>

<td>Mostly Untranslated</td>

<td></td>

<td></td>
</tr>

<tr>
<td><b>? </b>Messages</td>

<td></td>

<td></td>

<td>Text Untranslated</td>

<td></td>

<td></td>
</tr>

<tr>
<td>Program>Applikationer>gedit></td>

<td>Open, Print, Find, Line, Exit, Untitled</td>

<td></td>

<td>Untranslated</td>

<td></td>

<td></td>
</tr>

<tr>
<td>Program>Applikationer>gedit>PopUps
<br>(Ny, &Aring;ngra, G&ouml;r om, Line)</td>

<td></td>

<td></td>

<td>Untranslated</td>

<td></td>

<td></td>
</tr>

<tr>
<td>Program>Applikationer>gedit</td>

<td>Documents
<br>also >Untitled</td>

<td></td>

<td>Untranslated</td>

<td></td>

<td></td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="17%">&nbsp;Program>Applikationer>gedit>Arkiv</td>

<td VALIGN=TOP WIDTH="17%">Revert, Print Preview....,&nbsp; Close all</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;Untranslated&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="17%">&nbsp;Program>Applikationer>gedit>Redigera</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;Go to Line</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;Untranslated&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="17%">&nbsp;Program>Applikationer>gedit>Plugins</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;Untranslated&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="17%">&nbsp;Program>Applikationer>Dia>PopUps</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;Some Untranslated</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="17%">&nbsp;Program>Applikationer>Adressbok>Adresser/Telefon
<br>(gnomecard)</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;Untranslated</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;Also Web page (N&auml;tverk)</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="17%">&nbsp;Program>Applikationer>gnucash>
<br>Rapporter>Transaktionsrapport</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;Explanation Untranslated</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>
</tr>

<tr>
<td>Program>Applikationer>gnucash>Alternativ>
<br>Inst&auml;llningar>Allm&auml;n</td>

<td>Use accounting labels</td>

<td></td>

<td>Untranslated</td>

<td>Anv&auml;nd bokf&ouml;ringstermer</td>

<td></td>
</tr>

<tr>
<td>Program>Verktyg>S&ouml;kverktyg</td>

<td>Show Command</td>

<td></td>

<td>Untranslated</td>

<td></td>

<td>Also Dialog Box</td>
</tr>

<tr>
<td>Program>Verktyg>F&auml;rgvisaren(GColorsel)</td>

<td></td>

<td></td>

<td>Mixed Untranslated</td>

<td></td>

<td></td>
</tr>

<tr>
<td>Program>System>Systemlogg &ouml;vervakare>Visa</td>

<td>Preferences...</td>

<td></td>

<td>Untranslated</td>

<td></td>

<td>Also Dialog Box</td>
</tr>

<tr>
<td>Program>Inst&auml;llningar>GNOME Konrollcenter>Sawfish window manager</td>

<td></td>

<td></td>

<td>Mixed Untranslated</td>

<td></td>

<td></td>
</tr>

<tr>
<td>Program>Inst&auml;llningar>GNOME Konrollcenter>Skrivbord></td>

<td>Legacy Applicationa</td>

<td></td>

<td>Untranslated</td>

<td></td>

<td></td>
</tr>

<tr>
<td>Program>Inst&auml;llningar>GNOME Konrollcenter>Skrivbord>
<br>Temav&auml;ljare</td>

<td></td>

<td>foerhandsgranskning
<br>haer
<br>Testtextfaelt
<br>Tvaa
<br>AEro</td>

<td>'&aring;,&auml;,&ouml; &amp; &Auml;' has been diplayed as 'aa, ae,
oe &amp; AE'</td>

<td>f&ouml;rhandsgranskning
<br>h&auml;r
<br>Testtextf&auml;lt
<br>Tv&aring;
<br>&Auml;ro</td>

<td></td>
</tr>

<tr>
<td>Program>Inst&auml;llningar>Imlib-konfiguration</td>

<td></td>

<td></td>

<td>Mostly Untranslated</td>

<td></td>

<td></td>
</tr>

<tr>
<td>Program>Inst&auml;llningar</td>

<td></td>

<td>Menyeditor</td>

<td>'Swenglish'</td>

<td>Menyredigerare</td>

<td></td>
</tr>

<tr>
<td>Program>Inst&auml;llningar>Menyeditor</td>

<td></td>

<td>ingen ikon</td>

<td>Truncation</td>

<td></td>

<td></td>
</tr>

<tr>
<td>Program>Programutveckling>MemProf</td>

<td></td>

<td></td>

<td>DropDowns, PopUps &amp; Kill in english</td>

<td></td>

<td></td>
</tr>

<tr>
<td>Program>Programutveckling>LATTE</td>

<td></td>

<td></td>

<td>Mixed Untranslated</td>

<td></td>

<td></td>
</tr>

<tr>
<td>Program>Grafik>Eye of the Gnome>Alternativ>Inst&auml;llningar...</td>

<td></td>

<td></td>

<td>Mixed Untranslated</td>

<td></td>

<td></td>
</tr>

<tr>
<td>Program>Grafik>gPhoto</td>

<td></td>

<td></td>

<td>Untranslated</td>

<td></td>

<td></td>
</tr>

<tr>
<td>Program>N&auml;tverk</td>

<td></td>

<td></td>

<td>Mostly Untranslated</td>

<td></td>

<td>gFTP &amp; Balsa mostly translatted</td>
</tr>

<tr>
<td>Program>Multimedia>Ljudinspelare</td>

<td></td>

<td>Koer mixer...
<br>AAngra alla aendringar
<br>Paaboerja inspelning
<br>AAngra alla aendringar gjorda paa det aktuella ljudklippet
<br>Koer GNOME mixern
<br>En enkel ljudinspelare och ljuduppspelare foer GNOME. Tillaegnad min
katt, Malte.</td>

<td>'&aring;,&auml;,&ouml; &amp; &Aring;' has been diplayed as 'aa, ae,
oe &amp; AA'</td>

<td>K&ouml;r mixer...
<br>&Aring;ngra alla &auml;ndringar
<br>P&aring;b&ouml;rja inspelning
<br>&Aring;ngra alla &auml;ndringar gjorda p&aring; det aktuella ljudklippet
<br>K&ouml;r GNOME mixern
<br>En enkel ljudinspelare och ljuduppspelare f&ouml;r GNOME. Till&auml;gnad
min katt, Malte.</td>

<td></td>
</tr>

<tr>
<td>Program>Multimedia>Ljudinspelare>
<br>Alternativ>Inst&auml;llningar(grecord)</td>

<td></td>

<td>aa, ae &amp; oe</td>

<td>'Display problem', see above</td>

<td>&aring;, &aring; &amp;&ouml;</td>

<td>GLOBAL</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="17%">&nbsp;Program>Multimedia>Ljudinspelare>
<br>Alternativ>Inst&auml;llningar>Ljud</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;Samplingsfrekvens:</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;Truncation</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>

<td VALIGN=TOP WIDTH="17%">&nbsp;</td>
</tr>

<tr>
<td>Program>Filhanterare</td>

<td></td>

<td></td>

<td>Mixed Untranslated</td>

<td></td>

<td></td>
</tr>

<tr>
<td>Program>Applikationer>Gnumeric kalkylblad>Redigera</td>

<td>Select</td>

<td></td>

<td>Untranslated</td>

<td>V&auml;lj</td>

<td>also DropDown</td>
</tr>

<tr>
<td>Program>Applikationer>Gnumeric kalkylblad>Infoga</td>

<td>Add/modify comment...</td>

<td></td>

<td>Untranslated</td>

<td>L&auml;gg till/&auml;ndra kommentar...</td>

<td></td>
</tr>

<tr>
<td>Program>Applikationer>Gnumeric kalkylblad><b>A</b>+</td>

<td></td>

<td></td>

<td>Mixed Untranslated PopUps (<b>A</b>+)</td>

<td></td>

<td></td>
</tr>

<tr>
<td>Program>Verktyg>Typsnittsv&auml;ljare>Filtet>
<br>Vikt:/S&auml;tt Bredd:</td>

<td></td>

<td></td>

<td>Untranslated</td>

<td></td>

<td></td>
</tr>

<tr>
<td>Favoriter (Dialog box - Header)</td>

<td></td>

<td>Favoriter</td>

<td>Truncation</td>

<td></td>

<td></td>
</tr>

<tr>
<td></td>

<td></td>

<td></td>

<td></td>

<td></td>

<td></td>
</tr>

<tr>
<td></td>

<td></td>

<td></td>

<td></td>

<td></td>

<td></td>
</tr>

<tr>
<td></td>

<td></td>

<td></td>

<td></td>

<td></td>

<td></td>
</tr>
</table>

<p><b><font size=-1>Explanatory comments:</font></b>
<p><font size=-1>?Location of error? may include a book name, page number,
file name, URL, path followed to SW item a numbering structure, etc. The
location must be unique or in the case of a general comment, this must
be clearly marked as ?global?.</font>
<p><font size=-1>The ?US text? may be optional but must be included if
the translation error is of the type mistranslation, omission, or misunderstanding
of original.</font>
<p><font size=-1>The ?Translated text? must be quoted exactly as it appears
in the document.</font>
<p><font size=-1>The ?Decription of error/issue? must be as per the error
categories listed above. All descriptions of errors must be given fairly
and non-subjectively.</font>
<p><font size=-1>A ?Required/suggested correction? must be offered by the
Linguistic QA Specialist, except where there are large passages left untranslated
which must be provided by the original vendor/translator.</font>
<p><font size=-1>?Comments? is an optional column which may be used by
the vendor if he strongly disagrees with corrections suggested by the Linguistic
QA Specialist.</font>
<p><font size=-1><b>Important note:</b> Sometimes corrections are of the
type that instead of one grammatical construction (e.g. noun construct)
another grammatical form (e.g. infinitive) should be used, particularly
in (sub)headings or captions. E.g. not ?Bearbeiten von Bildern?, but rather
?Bilder bearbeiten?. In such cases, these global changes need be quoted
only once (but marked ?global?) if the corrections are to be implemented
by the vendor. The must be quoted for each and every instance if the corrections
are to be implemented by an engineer in SUN.</font>
<br>&nbsp;
<br>&nbsp;
<br>
<br>
<br>
<center>
<p><b><font size=-1>COMPLIANCE CHECKLIST - DOCUMENTATION/HELP</font></b></center>

<p><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<p><b><font size=-1>ERROR CATEGORY: Accuracy</font></b>
<br>&nbsp;
<table BORDER CELLPADDING=7 WIDTH="590" >
<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Error type</font></td>

<td VALIGN=TOP WIDTH="26%"><font size=-1>Max. errors allowed</font></td>

<td VALIGN=TOP WIDTH="20%"><font size=-1>Errors found</font></td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Omissions/additions (e.g., text,
callouts, titles, index markers, graphics)</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>S/W references incorrect</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Mistranslations</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Headers/footers incorrectly translated</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>TOC/Index errors</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Cross-references/index markers
deleted</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>
</table>

<p><b><font size=-1>Acceptable level: 0 - 3 error per 1000 words</font></b>
<p><b><font size=-1>No. of errors: Rating : Pass ? No Pass ?</font></b>
<br>&nbsp;
<br>&nbsp;
<p><b><font size=-1>ERROR CATEGORY: Terminology</font></b>
<br>&nbsp;
<table BORDER CELLPADDING=7 WIDTH="590" >
<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Error type</font></td>

<td VALIGN=TOP WIDTH="26%"><font size=-1>Max. errors allowed</font></td>

<td VALIGN=TOP WIDTH="20%"><font size=-1>Errors found</font></td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Glossary not adhered to</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>S/W references incorrect</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Inconsistent terminology</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>
</table>

<p><b><font size=-1>Acceptable level: 0 - 3 error per 1000 words</font></b>
<p><b><font size=-1>No. of errors: Rating : Pass ? No Pass ?</font></b>
<br>&nbsp;
<br>&nbsp;
<p><b><font size=-1>ERROR CATEGORY: Language</font></b>
<br>&nbsp;
<table BORDER CELLPADDING=7 WIDTH="590" >
<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Error type</font></td>

<td VALIGN=TOP WIDTH="26%"><font size=-1>Max. errors allowed</font></td>

<td VALIGN=TOP WIDTH="20%"><font size=-1>Errors found</font></td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Semantics</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Spelling</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Grammar</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Punctuation</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Hyphenation</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Cross-referencing</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>
</table>

<p><b><font size=-1>Acceptable level: 0 - 3 error per 1000 words</font></b>
<p><b><font size=-1>No. of errors: Rating : Pass ? No Pass ?</font></b>
<br>&nbsp;
<br>&nbsp;
<p><b><font size=-1>ERROR CATEGORY: Style</font></b>
<br>&nbsp;
<table BORDER CELLPADDING=7 WIDTH="590" >
<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Error type</font></td>

<td VALIGN=TOP WIDTH="26%"><font size=-1>Max. errors allowed</font></td>

<td VALIGN=TOP WIDTH="20%"><font size=-1>Errors found</font></td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>General style</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Register/tone</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Style guide not followed</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Language variants/slang</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>
</table>

<p><b><font size=-1>Acceptable level: 0 - 4 error per 1000 words</font></b>
<p><b><font size=-1>No. of errors: Rating : Pass ? No Pass ?</font></b>
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<p><b><font size=-1>ERROR CATEGORY: Country</font></b>
<br>&nbsp;
<table BORDER CELLPADDING=7 WIDTH="590" >
<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Error type</font></td>

<td VALIGN=TOP WIDTH="26%"><font size=-1>Max. errors allowed</font></td>

<td VALIGN=TOP WIDTH="20%"><font size=-1>Errors found</font></td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Country standards</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Local suitability</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Company standards</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Translation guide-lines not followed
(if applicable)</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>
</table>

<p><b><font size=-1>Acceptable level: 0 - 4 error per 1000 words</font></b>
<p><b><font size=-1>No. of errors: Rating : Pass ? No Pass ?</font></b>
<br>&nbsp;
<br>&nbsp;
<p><b>Overall rating: Pass/No Pass</b>
<p><b>Requires second QA cycle: Yes/No</b>
<br>&nbsp;
<br>&nbsp;
<br>
<br>
<br>
<center>
<p><b><font size=-1>COMPLIANCE CHECKLIST - SOFTWARE</font></b></center>

<p><b><font size=-1>ERROR CATEGORY: Accuracy</font></b>
<br>&nbsp;
<table BORDER CELLPADDING=7 WIDTH="590" >
<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Error type</font></td>

<td VALIGN=TOP WIDTH="26%"><font size=-1>Max. errors allowed</font></td>

<td VALIGN=TOP WIDTH="20%"><font size=-1>Errors found</font></td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Omissions/additions</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Mistranslations</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>
</table>

<p><b><font size=-1>Acceptable level: 0 - 3 error per 1000 words</font></b>
<p><b><font size=-1>No. of errors: Rating : Pass ? No Pass ?</font></b>
<br>&nbsp;
<br>&nbsp;
<p><b><font size=-1>ERROR CATEGORY: Terminology</font></b>
<br>&nbsp;
<table BORDER CELLPADDING=7 WIDTH="590" >
<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Error type</font></td>

<td VALIGN=TOP WIDTH="26%"><font size=-1>Max. errors allowed</font></td>

<td VALIGN=TOP WIDTH="20%"><font size=-1>Errors found</font></td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Glossary not adhered to</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Inconsistent terminology</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>
</table>

<p><b><font size=-1>Acceptable level: 0 - 3 error per 1000 words</font></b>
<p><b><font size=-1>No. of errors: Rating ?: Passed ? Failed ?</font></b>
<br>&nbsp;
<br>&nbsp;
<p><b><font size=-1>ERROR CATEGORY: Language</font></b>
<br>&nbsp;
<table BORDER CELLPADDING=7 WIDTH="590" >
<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Error type</font></td>

<td VALIGN=TOP WIDTH="26%"><font size=-1>Max. errors allowed</font></td>

<td VALIGN=TOP WIDTH="20%"><font size=-1>Errors found</font></td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Semantics</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Spelling</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Grammar</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Punctuation</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Abbreviations</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>
</table>

<p><b><font size=-1>Acceptable level: 0 - 3 error per 1000 words</font></b>
<p><b><font size=-1>No. of errors: Rating : Pass ? No Pass ?</font></b>
<br>&nbsp;
<br>&nbsp;
<p><b><font size=-1>ERROR CATEGORY: Functionality</font></b>
<br>&nbsp;
<table BORDER CELLPADDING=7 WIDTH="590" >
<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Error type</font></td>

<td VALIGN=TOP WIDTH="26%"><font size=-1>Max. errors allowed</font></td>

<td VALIGN=TOP WIDTH="20%"><font size=-1>Errors found</font></td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Core functionality</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Hotkey/shortcut functionality</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Platform/hardware compatibility&nbsp;</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Keyboard layout/code page</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>UI problems (alignment, sizing,
positioning, truncation)</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>
</table>

<p><b><font size=-1>Acceptable level: 0 - 3 error per 1000 words</font></b>
<p><b><font size=-1>No. of errors: Rating : Pass ? No Pass ?</font></b>
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<p><b>ERROR CATEGORY: Country</b>
<br>&nbsp;
<table BORDER CELLPADDING=7 WIDTH="590" >
<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Error type</font></td>

<td VALIGN=TOP WIDTH="26%"><font size=-1>Max. errors allowed</font></td>

<td VALIGN=TOP WIDTH="20%"><font size=-1>Errors found</font></td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Country standards</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Local suitability</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Company standards</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>

<tr>
<td VALIGN=TOP WIDTH="54%"><font size=-1>Translation guide-lines not followed
(if applicable)</font></td>

<td VALIGN=TOP WIDTH="26%">&nbsp;</td>

<td VALIGN=TOP WIDTH="20%">&nbsp;</td>
</tr>
</table>

<p><b><font size=-1>Acceptable level: 0 - 4 error per 1000 words</font></b>
<p><b><font size=-1>No. of errors: Rating : Pass ? No Pass ?</font></b>
<br>&nbsp;
<br>&nbsp;
<p><b>Overall rating: Pass/No Pass</b>
<p><b>Requires second QA cycle: Yes/No</b>
<br>&nbsp;
<br>&nbsp;
<p><b><font size=+1>A Pass/No Pass must be given for both the overall rating
and for all the different quality categories!</font></b>
<p><font size=-1><b>Important note:</b> A No Pass means that the vendor
must carry out an internal QA/edit of the <i>entire translation</i>, not
just the marked up pages/chapters.</font>
<p><font size=-1>A Pass means that the suggested corrections must be implemented
but that the rest of the translation can be left as is.</font>
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<p><b><font size=+1>Reference</font></b>
<p><b><font size=-1>Ratings and ratings parameters</font></b>
<p><font size=-1>The aim - excellent quality</font>
<p><b><font size=-1>Documentation, help</font></b>
<dir>
<dir>
<dir>
<dir>
<dir>
<dir><font size=-1><i>Language</i>: Describes functionality very accurately.
Information correctly translated, concise and easily accessible. Consistent
use of terminology and style. Adhering to glossary, style guide and any
guidelines. No grammar, punctuation or spelling errors. All page references
and cross-references correct. Complete index. Correct country standards
used.</font>
<p><font size=-1><i>Formatting</i>: All standard fonts and templates used.
No paragraph style or character formatting errors. All art referenced correctly.
No index, formatting or reference errors. All page references correct.
Help is complete with correct alignment and no display errors.</font>
<p><font size=-1><i>Functionality</i>: Documentation and help fully consistent
with software. Correct art pieces inserted throughout with all callout
references in documentation accurate. Technically accurate localisation
with no misleading statements, showing a thorough understanding of the
product. No topic or footnote errors in help.</font>
<p><b><font size=-1>Software</font></b>
<p><font size=-1><i>Language</i>: No language bugs, Completely, accurately
localised. Examples well localised. UI terms consistent and appropriate
to platform. Adhering to glossary and SUN guidelines. Describes functionality
accurately.</font>
<p><font size=-1><i>Formatting/functionality</i>: Dialog boxes all correctly
sized. No duplicate hotkeys. All text items localised, aligned correctly
and fully visible on the screen.</font>
<br>&nbsp;
<br>&nbsp;
<p><font size=-1>What to look out for - unsatisfactory quality:</font>
<p><b><font size=-1>Documentation, help</font></b>
<p><font size=-1><i>Language</i>: Product difficult to use due to omissions
in translated text, mistranslations due to misunderstanding the source
or lack of information. Discrepancies between software and documentation.
Information difficult to access. Examples not or not well localised. Writing
style poor, terminology inconsistent. Numerous grammar, punctuation or
spelling errors. Serious inconsistencies, errors in page references, cross-references
or index. Unacceptable errors in country standards.</font>
<p><font size=-1><i>Formatting</i>: Serious formatting and layout errors.
Standard fonts and templates not adhered to. Paragraph style or character
formatting errors. Art not referenced correctly. Help does not compile
or contains alignment and display errors. Requires a significant amount
of rework to comply with market requirements</font>
<p><font size=-1><i>Functionality</i>: Inconsistencies between documentation,
help and software. Jumps/popups not functioning in help. Incorrect art
pieces inserted or inaccurate callout references in documentation. Poor
understanding of product leading to inadequate technical localisations
throughout. Topic or footnote errors in help.</font>
<p><b><font size=-1>Software</font></b>
<p><font size=-1><i>Language</i>: Language bugs, inadequate or incomplete
localisation. Examples not or not well localised. Inconsistent UI terms
or not suitable for platform used. Not adhering to glossary or SUN guidelines.
Functionality not accurately expressed.</font>
<p><font size=-1><i>Formatting/functionality</i>: Significant number of
localisation bugs. It takes longer to report the bugs than to test the
product, demonstrating a lack of any QA check before hand over. Duplicate
hotkeys. Text items not aligned correctly or truncated on the screen. A
significant amount of rework is required to bring the software to an acceptable
standard.</font>
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;
<br>&nbsp;</dir>
</dir>
</dir>
</dir>
</dir>
</dir>
<font size=-1>The aim of this document is to outline SUN?s language quality
assurance matrix.</font>
<p><b><font size=-1>Goals</font></b>
<ul>
<li>
<font size=-1>to provide SUN Program Managers with an explicit and documented
system to evaluate a vendor?s quality level in any translation project
undertaken and to ensure that all translated products achieve an appropriate
level of language and internationalisation quality for the target market.</font></li>

<li>
<font size=-1>To define the roles and responsibilities for the Linguistic
QA Specialists</font></li>
</ul>
<font size=-1>This document provides information on how the language quality
of translated products should be assessed. It outlines the criteria used
for evaluating quality and describes the recommended reporting procedures.</font>
<p><font size=-1>This document is addressed to the Linguistic QA Specialists.
Their core responsibilities are:</font>
<ul>
<li>
<b><font size=-1>Language Quality Assurance</font></b></li>

<li>
<b><font size=-1>Terminology</font></b></li>
</ul>
<font size=-1>Note: Since all Linguistic QA Specialists used by SUN are
a) freelance linguists and b) not involved in the translation/localisation
process prior to delivery by the vendor they have no role in language support
during a translation project, stylistic or terminological guidelines for
translation or any scheduling issues. Their role is purely to assess the
?finished? and delivered translation and to suggest corrective action.</font>
<p><b><font size=-1>Prerequisites for a succesful QA cycle</font></b>
<p><font size=-1>Theses are dealt with in more detail in a separate document.
The following are purely some main checkpoints.</font>
<ul>
<li>
<font size=-1>The PM will schedule a QA phase appropriate to the size and
complexity of the material and provide requisite hardware.</font></li>

<li>
<font size=-1>The PM will provide all relevant information on the translated
product, including glossaries and style guide used by the vendor (whether
supplied by SUN or nor).</font></li>

<li>
<font size=-1>The PM will either forward the suggested corrections to the
vendor to be implemented, or arrange for the corrections to be implemented
by an engineer (in rare instances theLinguistic QA Specialist may be asked
to implement the corrections).</font></li>

<li>
<font size=-1>The Linguistic QA Specialist will return a clear feedback
on the quality found using the prescribed quality matrix and give recommended
solutions to the language problems found. All correspondence must be in
English to allow the PM or an engineer to access the information and possibly
plan for an additional QA cycle in case of major problems.</font></li>

<li>
<font size=-1>Every linguistic QA must state a clear Pass or No Pass which
can be included in the Vendor Scorecard Form.</font></li>

<li>
<font size=-1>Each Linguistic QA Specialist must have the SUN general glossary,
Style Guide and other relevant documents at the their disposal and refer
to these at all times.</font></li>

<li>
<font size=-1>The Linguistic QA Specialists are not responsible for functionality,
resizing and formatting issues.</font></li>
</ul>

<br>&nbsp;
<br>&nbsp;
<p><b>Language criteria to be taken into consideration</b>
<p><font size=-1>The criteria used by SUN to determine quality and errors
in printed and online documentation and software are:</font>
<p><font size=-1><i>Accuracy</i> omissions, additions, cross-references,
headers/footers</font>
<p><font size=-1><i>Terminology</i> glossary adherence, consistency, context,
abbreviations</font>
<p><font size=-1><i>Language</i> grammar, semantics, punctuation, spelling</font>
<p><font size=-1><i>Style</i> general style, register/tone, language variants/slang</font>
<p><font size=-1><i>Country</i> country standards, local suitability, company
standards</font>
<p><font size=-1><b>Functional criteria in software</b> - GUI terminology,
cross-application/cross-platform terminology, abbreviations, key combinations
and sequences, core functionality, hotkey/shortcut functionality, codepage,
platform/application compatibility</font>
<p><font size=-1><b>Formatting criteria in software</b> - alignment, sizing,
truncation, non-displaying characters</font>
<br>&nbsp;
<br>&nbsp;
<p><b>Materials to be used for the QA:</b>
<p><font size=-1>Supplied glossaries</font>
<p><font size=-1>Supplied style guide</font>
<p><font size=-1>List of outstanding queries if any</font>
<p><font size=-1>Complete Call-for-Work document</font>
<p><font size=-1>QA Feedback form supplied</font>
<br>&nbsp;
<br>&nbsp;
<p><b>Project elements and fundamental QA prerequisites</b>
<p><font size=-1>All material is provided in electronic format. QA takes
place on-screen, any comments are in report format. There is no mark-up
on paper except in exceptional cases such as marketing and packaging material
or artwork. The file formats used for almost all printed and online documentation
are HTML, SGML, and Frame (MIF). In the case of marketing material it is
important to QA the PostScript files. When checking for consistency across
all components, the software takes precedence over all other project elements,
i.e. documentation and online help are evaluated against the software and
made to conform to it. It is furthermore important to ensure that the translation
is in line with other products in the product line. The major product lines
in SUN are Java, Solaris and hardware-related products. There may in future
be an additional educational product line.</font>
<p><font size=-1>As a rule of thumb, between 10% and 20% of a translation
are QAed, or in the case of short documents a minimum of one day is set
aside for QA, in which case the entire document may be checked. For longer
translations the word count must be known and provided by the PMs on the
Product Information Sheet.</font>
<p><font size=-1>The Linguistic QA Specialists will select 10-20% of the
translation based on the word count provided. It is important to select
random samples of a translation for QA, i.e. not chapters 1 to 3 but rather
e.g. 10 pages from chpt. 4, all of chpt. 7, 2 appendices plus the letter
M from the index checked against the relevant pages.</font>
<p><font size=-1>When checking online help, it is important to follow this
sequentially by proceeding through the TOC (again the above rules for random
sampling apply). Links and context-sensitivity should be checked for functionality
but not as a method for proceeding through the help system. In the case
of software, all of the UI must be checked plus 10-20% of other messages.</font>
<p><font size=-1>For scheduling/pricing purposes, it is assumed that a
Linguistic QA Specialist can check 8000 words of printed/online documentation
per day and 4000 words of software per day.</font>
<p><b><font size=-1>QA of printed and online documentation:</font></b>
<p><font size=-1>The translated document is evaluated against the base
product documentation. In the case of context-sensitive online help, the
compiled files are used in the evaluation. The QA takes place sequentially
and not by proceeding via links or the context-sensitivity function. All
printed and online documentation and context sensitive help are evaluated
against the software and made to conform to it.</font>
<p><b><font size=-1>Software QA:</font></b>
<p><font size=-1>The localised compiled software is evaluated against the
US software. The software QA is of critical importance. All of the User
Interface as well as 10-20% other messages should be evaluated. Software
QA may also involve some software testing to a lesser or higher degree.
In such cases test scripts would be of great help to the Linguistic QA
Specialists. On the UI a No Error Pass is required.</font>
<p><font size=-1>Other elements - packaging, marketing, legal material.
For these the PostScript files or printouts are to be QAed. On all packaging,
marketing and legal material a No Error Pass is required.</font>
<br>&nbsp;
<br>&nbsp;
</body>
</html>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]