Gabor Hojtsy wrote:
>> > For translators, a diff should be as small as possible.
>>
>> Why?
>>
>> If I want to update pg-num-rows.xml in the de-tree, I see have two
>> options:
>>
>> first:
>> remove whitespaces, change the doc-skel and then update the
>> translation. This means redoing everything
Christopher Kings-Lynne wrote:
>> first:
>> remove whitespaces, change the doc-skel and then update the
>> translation. This means redoing everything Christopher has already
>> done in the en-pg-num-rows.xml.
>
>
> I'm actually doing a full rewrite of the PostgreSQL docs, so I'm afraid
> lots of
first:
remove whitespaces, change the doc-skel and then update the translation.
This means redoing everything Christopher has already done in the
en-pg-num-rows.xml.
I'm actually doing a full rewrite of the PostgreSQL docs, so I'm afraid
lots of translation might be required anyway :(
Chris
Hi Nuno, Goba
Thank you ;-)
Conni
I've picked the tag of the first file:
but it should be:
So, its just a typo in the tags..
Nuno
- Original Message -
Hi
> - look up diff of English file (from revcheck)
This script shows all german informix-files in the list of *Files
without Revision-comment* but they do have.
http://
> - look up diff of English file (from revcheck)
This script shows all german informix-files in the list of *Files
without Revision-comment* but they do have.
http://www.php.net/manual/de/revcheck.html#misstags
Spot the typo (the wrong colon):
BTW it is better to use a more up-to-date resource
Hi
> - look up diff of English file (from revcheck)
This script shows all german informix-files in the list of *Files
without Revision-comment* but they do have.
http://www.php.net/manual/de/revcheck.html#misstags
Just wondering
Conni
P.S. Goba: sorry, Hit the wrong button ;-)
Hi
> I rather to take the english file and
> replace the english for my language. In this way (from
> my point of view) is riskless to commit.
Yes, I think also that this is less error-prone.
Regards
Conni
> >>> I know that at least the Hungarian translators do that:
> >>>
> >>> - look up diff of English file (from revcheck)
> >>> - change the Hungarian file according to the diff
> >>>
> >>> If the diff contains irrelevant changes (ws), it is getting harder.
> >>> If ws is done in a separate commi
I know that at least the Hungarian translators do that:
- look up diff of English file (from revcheck)
- change the Hungarian file according to the diff
If the diff contains irrelevant changes (ws), it is getting harder.
If ws is done in a separate commit, it can be steped over (with
incrementa
Friedhelm Betz wrote:
[...]
Probably a lot less people care about WS in the translations, it does
not matter.
If it does not matter, why should these WS fixes be done in the en tree?
Just curiously asking
Talking to myself, sorry. To make it absolutly clear: I am strong +1 for
the new docstyle a
Gabor Hojtsy wrote:
I know that at least the Hungarian translators do that:
- look up diff of English file (from revcheck)
- change the Hungarian file according to the diff
If the diff contains irrelevant changes (ws), it is getting harder.
If ws is done in a separate commit, it can be steped ov
Hi all,
> >> I know that at least the Hungarian translators do
> that:
> >>
> >> - look up diff of English file (from revcheck)
> >> - change the Hungarian file according to the
> diff
> >>
> >> If the diff contains irrelevant changes (ws), it
> is getting harder. If
> >> ws is done in a separa
I know that at least the Hungarian translators do that:
- look up diff of English file (from revcheck)
- change the Hungarian file according to the diff
If the diff contains irrelevant changes (ws), it is getting harder. If
ws is done in a separate commit, it can be steped over (with
incrementa
Gabor Hojtsy wrote:
> For translators, a diff should be as small as possible.
Why?
If I want to update pg-num-rows.xml in the de-tree, I see have two
options:
first:
remove whitespaces, change the doc-skel and then update the
translation. This means redoing everything Christopher has already
d
> For translators, a diff should be as small as possible.
Why?
If I want to update pg-num-rows.xml in the de-tree, I see have two options:
first:
remove whitespaces, change the doc-skel and then update the translation.
This means redoing everything Christopher has already done in the
en-pg-num-r
Hi,
> For translators, a diff should be as small as possible.
Why?
If I want to update pg-num-rows.xml in the de-tree, I see have two
options:
first:
remove whitespaces, change the doc-skel and then update the
translation. This means redoing everything Christopher has already
done in the en-pg-
17 matches
Mail list logo
