From david.suarez at yahoo.com  Wed Dec 19 21:54:46 2007
From: david.suarez at yahoo.com (=?ISO-8859-1?Q?David_Su=E1rez_Pascal?=)
Date: Wed, 19 Dec 2007 15:54:46 -0600
Subject: [Po4a-devel] XML attribute translation
Message-ID: <35cb4400712191354o4e8464bfoe4b9bbecc2fa624@mail.gmail.com>

Hi, I'm employing po4a to manage translation of DocBook XML files and
until now it has served me well. However I added a new feature to the
original document requiring employment of XML attributes. The problem
is po4a seems to be not capable of managing translation of these. Is
that true or am I missing something on the config file?

Thanks,
David.


From jvprat at gmail.com  Thu Dec 20 00:52:55 2007
From: jvprat at gmail.com (Jordi Vilalta)
Date: Thu, 20 Dec 2007 01:52:55 +0100
Subject: [Po4a-devel] XML attribute translation
In-Reply-To: <35cb4400712191354o4e8464bfoe4b9bbecc2fa624@mail.gmail.com>
References: <35cb4400712191354o4e8464bfoe4b9bbecc2fa624@mail.gmail.com>
Message-ID: <f41149b20712191652j18947a81sc62157e2c4dfa617@mail.gmail.com>

Hi,

2007/12/19, David Su?rez Pascal:
> Hi, I'm employing po4a to manage translation of DocBook XML files and
> until now it has served me well. However I added a new feature to the
> original document requiring employment of XML attributes. The problem
> is po4a seems to be not capable of managing translation of these. Is
> that true or am I missing something on the config file?

po4a should be able to translate the attributes, but you have to
specify which ones. If those are standard DocBook XML attributes, then
just report which ones and those will be added to the docbook module.
If they are custom attributes, you have to specify them in the module
options.

For reference, look at these:
* the "attributes" option in the module options in
http://po4a.alioth.debian.org/man/man3pm/Locale::Po4a::Xml.3pm.php
* "Specifying options for the modules" in
http://po4a.alioth.debian.org/man/man1/po4a.1.php

I hope it helps.

Regards,

Jordi Vilalta


From kaloian at doganov.org  Fri Dec 28 19:11:48 2007
From: kaloian at doganov.org (Kaloian Doganov)
Date: Fri, 28 Dec 2007 21:11:48 +0200
Subject: [Po4a-devel] Turning off wrapping for a specific XHTML tag
Message-ID: <87d4sqljm3.fsf@doganov.org>

Using po4a to process XHTML documents, I have to turn of wrapping for a
specific XHTML tag (<script>) still considering the containing text as
translatable.  Po4a's Xml module provides a way to specify this using
the `W' character in the `tags' option:

   -o "tags=W<script>"

Unfortunately this leads to skipping the containing text of <script> as
non-translatable.  I can avoid this by adding `tagsonly' option, but
this way I practically have to list all possible XHTML tags in `tags',
just to turn off wrapping for one of them.

It would be much easier if there was a way to specify this wrap-flag
individually for a tag, without having to deal with global
skipping/non-skipping of all mentioned tags.

-- 
Protect your digital freedom and privacy, eliminate DRM, learn more at
http://www.defectivebydesign.org/what_is_drm



From kaloian at doganov.org  Fri Dec 28 20:49:46 2007
From: kaloian at doganov.org (Kaloian Doganov)
Date: Fri, 28 Dec 2007 22:49:46 +0200
Subject: [Po4a-devel] Turning off wrapping for a specific XHTML tag
References: <87d4sqljm3.fsf@doganov.org>
Message-ID: <87myruk0id.fsf@doganov.org>

Kaloian Doganov <kaloian at doganov.org> writes:

    It would be much easier if there was a way to specify this wrap-flag
    individually for a tag, without having to deal with global
    skipping/non-skipping of all mentioned tags.

Also, it will be useful if the wrapping of the <script> tag is turned
off by default in the Xhtml module.  The <script> tag by definition
contains code fragment of a syntax which Po4a does not understand.  The
most widely used language is ECMAScript, of course, and ECMAScript's
syntax almost ignores whitespace, with some notable exceptions.  For
example:

   <script>
   var label1 = "Hello";
   var label2 = "World"; // Please replace with your own messages!
   </script>

Becomes:

   <script>
   var label1 = "Hello"; var label2 = "World"; // Please
   replace with your own messages!
   </script>

which is not a valid ECMAScript code, so the interpreter ignores and the
document is broken.

Also, a <script> tag can contain other languages as well, for example
Python or Basic, where whitespace is even more significiant.  Therefore,
wrapping of such code fragments is not a good idea per se.

-- 
Protect your digital freedom and privacy, eliminate DRM, learn more at
http://www.defectivebydesign.org/what_is_drm