TeraByte Unlimited

Thanks very much for sharing that information, especially to the level of detail that you are showing. It will be a big help to others who want to boot IFL from the ISO file.

It looks like it's using the ASCII version instead of the ANSI version on
the build. Both for the GUI and CUI version. Should probably be using ANSI
for GUI and ASCII for CUI, but will check.


"Kempy" wrote in message news:[email protected]...

Hi,

I did a little research and I think i found something.

I write that in hex (dec) notation because I don't know if the characters
will get through the browser.

Informations taken from wiki.

a)
The german mutated vowel from DOS cp437/cp850 at position 0x9A (154) is
displayed in the german imagel (IFL) as the character at position 0x9A (154)
in windows cp1252. Position 0x9A (154) is undefined in western ISO-8859-15,
the correct german mutated vowel is at position 0xDC (220) in western
ISO-8859-15 and windows cp1252.

b)
The german mutated vowel from DOS cp437/cp850 at position 0x84 (132) is
displayed in the german imagel (IFL) as the character at position 0x84 (132)
in windows cp1252. Position 0x84 (132) is undefined in western ISO-8859-15,
the correct german mutated vowel is at position 0xE4 (228) in western
ISO-8859-15 and windows cp1252.

c)
The german mutated vowel from DOS cp437/cp850 at position 0x81 (129) is
displayed in the german imagel (IFL) as the character at position 0x81 (129)
in windows cp1252, what is wrong, as position 0x81 (129) is undefined in
windows cp1252. Position 0x81 (129) is undefined in western ISO-8859-15, the
correct german mutated vowel is at position 0xFC (252) in western
ISO-8859-15 and windows cp1252.

d)
The german mutated vowel from DOS cp437/cp850 at position 0x94 (148) is
displayed in the german imagel (IFL) as the character at position 0x94 (148)
in windows cp1252. Position 0x94 (148) is undefined in western ISO-8859-15,
the correct german mutated vowel is at position 0xF6 (246) in western
ISO-8859-15 and windows cp1252.

To make it complete

0x8E (142) (DOS cp437/cp850) = 0xC4 (196) (western ISO-8859-15 and windows
cp1252)
0x99 (153) (DOS cp437/cp850) = 0xD6 (214) (western ISO-8859-15 and windows
cp1252)
0xE1 (225) (DOS cp437/cp850) = 0xDF (223) (western ISO-8859-15 and windows
cp1252)

I think that's the way to go/look for.

regards.

TeraByte Support wrote:
> It looks like it's using the ASCII version instead of the ANSI version on
> the build. Both for the GUI and CUI version. Should probably be using
> ANSI
> for GUI and ASCII for CUI, but will check.
>

I don't think that ASCII is used, which is 7-Bit, means 0-127 character positions only.

I don't know how IFD-CUI_de looks, I don't use it, but IFD-GUI_de is characterwise ok, only that Kpoieren/Kopieren typing mistake is here too.
The only that troubles are IFL-GUI_de and IFL-CUI_de.

regards

it's been straighten out for next version.

"Kempy" wrote in message news:[email protected]...

TeraByte Support wrote:
> It looks like it's using the ASCII version instead of the ANSI version on
> the build. Both for the GUI and CUI version. Should probably be using
> ANSI
> for GUI and ASCII for CUI, but will check.
>

I don't think that ASCII is used, which is 7-Bit, means 0-127 character
positions only.

I don't know how IFD-CUI_de looks, I don't use it, but IFD-GUI_de is
characterwise ok, only that Kpoieren/Kopieren typing mistake is here too.
The only that troubles are IFL-GUI_de and IFL-CUI_de.

regards