Re: Lampadas Bugzilla, status update, roadmap

[Ismael Olea <ismael olea org>]

El lun, 12-08-2002 a las 21:52, Alexander Bartolich 

> After a confusing run of 'info gettext' and a brief look at
> real-world .po files (WindowMaker-0.8) I have some questions.
> 
> We have separate directories for each table.
> Each directory holds separate files for each language.
> Each file defines a complete record, which can consist
> of several strings.
> 
> Can we have multiple .po files for one language?
> In different directories? Streaming them into a single file
> will make msgids even messier then it already seems it has to be.

The easy way is having _one_ po file. Is really easy to maintain.

And don't care about caos. If somebody needs to know the context of a
string the gettext system writes the filename and linenumber where it
occurs.
 
> The simplest example looks like this:
> 
> --- EN.m4 ---
> insert(strwelcometo,        [Welcome to])
> 
> --- DE.m4 ---
> insert(strwelcometo,        [Willkommen zu])
> 
> We absolutely need the key ('strwelcometo') to generate a SQL
> statement. The natural approach is thus:
> 
> --- EN.po ---
> msgid "strwelcometo"
> msgstr "Welcome to"
> 
> --- DE.po ---
> msgid "strwelcometo"
> msgstr "Willkommen zu"
> 
> Does this make sense for users of your tool?
> Or do you rely on something having real text?
> 
> --- DE.po ---
> # key=strwelcometo
> msgid "Welcome to"
> msgstr "Willkommen zu"
> 
> A more complicated example is
> 
> --- EN.m4 ---
> insert([my], [My Home], [],
> [
>      <p>This is your personal home page.</p>
>      <p>This table lists documents you have volunteered to
>         contribute to:</p>
>      <p>|session_user_docs|</p>
> ], 1)
> 
> Can we have linefeeds in a msgstr?
> And can we generate artificial msgids like
> 
> msgid "my_title"
> msgstr "My Home"
> msgid "my_menu_name"
> msgstr ""
> msgid "my_page"
> msgstr "<p>This is your per...
> 
> If you can live with this non-sensical msgids it's not difficult
> to produce .po files. The way back looks more challenging, though.
> 
> One problem I see with all this clever text processing is error
> handling. My m4-hack provides almost no syntax checking. Errors
> are raised by psql, and it requires some weird thinking to find
> the missing ] or ). Adding another layer makes me nervous.
> 
> We also have an alternative approach. I actually finished
> the export command back then, so we can generate a clean m4-file
> from database contents. Perhaps online editing of strings through
> lampadas is the better solution.
> 
> I also read that intltool provides a built-in solution for XML.
> A one-way conversion from m4 to XML is easy (implementing the
> macro/shell code in XSLT is not, but then you can't have everything).
> 
> 
> ______________________
> http://lists.tldp.org/
-- 
	A.Ismael Olea González

	mailto:ismael olea org	http://www.olea.org
	http://aduaneros.olea.org, la ONG sin futuro.

	El mundo debe empezar a tener miedo a un planeta OLEA