Please replace it an actual example, if you can.
3. Changes list from Ver. 2.11.62 to the latest Version.
I am translating LilyPond Documentation Ver. 2.11.62, but the latest version is
2.12.1. So, I want to get the changes list from Ver. 2.11.62 to Ver. 2.12.1. Can
I get it?
Tha
(installed: 1.78)
ERROR: Please install required programs: mpost
...
I am using Ubuntu 8.10.
I found texi2html ver. 1.78 by "sudo apt-get install texi2html", but I
do not know how to install texi2html ver. 1.79 into Ubuntu.
And "MetaPost" for "mpost" is not fou
.py", line 172, in
os.system ('xgettext -c -L Python --no-location -o ' + output_file + ' ' +
node_list_filename)
TypeError: cannot concatenate 'str' and 'file' objects
make: *** [new-lang] エラー 1
====
What shold I
-Japanese-translation-by-sawada.tar.gz
My patches look dirty because I changed something on scripts directries to do
"make web" completely.
I think my patch should show only changes on "python/langdefs.py", and
addition of "Documentation/ja/" and its files.
How do I ge
ch translators are often needed to
> complete translation of one file ? Thanks in advance!
It is alright. I can rewrite my name to "Yoshiki Sawada".
(Both of "Sawada, Yoshiki" and "Yoshiki Sawada" are not my true name.
It must be written with Chinese characters
efor, I just want to know whether my patch works well or not.
Thanks,
Sawada, Yoshiki
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
fo
> l.69: Unicode char \u8:譜 not defined for Texinfo
> l.69: Unicode char \u8:刻 not defined for Texinfo
>
I always get the messages like above while I am doing "make web".
It will fail. But, I do "make web" twice or three
Hi,
I will add a follow up.
I guess the problem is caused by something participating with Japanese font.
Therefore, if your computer does not have the font, it may be not able to fixed.
Thanks,
Sawada, Yoshiki
___
lilypond-devel mailing list
e translation in the source
codes until Texinfo supports Japanese. However, I want to make my translation
available in the web. I believe my translation will help Japanese users to
understand LilyPond more easily and is needed as the material for proofreading
as you think.
Thanks,
Sawada, Yos
take a different set of languages? For
> the tarball distribution, I still want to build the PDFs.
I took the latest source code by "git". Therefore, I can revert it.
But, I do not have the privilege. Revert it, John, please.
Thanks,
Sawada, Yoshiki
John Mandereau gmail.com> wrote:
> As it's possible to distribute Japanese translation at least in one compiled
> format, namely Texi2HTML. However, it is reasonable to enable the
> compilation of the Japanese docs only after you have provided a patch (or a
> patch set) that address these poi
Hello Reinhold,
Reinhold Kainhofer kainhofer.com> wrote:
> These translations are done directly in texi2html. I'm attaching the current
> i18n/ja file from the texi2html distribution. You might want to update the
> translation directly in that file and send it to Patrice Dumas (the main
> dev
n discuss with Japanese,
they can join to this community more easily.
I think it is the great waste of resources to work on LilyPond individually.
Therefore, integrating Japanese documents in the official sources is needed
as the common material for discussions of Japanese.
Hello Werner,
Werner LEMBERG gnu.org> wrote:
> Since there is such a great number of Japanese LilyPond users not
> fluent of English, it would be most important to create a `central'
> Japanese lilypond user forum, with one or more guys who forward more
> difficult questions to the English maili
Hello John and everyone,
I put patches for Japanese documentation at:
http://irjb.s346.xrea.com/wiki/Patches+for+LilyPond+Document.html
The second patch in it is the new patch. Try it, please.
If there are something to fix or do more, tell me.
I will keep translating advanced.
Thanks,
Yoshiki
John Mandereau gmail.com> wrote:
> > It is good that Texi2HTML can handle Japanese even if Texi2DVI cannot handle
> > it. I think we should turn off texi2dvi for Japanese Documentation.
>
> Yes, this is what I did in the makefiles.
That is great! I was looking at "GNUmakefile"s to search for the
John Mandereau gmail.com> wrote:
> I should have replied earlier to other messages... I applied all changes
> that didn't add files related to the Notation Reference or Application
> Usage, and made a small fix to get the documentation to compile
> successfully. Your translation is now in the
Hello Carl,
Carl D. Sorensen byu.edu> wrote:
> I found a place in ja/user/fundamentals.itely where a line ended in @c c,
> which caused make web to fail. I fixed it and pushed a patch to git, so
> it's taken care of now.
Thank you for your pointing my mistake. Thanks to you, I got the opportu
AL_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
ction 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
ng to buy another machine.
Thanks,
Sawada, Yoshiki
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
uot;, "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 the
Hello John,
John Mandereau 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
Hello "nice" Graham,
Graham Percival 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, t
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 th
Request
1. NR 1.1.3 Displaying pitches -> Clef
In "See also", the reference to Internals Reference: "Clef" is translated to
"音部記号" by ja.po file. But it should not be translated because it is a object
name.
Thanks,
Sawada, Yoshiki
o the page twice. And it is enough to reference to
Snippets. Of course, this is my opinion.
NR is very long to translate, especially 1.1 Pitches and 1.2 Rhythms.
Therefore, my translation does not look like progressing so much.
It will take a while to release the next patch.
Thanks,
Sawada, Yoshiki
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hello John,
John Mandereau gmail.com> wrote:
> > Request
> > 1. NR 1.1.3 Displaying pitches -> Clef
> >
> > In "See also", the reference to Internals Reference: "Clef" is translated
> > to
> > "音部記号" by ja.po file. But it should not be translated because it is a object
> > name.
> >
> I'm not top posting.
Hello John,
I am really sorry to reply too late. I am recently busy to get and prepare for
the new job.
I released the new patch for ja doc. It provides files for NR and some fixes.
http://irjb.s346.xrea.com/wiki/Patches+for+LilyPond+Document.html
Add "Documentation/ja/u
> I'm not top posting.
Hello John,
I am really sorry to reply too late. I am recently busy to get and prepare for
the new job.
I released the new patch for ja doc. It provides files for NR and some fixes.
http://irjb.s346.xrea.com/wiki/Patches+for+LilyPond+Document.html
Add "Documentation/ja/u
eck it out.
Sincerely,
Sawada, Yoshiki (Japanese)
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
31 matches
Mail list logo
