Kolbjørn Stuestøl (Sonntag, 10. Mai 2009, 13:54): > Ulf-D. Ehlert skreiv: > > Does > > $ tools/xml2po src/introduction/whats-new.xml > > produce image references? > > In a way, but the image paths are not valid > Output: > Warning: image file > 'src/introduction/images/using/empty-image-window.png' not found. That's ok. We suppress these warnings in the Makefile(s) (see definition of "xml2pot" in Makefile.GNU). > The actual images are in the 'images/C/using' path so the > 'src/introduction/' part of the path should be omitted? Yes. The standard xml2po program expects the same directory structure for XML and HTML (no subdirectories). If we decide to use our own patched version of 'xml2po' instead of the standard xml2po program, we can try to change the code so that the image files are found and the md5sums are generated (or we can also remove this feature). > Images refs in the pot file unchanged: > #. When image changes, this message will be marked fuzzy or > untranslated for you. > #. It doesn't matter what you translate it to: it's not used at all. > #: src/introduction/whats-new.xml:45(None) > msgid "" > "@@image: 'images/using/empty-image-window.png'; md5=THIS FILE > DOESN'T EXIST" > msgstr "" So there *are* image references in the POT files? > > If the first command does not produce image references, Apparently it did, so there was no need to try the following commands. > Output: > submodes_path = "/usr/share/xml2po" > > > Check if the module exists, e.g. > > $ ls /usr/share/xml2po/docbook.py > > Output: > /usr/share/xml2po/docbook.py Everything is fine, the required module exists... > No output, i.e. not found ;-) > I also tried 'locate -c docbook.py' and 'locate -c xml2po'. Both > returned '0'. ... so you didn't need to look for that file, you had already found it! (BTW, it seems that you locate database is not initialized (man updatedb); according to the man page, with "-c" option you will get only the number of matches, not the list of files.) > Command: > ln -s /usr/share/xml2po /usr/share/xml/ > Output: > ln: creating symbolic link `/usr/share/xml/xml2po': File exists File exists, of course! > export PYTHONPATH=/usr/share/xml2po You don't need this, the module is just where xml2po expects it. > Is there any way to check out that a command is fulfilled with > success? Cygwin is *supposed* to emulate Linux and, as in Linux, the > commands are sometimes a bit difficult to recognize. So I run lots of > "info ..." commands searching for help on the commands, but I have to > know what to search for ;-) From the Advanced Bash-Scripting Guide: "Every command returns an exit status (sometimes referred to as a return status or exit code). A successful command returns a 0, while an unsuccessful one returns a non-zero value that usually can be interpreted as an error code. Well-behaved UNIX commands, programs, and utilities return a 0 exit code upon successful completion..." You can always get the exit code of the last executed command with $ echo $? Try $ true; echo $?; false; echo $? > Tried: > touch -c src/introduction/whats-new.xml > make -f Makefile.GNU -d pot/introduction.pot >test-pot.txt > and got 27 MB of text, but not how the pot file is build. The "-d" option produces many debugging messages. > Are there > any way to follow the making of the pot file(s) step by step/line by > line? Try $ make -f Makefile.GNU -n pot/introduction.pot or $ make -f Makefile.GNU pot/introduction.pot VERBOSE=2 or read the Makefile.GNU (search for "xml2pot"). Bye, Ulf
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Gimp-docs mailing list Gimp-docs@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
