Re: Translation tools for documentation
- From: Danilo Segan <danilo gnome org>
- To: Tim Foster <Tim Foster Sun COM>
- Cc: "Francisco Javier F. Serrador" <serrador tecknolabs com>,=?utf-8?b?SW50ZXJuYWNpb25hbGl6?= =?utf-8?b?YWNpw4M=?= =?utf-8?b?woM=?= =?utf-8?b?w4LCs24gR25vbWU=?= <gnome-i18n gnome org>
- Subject: Re: Translation tools for documentation
- Date: Tue, 30 Mar 2004 11:04:16 +0200
Hi Tim,
Today at 9:33, Tim Foster wrote:
> Nope, actually we haven't done that yet ! That's a pretty hard thing to
> achieve, and get right all the time - it'd be an interesting problem to
> work on though. Basically, you're talking about sub-flows :
>
> "Here is < some list > an interesting list"
Thanks for all the pointers here (about XLIFF "sub-flows" etc).
>> Still, since I
>> cannot imagine how are you supporting sentence-reordering with
>> sentence-based translations, I suppose you've discovered that it's
>> very rarely needed
>
> Yep - translators don't seem to mind that it's not there.
Ok, that's interesting to know.
>> I'd like to see that solved for gettext as well: "xml-format" tag for
>> GNU gettext (like c-format), which would indicate that string needs to
>> be correct XML.
>
> Does it do printf-style format checking at the moment ? I've got a
> parser that recognises these which I need to build into the editor at
> some stage so we can nicely highlight things like "%%+05d".
Yes, it does handle printf-style format checking. I believe that's
the main point of "c-format" keyword :) I don't know how complete
are the checks it does, but I have yet to come across a case where it
doesn't work well.
Cheers,
Danilo
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]