Tiny Core Extensions > TCE Q&A Forum

German keyboard - Euro sign

<< < (2/3) > >>

Misalf:
Why can Apps display "€" then?

curaga:
Huh, I guess I was wrong then, the font does include the euro symbol.

The single-line text input is a different widget from the wide rich text one editor uses, which may have an effect.

nitram:

--- Quote from: curaga on September 30, 2015, 10:03:20 AM ---The single-line text input is a different widget from the wide rich text one editor uses...

--- End quote ---
Just a thought.
Test this theory by opening default TC editor, trying Euro symbol in a new document.
Then in editor select Search > Find, a single-line text input line, and try the Euro symbol there.

Update: Just tested myself, copy/paste Euro symbol from post above into editor document gives a ? (question mark), pasting it into editor's search/find input line displays proper Euro symbol. Well it looks like this € - is that a proper Euro? Anyway, strange.

nitram:
Been working in FLTK 1.1 a lot lately and have the manual handy, not sure if this is helpful:

--- Quote ---Character Encoding
FLTK 1 supports western character sets using the eight bit encoding of the user-selected global code page. For
MS Windows and X11, the code page is assumed to be Windows-1252/Latin1, a superset to ISO 8859-1. On
Mac OS X, we assume MacRoman.
FLTK provides the functions fl_latin1_to_local, fl_local_to_latin1,
fl_mac_roman_to_local, and fl_local_to_mac_roman to convert strings between both
encodings. These functions are only required if your source code contains "C"-strings with international
characters and if this source will be compiled on multiple platforms.
Assuming that the following source code was written on MS Windows, this example will output the correct
label on OS X and X11 as well. Without the conversion call, the label on OS X would read
Fahrvergn¸gen with a deformed umlaut u.
  btn = new Fl_Button(10, 10, 300, 25);
  btn->copy_label(fl_latin1_to_local("Fahrvergnügen"));
If your application uses characters that are not part of both encodings, or it will be used in areas that
commonly use different code pages, yoou might consider upgrading to FLTK 2 which supports UTF-8
encoding.

--- End quote ---

curaga:
On a Xorg + xft-fltk-1.3 system, the euro symbol works fine in all widgets.

@nitram
FLTK 1.3 supports utf-8 fully.

Navigation

[0] Message Index

[#] Next page

[*] Previous page