IssueRaiser

I can confirm that text encoding is still a real pain in Japan.

I can confirm that text encoding is still a real pain in Japan. Despite the fact that we now have UTF-8, which should be used whenever possible, legacy encodings like SJIS, EUC, etc. still abound. For instance, whenever I download CSV bank or credit card data here in Japan, I always have to convert the file from one of those encodings before using it. At work in Tokyo, I deal with email in these encoding (or worse -- parts of the email in SJIS, with other parts in EUC). So yes, I think the barbaric text encodings of yesteryear are still a pain point for Japanese users. (Even so, I agree that it doesn't merit top billing in the window toolbar.) Off-topic bonus tip for aspiring text editor authors : make an awesome autocompletion UI, but leave the indexing/autocompletion up to third party open source plugins. Look at Chocolat.app for what the completion UI should look like (a big, attractive complex popover view (not just a menu) with optional documentation display), but open up the actual dynamic completion itself to your users. There is no way a small team can do good completion in tons of languages, but providing a great UI is totally doable.

Posted by veidr on Nov 21, 2014, 1:00 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.9,000 issues0 comments

ux (FinTech)

I can confirm that text encoding is still a real pain in Japan.

veidrNov 21, 2014, 1:00 AM

I can confirm that text encoding is still a real pain in Japan. Despite the fact that we now have UTF-8, which should be used whenever possible, legacy encodings like SJIS, EUC, etc. still abound. For instance, whenever I download CSV bank or credit card data here in Japan, I always have to convert the file from one of those encodings before using it. At work in Tokyo, I deal with email in these encoding (or worse -- parts of the email in SJIS, with other parts in EUC). So yes, I think the barbaric text encodings of yesteryear are still a pain point for Japanese users. (Even so, I agree that it doesn't merit top billing in the window toolbar.) Off-topic bonus tip for aspiring text editor authors : make an awesome autocompletion UI, but leave the indexing/autocompletion up to third party open source plugins. Look at Chocolat.app for what the completion UI should look like (a big, attractive complex popover view (not just a menu) with optional documentation display), but open up the actual dynamic completion itself to your users. There is no way a small team can do good completion in tons of languages, but providing a great UI is totally doable.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue