Sven could you update the class comments of such classes and we should
finish to get rid of them.
Your solution is much nicer.
Stef
Le 5/6/16 à 21:40, Sven Van Caekenberghe a écrit :
On 05 Jun 2016, at 21:07, Hilaire <hila...@drgeo.eu> wrote:
Hello Sabine,
Just a suggestion.
If your string is not pure ascii you may need to convert it to UTF8
first as this is what likely expect your OS host.
Indeed Pharo string are not internally encoded as utf8
If that is the case, that the OS expects a different encoding, then the
OS(Sub)Process implementation should deal with it, not the user of the API.
Check the UTF8TextConverter class to do so.
No, these converters are conceptually wrong, since they encode String to
String, while it should be String to ByteArray.
The ZnCharacterEncoder hierarchy should be used instead.
String>>#utf8Encoded is a convenience method that can be used to do a quick
conversion.
Hilaire
Le 05/06/2016 18:39, Sabine Manaa a écrit :
on command line, this works, my file is copied:
cp /Library/WebServer/Documents/reports/bär.pdf
/Library/WebServer/Documents/reports/test.pdf
In Pharo (4+5) this does not work (file not copied, no error message)
OSProcess command: 'cp /Library/WebServer/Documents/reports/bär.pdf
/Library/WebServer/Documents/reports/test-a.pdf'.
This works (file is copied):
OSProcess command: 'cp /Library/WebServer/Documents/reports/bar.pdf
/Library/WebServer/Documents/reports/test-b.pdf'.
Seems that german umlauts don't work.
Is there something, I can I do, I don't want to replace the umlauts in
filenames...
Regards
Sabine
--
Dr. Geo
http://drgeo.eu
