I have managed to install fltk 1.3.9 on top of 1.4 just for this
experiment. I'll need to reinstall 1.4 as soon as possible as my
app relies on the 1.4 API. I do have the two compilations in the
build directories, but to compile using them involves switching
the execute path (for fltk-config), the library path (for the fltk
libraries) and the include path (the API has changed).
As I expected it behaves as intended. I attach screenshots of the
"about" dialog in the two cases, which show the problem in
rendering the text.
You can see that the only problems are with the i-acute (should
it be an e-acute in Ren¨¦ not Ren¨ª?), n-tilde and c-cedilla, which
I presume are between 128 and 255. The other characters (Greek,
Russian and the Polish e-hook) are presumably already coded as
UTF-8.
In the version of coordinates.cxx you sent I noticed you removed
the degree, minute and second (¡ã, ', '') altogether rather than
replace the ¡ã with the UTF-8 equivalent 0xC2 0xB0 (octal escape
\302\260).
Phil.
?
On 31/03/2024 22:31, Dave, W1HKJ wrote:
toggle quoted message
Show quoted text
Can you build fltk-1.3.9 and
test an fldigi build against that lib version?
Dave
On 3/31/24 16:17, Philip Rose, GM3ZZA
via groups.io wrote:
Managed to get some time to myself after the birthday party
and Easter dinner.
I tried this Dave, but it didn't seem to solve this
particular case. I downloaded the latest fldigi alpha
(4.2.04.09) first, ran .configure and make, then tested. Then
copied the two files into src/misc and src/synop-src. Then ran
"make clean", "make -j4" and "sudo make install", so I hope
that picked up the changes.
?
It happens when I mouse over a callsign in the RX window. The
tooltip that pops up with the info on the DX entity contains
the degree sign (or rather doesn't) for the bearing
information.
As it's a tooltip I can't move the mouse to copy what it
says.
Phil.
On 30/03/2024 22:53, Dave, W1HKJ
wrote:
At your convenience
Phil.? Happy Birthday to your grandaughter and Happy
Easter to you and your family.
Dave
On 3/30/24 17:43, Philip Rose,
GM3ZZA via groups.io wrote:
Dave,
They
were run-time warnings. I'll not be able to do it
tomorrow, as it's my granddaughter's 5th?birthday
as well as being Easter Sunday,?
Phil.
Phil,
Try substituting the attached for the original files.?
Let me know if there are still compile warnings.
Dave
On 3/30/24 14:36, Philip
Rose, GM3ZZA via groups.io wrote:
Hi Dave,
It's an old Dell Intel laptop repurposed
with Debian bookworm. I use the default window
manager. I built the latest FLTK git using default
configuration so Wayland and pango are enabled.
From what I understand from the FLTK
forum having had similar problems in my app, pango
expects UTF8 characters. It's what draws characters
on screen which are not specified in the supplied
font.
I will understand if you don't want to
support this yet.
73 Phil GM3ZZA
On 30 March 2024, at 17:28, "Dave, W1HKJ" <w1hkj@...>
wrote:
Phil,
I have a brand new Pi5 running PiOS Bookworm with
one of several desktop managers (preference is Mate
Desktop).? I am not seeing the errors you report.?
What processor for the target build.? Is the OS
install a base Debian or a derivative?
David
On 3/30/24 11:31, Philip
Rose, GM3ZZA via wrote:
I had a quick look.
There are quite a lot of degree signs coded in
string literals and these will be the extended ASCII
0xB0 rather than the UTF-8 U+00B0 ("\302\260"). One
of the files was "coordinates.cxx" (IIRC) in the
<< operator. The others were large menu_items
as part of a special character list.
Phil.
I compiled fldigi from
4.2.04.05 using the then latest fltk 1.4 on
debian bookworm and I keep getting the
following warning:
(process:21094): Pango-WARNING **:
22:50:00.323: Invalid UTF-8 string passed to
pango_layout_set_text()
>From my own experience this is when an
extended ASCII character is used rather than
its UTF-8 equivalent. I noticed today as I
hovered over a callsign the tooltip window
came up and displayed latitude and longitude
with the degree symbol replaced by the black
diamond used for an unprintable character. At
the same time the pango warning came up.
If you want I can look at the fldigi code
tomorrow.
73 Phil.
Philip Rose, GM3ZZA
