[Po4a-devel]Mising tag

[Denis Barbier]

On Wed, Apr 07, 2004 at 05:41:46PM +0200, juanrafael.fernandez@hispalinux.es wrote:
> I think this is the right list,

Welcome ;)

> so let's continue the thread.
> 
> Thank you very much for the prompt adoption of my proposals. Anyway
> I still haven't been able to use the tool not even with the cvs
> version.
> 
> 1.- po4a-gettextize stopped at <jobtitle>
>     <jobtitle>Professeur de sciences physiques</jobtitle>
>     (I have included it under "translate" in my local version)
>     and later at <city>
>     (also under "translate", you know some city names must be translated).

Hmmm, we should definitely check the full DocBook supported tags.
Martin, do you have some time?  Otherwise I'll do it.

> 2.- I'm not a/the developer, but maybe a better approach would be a
>     default "translate" for all tags that are not known. It's better
>     than failing, I'm afraid, and I don't see any harm in it.
> 
> 3.- Also the constrain that both files have exactly the same structure
>     is a real problem. I have a tendency to improve the tagging with
>     <acronym>... which is not that important, but how about the
>     mark-up for translators, which is normally
>     <articleinfo>
> 	<author>
> 	...
> 	</author>
> 	<othercredit>
> 	    <firstname>
> 	    ...
> 	    <surname>
> 	    ...
> 	    <contrib>
> 		Traducción al español
> 	    </contrib>
> 	    ...

Po4a-gettextize is a very special tool, it has to guess which strings
are translations of others, and the only information that can be used
is the document structure.  If both documents have an identical
structure, the 1x1 determination of translations is straightforward.
But when they differ, this task may become quite hard, so at the moment
it is better to stop than provide wrong translations.
When the PO file is created, you can change the structure of the
translated document (search for "addendum" in po4a(7)).

As po4a-gettextize is performed only once, maybe we did not pay enough
attention to solve these problems, and focused on po4a-translate which
is much more used.  But of course if you are unable to generate your
PO file, this becomes quite critical.
A workaround is to slightly modify your translated document to remove
extra tags, and put them later in addenda when your PO file is generated.

Denis