In your command window, do chcp 1252 and rerun your rexx below
Från: Erich Steinböck
Skickat: måndag den 13 oktober 2014 11:12
Till: Open Object Rexx Developer Mailing List
Mostly applying to us "international" guys, there's one topic I'd like to bring
up regarding string objects.
Technically speaking it's impossible to correctly interpret any string content,
as string instances do not provide a means to define their encoding.
Today this makes it difficult to correctly accept input and generate output
with local language special characters (e. g. German Umlaut characters).
A simple example (that really doesn't cover the full story) under Windows 7:
rexx -e "say 'Ölrückstände'" -> ╓lrⁿckstΣnde
Inline image 1
Should String and Stream classes be enhanced to know their encoding?
Erich
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://p.sf.net/sfu/Zoho
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
