Re: gnome-db2html2 and i18n

[Ali Abdin <aliabdin aucegypt edu>]

* Alexander Kirillov (kirillov@math.sunysb.edu) wrote at 17:59 on 25/08/00:
> 
> Here is one more bug: it seems that gnome-db2html2 is not
> internationalized (hope I spelled this correctly...). As you know,
> DocBook allows to specify the language of the document by using lang
> attribute,  e.g. 
> <book id="index" lang="ru">
> 
> What gnome-db2html2 needs to do (and doesn't at the moment) is:
> 
> 1. Modify all text strings it produces, such as "copyright" (generated
>    by <copyright>), "the section"
>    (generated by <xref>), etc, according to the language
>
>
> 2. Same for navigation labels "next", "prev" (when they are created) 

Okay - thanks for pointin this out - this should go into the Eazel bugtracker
:) We should 'i18n' the strings and they should go into the .po files of each
language. 

Ick - wait - this won't work .po files are for your /current/ locale and not
the doc's locale. Does anybody know a way around this? Do I have to include
some sort of header/table in the source with the different translations?
 
Suggestions welcomed :)

> 3. For languages which use encoding other than default iso8859-1, it
>    also needs to put appropriate meta tag in html output, e.g. 
> 
> <META http-equiv="Content-Type" content="text/html; charset=KOI8-R">
> 
> By the way, I am not sure how this should be done - do we need to have
> a table that lists default encodings for each language? Or do we
> require doc author to specify encoding as attribute:
> 
> <book id="index" lang="ru" encoding="KOI8-R">

I think the encoding should be present. This should be filed as a 'separate'
bug report from the above.

> But anyway, in the current form help systme is unusable for languages
> using encoding other than iso8859-1 - fixing this should be a top
> priority. 

Well - I agree that it should be fixed but I don't consider it 'top priority'
really - I mean the whole document is 'translated' so having a few words taht
are not translated is not really a huge issue.

It /should/ be fixed before release though.

Regards,
Ali