4:59 a.m.
Sorry for being so ignorant.
Is po4a English centric? I mean, what if somebody translate a manual
starting from a language different from English (say French, like many
Framasoft projects)? Does it still work? If so, this passage in the po4a
manual might be misleading:
man po4a:
"Depending on your settings, po4a will discard the partially translated
documents, or produce a document mixing English (for the new or modified
paragraphs) and the target language (for paragraphs where translation is
already in the PO file)."
if it could be some other than English language, instead of English
should be used "source language" or something similar?
--
Amike,
Marco Ciampa
6:04 p.m.
Hello Marco,
thanks for your question. I started updating the doc to reflect your point,
which is perfectly valid, and at the end, I reworte the QUICK START part of the
po4a(1) documentation. The new version is here:
https://github.com/mquinson/po4a/blob/master/po4a#L602
Please comment before I update the POT files to ask translators to start the
translation.
Thanks for reporting,
Mt
Le samedi 20 août 2022 à 09:59 +0000, Marco Ciampa a écrit :
Sorry for being so ignorant.
Is po4a English centric? I mean, what if somebody translate a manual
starting from a language different from English (say French, like many
Framasoft projects)? Does it still work? If so, this passage in the po4a
manual might be misleading:
man po4a:
"Depending on your settings, po4a will discard the partially translated
documents, or produce a document mixing English (for the new or modified
paragraphs) and the target language (for paragraphs where translation is
already in the PO file)."
if it could be some other than English language, instead of English
should be used "source language" or something similar?
--
Amike,
Marco Ciampa
_______________________________________________
Devel mailing list -- devel(a)lists.po4a.org
To unsubscribe send an email to devel-leave(a)lists.po4a.org
--
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
7:26 p.m.
On Sun, Aug 21, 2022 at 01:04:58AM +0200, Martin Quinson wrote:
Hello Marco,
thanks for your question. I started updating the doc to reflect your point,
which is perfectly valid, and at the end, I reworte the QUICK START part of the
po4a(1) documentation. The new version is here:
https://github.com/mquinson/po4a/blob/master/po4a#L602
Please comment before I update the POT files to ask translators to start the
translation.
Thanks for reporting,
Mt
some people find it easier to interact with the translators through an
online platform such as S<weblate>, but this is beyond the scope of
S<po4a>.
I would say:
some people find it easier to interact with the translators through an
online platform such as S<weblate>; although this is beyond of its scope,
using S<po4a> for producing .po files can enable the use of such
collaborative platforms.
Anyway it seems to me ok, good work, very useful...
--
Amike,
Marco Ciampa
3:35 a.m.
On Sun, Aug 21, 2022 at 12:26:09AM +0000, Marco Ciampa wrote:
On Sun, Aug 21, 2022 at 01:04:58AM +0200, Martin Quinson wrote:
> Hello Marco,
>
> thanks for your question. I started updating the doc to reflect your point,
> which is perfectly valid, and at the end, I reworte the QUICK START part of the
> po4a(1) documentation. The new version is here:
> https://github.com/mquinson/po4a/blob/master/po4a#L602
>
> Please comment before I update the POT files to ask translators to start the
> translation.
>
> Thanks for reporting,
> Mt
some people find it easier to interact with the translators through an
online platform such as S<weblate>, but this is beyond the scope of
S<po4a>.
I would say:
some people find it easier to interact with the translators through an
online platform such as S<weblate>; although this is beyond of its scope,
using S<po4a> for producing .po files can enable the use of such
collaborative platforms.
Obviously this is only an example of what I meant to say, it could be
incorrect or not clear; I'm not a native English speaker so please do
what you think is better.
Anyway it seems to me ok, good work, very useful...
I spotted another passage:
"
What about the other translation tools for documentation using gettext?
As far as I know, there are only two of them:
"
I would say:
There are a few of them. Here is a possibly incomplete list:
poxml
[...]
po-debiandoc
[...]
xml2po.py
Used by the GIMP Documentation Team since 2004, works quite well even if,
as the name suggests, only with XML files and needs specially configured
makefiles.
sphinx
The Sphinx Documentation Project
(https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) also uses
extensively gettext to manage its translations. Unfortunately, it works
only for a few text formats, rest and markdown, although it is perhaps
the only tool that does this managing the whole translation process.
...and more tools are coming at the horizon...
"
... as I said, these are only suggestions. Please do adapt these at your will.
--
Amike,
Marco Ciampa
5:22 a.m.
Hello,
I integrated most of your comments. Thanks for your help, Marco.
Bye, Mt.
Le dimanche 21 août 2022 à 08:35 +0000, Marco Ciampa a écrit :
On Sun, Aug 21, 2022 at 12:26:09AM +0000, Marco Ciampa wrote:
> On Sun, Aug 21, 2022 at 01:04:58AM +0200, Martin Quinson wrote:
> > Hello Marco,
> >
> > thanks for your question. I started updating the doc to reflect your
> > point,
> > which is perfectly valid, and at the end, I reworte the QUICK START part
> > of the
> > po4a(1) documentation. The new version is here:
> > https://github.com/mquinson/po4a/blob/master/po4a#L602
> >
> > Please comment before I update the POT files to ask translators to start
> > the
> > translation.
> >
> > Thanks for reporting,
> > Mt
>
> some people find it easier to interact with the translators through an
> online platform such as S<weblate>, but this is beyond the scope of
> S<po4a>.
>
> I would say:
>
> some people find it easier to interact with the translators through an
> online platform such as S<weblate>; although this is beyond of its scope,
> using S<po4a> for producing .po files can enable the use of such
> collaborative platforms.
Obviously this is only an example of what I meant to say, it could be
incorrect or not clear; I'm not a native English speaker so please do
what you think is better.
> Anyway it seems to me ok, good work, very useful...
I spotted another passage:
"
What about the other translation tools for documentation using gettext?
As far as I know, there are only two of them:
"
I would say:
There are a few of them. Here is a possibly incomplete list:
poxml
[...]
po-debiandoc
[...]
xml2po.py
Used by the GIMP Documentation Team since 2004, works quite well even if,
as the name suggests, only with XML files and needs specially configured
makefiles.
sphinx
The Sphinx Documentation Project
(https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) also uses
extensively gettext to manage its translations. Unfortunately, it works
only for a few text formats, rest and markdown, although it is perhaps
the only tool that does this managing the whole translation process.
...and more tools are coming at the horizon...
"
... as I said, these are only suggestions. Please do adapt these at your will.
--
Amike,
Marco Ciampa
_______________________________________________
Devel mailing list -- devel(a)lists.po4a.org
To unsubscribe send an email to devel-leave(a)lists.po4a.org
853
days inactive
855
days old
4 comments
2 participants
participants (2)
-
Marco Ciampa -
Martin Quinson