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
Op maandag 19-01-2009 om 12:08 uur [tijdzone -0200], schreef Han-Wen
Nienhuys:
> OK thanks. For reasons I do not understand, issuing a
Yes, well: UTSL! See gub/specs/glibc-core.py:
def install_command (self):
return (glibc.Glibc.install_command (self)
.replace (' ins
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:譜
I can't remember the status of this change, but LGTM
--
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
OK thanks. For reasons I do not understand, issuing a
PATH=/home/lilydev/vc/gub3/target/linux-x86/root/usr/cross/bin/:$PATH
make install_root=/tmp/isr install
triggers a compile of iconv, which ends in
c_eh `i686-linux-gcc --print-file-name=crtend.o`
/home/lilydev/vc/gub3/target/linux-x86/bui
Op maandag 12-01-2009 om 10:53 uur [tijdzone +0100], schreef Jan
Nieuwenhuizen:
> Google tells me it's probably easiest to ask you to use the new
> -X/--no-verify command line option to setup.exe.
Does this work, can I upload to Cygwin?
Jan.
--
Jan Nieuwenhuizen | GNU LilyPond - The music typ
Op zaterdag 17-01-2009 om 21:03 uur [tijdzone -0200], schreef Han-Wen
Nienhuys:
> trying a manual
>
> $ make DESTDIR=/tmp/foobar installp
> why does DESTDIR not work on glibc-core?
glibc (traditionally) uses install_root (an noone ever fixed this).
Jan.
--
Jan Nieuwenhuizen | GNU LilyPond -
> 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
