Re: [Inkscape-devel] Re : Re : Re : Re : I suck at Perl (orcheck-markup)
Hi,
if i try to update the de.po with "msgmerge -Uv de.po inkscape.pot" on Windows, i get a different error message: ----- inkscape.pot:18745: Schlüsselwort »msgctxt« ist unbekannt inkscape.pot:18745:8: parse error -----
Keyword »msgctxt« is unknown
So i get at least 104 Error messages.
Can someone fix this problem?
Sincerely,
UweSch
De : Peter Moulder <Peter.Moulder@...2349...> À : Nicolas Dufour <nicoduf@...48...>
Another check-markup related issue: [it doesn't support msgctxt lines]
It's past my bedtime, so I haven't tested interesting cases yet, but try the attached patch.
Thanks for the patch. Unfortunately, it still doesn't work. But the error message is different now:
... fr.po: parse error; may be a bug in po/check-markup: #: ../src/ui/tool/transform-handle-set.cpp:479 ...
And the fuzzy lines are now correctly ignored.
Regards, -- Nicolas
------------------------------------------------------------------------------
_______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi,
De : Uwe Schöler - OSS-Marketplace.com <mail@...2227...> if i try to update the de.po with "msgmerge -Uv de.po inkscape.pot" on Windows, i get a different error message:
inkscape.pot:18745: Schlüsselwort »msgctxt« ist unbekannt inkscape.pot:18745:8: parse error
The current Windows devlibs gettext version is 0.14.5, and the context macro I've activated recently was added in version 0.15 (and gtk 2.16). The most recent Windows version I've found is 0.17 (from http://ftp.logilab.org/pub/gettext/). I'm going to test it and see if we can include it in the devlibs.
Regards, -- Nicolas
De : Nicolas Dufour <nicoduf@...48...> The most recent Windows version I've found is 0.17 (from http://ftp.logilab.org/pub/gettext/). I'm going to test it and see if we can include it in the devlibs.
Both merging a contextualized po file with this package and using it in Inkscape work successfully!
Krzysztof, would you be willing to investigate potential conflicts between gettext 0.17 files and the current devlibs (intl.dll and maybe others)?
Regards, -- Nicolas
2010/5/25 Nicolas Dufour <nicoduf@...48...>:
De : Nicolas Dufour <nicoduf@...48...> The most recent Windows version I've found is 0.17 (from http://ftp.logilab.org/pub/gettext/). I'm going to test it and see if we can include it in the devlibs.
Both merging a contextualized po file with this package and using it in Inkscape work successfully!
Krzysztof, would you be willing to investigate potential conflicts between gettext 0.17 files and the current devlibs (intl.dll and maybe others)?
The 0.17 version found on that website uses different DLL names. I'd stick to the version of gettext contained in the devlibs (it comes from the GTK development bundle, IIRC), because changing it will require rebuilding the whole GTK stack.
As I understand it: 1. the current runtime version is OK 2. the current tools version, msgmerge in particular, cannot handle msgctxt messages, but this is only an issue when updating the translation templates and can be solved by downloading newer gettext binaries
Regards, Krzysztof
Hi,
As I understand it:
- the current runtime version is OK
Yes. Nothing wrong with the current installed dlls.
- the current tools version, msgmerge in particular, cannot handle
msgctxt messages, but this is only an issue when updating the translation templates and can be solved by downloading newer gettext binaries
That's what I first thought, but no, not exactly. btool will stop if the following files (from gettext-0.17-win32\bin) are not in the devlibs\bin folder:
msgfmt.exe libintl-8.dll libgesttextsrc-0-17.dll libgettextlib-0-17.dll libiconv-2.dll
After copying these file, I've been able to run btool successfully. Thus I think it's the minimum requirement if we want to use the context C_() macro. But we could also copy all the gettext-0.17-win32\bin content with no risk, so that translators have all the needed tools without having to download gettext.
My only doubt is about the gettext lib and include folders. Do we really need them?
Regards, -- Nicolas
2010/5/26 Nicolas Dufour <nicoduf@...48...>:
That's what I first thought, but no, not exactly. btool will stop if the following files (from gettext-0.17-win32\bin) are not in the devlibs\bin folder:
msgfmt.exe libintl-8.dll libgesttextsrc-0-17.dll libgettextlib-0-17.dll libiconv-2.dll
After copying these file, I've been able to run btool successfully. Thus I think it's the minimum requirement if we want to use the context C_() macro. But we could also copy all the gettext-0.17-win32\bin content with no risk, so that translators have all the needed tools without having to download gettext.
I encountered that too. Right now I'm trying to build a version of gettext 0.18 that links against intl.dll and iconv.dll from our devlibs, so that the libraries are not duplicated. I also upgraded Python to 2.6.5 and it appears to work correctly.
My only doubt is about the gettext lib and include folders. Do we really need them?
No, they are not needed, as we use the headers from gettext-runtime that come in the official GTK+ Windows bundle.
Regards, Krzysztof
From: Krzysztof Kosiński [mailto:tweenk.pl@...400...] 2010/5/26 Nicolas Dufour <nicoduf@...48...>:
That's what I first thought, but no, not exactly. btool will stop if the
following files (from gettext-0.17-win32\bin) are not in the devlibs\bin folder:
msgfmt.exe libintl-8.dll libgesttextsrc-0-17.dll libgettextlib-0-17.dll libiconv-2.dll
After copying these file, I've been able to run btool successfully. Thus
I think it's the minimum requirement if we want to use the context C_() macro. But we could also copy all the gettext-0.17-win32\bin content with no risk, so that translators have all the needed tools without having to download gettext.
I encountered that too. Right now I'm trying to build a version of gettext 0.18 that links against intl.dll and iconv.dll from our devlibs, so that the libraries are not duplicated. I also upgraded Python to 2.6.5 and it appears to work correctly.
My only doubt is about the gettext lib and include folders. Do we really
need them?
No, they are not needed, as we use the headers from gettext-runtime that come in the official GTK+ Windows bundle.
I have tried to copy the files as mentioned, but I still get an error (r9450):
Make error line 452: <msgfmt> problem: po/nl.po:18250: keyword "msgctxt" unknown po/nl.po:18250:8: parse error po/nl.po:18255: keyword "msgctxt" unknown po/nl.po:18255:8: parse error po/nl.po:18260: keyword "msgctxt" unknown ...
Regards Preben
W dniu 26 maja 2010 17:25 użytkownik Preben Soeberg <prsodk@...400...> napisał:
I have tried to copy the files as mentioned, but I still get an error (r9450):
Make error line 452: <msgfmt> problem: po/nl.po:18250: keyword "msgctxt" unknown po/nl.po:18250:8: parse error po/nl.po:18255: keyword "msgctxt" unknown po/nl.po:18255:8: parse error po/nl.po:18260: keyword "msgctxt" unknown
Try devlibs revision 15, they contain updated gettext tools Regards, Krzysztof
From: Krzysztof Kosiński [mailto:tweenk.pl@...400...]
W dniu 26 maja 2010 17:25 użytkownik Preben Soeberg <prsodk@...400...> napisał:
I have tried to copy the files as mentioned, but I still get an error (r9450):
Make error line 452: <msgfmt> problem: po/nl.po:18250: keyword "msgctxt" unknown po/nl.po:18250:8: parse error po/nl.po:18255: keyword "msgctxt" unknown po/nl.po:18255:8: parse error po/nl.po:18260: keyword "msgctxt" unknown
Try devlibs revision 15, they contain updated gettext tools
Now at devlibs rev. 17, still having the same problem:
Make error line 452: <msgfmt> problem: po/fr.po:18690: keyword "msgctxt" unknown po/fr.po:18690:8: parse error po/fr.po:18695: keyword "msgctxt" unknown po/fr.po:18695:8: parse error ...
I'm not near a computer for the next week or so.
Regards Preben
W dniu 30 maja 2010 14:33 użytkownik Preben Soeberg <prsodk@...400...> napisał:
Now at devlibs rev. 17, still having the same problem:
Make error line 452: <msgfmt> problem: po/fr.po:18690: keyword "msgctxt" unknown po/fr.po:18690:8: parse error po/fr.po:18695: keyword "msgctxt" unknown po/fr.po:18695:8: parse error ...
I'm not near a computer for the next week or so.
I think you have an obsolete version of gettext tools installed in your MinGW directory, or somewhere in your PATH before the devlibs bin/ directory. Make sure that the msgfmt.exe from devlibs is first in your PATH.
Regards, Krzysztof
participants (4)
-
Krzysztof Kosiński -
Nicolas Dufour -
Preben Soeberg -
Uwe Schöler - OSS-Marketplace.com