Please Make The Site Nls Friendly

Please make the site NLS friendly.

National Language Support (NLS)

It seems the site is not supporting Asian characters.

I'd have to pay someone to do it and it would likely not be used very much. Plus I can't read them so it would be impossible to moderate.

I would recommend installing the Google Translate extension for Chrome. You can set it to automatically translate to and from certain languages, which makes participating in sites that aren't in your native language much easier.

I use it when shopping on international sites ( Amazon Japan, Amazon Italy, FNAC, etc.) and it works very well, admittedly less so when alphabets utilize letters/characters outside of the regular western alphabet. I've not tried translating to or from Hebrew.

The issue with Google translation is: you have to be able to type (or past) the original language in order to get the translation.

You're thinking of the translate feature on the Google website. I'm talking about the browser extension. One click and it re-renders the current page in your chosen language, or you can set it to auto-translate certain languages.

No typing or pasting needed.

My Edge browser auto-translates. I use it all of the time for overseas auction catalogs on SAN.

The issue is not with translation.
It's about posting on SCF using Asian fonts (i.e. Thai, Chinese, Japanese)

When I post something.. this is the result:
#32121;#31992;#12398;#36664;#20986;#29992;#26908;#26619;#32025;

even though the preview is ok.

This is primarily an English language community. If you were to post in non-western alphabets, likely less than 1% of the membership could read it anyway, and additionally it becomes very difficult for moderators to tell legitimate content from spammers who also tend to use Asian alphabets in their postings.

If you're wanting to post Asian characters from certain stamps or overprints for discussion, you could always post an image.

The original SQL database 'datatype' would have to be configured as 'NVARCHAR' to support storing non-English characters. I suspect that it was not originally configured with this datatype (using this datatype results in using more database storage). If this is the case, trying to now convert the entire existing forum SQL database would be gruesome (and costly).

I also assume that the 'preview', since it is not using the SQL database, is displaying the characters just fine. But if you try to post with non-English characters when it goes to commit the post to the database and converts the non-English characters to numeric values.
Don