Subj : Re: WX
To : KenDB3
From : Digital Man
Date : Sun Mar 06 2016 08:35 pm
Re: Re: WX
By: KenDB3 to Digital Man on Sun Mar 06 2016 10:41 pm
> Re: Re: WX
> By: Digital Man to KenDB3 on Sat Mar 05 2016 07:37 pm
>
> >> The only thing the GitHub code has over Ver 1.04 is the beginnings of
> >> language support (aka internationalization) for Spanish and Italian
> >> (other translations are welcome if someone wants to submit some).
> >> However, for languages other than English I've made the characters
> >> UTF-8/Unicode as opposed to CP437, since the accents on non-English
> >> characters will not show up correctly in CP437. (Ex. Monday in Italian
> >> is Luned�, ending in an "i" with the grave accent which looks awkward
> >> in CP437).
>
> DM> Are you using a terminal program that supports UTF-8?
>
> DM> Most BBS terminal programs that I'm aware of (e.g. SyncTERM) do not
> DM> support UTF-8, so that's not going to work well with the majority of
> DM> clients. Or is this for a web UI (where UTF-8 is widely supported)?
>
> So, it is for the Terminal, and not a Web UI.
>
> Honestly, this was my attempt to support a request I got (on GitHub) for
> i18n support. First, I had to look up "i18n" to find out it meant
> internationalization. But, then I saw that Weather Underground's API
> actually supports this, but it's a bit of a catch-22.
>
> The data that comes back has UTF-8 characters, like the days of the week
> example I threw into my last post. I am pretty sure the W.U. API wasn't
> expecting much stuff other than Web UI. I really have no idea what character
> set would support the accented characters besides UTF-8, but I tested with
> few different fonts in SyncTERM, including ISO-8859-15 West European and
> ISO-8859-2 Central European, but no luck.
>
> I'm able to see everything in UTF-8 just fine using PuTTY release 0.66,
> using UTF-8 as the Remote Character Set on the Translations tab, and with a
> font of Courier (14-pt, Clear Type) on the Appearance tab.
Right, but how does the rest of the BBS look with PuTTY set that way? Probably
not very good. Right now, Synchronet doesn't support any way of detecting or
tracking the user's character set or encoding and pretty much assumes CP437.
You can send UTF-8 from your script, but most clients aren't going to display
it correctly and there's really no way for you to know which clients will or
will not display it correctly.
digital man
Synchronet "Real Fact" #1:
Synchronet version 2 for DOS and OS/2 was released to the public domain in 1997.
Norco, CA WX: 54.3�F, 74.0% humidity, 0 mph ESE wind, 0.20 inches rain/24hrs
---
� Synchronet � Vertrauen � Home of Synchronet � telnet://vert.synchro.net
