Hi,
On Sat, 27 Nov 2004, Nicolas François wrote:
On Tue, Nov 23, 2004 at 12:44:47AM +0100, Nicolas François wrote:
> I will also do a review of the English version (I'm preparing a patch,
> which should not change translation, for some typos and will send it to
> the list for a review so that other translators could just unfuzzyfy their
> strings).
Here it is.
I'm having a look at it. Here are the issues I find:
-----
po4a-updatepo -f E<lt>fmtE<gt> (-m E<lt>master.docE<gt>)+ (-p
E<lt>XX.poE<gt>)+
-(XX.po are the output, all others are input)
+(XX.po is the output, all others are inputs)
po4a-updatepo accepts more than one po file, so the plural form can be
correct here.
-----
It is possible to give more than one po file (if you want to update several
-languages at once), and several documentation file (if you want to store
-the translations of several documents in the same po files).
+languages at once), and several documentation files (if you want to store
+the translations of several documents in the same po file).
I think that "in the same po _files_" was fine because it speaks of
updating one or more po files.
-----
-po4a - framework to translate documentation and other material
+po4a - framework to translate documentations and other materials
"documentations" sounds strange to me. I think this should be
"documents"
or "documentation".
-----
-Translating documentation is not very difficult in itself. Texts are far
+Translating documentations is not very difficult in itself. Texts are far
longer than the messages of the program and thus take longer to be achieved,
but no technical skill is really needed to do so. The difficult part comes
when you have to maintain your work. Detecting which parts did change and
need to be updated is very difficult, error-prone and highly unpleasant. I
-guess that this explains why so much translated documentation out there is
+guess that this explains why so much translated documentations out there are
outdated.
The same here... I prefer "documentation".
-----
Unfortunately, po4a still miss support for several major documentation
Should this "miss" be replaced by "misses"?
-----
+(which comes with the Perl documentation), for example. To make short, each
+language have its specific syntactic rules, and there is no way to build
Shouldn't it say "each language _has_"?
-----
The first change is about font change specifications. In nroff, there is
-several way to specify if a given word should be written in small, bold or
+several ways to specify if a given word should be written in small, bold or
I think that it should be "In nroff, there _are_ several ways..."
-----
I think that the rest of the patch is okay. Nice job ;)
Regards,
Jordi Vilalta