-----BEGIN PGP SIGNED MESSAGE-----
On Thursday 14 June 2001 09:49, Richard Braakman wrote:
> Hi, I've been working on a translation for nl. (It's going slowly,
> so I'm targeting it for the 1.8 release.)
Wonderful, thanks a lot.
> You see, its fields are tab-separated, but the entries vary greatly
> in width. This is not so bad yet for the de_DE column, but later
> columns are not really columns at all anymore. And the lines become
> much longer than my window is wide, adding to the confusion :)
I never intended to use the gnc-glossary file directly. Instead, each time
I edit it, I import the tab-delimited ascii file into my favorite
spreadsheet program, do my changes, print if I want to, and export it as
ascii grid again.
> I propose using a multiline format for the glossary, for example:
>
> Term: account
> Explanation: A detailed record of money spent and received
> de: Konto
> nl: rekening
I disagree, but I agree with that the tab-delimited ascii file is not a
long-term solution. My proposal would be that the glossary origin, i.e.
the english terms and the descriptions, stay in this tab-delimited format.
Each translation, however, is done in a seperate po-file.
Did you check out the gnome-i18n module? In gnome-i18n/glossary they do
exactly that, they just call the tab-delimited file a .csv file. In that
directory they provide a *simple* script csv-to-po as well.
I can create the necessary directory plus the conversion script. I will
be done with that by the end of next week.
Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
iQCVAwUBOynQRWXAi+BfhivFAQHevAP9GsbAThrovnK7VhLiWYuz1Bf+LG22Wb7t
jPI/FY0Xhc7gPfMHT0YCzae7dWG/iWJyt87vFK8VHK4eGBsVldpxMy7PZ7nV4MoB
hL5o3krjQHn9TIBe3PyDbFb6bKOe57ebmh+9gmCMWGsmXleXczFv/dnfxoHcliNx
324CqtfX8X0=
=31MU
-----END PGP SIGNATURE-----
_______________________________________________
gnucash-devel mailing list
[EMAIL PROTECTED]
http://www.gnumatic.com/cgi-bin/mailman/listinfo/gnucash-devel
