Re: How to handle XML elements in import filters' translations?
Asgeir Frimannsson <[email protected]> Wed, 29 Jun 2005 10:18:45 +1000
| Newsgroups | gmane.comp.kde.devel.kbabel |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 17 Jun 2005 07:17, Asgeir Frimannsson wrote: > On Thu, 16 Jun 2005 23:54, Stanislav Visnovsky wrote: > > Asgeir? IIRC you've done some work in this area, right? > > I have some thoughts on how we can improve this yes. - But I have a thesis > due this week, so will try and get back to this mail over the weekend :) It became a very long weekend sorry :) > Dňa Ut 14. Jún 2005 23:51 Nicolas Goutte napísal: > > I have noticed that Qt's translation files and XLIFF can have child > > elements in their translation elements (for example in <source> and > > <target> elements in XLIFF). > > > > However I have not much of an idea how we could show it to the user, as > > the user might have to translate XML and HTML tags and the XLIFF export > > filter should not try to take them as child elements. On the other side, > > if she show such tags to translators as <tag> instead of <tag> they > > would probably not be happy. Let's take an XLIFF example: Example-A: <source>This is a <tag>. This is a <ph id="1">placeholder</ph>. See the difference?</source> Here, "<tag>" should be displayed to translators as "<tag>", while some other form of visual indication should be given for representing the ph element contents. As an example, see how transolution [1] does this: http://people.redhat.com/asgeirf/transolution.png So how do we practically do this? I think the only feasible way is to replace PO as the data model, and model a richer format such as XLIFF (both PO [2] and TS can be fully mapped to XLIFF - keeping translators happy). As Nicolas has indicated in the svn log messages over the past weeks, a lot of what we're doing now, in regards to supporting XLIFF and TS, is 'hacks' using PO fields to store data. Well, I guess this is partly what I'm addressing in the Summer of Code project :) cheers, asgeir [1] http://transolution.python-hosting.com/ [2] http://xliff-tools.freedesktop.org/snapshots/po-repr-guide/wd-xliff-profile-po.html