Hi again,
Here is an up-to-date report, with still some affected languages:
ca
cs
de
el
fr
gl
id
ja
pt_BR
ru
if you could please review it before the release it would be great!
Thanks in advance for your work
El sáb., 29 feb. 2020 a las 22:40, Jordi Mas ()
escribió:
> Thanks for generating
Thanks for generating this. It's really useful. I tried to fix most of it.
Jordi,
On Tue, Feb 18, 2020 at 12:13 PM Daniel Mustieles García via gnome-i18n <
gnome-i18n@gnome.org> wrote:
> Hi all,
>
> As usual, I've created a report (attatched) with the languages containing
> typos or errors in
Hi Daniel,
thanks for your report. I´ll fix all the errors in gl translations ASAP.
Regards,
Fran
On Tue, 18 Feb 2020 at 12:13, Daniel Mustieles García via gnome-i18n <
gnome-i18n@gnome.org> wrote:
> Hi all,
>
> As usual, I've created a report (attatched) with the languages containing
> typos
Hi all,
As usual, I've created a report (attatched) with the languages containing
typos or errors in tags in documentation files. Here is the list of the
affected languages:
ca
cs
da
de
el
fr
gl
id
ja
pl
pt_BR
ru
Please fix them before the new release, to avoid errors when compiling the
Hi Ask,
Yes, but since I download all the PO files from DL in a folder an then
check them I have no way to guess which module they belong to. Only the PO
file might give us a clue but as you've said it's not always clear.
A possible solution could be extract each set in separate folders (core,
Thanks Daniel.
For future reference, it might be helpful to include also the project
directory. This is because gimp-help-2 has files like "glossary.po"
which are not sufficient to tell where the file comes from.
Best regards
Ask
Am Di., 3. Sept. 2019 um 12:12 Uhr schrieb Daniel Mustieles
Thanks for the report,I just fixed the issues with Romanian.
Regards,Daniel
În data de Ma, 03-09-2019 la 12:12 +0200, Daniel Mustieles García via
gnome-i18n a scris:
> Hi all,
>
> As usual,
> I've created a report (attatched) with the languages containing
> typos
> or errors in tags in
Hi all,
As usual, I've created a report (attatched) with the languages containing
typos or errors in tags in documentation files. Here is the list of the
affected languages:
ca
cs
da
es
fr
ja
pt_BR
ro
ru
Please fix them before the new release, to avoid errors when compiling the
affected
Should we disable the check for undefined entity? Some errors would
go undetected, but people might pay more attention since they will all
be real errors.
If such errors don't break the compile process, it's ok for me to remove
that check until we have completely clear how to detect them
Here is the las report, and these are the affected languages:
de
el
fr
ja
pt_BR
ro
sl
Note that this report also contains errors in non-core modules, which are
not under the release cycle, so no need to fix them ASAP (but highly
recommended).
Cheers!
2014-09-18 23:24 GMT+02:00 Christian
And now with the report attatched
Sorry...
2014-09-20 19:21 GMT+02:00 Daniel Mustieles García
daniel.mustie...@gmail.com:
Here is the las report, and these are the affected languages:
de
el
fr
ja
pt_BR
ro
sl
Note that this report also contains errors in non-core modules, which are
Hello
The mismatched tag and not well-formed are generally real errors.
I still don't have a way of telling which constructs are legal in the
case of undefined entity which may therefore (and frequently does)
give false positives e.g. in Japanese and Brazilian-Portuguese. If we
had a way to know
Am Mittwoch, den 10.09.2014, 12:51 +0200 schrieb Daniel Mustieles
García:
Hi all,
As usual, I've created a report (attatched) with the languages
containing typos or errors in tags in documentation files. Here is the
list of the affected languages:
cs
de
de should be fixed. Thank you for
Hi all,
As usual, I've created a report (attatched) with the languages containing
typos or errors in tags in documentation files. Here is the list of the
affected languages:
cs
de
el
es
fi
fr
hu
id
it
ja
pt_BR
ro
sl
sv
Please fix them before the new release, to avoid errors when compiling the
14 matches
Mail list logo
