Re: GWorkspace startup - Setting unknown econding

[Fred Kiefer]

Turns out I was wrong here. Of course the bison grammar was wrong and needed 
correction, but this was not what caused this issue. Here 10000 is a valid code 
page that should be mapped to Mac Roman. The handing of many other code pages 
is still missing as we don’t ave constants for these in base. This specific one 
was important as it gets used a lot on the Mac.

Please give the new code a try,
Fred

> Am 26.05.2020 um 15:44 schrieb Fred Kiefer <fredkiefer@gmx.de>:
> 
> Most likely I made an error in the rtfGrammer.y file on line 212. The 
> statement "$$ = 3" should just read "3". I will correct that and regenerate 
> the dependent files as soon as I am back home, that is sometimes next 
> weekend. You could check whether this is the case by looking at your RTF 
> files, they must use the pc encoding to tricker this behaviour.
> 
> Hope this helps,
> Fred
> 
> On the road
> 
> Am 26.05.2020 um 12:05 schrieb Riccardo Mottola <riccardo.mottola@libero.it>:
> 
>> Hi,
>> 
>> after checking the strange encoding bug, I have another strange error in 
>> GWorkspace which is either new or I never noticed.
>> I get several of these:
>> 
>> 2020-05-26 09:37:22.971 GWorkspace[13276:100105] Setting unknown encoding 
>> 10000
>> 
>> 
>> this is not 32bit or 64bit dependent at all.
>> 
>> The only occourence I see is in RTFConsumer.m line 1426 in libs gui, where 
>> indeed a value "10000" looks like bogus.
>> 
>> However, if I try to run GWorkspace in the debugger with:
>> 
>> 
>> (gdb) b RTFConsumer.m:1426
>> No source file named RTFConsumer.m.
>> Make breakpoint pending on future shared library load? (y or [n])
>> 
>> 
>> even after the executable has been run. Why that? Perhaps it is totally 
>> unrelated
>> 
>> Input appreciated.
>> 
>> Riccardo
>> 
> 
>