9:29 p.m.
Hello,
As a competition, I suggest po4a add 'translator-credits' support.
po4a-updatepo will generate 'translator-credits':
#: ../source/book.xml:0
msgid "translator-credits"
msgstr ""
"alice <alice(a)example.com>, 2005-2008\n"
"bob <bob(a)example.com>, 2005,2008"
if the source xml have info (bookinfo|articleinfo|info) element,
po4a-translate will
add 'othercredit' and 'copyright' like this:
<othercredit class="translator">
<firstname>alice</firstname>
<email>alice(a)example.com</email>
</othercredit>
<othercredit class="translator">
<firstname>bob</firstname>
<email>bob(a)example.com</email>
</othercredit>
<copyright>
<year>2005</year>
<year>2006</year>
<year>2007</year>
<year>2008</year>
<holder>alice <alice(a)example.com></holder>
</copyright>
<copyright>
<year>2005</year>
<year>2008</year>
<holder>bob <bob(a)example.com></holder>
</copyright>
Any comment?
Best Regards,
--
Dongsheng Song
8:40 a.m.
New subject: [Po4a-devel] [RFC] [Docbook] Add 'translator-credits' support
On Tue, Mar 03, 2009 at 11:29:07AM +0800, dongsheng.song(a)gmail.com wrote:
Hello,
As a competition, I suggest po4a add 'translator-credits' support.
po4a-updatepo will generate 'translator-credits':
#: ../source/book.xml:0
msgid "translator-credits"
msgstr ""
"alice <alice(a)example.com>, 2005-2008\n"
"bob <bob(a)example.com>, 2005,2008"
if the source xml have info (bookinfo|articleinfo|info) element,
po4a-translate will
add 'othercredit' and 'copyright' like this:
<othercredit class="translator">
<firstname>alice</firstname>
<email>alice(a)example.com</email>
</othercredit>
<othercredit class="translator">
<firstname>bob</firstname>
<email>bob(a)example.com</email>
</othercredit>
<copyright>
<year>2005</year>
<year>2006</year>
<year>2007</year>
<year>2008</year>
<holder>alice <alice(a)example.com></holder>
</copyright>
I would prefer that the translator string contains the information and the
formating tags.
Otherwise, I will have to parse and support too many things.
(what is a year, a firstname, a surname, a company, etc.)
Then I would prefer to have it as an option since it is not always wanted
and might be fragile (there might be an <info> tag that does not refer to
the document.
Also, only the first <info> should receive this extra information.
Otherwise, it looks feasible. But requires changes in the Xml module and
in the Docbook module.
This will have to be configurable from the Xml module point of view
because different format may want to use this for different tags.
Also for Docbook, multiple tags will require this to support different
versions of Docbook (looking at the history, the <*info> tags have never
been really stable)
--
Nekral
7:56 p.m.
New subject: [Po4a-devel] [RFC] [Docbook] Add 'translator-credits' support
2009/3/3 Nicolas François <nicolas.francois(a)centraliens.net>:
On Tue, Mar 03, 2009 at 11:29:07AM +0800, dongsheng.song(a)gmail.com
wrote:
> Hello,
>
> As a competition, I suggest po4a add 'translator-credits' support.
>
> po4a-updatepo will generate 'translator-credits':
>
> #: ../source/book.xml:0
> msgid "translator-credits"
> msgstr ""
> "alice <alice(a)example.com>, 2005-2008\n"
> "bob <bob(a)example.com>, 2005,2008"
>
> if the source xml have info (bookinfo|articleinfo|info) element,
> po4a-translate will
> add 'othercredit' and 'copyright' like this:
>
> <othercredit class="translator">
> <firstname>alice</firstname>
> <email>alice(a)example.com</email>
> </othercredit>
> <othercredit class="translator">
> <firstname>bob</firstname>
> <email>bob(a)example.com</email>
> </othercredit>
>
> <copyright>
> <year>2005</year>
> <year>2006</year>
> <year>2007</year>
> <year>2008</year>
> <holder>alice <alice(a)example.com></holder>
> </copyright>
I would prefer that the translator string contains the information and the
formating tags.
Otherwise, I will have to parse and support too many things.
(what is a year, a firstname, a surname, a company, etc.)
I don't think so, as xml2po has implement this, and translator like it.
Then I would prefer to have it as an option since it is not always
wanted
and might be fragile (there might be an <info> tag that does not refer to
the document.
Also, only the first <info> should receive this extra information.
Otherwise, it looks feasible. But requires changes in the Xml module and
in the Docbook module.
This will have to be configurable from the Xml module point of view
because different format may want to use this for different tags.
Also for Docbook, multiple tags will require this to support different
versions of Docbook (looking at the history, the <*info> tags have never
been really stable)
No, a valid Docbook document has only one qualified <*info>, we can only do
the process at the following xpath:
/article/articleinfo (DocBook 4.x)
/book/bookinfo (DocBook 4.x)
/article/info (DocBook 5.x)
/book/info (DocBook 5.x)
---
Dongsheng Song
4:23 a.m.
New subject: [Po4a-devel] [RFC] [Docbook] Add 'translator-credits' support
On Wed, Mar 04, 2009 at 09:56:54AM +0800, dongsheng.song(a)gmail.com wrote:
2009/3/3 Nicolas François <nicolas.francois(a)centraliens.net>:
> On Tue, Mar 03, 2009 at 11:29:07AM +0800, dongsheng.song(a)gmail.com wrote:
>> Hello,
>>
>> As a competition, I suggest po4a add 'translator-credits' support.
>>
>> po4a-updatepo will generate 'translator-credits':
>>
>> #: ../source/book.xml:0
>> msgid "translator-credits"
>> msgstr ""
>> "alice <alice(a)example.com>, 2005-2008\n"
>> "bob <bob(a)example.com>, 2005,2008"
>>
>> if the source xml have info (bookinfo|articleinfo|info) element,
>> po4a-translate will
>> add 'othercredit' and 'copyright' like this:
>>
>> <othercredit class="translator">
>> <firstname>alice</firstname>
>> <email>alice(a)example.com</email>
>> </othercredit>
>> <othercredit class="translator">
>> <firstname>bob</firstname>
>> <email>bob(a)example.com</email>
>> </othercredit>
>>
>> <copyright>
>> <year>2005</year>
>> <year>2006</year>
>> <year>2007</year>
>> <year>2008</year>
>> <holder>alice <alice(a)example.com></holder>
>> </copyright>
>
> I would prefer that the translator string contains the information and the
> formating tags.
>
> Otherwise, I will have to parse and support too many things.
> (what is a year, a firstname, a surname, a company, etc.)
>
I don't think so, as xml2po has implement this, and translator like it.
I will have a look, but at least for my name (Nicolas and François are
both very common firstnames or surnames in France), it would be impossible
to identify the first name. (And compound names or firstnames could make
it even more surprising (Pierre Jean François).
I don't know what the Berne Convention specifies about copyright, but
dates could maybe also be written in non-latin glyphs. This would make it
very hard to differentiate between names and dates.
An option could be to support both a very strict syntax (all lines using a
"Name <email>\n" syntax) and a more liberal syntax (if a line does not
match [^<]+\s+<[^>]+@[^>]+>(\\n)?
> Then I would prefer to have it as an option since it is not
always wanted
> and might be fragile (there might be an <info> tag that does not refer to
> the document.
>
> Also, only the first <info> should receive this extra information.
>
> Otherwise, it looks feasible. But requires changes in the Xml module and
> in the Docbook module.
> This will have to be configurable from the Xml module point of view
> because different format may want to use this for different tags.
>
> Also for Docbook, multiple tags will require this to support different
> versions of Docbook (looking at the history, the <*info> tags have never
> been really stable)
>
No, a valid Docbook document has only one qualified <*info>, we can only do
the process at the following xpath:
/article/articleinfo (DocBook 4.x)
/book/bookinfo (DocBook 4.x)
/article/info (DocBook 5.x)
/book/info (DocBook 5.x)
I think it is possible to put an info quite everywhere, even inside a
para:
http://www.docbook.org/tdg5/en/html/para.html
You can also have an article (or chapter) with an info, inside a book with
an info.
Adding a translator credit inside each info looks too much. Adding a
translator credit to the first <info> may be better, but may require the
usage of options to define which of these files have to add a translator
credit.
Best Regards,
--
Nekral
6:27 a.m.
New subject: [Po4a-devel] [RFC] [Docbook] Add 'translator-credits' support
2009/3/4 Nicolas François <nicolas.francois(a)centraliens.net>:
I will have a look, but at least for my name (Nicolas and François
are
both very common firstnames or surnames in France), it would be impossible
to identify the first name. (And compound names or firstnames could make
it even more surprising (Pierre Jean François).
I don't know what the Berne Convention specifies about copyright, but
dates could maybe also be written in non-latin glyphs. This would make it
very hard to differentiate between names and dates.
An option could be to support both a very strict syntax (all lines using a
"Name <email>\n" syntax) and a more liberal syntax (if a line does not
match [^<]+\s+<[^>]+@[^>]+>(\\n)?
Yes, We can only make a simple agreement。
I think it is possible to put an info quite everywhere, even inside a
para:
http://www.docbook.org/tdg5/en/html/para.html
You can also have an article (or chapter) with an info, inside a book with
an info.
Adding a translator credit inside each info looks too much. Adding a
translator credit to the first <info> may be better, but may require the
usage of options to define which of these files have to add a translator
credit.
Maybe my description is not clear. Yes, docbook document has many
<*info>. But we should only modify the following <*info>:
/article/articleinfo (DocBook 4.x)
/book/bookinfo (DocBook 4.x)
/article/info (DocBook 5.x)
/book/info (DocBook 5.x)
Every docbook document only has one such <*info>.
---
Dongsheng Song
12:19 p.m.
New subject: [Po4a-devel] [RFC] [Docbook] Add 'translator-credits' support
On Wed, Mar 04, 2009 at 08:27:39PM +0800, dongsheng.song(a)gmail.com wrote:
Maybe my description is not clear. Yes, docbook document has many
<*info>. But we should only modify the following <*info>:
/article/articleinfo (DocBook 4.x)
/book/bookinfo (DocBook 4.x)
/article/info (DocBook 5.x)
/book/info (DocBook 5.x)
Just to be explicit, /book/article/book (DocBook 5.x) would not receive
any information about the translator, right?
I will enter this as a wishlist bug the the Debian BTS (and also the bug
regarding <screen>), as this will require more work than I planed for the
next release.
Thanks for the suggestions,
--
Nekral
8:15 p.m.
New subject: [Po4a-devel] [RFC] [Docbook] Add 'translator-credits' support
2009/3/5 Nicolas François <nicolas.francois(a)centraliens.net>:
On Wed, Mar 04, 2009 at 08:27:39PM +0800, dongsheng.song(a)gmail.com
wrote:
>
> Maybe my description is not clear. Yes, docbook document has many
> <*info>. But we should only modify the following <*info>:
>
> /article/articleinfo (DocBook 4.x)
> /book/bookinfo (DocBook 4.x)
> /article/info (DocBook 5.x)
> /book/info (DocBook 5.x)
Just to be explicit, /book/article/book (DocBook 5.x) would not receive
any information about the translator, right?
What's the mean '/book/article/book' ?
I will enter this as a wishlist bug the the Debian BTS (and also the
bug
regarding <screen>), as this will require more work than I planed for the
next release.
Good news, I hope to implement in the in the near future, may be 0.37 ?
Thanks you,
---
Dongsheng Song
4:41 a.m.
New subject: [Po4a-devel] [RFC] [Docbook] Add 'translator-credits' support
On Thu, Mar 05, 2009 at 10:15:52AM +0800, dongsheng.song(a)gmail.com wrote:
2009/3/5 Nicolas François <nicolas.francois(a)centraliens.net>:
> On Wed, Mar 04, 2009 at 08:27:39PM +0800, dongsheng.song(a)gmail.com wrote:
>>
>> Maybe my description is not clear. Yes, docbook document has many
>> <*info>. But we should only modify the following <*info>:
>>
>> /article/articleinfo (DocBook 4.x)
>> /book/bookinfo (DocBook 4.x)
>> /article/info (DocBook 5.x)
>> /book/info (DocBook 5.x)
>
> Just to be explicit, /book/article/book (DocBook 5.x) would not receive
> any information about the translator, right?
>
What's the mean '/book/article/book' ?
I have no idea, but this is allowed in db5:
http://www.docbook.org/tdg5/en/html/article.html
> I will enter this as a wishlist bug the the Debian BTS (and also
the bug
> regarding <screen>), as this will require more work than I planed for the
> next release.
>
Good news, I hope to implement in the in the near future, may be 0.37 ?
Yes, that should be possible.
Best Regards,
--
Nekral
8:15 p.m.
New subject: [Po4a-devel] [RFC] [Docbook] Add 'translator-credits' support
2009/3/3 Nicolas François <nicolas.francois(a)centraliens.net>:
On Tue, Mar 03, 2009 at 11:29:07AM +0800, dongsheng.song(a)gmail.com
wrote:
> Hello,
>
> As a competition, I suggest po4a add 'translator-credits' support.
>
> po4a-updatepo will generate 'translator-credits':
>
> #: ../source/book.xml:0
> msgid "translator-credits"
> msgstr ""
> "alice <alice(a)example.com>, 2005-2008\n"
> "bob <bob(a)example.com>, 2005,2008"
>
> if the source xml have info (bookinfo|articleinfo|info) element,
> po4a-translate will
> add 'othercredit' and 'copyright' like this:
>
> <othercredit class="translator">
> <firstname>alice</firstname>
> <email>alice(a)example.com</email>
> </othercredit>
> <othercredit class="translator">
> <firstname>bob</firstname>
> <email>bob(a)example.com</email>
> </othercredit>
>
> <copyright>
> <year>2005</year>
> <year>2006</year>
> <year>2007</year>
> <year>2008</year>
> <holder>alice <alice(a)example.com></holder>
> </copyright>
I would prefer that the translator string contains the information and the
formating tags.
Otherwise, I will have to parse and support too many things.
(what is a year, a firstname, a surname, a company, etc.)
I don't think so, as xml2po has implement this, and translator like it.
Then I would prefer to have it as an option since it is not always
wanted
and might be fragile (there might be an <info> tag that does not refer to
the document.
Also, only the first <info> should receive this extra information.
Otherwise, it looks feasible. But requires changes in the Xml module and
in the Docbook module.
This will have to be configurable from the Xml module point of view
because different format may want to use this for different tags.
Also for Docbook, multiple tags will require this to support different
versions of Docbook (looking at the history, the <*info> tags have never
been really stable)
No, a valid Docbook document has only one qualified <*info>, we can only do
the process at the following xpath:
/article/articleinfo (DocBook 4.x)
/book/bookinfo (DocBook 4.x)
/article/info (DocBook 5.x)
/book/info (DocBook 5.x)
---
Dongsheng Song
5896
days inactive
5898
days old
8 comments
2 participants
participants (2)
-
Dongsheng Song -
Nicolas François