[php-src] Issue #8308: The return value of mb_list_encodings() doesn't contain 'SJIS-win'
| From: | alexdowad | Date: | Thu, 07 Apr 2022 19:55:40 +0000 |
| Subject: | [php-src] Issue #8308: The return value of mb_list_encodings() doesn't contain 'SJIS-win' | ||
| Groups: | php.bugs | ||
| Request: | Send a blank email to php-bugs+get-240777@lists.php.net to get a copy of this message | ||
Issue: https://github.com/php/php-src/issues/8308
Comment Author: alexdowad
@zonuexe, these are interesting points, though what I was trying to ask was a bit different.
Let me try again. Let's imagine you are starting a new PHP-based software project right now.
You need to ingest SJIS-encoded data provided by users, and convert to Unicode for processing. Maybe
it's for CSV import. Would you use
mb_convert_encoding with
"SJIS", "SJIS-win", "CP932", or
something else? Why?
Have you ever developed such software projects in the past? If so, which of
mbstring's text encodings did you use? And most importantly, why? (I hope the
answer will not be "I just flipped a coin". 😅 )
It may be that none of the programmers who are sharing in this discussion know why they should
choose SJIS-win or CP932. It may be that almost none of the (presumably
many) PHP users who have ever used mbstring for this purpose, over its entire history,
have ever understood why they should choose SJIS-win over CP932, or vice
versa. If so, well... it is what it is. But it would be helpful, and appreciated, if we can be clear
about that.
I'm still hoping that somebody who is following this discussion *does* have reasons for
choosing one variant or another.