> Nyquist itself is case insensitive ASCII - no Unicode support at all, > and I think that is unlikely to change in the foreseeable future, > It "may" be possible to allow Unicode characters in the header > statements as those are ignored (commented out) for Nyquist. I'll > mention when work starts on version 5 headers. > > Steve > Well, it does actually translate my surname correct after converting to utf-8 (which I did previously actually). However, I'm not sure if the encoding would function with all platforms. I think that strings are already translated from/to Unicode. For example: Within the Nyquist prompt, I have 3 possibilities to let my name appear in the message box: (print "hänggi") (print "h\303\244nggi") (print "h\344nggi") Only the last one throws a warning out. However, it's needed to e.g. access my document folder within XLISP. In other words, Nyquist translates the first string into the second one which has afterwards to be translated into the third one (file operations only). Something similar happens after a crash. Audacity warns at recovery time, although it works properly. The reason is just that darn "ä" in my user path. I think I'll stick to the "ae" for the time being. Thanks Steve. Robert The audacity4blind web site is at //www.freelists.org/webpage/audacity4blind Subscribe and unsubscribe information, message archives, Audacity keyboard commands, and more... To unsubscribe from audacity4blind, send an email to audacity4blind-request@xxxxxxxxxxxxx with subject line unsubscribe