Bug 380793 - Encoding problems on Windows in non-latin1, non-multibyte locales
Summary: Encoding problems on Windows in non-latin1, non-multibyte locales
Status: RESOLVED FIXED
Alias: None
Product: rkward
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified All
: NOR normal
Target Milestone: ---
Assignee: RKWard Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-11 10:34 UTC by Thomas Friedrichsmeier
Modified: 2024-08-03 14:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Friedrichsmeier 2014-11-11 10:34:30 UTC
-- This ticket was imported from http://sourceforge.net/p/rkward/bugs/136 on 2017-05-30 15:27:01 +0100 --
There appear to be some rather strange encoding problems in non-latin1, non-multibyte locales on Windows. Example is Lithunian (ISO-8859-13 / CP1257).

Some of this may or may not be RKWard's fault, but RKWard could do a better job of passing to-be-evaluated strings to the backend with specified encoding.
a) When using mkChar() from a string -> R_ParseVector()
b) For stdin. Can maybe use "--encoding" command line option.

Symptoms include (not all may be RKWard's fault)
- Stripping of special chars to ascii siblings
- Misprinting of chars in the console
- Misprinting of chars only after summary() ? Whatever that is about.

See https://sourceforge.net/p/rkward/mailman/message/33025657/ and parents.-- Labels: encoding, windows --
Comment 1 Andrew Crouthamel 2018-11-12 02:50:12 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-21 04:41:55 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Thomas Friedrichsmeier 2018-11-23 17:35:06 UTC
The bar to reproducing this is relatively high, as it is a windows only bug.

I believe it is still valid (as I have not done anything to fix it, and it happens outside the domain of qt), and should be kept open as a reminder to look into this. I'll try to give it a better look when the time comes for the next release (which always involves getting my Windows development environment back to speed).

Thanks a lot for trimming the fat from our list of bugs!