[ previous ] [ next ] [ threads ]
 
 From:  "John Lin" <0chiehchen at gmail dot com>
 To:  "Chris Dickens" <chris at object dash zone dot net>
 Cc:  "Stefan Frank" <Mono dot Developer at rootservices dot biz>, "MonoWall-Developers List" <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall-dev] UTF-8 as default encoding...
 Date:  Mon, 10 Apr 2006 18:21:51 +0800
Hi Chris,

Thanks for explaining UTF-8 for everyone!!!

For IP addresses on your example, it will be no problem for the current
M0n0wall implementation if switched to UTF-8.  When browser is in UTF-8, it
will only save international characters in UTF-8 format.  Since it will save
Alphanumberic characters in the ASCII format, the IP address will be passed
down exactly the way it is entered.


Best regards,

John


On 3/19/06, Chris Dickens <chris at object dash zone dot net> wrote:
>
> By the way, for those who are unfamiliar - the point of UTF-8 encoding is
> to
> store extended character sets such as Simplified Chinese, Japanese, etc.
> in
> places where only 8-bit characters are traditionally allowed.
> (Roman/Western
> languages)  As John has pointed out, a single Chinese character may appear
> as two Roman characters within UTF-8 encoding - this is "expansion" is
> necessary to store the foreign characters without modification to the
> underlying system.  To support UTF-8 encoding for informational fields
> should require little effort on the m0n0 development team.  Fields which
> contain things like IP addresses and whatnot might need an additional
> check
> routine to make sure that only valid characters are input there and that
> should be all.  A simple regular expression check should suffice.
>
> I would offer to assist, but my area of expertise is within the Microsoft
> .net Framework, so I only follow the discussion in this mailing list from
> an
> academic point of view.
>
> Ironic that I know so much about this, I have learned a lot about dealing
> with these matters because my fiancee is Chinese and I have taken up
> learning Chinese for her. :-)
>

>
> --Chris
> The Object Zone
> http://www.object-zone.net/
>
> -----Original Message-----
> From: John Lin [mailto:0chiehchen at gmail dot com]
> Sent: Saturday, March 18, 2006 10:53 PM
> To: Stefan Frank
> Cc: MonoWall-Developers List
> Subject: Re: [m0n0wall-dev] UTF-8 as default encoding...
>
> Hello Stefan,
>
> Actually, I am already doing this.  For example, when using Captive Portal
> -> Users page.  When adding a user, I change the encoding to UTF-8 on my
> browser.  Then, I started to type username in alphanumeric only, and type
> Full Name in Traditional Chinese, and save it.  When I am in user list
> page,
> at first it displays Full Name with garbled characters, then I manually
> change to UTF-8 on my browser again, and this display Chinese correctly.
>
> I also tried this with PPTP user management page and it works okay.
>
> The only thing is that I got to change to UTF-8 manually each time.  It is
> harder to ask other administrator to do this.
>
> So, I think it works well for storing international languages using UTF-8
> with Names, which stores in m0n0's own configuration file.  UTF-8 should
> be
> no problem for most cases since it is storing in multiple ASCII
> characters,
> which for any program should read as some LONG English characters.
>
> Thank you for your development effort for m0n0wall!  It is a great
> software
> and I am introducing this to all my friends in Taiwan and USA...
>
>
> John
>
>
> On 3/19/06, Stefan Frank <Mono dot Developer at rootservices dot biz> wrote:
> >
> > Hello John,
> >
> > No problem everyone is invited to ask or send his comments here. It isnt
> > only just the space/size of additional files. There are sometimes things
> > to do so that non-English characters can be handled correctly. I am not
> > really sure with that things.
> >
> > If the Page default encoding will be changed to UTF-8, then i ask my
> self
> > how the webGUI or other tools should work with non-English characters?
> > For example what happens if japanese or chinese characters are in use?
> >
> > I am not sure but if the tools or software thats in use cant work with
> > "unknown" characters or need a recompiled version who wants to do that?
> >
> > I have no problems if m0n0wall get multi-language support but i guess
> > this will bring a lot of additional work.
> >
> > --
> > Best regards,
> > Stefan Frank
> >
> > Looking for Monowall Adjustment?
> > http://M0n0WaLL.RootServices.Biz
> >
> >
> >
> >
> >
> > John Lin schrieb:
> > > Hello Stefan,
> > >
> > > Thank you for your prompt reply.  Yes, I understand that...  and I
> think
> > I
> > > saw other posts regarding support of multi-languages in m0n0; and the
> > answer
> > > from the group is no since it require alot of space.
> > >
> > > However, all I am asking is just to use UTF-8 encoding as default and
> > still
> > > use English as the default presentation language.  This way, at least
> > users
> > > will be able to store non-English characters.  It would be something
> > like
> > > user's First/Last name for administration use.
> > >
> > > It would be just changing all pages with Western as the default
> encoding
> > to
> > > UTF-8.
> > >
> > > Best regards,
> > >
> > > John
> > >
> > >
> > > On 3/19/06, Stefan Frank <Mono dot Developer at rootservices dot biz> wrote:
> > >
> > >> Hello John,
> > >>
> > >> AFAIK the answer will be simple no ... m0n0wall is build as "small as
> > >> possible"
> > >> software. For example english isnt the native language from a lot
> users
> > >> here, and
> > >> it will require a lot of time for translations and maintaining them.
> > >>
> > >> --
> > >> Best regards,
> > >> Stefan Frank
> > >>
> > >> Looking for Monowall Adjustment?
> > >> http://M0n0WaLL.RootServices.Biz
> > >>
> > >>
> > >>
> > >> John Lin schrieb:
> > >>
> > >>> Hi!
> > >>>
> > >>> Any one think of using UTF-8 on m0n0wall would be a useful
> > >>>
> > >> feature?  This
> > >>
> > >>> will support storing information with International languages...
> > >>>
> > >>> Thank you in advance!
> > >>>
> > >>> John
> > >>>
> > >>>
> > >>>
> > >>
> > >>
> > >
> > >
> >
> >
> >
>
>