4coder » Forums » Non english keyboards
mrmixer
Simon Anciaux
206 posts
#6810 Non english keyboards
1 year, 1 month ago

Hi,
I just tried 4coder and it doesn't recognise several keys on my keyboard. I'm using a AZERTY keyboard, it's a French layout keyboard, but it is set in windows (7 64bit) as a Belgian layout (there are small differences):
- Belgian layout
- French layout

The letter keys function as expected (meaning azerty/qwerty as no problem) but diacritic ('é', 'à', 'ç'... ) and characters that requires "Alt Gr" don't work properly for some keys.

E.g. to write a '[' I use "Alt Gr" + "^" but nothing happens in 4coder. But "Alt Gr" + "$" to write ']' works.
Diacritic keys don't print anything.

I tried setting the layout in windows as a French layout and it switches the layout correctly (e.g. the '-' become the '=') but the problem with diacritic and "Alt Gr" characters is still there. I also try the "Ctrl + Alt" option with no changes.

I can work without diacritic, but not being able to write '[' or '{' is a lot harder.

Is there anything I can do to make it work or do I have to wait for a future version ?


Mr4thDimention
Allen Webster
240 posts
2 projects

Heyo

#6818 Non english keyboards
1 year, 1 month ago

Hi thanks for letting me know about the issue. AltGr was working at one point, but it may be broken in the current version. I will take a look at it and try to make sure it's working in the French layout for the next release. Until then there's probably nothing you can do to make it work.
mrmixer
Simon Anciaux
206 posts
#6835 Non english keyboards
1 year, 1 month ago

Just to be clear, the layout I'm using is French Belgium (or Belgian, I'm not sure what it's called in English), not French France.

Thanks
Mr4thDimention
Allen Webster
240 posts
2 projects

Heyo

#6856 Non english keyboards
1 year, 1 month ago

Quick update,

Looks like there was a bug handling dead keys because the other layouts I dealt with either did not have dead keys, or the dead keys were not on the same key as important things like '['. Should be better for now.
mrmixer
Simon Anciaux
206 posts
#6875 Non english keyboards
1 year, 1 month ago

Thanks.

I don't know if you plan to make diacritics ( 'à', 'ç', 'é' ... ) work in the next update, but if not, could you print de default font character (often a square) when a character is not recognised so I can work with a file that contains them even if I can't write them.
Jim0_o
Jim R. Didriksen
47 posts
#6877 Non english keyboards
1 year, 1 month ago

(If t/*)That would be UTF-8 multi-character support I can seconds it, I wants my ÆØÅ (and Ü Ä if you're not busy).

I only need them for commenting in my own language if that matters, I don't use them in code since opening a file in the wrong editor will 'f' them up without asking.

- Jim RMHD
doublenibble
8 posts

None

#10044 Non english keyboards
6 months, 1 week ago

I would like to be able to type scandic letters (ö, ä and å). Also, I would like to be able to bind what is typically called tilde key in english keyboards (left of '1' and above tab). It makes '§' character. Is it possible to bind this key now?

None
Mr4thDimention
Allen Webster
240 posts
2 projects

Heyo

#10051 Non english keyboards
6 months ago

I still need to get to utf-8 support. All those missing non-english characters will be supported when I do that.
doublenibble
8 posts

None

#10054 Non english keyboards
6 months ago

Mr4thDimention:
I still need to get to utf-8 support. All those missing non-english characters will be supported when I do that.


Thank you for all your hard work on 4coder. I use Visual Studio for daily work, but I believe I can switch over if I can get my binds to work. No rush, just good to know that utf-8 support is coming eventually.

None
doublenibble
8 posts

None

#10233 Non english keyboards
5 months, 3 weeks ago

Had yet another frustrating day with Visual Studio freezes, which brought me back to try 4coder. Checking the TODO.txt file in 4coder today I saw that unicode buffer mode and support for full length unicode file names are listed there. This seems like a lot of work and it will probably be a while until utf-8 support is ready.

Meanwhile, would it be possible to extend characters that can be used to also cover the extended ASCII characters or is there any workaround using 4coder super to bind for example extended ASCII char 245? This alone would solve all my input problems. I don't need to be able to actually type any of the characters into a buffer.

None
Mr4thDimention
Allen Webster
240 posts
2 projects

Heyo

#10243 Non english keyboards
5 months, 3 weeks ago

Hmm interesting idea, I could potentially extend the input system without having to mess with buffer representation. Not sure why I didn't think of it myself actually.
godratio
Ray Garner
27 posts
#10254 Non english keyboards
5 months, 3 weeks ago

I am in Japan and yes I second the UTF-8 support is a big time feature.

I want to share how cool 4Coder is with my Japanese co workers but when I open a source code file with Japanese comments
Its just big red text going straight across the screen so they wont accept it and they will just laugh at me.

To be honest this should be your no.1 priority I think.
Kapsy
6 posts
#10256 Non english keyboards
5 months, 3 weeks ago Edited by on Jan. 7, 2017, 9:43 a.m.

Hey Ray I'm in Japan too! Gimme a shout sometime at shinobinz(at)gmail(dot)com. Apologies for the spam but it seems there's no way to PM on the Handmade Network.

To keep this post on topic, yes I would agree UTF-8 support is needed - alongside OSX support. In my efforts to learn the language I'll often include Japanese comments too.
Mr4thDimention
Allen Webster
240 posts
2 projects

Heyo

#10265 Non english keyboards
5 months, 3 weeks ago

godratio:
I am in Japan and yes I second the UTF-8 support is a big time feature.

I want to share how cool 4Coder is with my Japanese co workers but when I open a source code file with Japanese comments
Its just big red text going straight across the screen so they wont accept it and they will just laugh at me.

To be honest this should be your no.1 priority I think.


It is actually my no.2 priority, right after wrangling, organizing, clearing out, and setting up some proper testing for all the existing features.
doublenibble
8 posts

None

#11561 Non english keyboards
2 months, 3 weeks ago Edited by on April 1, 2017, 9:47 p.m.

Unicode characters in buffers seem to be working quite well now. Unfortunately I still can't figure out a way to bind any non-ASCII input characters as keys. This works as expected:

1
    bind(context, ',', MDFR_CTRL, change_active_panel);

but this doesn't:

1
    bind(context, '§', MDFR_CTRL, change_active_panel);

Is there any way for me to bind this key? I tried changing my keys to some combinations that I can bind for 4coder, but I just can't get used to the new binds.

None