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
Sawada a écrit :
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.
I provided all files which were created by "make ISOLANG=ja new-lang".
The command produ
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
> There are many LilyPond users in Japan and they need information
> about LilyPond in Japanese. I want them to join to LilyPond
> community without hesitating. They are solving their problems
> individually.
Since there is such a great number of Japanese LilyPond users not
fluent of English, i
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 24. Januar 2009 07:48:01 schrieb Sawada, Yoshiki:
> Now, I face one problem.
> Text strings which appear in navigation sections of my HTML files (such as
> "[ Introduction >> ]") look strange.
These translations are done directly in texi2
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
Han-Wen Nienhuys a écrit :
Can you make it so doc and web take a different set of languages? For
the tarball distribution, I still want to build the PDFs.
I'm not sure I understand what you mean with 'doc' and 'web', I assume PDF
and HTML, respectively. Japanese docs compilation will remain
Sawada a écrit :
I'm sure. Perhaps, we should not include Japanese translation in the source
codes until Texinfo supports Japanese. However, I want to make my translation
available in the web.
As it's possible to distribute Japanese translation at least in one compiled
format, namely Texi2HTML
Han-Wen Nienhuys gmail.com> writes:
> > I'll make it possible to enable building Japanese documentation in HTML only
> > this week-end, so that "make web" goes on working. Of course, it is up to
> > you to judge whether the translation is in a good shape for inclusion in the
> > official documen
On Wed, Jan 21, 2009 at 9:51 PM, John Mandereau
wrote:
> Repeating "make web" until it succeeds hides the fact it's currently not
> possible to build the Texinfo manuals in Japanese as Werner pointed out;
> I'll make it possible to enable building Japanese documentation in HTML only
> this week-en
Hello John,
John Mandereau gmail.com> wrote:
> I'm sorry for the delay, and unfortunately I am still quite busy.
Don't mind it. I know you have your own life.
> Repeating "make web" until it succeeds hides the fact it's currently not
> possible to build the Texinfo manuals in Japanese as Wern
Hello Yoshiki,
I'm sorry for the delay, and unfortunately I am still quite busy.
Sawada a écrit :
Hello everyone,
./lilypond-learning.pdftexi:58: Paragraph ended before \documentlanguagetrywith
outunderscore was complete.
\par
I always get the messages like above while I a
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
lilypon
Hello everyone,
> ./lilypond-learning.pdftexi:58: Paragraph ended before
> \documentlanguagetrywith
> outunderscore was complete.
>
>\par
> l.58
>
> l.69: Unicode char \u8:音 not defined for Texinfo
> l.69: Unicode char \u8:楽 not defined for Texinfo
> l.69: Unicode char \u8:譜
> We would need a texi2latex translation so that we could use my CJK
> package (to be more precise, my CJKutf8.sty file).
Alternatively, texinfo.tex needs to be hacked for (hard-coded)
Japanese support.
Werner
___
lilypond-devel mailing list
lil
> someone added a japanese translation of the docs, but after enabling
> it (so it is distributed), I get error (see below). Can someone fix
> this, or disable the translation? This is a blocking issue for
> releasing 2.12.2.
The Japanese translation is for texi2html only, I believe. I can't
s
Hi Han-Wen,
Han-Wen Nienhuys a écrit :
someone added a japanese translation of the docs, but after enabling
it (so it is distributed), I get error (see below). Can someone fix
this, or disable the translation? This is a blocking issue for
releasing 2.12.2.
I suggest not to enable it or revert
Hi,
someone added a japanese translation of the docs, but after enabling
it (so it is distributed), I get error (see below). Can someone fix
this, or disable the translation? This is a blocking issue for
releasing 2.12.2.
(/home/lilydev/vc/gub/target/linux-x86/build/lilypond-localhost--home-li
19 matches
Mail list logo
