Perfect... Problem solved... Many thanks.
Sorry... didn't want to hurry you... It is not urgent... just a little more confort... I use Freeplane quite everyday... thank you very much for it.
May this help? Tried "not french" accented characters: Ã, ã. The tilde is accessed by holding AltGr, like the acute accent. Both work. May the acute accent be the problem? I attached a picture with the layout of a CH-fr keyboard and the two keys circled.
OK. For me, the issue is solved. Thanks and have a nice day.
Works perfectly... But now, I have another problem... I want to make some preparations for lessons and store them on OneDrive Enterprise. I had to fix some problems with special caracters / spaces in my file and directory names and with absolute / relativ pathes... could manage it. It works when I make a copy to a local drive or an USB key, but when I try to start it on OneDrive, I get an error message (see attachment)... Is it possible? What do I do wrong?
I always tested with the letter "É" thinking it should be the same with the other letters... but it is not! All the other letters I tested now work perfectly, but not "É". In fact, the problem seems to come from the acute accent as the first "letter" in a new (never edited) node, because Ú doesn't work too. Each time I tried, it "eats" the accent and only the "E" or the "U" appeared in the node (same with the other vowels). Same behaviour with on screen keyboard (osk-win10), even if I access the...
scanner.xml: time stamp on file doesn't change - only one "fr-ch" entry after multiple freeplane startups -> ok log file: the entries about "date" and "format" disapeared -> ok date recognition in nodes -> ok number recognition: my win10 is set to "comma" as decimal separator, but only the decimal point is recognised as number (see attachment); not a big problem,.. I can live with that...
Other trial: when I create a new node and hit "enter" before starting to edit, I get the second behaviour I discribed above... Rem.: win10 is configured to "swiss - french" localisation; could that be the source of the problem?