Re: Patch for ja doc and two Questions
Hello guys, Graham Percival graham at percival-music.ca wrotes Yes, I'm a very nice person. ;) The humor like yours may be called Oyaji Gyagu in Japan Hidoi! Boku wa oyaji desu? Boku wa tada san-juu-sai! :( Translation: you're mean! I'm an old man? I'm only 30 years old! Sorry! I do not know you guys can speak Japanese. But a man whose age is over thirty has certain qualification to be an Oyagi. It means a matured man rather than an old man. I am an Oyagi too and love Oyagi Gyagu :-) Thanks, Sawada, Yoshiki ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ja doc and two Questions
Hello John, John Mandereau john.mandereau at gmail.com wrote: It does not work. But I fixed Lilypond-book.py as following: (line 939) if not langdefs.LANGDICT[document_language].enable_ly_identifier_l10n: ^^^ I guess the property name enable_ly_identifier_l10n should be changed to disable_ly_identifier_l10n. I prefer to avoid double negations, but I fixed it anyway. Sorry for the confusion, I wrote this code too late at night Yes, please. Do not mind it. Such errors can easily happen. Skeleton .itely files (i.e. files which don't contain any translation) should be added only if you have already translated some portion in the same manual. As you probably haven't translated anything in the Notation Reference (NR, lilypond.tely) yet, you needn't add any .itely file that belongs to the NR. I understand. When I release patches for NR, I will include skeleton files for it. Thank you for your teaching. Thanks, Yoshiki ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ja doc and two Questions
Hello nice Graham, Graham Percival graham at percival-music.ca writes: nice is not needed, that's a Grahamism, Yes, I'm a very nice person. ;) The humor like yours may be called Oyaji Gyagu in Japan :-) Basically, it came down to this: if somebody doesn't know what they're doing, then they would probably rather have the 45-minute doc build be low-priority (so they can still use mail or browse the web or whatever), rather than high-priority. I can't think of any instance where anybody without serious unix knowledge[1] would *want* a long build to take priority over other things, so I made the copypaste command match that. I am sure. I misunderstood that nice without any value for the priority do not have any effect. I will use it for the next building. Thank you very much. Thanks, Yoshiki ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ja doc and two Questions
On Tue, Feb 17, 2009 at 08:54:44AM +, Sawada, Yoshiki wrote: Hello nice Graham, Graham Percival graham at percival-music.ca writes: nice is not needed, that's a Grahamism, Yes, I'm a very nice person. ;) The humor like yours may be called Oyaji Gyagu in Japan :-) Hidoi! Boku wa oyaji desu? Boku wa tada san-juu-sai! :( Translation: you're mean! I'm an old man? I'm only 30 years old! Ja mata ne, - Graham the grumpyness makes me seem older Percival ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ja doc and two Questions
Hidoi! Boku wa oyaji desu? Boku wa tada san-juu-sai! :( Soo desu ne! Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ja doc and two Questions
On Sat, Feb 14, 2009 at 03:04:55AM +0100, John Mandereau wrote: Sawada wrote: In that sub subsection, there is a command as following: nice make LILYPOND_EXTERNAL_BINARY=/path/to/bin/lilypond web I wonder nice is not needed, though it is harmless. nice is not needed, that's a Grahamism, Yes, I'm a very nice person. ;) but I think it's not a problem if it remains there, I'd expect people who run this command with no knoweledge of nice comand to do man nice :-) Basically, it came down to this: if somebody doesn't know what they're doing, then they would probably rather have the 45-minute doc build be low-priority (so they can still use mail or browse the web or whatever), rather than high-priority. I can't think of any instance where anybody without serious unix knowledge[1] would *want* a long build to take priority over other things, so I made the copypaste command match that. [1] Sure, somebody running a build-box server for multiple open-source projects might want the lilypond build to be higher priority than a complete freebsd build... but that's a pretty special case, and the persons involved would have sufficient unix knowledge to remove or modify the nice command. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ja doc and two Questions
Sawada a écrit : It does not work. But I fixed Lilypond-book.py as following: (line 939) if not langdefs.LANGDICT[document_language].enable_ly_identifier_l10n: ^^^ I guess the property name enable_ly_identifier_l10n should be changed to disable_ly_identifier_l10n. I prefer to avoid double negations, but I fixed it anyway. Sorry for the confusion, I wrote this code too late at night :-) I am sure. I have one question about this. Should I include untranslated texinfo files into patches? For example, I am translating Learning Manual, but do not start to translate rhythms.itely yet. Should I include rhythms.itely into Documentation/ja/user/ for patches? In fact, I can do make web only with lilypond.tely, notation.itely and pitches.itely. Skeleton .itely files (i.e. files which don't contain any translation) should be added only if you have already translated some portion in the same manual. As you probably haven't translated anything in the Notation Reference (NR, lilypond.tely) yet, you needn't add any .itely file that belongs to the NR. Best, John ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ja doc and two Questions
Hello John, John Mandereau john.mandereau at gmail.com wrote: How did you set the execution bit? Have you used a Windows machine or some non-Unix filesystem? Yes, I mount a NTFS from Linux. I have installed both of Windows and Linux into one machine. I edit text on Windows (because my favorite text editor is available only on Windows), then reboot my machine to boot Linux and compile LilyPond documents on it (because I could not build LilyPond on cygwin. In fact, I spent a day to try building LilyPond on cygwin, but I could not do it). This way is really troublesome. I am seriously thinking to buy another machine. Thanks, Sawada, Yoshiki ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ja doc and two Questions
On Sat, Feb 14, 2009 at 1:24 PM, Sawada, Yoshiki sawada.yosh...@gmail.com wrote: How did you set the execution bit? Have you used a Windows machine or some non-Unix filesystem? Yes, I mount a NTFS from Linux. I have installed both of Windows and Linux into one machine. I edit text on Windows (because my favorite text editor is available only on Windows), then reboot my machine to boot Linux and compile Doesnt it run under Wine? -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ja doc and two Questions
Hello John, John Mandereau john.mandereau at gmail.com wrote: 1. Release of the new patch for ja doc OK, I applied your patch, but made further fixes in the source, and made comments at the end of this email. I thank you for your work. 2. About .po file The simplest way I can see is to disable translation of variable names in Japanese documentation, which I just did in lilypond-book and langdefs. Please check if it works. It does not work. But I fixed Lilypond-book.py as following: (line 939) if not langdefs.LANGDICT[document_language].enable_ly_identifier_l10n: ^^^ I guess the property name enable_ly_identifier_l10n should be changed to disable_ly_identifier_l10n. ^^^ 3. About Building documentation without compiling LilyPond of 1.2.4 Building documentation, Application Usage nice is not needed, that's a Grahamism, but I think it's not a problem if it remains there, I'd expect people who run this command with no knoweledge of nice comand to do man nice There are other variations of this command (e.g. using -j make flag)... it's not possible to list all possibilities in the compilation documentation. I just think commands which are not needed should not be included. They may cause confusions. Now, I have another question about LilyPond documents. Thus, I will make a new thread about them. @untranslated in Documentation/ja/user/converters.itely are right, but this file shouldn't contain the English translation, so I removed it. I am sure. I have one question about this. Should I include untranslated texinfo files into patches? For example, I am translating Learning Manual, but do not start to translate rhythms.itely yet. Should I include rhythms.itely into Documentation/ja/user/ for patches? In fact, I can do make web only with lilypond.tely, notation.itely and pitches.itely. Also, the Japanese texidoc in input/lsr/piano-template-simple.ly is missing in input/texidocs, It is a my fault. I will include it into the next patch. and you may want to translate snippet titles as well, writing them in doctitleja header fields. Thank you for your advice. I add doctitleja fields to snippet files. Thanks, Sawada, Yoshiki ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ja doc and two Questions
Hello John and everyone, I am very sorry for putting the wrong patch. Please use 0001-ja-doc.patch.org.gz instead of 0001-ja-doc.patch.gz in: http://irjb.s346.xrea.com/wiki/Patches+for+LilyPond+Document.html And change access modes from 755 to 644 following the instruction written in the page. I am really sorry for wasting your time. Thanks, Sawada, Yoshiki ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ja doc and two Questions
Hello Yoshiki, Sawada wrote: Please use 0001-ja-doc.patch.org.gz instead of 0001-ja-doc.patch.gz in: http://irjb.s346.xrea.com/wiki/Patches+for+LilyPond+Document.html And change access modes from 755 to 644 following the instruction written in the page. How did you set the execution bit? Have you used a Windows machine or some non-Unix filesystem? I am really sorry for wasting your time. That's not a problem, I'm sorry I didn't comment your patch earlier. I'm doing it in another reply. Best, John ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch for ja doc and two Questions
Sawada wrote: 1. Release of the new patch for ja doc I put it in the following page: http://irjb.s346.xrea.com/wiki/Patches+for+LilyPond+Document.html Please do not remove *.itely files for AU and Japanese messages catalog (i.e. Documentation/ja/user/i18n/ja). OK, I applied your patch, but made further fixes in the source, and made comments at the end of this email. 2. About .po file Some words in .po files (i.e. msgids) are used as both words in text and variable names (or context IDs) in LilyPond inputs. I want to translate words in text, but not variable names. The reason is because I can use multi-byte characters in text, but not in codes for LilyPond (and programming languages) . For example, dynamics and ossia are used as words in *.itely files and variable names in *.ly files. I want to translate dynamics as a word to 強弱記号 (dynamics), but not to translate dynamics as a variable name. How do I do this? The simplest way I can see is to disable translation of variable names in Japanese documentation, which I just did in lilypond-book and langdefs. Please check if it works. 3. About Building documentation without compiling LilyPond of 1.2.4 Building documentation, Application Usage In that sub subsection, there is a command as following: nice make LILYPOND_EXTERNAL_BINARY=/path/to/bin/lilypond web I wonder nice is not needed, though it is harmless. nice is not needed, that's a Grahamism, but I think it's not a problem if it remains there, I'd expect people who run this command with no knoweledge of nice comand to do man nice :-) There are other variations of this command (e.g. using -j make flag)... it's not possible to list all possibilities in the compilation documentation. @untranslated in Documentation/ja/user/converters.itely are right, but this file shouldn't contain the English translation, so I removed it. Also, the Japanese texidoc in input/lsr/piano-template-simple.ly is missing in input/texidocs, and you may want to translate snippet titles as well, writing them in doctitleja header fields. Best, John ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Patch for ja doc and two Questions
Hello everyone, I released the new patch for Japanese documents. And I have two questions. 1. Release of the new patch for ja doc I put it in the following page: http://irjb.s346.xrea.com/wiki/Patches+for+LilyPond+Document.html Please do not remove *.itely files for AU and Japanese messages catalog (i.e. Documentation/ja/user/i18n/ja). 2. About .po file Some words in .po files (i.e. msgids) are used as both words in text and variable names (or context IDs) in LilyPond inputs. I want to translate words in text, but not variable names. The reason is because I can use multi-byte characters in text, but not in codes for LilyPond (and programming languages) . For example, dynamics and ossia are used as words in *.itely files and variable names in *.ly files. I want to translate dynamics as a word to 強弱記号 (dynamics), but not to translate dynamics as a variable name. How do I do this? 3. About Building documentation without compiling LilyPond of 1.2.4 Building documentation, Application Usage In that sub subsection, there is a command as following: nice make LILYPOND_EXTERNAL_BINARY=/path/to/bin/lilypond web I wonder nice is not needed, though it is harmless. Thanks, Sawada, Yoshiki ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
