Hi,
<[EMAIL PROTECTED] ( Marc) (A.) (Lehmann )> writes:
> > Am Son, 2001-10-07 um 18.09 schrieb 1002470948:
> >
> > >
> > > Willkommen zu GIMP
>
> just a nitpick, that should have been "de-DE" etc.
I have never seen "de-DE" being used anywhere, not even in XML files. A
quick search in
> Am Son, 2001-10-07 um 18.09 schrieb 1002470948:
>
> >
> > Willkommen zu GIMP
just a nitpick, that should have been "de-DE" etc. (I hope the next xml
revision will allow the much better three-letter-iso-639 codes).
--
-==- |
---
Am Son, 2001-10-07 um 18.09 schrieb 1002470948:
>
>
>
> Welcome to The GIMP
> Willkommen zu GIMP
> Bienvenue sr GIMP
>
>
> The advantage is that translators can use their standard tools and can
> decide to edit the po file in whatever encoding they like. The parser to
> rea
Sven Neumann wrote:
[snip]
> The advantage is that translators can use their standard tools and can
> decide to edit the po file in whatever encoding they like. The parser to
> read this file should be pretty much straightforward including the
> language handling. This solution will require some
> The format I've outlined above still has one problem unrelated to i18n:
> Do we want to allow paragraphs in tips for nicer layouting and how do
> we represent them? By adding a ... tag ?!
No. Any tip long enough to require an additional paragraph should not
be a tip. That information should
Hi,
I think the mails on the list show that there is a lot of confusion about
how intltool (former xml-i18n-tools) works and how it can be used for our
purposes. We seem to agree that a simple XML format for the tips would be
nice and extensible enough for future additions. What remains is the
