ArnoldTheresius writes: > Colin Hall-3 wrote >> Colin Hall writes: >> >>> Colin Hall writes: >>> >>>> Eluze writes: >>>> >>>>> Am 15.02.2013 17:40, schrieb Phil Holmes: >>>>>> "Eluze" < > >> eluzew@ > >> > wrote in message >>>>>> news: > >> 1360940582460-140993.post@.nabble > >> ... >>>>>>> if in the command-line I enter >>>>>>> >>>>>>> /lilypond/ or /lilypond -h/ >>>>>>> >> ... >> New tracker: >> >> http://code.google.com/p/lilypond/issues/detail?id=3184 >> >> Cheers, >> Colin. >> >> -- >> Colin Hall >> >> _______________________________________________ >> bug-lilypond mailing list > >> bug-lilypond@ > >> https://lists.gnu.org/mailman/listinfo/bug-lilypond > > Just a different observation, which may be related to the same or a similar > origin: > > On WindowsNT and WindowsXP I did use the command line of lilypond > (directly). Before that I selected the UTF-8 codepage '65001' and selected > the true type font. Then I got the correct command line output. > Starting with Windows7 the command line output was not displayed correctly > anymore. > As a workaround I wrapped my lilypond start into a simple C program (Windows > UNICODE-mode), which launches the original lilypond command with the output > redirected into pipes, and using WriteConsoleW() to output the conversion of > the UTF-8-Bytestream to UTF-16. > I still did'nt find the time to create a good example (sample code) of my > workaround. That's the reason I did not tell you about this problem. > Possibly this problem here roots from the same origin. > > ArnoldTheresius
Thanks, Arnold. I've added a comment on the tracker: http://code.google.com/p/lilypond/issues/detail?id=3184#c6 Cheers, Colin. -- Colin Hall _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
