Subject: Re: commit -- Matrix stylesheet patch
From: Karl Ove Hufthammer (huftis@bigfoot.com)
Date: Sat Mar 31 2001 - 17:21:50 CST
----- Original Message -----
From: "Tom Briggs" <tomabi@jules.briggs.cx>
To: "Karl Ove Hufthammer" <huftis@bigfoot.com>
Cc: <abiword-dev@abisource.com>
Sent: Saturday, March 31, 2001 8:27 PM
Subject: commit -- Matrix stylesheet patch
> The locale matrix raises one burning question in my mind - how can the
> en-US translation not be 100% complete?
The locale matrix and the translation matrix are two different matrices. In the
translation matrix (generated by the dumpstrings.pl perl script abi/), 'en-US'
is at 99%. (The reason for this not being at 100%, is that one of the other
translations contains strings which were removed from the 'en-US' translation
(since they were no longer needed). They should of course be removed from all
translations.)
The locale matrix keeps track of how good AbiWord is working in different
locales. See the column explanation at the bottom of the document. Only the 'UI'
section has something to do with the actual *translation*. I remember there were
some issues with smart quotes being converted to plain quotes when saving. If
this bug isn't fixed, the 'Saving' cell must be marked 'buggy' for 'en-US'.
> How can be 0% complete, for that
> matter? :)
Because all 'en-US' cells are marked 'unknown'. Only cells with a value of 'yes'
(i.e., the feature is fully working) count in the percentage total. This needs
updating!
> And how to do I determine what percentage of the en-US
> translation is complete so I can update the matrix?
(The translation matrix can be automatically generated from the source; I assume
you're talking about the *locale* matrix here.) You'll have to check each
category ('Auto', 'Override' &c.) to see if the feature is working. Example:
For 'auto', just remove your preference file. If AbiWord starts up with the
'en-US' localization (and you're using an US English OS or has chosen US English
as your preferred language), mark this as 'yes' in the XML file (not the HTML
file). (You can see how this is done in the 'ui_matrix.xml' file -- just add an
value="yes" attribute).
Next you'll need to check if AbiWord accepts overriding the UI language. (It
does, so you can mark this 'yes'.)
For the 'UI' cell, you have to go through each and every dialog box and see if
there are any truncated labels (preferably on all platforms).
And so on ...
If you find a buggy (or not working) feature, mark the cell as 'no', 'buggy' or
'partially', create a BugZilla bug report (unless one already exists) and
reference this bug in the 'XML' file (examine the UI matrix XML file to see how
this is done). When you're finished, run the XML file through a XSLT processor
(if you don't have one, send the file to me and I'll do it) to generate the
corresponding HTML file. Check the new XML and HTML files into the tree.
-- Karl Ove Hufthammer
This archive was generated by hypermail 2b25 : Sat Mar 31 2001 - 17:51:40 CST