3:10 p.m.
Waa, that's impressive! What are your plan for the future? Did you reach a
releasable state, or do you what to improve furter your code? We're on your
order on this one ;) Could you please update the changelog?
As usual, I'm really impressed here.
Thanks for your time, Mt.
On Sat, Jan 08, 2005 at 10:44:30AM +0000, Nicolas FRAN??OIS wrote:
Update of /cvsroot/po4a/po4a/lib/Locale/Po4a
In directory haydn:/tmp/cvs-serv9174/lib/Locale/Po4a
Modified Files:
TeX.pm
Log Message:
Some cleanups and comments.
New functionnalities:
* Better handling of the spaces surrounding commands. They are now kept as close to the
original as possible.
* Start using "% po4a: " line for parser personalisation.
* It is now possible to build a derivated parser.
* Handle file inclusion (based on Transtractor's read).
1:59 p.m.
Hello,
On Sat, Jan 08, 2005 at 10:10:51PM +0100, Martin Quinson wrote:
Waa, that's impressive! What are your plan for the future? Did
you reach a
releasable state, or do you what to improve furter your code? We're on your
order on this one ;) Could you please update the changelog?
Thanks for all your compliments.
I don't think the TeX module is releasable now. I would first like to test
it (translate one chapter of the book, do a gettextization with an old
translation of a Python Documentation section). I would also like to
release a LaTeX module, which should include some default customization
(include common commands in the right categories, add a tabular
environment, ...)
Here is a TODO list:
* tabular environment (has to be done in LaTeX)
* more "% po4a :" capabilities (e.g. a method for
* parsing '% po4a :' lines in the tex file (in parse)
* a category for the commands that can be translated separately when
they are at the beginning or end of a buffer
Known issues:
* all FIXME in the source
* empty lines in a command argument
* handling of '\ ' (it works, but is not done correctly)
BTW, thank to Juan Rafael for his answer on this subject
* an issue with the TOC of Nicolas' book (this is probably a minor issue)
I've got a LaTeX module locally. I need to clean it (remove all commands
peculiar to Nicolas' book, and add "% po4a: " lines instead).
Then, the tabular environment, and the last TODO point may be needed (they
both introduce important change in the PO file). After this, the POs
should be stable enough and the TeX module would probably be releasable
(if it was usable during tests).
--
Nekral
12:56 p.m.
New subject: [Po4a-devel]Status of the TeX module
Hello all,
I've got much less time currently.
Here is an update of the TeX module progress.
On Sun, Jan 09, 2005 at 08:59:26PM +0100, Nicolas François wrote:
I don't think the TeX module is releasable now. I would first
like to test
it (translate one chapter of the book, do a gettextization with an old
translation of a Python Documentation section). I would also like to
release a LaTeX module, which should include some default customization
(include common commands in the right categories, add a tabular
environment, ...)
I've made a PythonDoc module and tested a gettextization of the Python
Reference Manual without any big issue (only usual issues, gettextization
is not an easy thing, but the french translation was is a quite good
shape).
The updatepo showed 556 translated messages, 166 fuzzy and 161
untranslated (gettextization on Python 2.0, updatepo to Python 2.4). This
is a quite good news, I will propose po4a to the team which is trying to
bring the Python french translation project back to life.
Note: I noticed only one difference on the PDF after a po4a-normalization (a
diff "with my eyes"):
a verbatim block contained a '%' character that I wrongly considered as
the beginning of a comment.
Here is a TODO list:
* tabular environment (has to be done in LaTeX)
* more "% po4a :" capabilities (e.g. a method for
parsing '% po4a :' lines in the tex file (in parse)
more "% po4a
:" capabilities have been added.
Still some lack: specifying the arguments that must be translated
* a category for the commands that can be translated separately
when
they are at the beginning or end of a buffer
Done. Tested with PythonDoc, still
not with Nicolas' book.
* more documentation
Known issues:
* all FIXME in the source
Even more FIXME and TODO in the source
* empty lines in a command argument
* handling of '\ ' (it works, but is not done correctly)
* an issue with the TOC of Nicolas' book (this is probably a minor issue)
* an issue with a % in a verbatim block (which should not be
interpreted as the beginning of a comment). It won't be easy to fix
because I don't have any idea of the environment when I'm dealing
with the '%'.
I've got a LaTeX module locally. I need to clean it (remove all commands
peculiar to Nicolas' book, and add "% po4a: " lines instead).
I will find time to commit it this week-end (with the PythonDoc module)
Then, the tabular environment, and the last TODO point may be needed
(they
both introduce important change in the PO file). After this, the POs
should be stable enough and the TeX module would probably be releasable
(if it was usable during tests).
I will give the tabular environment a try this week-end.
--
Nekral
7019
days inactive
7046
days old
2 comments
2 participants
participants (2)
-
Martin Quinson -
Nicolas François