[syslinux] Allowed code pages and encodings to write f0.txt through f1.txt?

H. Peter Anvin hpa at zytor.com
Wed Mar 27 09:29:08 PDT 2013

On 03/27/2013 03:44 AM, Ady wrote:
> In my experience, in Syslinux I haven't been able to _display_ the 
> three characters that distinguish cp865 from cp437. I have tried 
> different combinations of opening and/or viewing and or saving the 
> text file with either cp865 or cp437 (or even with 1252), without 
> success regarding the 3 diff. characters once in Syslinux. This is 
> only my experience, and maybe others were successful with cp865.

Yes, the only reason for 865 is that some Nordic PCs at least used to
default to it in the BIOS.  Since the characters in 437 are so unlikely
in filenames it was a quick hack.

> Implementing support for UTF in:
> _ DISPLAY files
> _ DISPLAY directive
> _ F1-F12 directive(s)
> _ cfg files
> _ SAY directive
> _ MENU HELP directive
> _ TEXT HELP - ENDTEXT directive(s)
> _ cat.c32 and other c32 modules
> _ using (absolute or relative) paths
> should help for internationalization and would make the difference 
> irrelevant.
> Maybe parts of those implementations are simpler than others.

Most of those bits don't need any change at all, just the terminal code.


More information about the Syslinux mailing list