Re: Strings with umlauts and such

For testing purposes I've put some users in an HoH

That was a good idea. However, you do not say if you have also written use utf8; in your source. Did you do that?

but I still end up with something like "K?hne" in Azure

Try posting it to something which you control rather than Azure. That way you can determine if the problem is internal to Azure or not. Even just saving it to a local file with a known encoding would do for starters.

Unicode looks big and scary the first time you have to deal with it but it's not so bad in the long run. Good luck.

(edited for typo)

🦛

Comment on Re: Strings with umlauts and such Download Code

Replies are listed 'Best First'.
Re^2: Strings with umlauts and such by PeterKaagman (Beadle) on Aug 13, 2024 at 10:49 UTC
When reading up on unicode I came across something I took as a warning not to use "use UTF-8". So I did not. The remark about using utf-8 in the code did confuse me: using Kühne in a string is using utf-8 in the code? Must give your suggetion to take Azure out of the equating some thought, not really sure how to go about that.	[reply]
Re^3: Strings with umlauts and such by hippo (Archbishop) on Aug 13, 2024 at 11:12 UTC
using Kühne in a string is using utf-8 in the code? It is, if it is written with utf-8 encoding. `use utf8;` tells perl that your source code includes literal utf-8 characters. If you don't include that but insert literal utf-8 characters in your code, all manner of bad things will ensue. See utf8. There is almost no reason not to `use uft8;` in all your code these days. 🦛	[reply] [d/l] [select]