Quote from GP4Flo :

There is a small issue with the codepage selection. When I try to select Central European by typing ^E, LFS writes an Ê. Not a big problem, because it's still possible to select the codepage, by pressing ^ SPACE E.

This is a general thingie which was different before [EDIT] in S1 [/EDIT]. You always have to press ^ twice, or ^+space to get one ^.
This means, to write ^^ you must write ^^^^ or ^+space+^+space

Now comes the problem:
You cant convert ^ to ^+space in the LFS code, because then it's no longer possible to write Ê...

Scawen, when you press ^ only once, no character will appear, because it waits for
a) another character to write Ê etc, or
b) a spacer or another character which doesnt have any "special version" with an ^ on top in order to write ^

GP4Flo : how about if you let go of the shift key, after pressing the ^ character and before the E? Then your German windows should actually send the ^ to LFS, without doing that character conversion? (I really don't know - we can't get accents at all on a UK keyboard without typing in some strange codes).

EDIT : one way or another - the way to do it is to send a ^ to LFS then send a E to LFS. It should be the same as making ^E appear in notepad (but this will be invisible in LFS).

Quote from Scawen :

GP4Flo : But about the ^E, that must be some funny thing with the German keyboard input.

Yep, it's the same if I try to write ^E in other windows apps. But concerning Orion's example, there is a difference when writing several ^^s. In windows I get ^^ when pressing ^ twice, in LFS I only get one ^. Not a big deal, but I wonder why LFS handles this char different then windows.

Edit:

Quote from Scawen :

GP4Flo : how about if you let go of the shift key, after pressing the ^ character and before the E? [...]

That works fine. This is what I meant when I wrote "it's still possible to select the codepage, by pressing ^ SPACE E."

Yes it's the same in LFS as in any other text input area, thus ^+shift doesnt work; you need to write ^+space.
In S1 it was different though.

Quote from GP4Flo :

Yep, it's the same if I try to write ^E in other windows apps. But concerning Orion's example, there is a difference when writing several ^^s. In windows I get ^^ when pressing ^ twice, in LFS I only get one ^. Not a big deal, but I wonder why LFS handels this char different then windows.

Hehe That's because ^^ in LFS, is the only way to write ^

Because ^ is a special character in LFS, with so many meanings. It's a slight conflict because it's also a special character on your Windows keyboard input system, as i've just learned

Quote from Scawen :

Hehe That's because ^^ in LFS, is the only way to write ^

Hmm not really, you can also write ^+space to get ^
As written above, everything is the same in LFS and windows, except writing ^^ resulting in ^ in LFS, and ^^ in Windows.

One last question, is it possible to let the ^ stay when I press space afterwards? For example to write ^hello^ I have to type '^ SPACE hello ^ SPACE' in windows, but this doesn't work in LFS because the ^ disappears right after typing the h.

Quote from GP4Flo :

One last question, is it possible to let the ^ stay when I press space afterwards? For example to write ^hello^ I have to type '^ SPACE hello ^ SPACE' in windows, but this doesn't work in LFS because the ^ disappears right after typing the h.

whoops, I didnt notice that
odd

Quote from ORION :

Hmm not really, you can also write ^+space to get ^
As written above, everything is the same in LFS and windows, except writing ^^ resulting in ^ in LFS, and ^^ in Windows.

No, "^" + " " appears as " "

From my point of view, ^ + *something* always has a special meaning, for example, changing colours, writing illegal filename characters in a filename, selecting a codepage.

If that *something* is unassigned, then ^+*something* is just *something*.

Quote from GP4Flo :

One last question, is it possible to let the ^ stay when I press space afterwards? For example to write ^hello^ I have to type '^ SPACE hello ^ SPACE' in windows, but this doesn't work in LFS because the ^ disappears right after typing the h.

Umm... you are confusing me now.

You will have to work it out yourself, because i don't understand the german keyboard system.

If you write in notepad : "^^hello^^" then paste that into LFS, it will appear as "^hello^"

My point is, LFS has a special meaning for "^^" and that meaning is "^"

Would the easiest way to change LFS's special character from ^ to, say, ¬? You could make a patch(a) that reads the ^ in filenames, skins, etc and converts them to ¬, then a second patch(b) that only works with ¬, and ^ becomes a language tool only.

I have no idea how deeply coded ^ is within LFS.exe though, but I expect I'm wrong (again).

Edit: I also assumed that most languages don't use the ¬ key, but again I might be wrong. I'm pressing shift and the key next to 1. AltGr and the key next to 1 does ¦, and on it's own it does `. Surely there must be a key/character no one uses, but everyone has?

Quote from Scawen :

No, "^" + " " appears as " "

Exactly that seems to be the problem, as it appears as "^".
And as Flo said:
press "^" + " " -> LFs shows "^"
now press "h" for example, and LFS shows "h" - the "^" is gone illepall

[EDIT]I have a German OS and kb, but using English language setting in LFS

Quote from Scawen :

My point is, LFS has a special meaning for "^^" and that meaning is "^"

Now I'm confused as well....all I'm seeing is infinite recursion in that statement

Quote from Scawen :

From my point of view, ^ + *something* always has a special meaning, for example, changing colours, writing illegal filename characters in a filename, selecting a codepage.
[...]
My point is, LFS has a special meaning for "^^" and that meaning is "^".

What I meant is, that there would be an exception for ^ + space so you can easily write a single ^. LFS would replace the ^ + space by an ^^ internally, resulting in a single ^ on screen.

Ahh, really confusing all those ^


Edit:

Quote from tristancliffe :

Would the easiest way to change LFS's special character from ^ to, say, ¬?

I don't think that's really needed. The things I mentioned are only "cosmetical" problems, nothing really serious.