Re: Looking for the original of the Spanish gnome-user-guide translation
- From: Shaun McCance <shaunm gnome org>
- To: Danilo Šegan <danilo gnome org>
- Cc: kms passback co uk, gnome-doc-list gnome org
- Subject: Re: Looking for the original of the Spanish gnome-user-guide translation
- Date: 24 Sep 2004 13:29:54 -0500
On Fri, 2004-09-24 at 13:04, Danilo Šegan wrote:
> Today at 19:47, Shaun McCance wrote:
>
> > Would this be a good time to mention that xml2po rocks my world?
>
> Well, not really, since I believe the User Guide is the one that is
> going to cause most problems for current xml2po implementation
> (because of entities being used in XML files without DTD, such as
> part1.xml). If you try merging translations back, you'll notice that
> libxml2.serialize() simply drops entities which are not resolved
> properly, which of course sucks (or *I* do it using try..except code,
> I don't remember right now ;).
>
> Anything else apart from these part1.xml and part2.xml should be fine
> in translations, but that doesn't help much if you're looking for
> complete translations. I'll have to ask libxml2 folks on how to
> manage this appropriately.
I'll be switching things over to use XInclude anyway, so this shouldn't
really be a problem. I really think you shoud just expand entities when
syncing, and not bother with trying to recreate them in the translated
documents.
Except SYSTEM entities, they're just a typing convenience. And their
usage might not even be correct in many languages, given different
grammatical constructs. Maintaining them as-is seems like it would
cause a lot of problems. Alternately, you might want to mark the
internal subset for translation. And even then I think you should
resolve the entities when syncing. So you'd really just be allowing
translators to create their own internal subset.
As for SYSTEM entities, I think they're a total pain. If they use
entities themselves, they have to get them from their parent XML file.
Which means that they're not well-formed XML on their own. And you
can't throw an internal subset in them, because entity inclusion is
nothing more than a text slurp. Just resolve them when syncing, and
transators can translate the text in the context of the file they're
included into.
It'd be really nice to do some real-time chatting with you to resolve
some issues. Email just drags out too much. You don't come on IRC
anymore though, and I haven't managed to catch you on Jabber.
--
Shaun
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]