There is no UNICODE support, so no UTF-8 specifically. RouterOS strings are all single-byte. And the default “code page” is Latin-1 for the extended chars. So your choices look like these:
Maybe some future V8 will add UTF-8 or something.
Why would anyone want to introduce all kinds of multi-language issues into network equipment ?
You do realize this might require a COMPLETE review of all code to make sure all texts and whatever is being displayed is using the proper language tables ?
IMHO this ain’t gonna happen. I don’t see the added value either.
That very well may be true. But allowing comments to contain like UTF-8 unicode, is different than say a French Winbox.
But I have to imagine whatever “multiplatform client” there working have to deal with UTF-8 at some level, as be very hard to implement a UI using old Windows codepages in any modern dev tools… But maybe that’s why all we’ve seen of this is an icon.
It comes up since you can’t use emoji in comments for me. But also /tool/fetch sometimes when you interact the default is almost-always UTF-8.