Re: japanese characters

This WebDNA talk-list message is from

1997


It keeps the original formatting.
numero = 11327
interpreted = N
texte = >Can you explain more how this will work? The ability to do Japanese is >one of >the reasons we chose WebCatalog. Ideally, we'd like the customers to >select the >language of their choice (English, German, French and Japanese are the >highest >priorities for implementation). > >Will we have to buy a different version of WebCatalog for the double-byte >features? We will make the English version of the store functional before >we do >Japanese, but we are looking ahead.Sandy:I can tell you right off the bat that handling double-byte character sets (like Japanese) is not a trival task. WebCatalog is one of the very few net catalog products on ANY platform that supports double-byte characters. We have been usuing v1.6.1 successfully with Japanese charcters being served from the templates *and* database (www.crazyshirts.com). I have had no problem serving double-byte characters so far from v 2.0. The NT version I believe doesn't completely support double-byte characters...yet. You should have no problem working with Japanese character sets. Have fun working with Japanese!Aloha,Olin ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Olin Kealoha Lagon (v) 808.539.3978 Director of Website Creation & Sales (f) 808.539.3766 WorldPoint Interactive, Inc. (c) 808.291.1610 www.worldpoint.com (e) olin@worldpoint.com Associated Messages, from the most recent to the oldest:

    
  1. Re: japanese characters (Sandra L. Pitner <76501.3521@CompuServe.COM> 1997)
  2. Re: japanese characters (Olin 1997)
  3. Re: japanese characters (Sandra L. Pitner <76501.3521@CompuServe.COM> 1997)
  4. Re: japanese characters (Olin 1997)
  5. Re: japanese characters (Sandra L. Pitner <76501.3521@CompuServe.COM> 1997)
  6. Re: japanese characters (Grant Hulbert 1997)
  7. japanese characters (Olin 1997)
>Can you explain more how this will work? The ability to do Japanese is >one of >the reasons we chose WebCatalog. Ideally, we'd like the customers to >select the >language of their choice (English, German, French and Japanese are the >highest >priorities for implementation). > >Will we have to buy a different version of WebCatalog for the double-byte >features? We will make the English version of the store functional before >we do >Japanese, but we are looking ahead.Sandy:I can tell you right off the bat that handling double-byte character sets (like Japanese) is not a trival task. WebCatalog is one of the very few net catalog products on ANY platform that supports double-byte characters. We have been usuing v1.6.1 successfully with Japanese charcters being served from the templates *and* database (www.crazyshirts.com). I have had no problem serving double-byte characters so far from v 2.0. The NT version I believe doesn't completely support double-byte characters...yet. You should have no problem working with Japanese character sets. Have fun working with Japanese!Aloha,Olin ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Olin Kealoha Lagon (v) 808.539.3978 Director of Website Creation & Sales (f) 808.539.3766 WorldPoint Interactive, Inc. (c) 808.291.1610 www.worldpoint.com (e) olin@worldpoint.com Olin

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

date pref (1999) Emailer port change (1997) carriage returns in data (1997) Re2: Calculating multiple shipping... (1997) Ok here is a question? (1997) Email password -- was Classified Ads 4 Sale (1998) AppleScript does not work properly ... (2000) Web Catalog 2 demo (1997) Calendar (1997) database size? (1997) WCS Newbie question (1997) [WebDNA] TCPConnect example doesn't work (2017) Tab Charactor (1997) Bug? (1997) Math Context (1998) Location of Browser Info.txt file (1997) Shownext! (1998) Problems passing [SKU] with $Replace in 2.0 (1997) Emailer (WebCat2) (1997) RE: Forcing Paragraph Breaks on Results (1998)