|Mailing List firstname.lastname@example.org Archived Message #208||back to list|
On 08/15/21 08:57 am, Alfredo Fernï¿½ndez Dï¿½az wrote:
Lewis, did you notice I reported this was a problem that showed up /on a
Russian system/, and nowhere else? -- Ulrich's name was always properly
processed and rendered on my main system (main CP always 850).
You got me there.
I was only testing in English. My first go-round told me that XWP was not installed,
as it couldn't match Ulrich's name in the db.
Once I converted the script to UTF-8, all was right with the world.
Now, let's convert the WIS to UTF (and change its CODEPAGE attribute
accordingly), and fire up WarpIN on that again: see lsw@ru_CP850.png, look
at my name again.
That is a UTF conversion problem, which may or may not be related to the one
I reported initially, but we definitely brought it up converting the WIS to
CP 1208 aka UTF8.
The WarpIN source says that we handle extracted files (EXTRACTFROMPCK) like so:
So, we convert the CP850 Readme to UTF-8. So far, so good. However, when we
then need to convert to the display codepage (CP866, in this case), we run
into a slight problem (note that Readme.UTF8 is the original readme which I
converted via iconv):
[j:\] iconv -f UTF-8 -t 866 Readme.UTF8 > Readme.866
iconv.exe: Readme.UTF8:108:12: cannot convert
Line 108, char 12 is "ï¿½" in your name.
Hmmm... I'm not sure what to do here.
There is a WarpIN preference for display codepage, which defaults to process
codepage. However, on a Russian system, it would seem highly illogical to
change this merely to read a few characters which can't be rendered in 866.
Also, this is not a font thing. I have dropped myriad fonts onto the dialog,
all with the same result: "?" for the characters in your name.
I fall back on my contention that this is not a WarpIN bug.
WarpIN accepts the
content of an external file as the same codepage as specified for the WIS, and
then converts to UTF-8, and finally to the display codepage. It's a conundrum,
I grant you. I just haven't figured an adequate workaround as yet.
Mail to ListMaster