Re: [WebDNA] multi-language sites in current versions of webdna?

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 105666
interpreted = N
texte = Thanks for replying Mike! OK, so this is good reassurance. For now I am just glad to hear you were storing/retrieving multi-byte language content with webdna. I guess than rather than think too much now, I will bring up the issues as/when they come up (if/when I get stuck). (I will not actually start on this for some weeks). For now let me just ask - UTF-8 may help simplify since the days you coded those sites, Mike, but do you think that somehow means that there is a better way to serve up various languages' pages other than what I first proposed - i.e. to have one content.db per language? (where each db record is the content for a given page... each field another text/graphic block on the page).. ? Thanks for writing, -G On Jul 23, 2010, at 5:09 PM, Michael A. DeLorenzo wrote: > We were using WebCat in the late 90's to serve multi-lingual > websites. It > was the only thing we could find that could handle the double-byte > character > sets. We progressed to the point of developing sites in multiple > languages > for Disney, Lazard, Daimler Chrysler, Kodak etc. We used language > tags to > denote the duplicate files, databases, photos, etc throughout the > site. > Something like logo_EN, logo_ES, logo_JA, etc. for the same file in > different languages. Then we used different charsets in the header > to denote > which language. These days you just use Unicode. We also had a "source > language" and then a copy of each database for each "target" language. > Content_EN.db, Content_ES.db, etc... We also had to figure out how > to use > the translations for double-byte languages like Japanese and Thai in > Photoshop and Illustrator without messing up the encoding when you > copy and > paste the text from the translations. There are other > issues.....feel free > to contact privately if you need some more pointers. > > I know there are others on the list that currently do this with much > less > effort than we used in the 90's. With the use of Unicode thing have > been > greatly simplified. Hopefully they will chime in here with some > updated > info. > > Mike Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] multi-language sites in current versions of webdna? (Govinda 2010)
  2. RE: [WebDNA] multi-language sites in current versions of webdna? ("Michael A. DeLorenzo" 2010)
  3. Re: [WebDNA] multi-language sites in current versions of webdna? (Steve Craig 2010)
  4. Re: [WebDNA] multi-language sites in current versions of webdna? (Govinda 2010)
  5. RE: [WebDNA] multi-language sites in current versions of webdna? ("Michael A. DeLorenzo" 2010)
Thanks for replying Mike! OK, so this is good reassurance. For now I am just glad to hear you were storing/retrieving multi-byte language content with webdna. I guess than rather than think too much now, I will bring up the issues as/when they come up (if/when I get stuck). (I will not actually start on this for some weeks). For now let me just ask - UTF-8 may help simplify since the days you coded those sites, Mike, but do you think that somehow means that there is a better way to serve up various languages' pages other than what I first proposed - i.e. to have one content.db per language? (where each db record is the content for a given page... each field another text/graphic block on the page).. ? Thanks for writing, -G On Jul 23, 2010, at 5:09 PM, Michael A. DeLorenzo wrote: > We were using WebCat in the late 90's to serve multi-lingual > websites. It > was the only thing we could find that could handle the double-byte > character > sets. We progressed to the point of developing sites in multiple > languages > for Disney, Lazard, Daimler Chrysler, Kodak etc. We used language > tags to > denote the duplicate files, databases, photos, etc throughout the > site. > Something like logo_EN, logo_ES, logo_JA, etc. for the same file in > different languages. Then we used different charsets in the header > to denote > which language. These days you just use Unicode. We also had a "source > language" and then a copy of each database for each "target" language. > Content_EN.db, Content_ES.db, etc... We also had to figure out how > to use > the translations for double-byte languages like Japanese and Thai in > Photoshop and Illustrator without messing up the encoding when you > copy and > paste the text from the translations. There are other > issues.....feel free > to contact privately if you need some more pointers. > > I know there are others on the list that currently do this with much > less > effort than we used in the 90's. With the use of Unicode thing have > been > greatly simplified. Hopefully they will chime in here with some > updated > info. > > Mike Govinda

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:

Running _every_ page through WebCat ? (1997) WebCat2b13MacPlugIn - More limits on [include] (1997) Country & Ship-to address & other fields ? (1997) setting line item numbers (1998) Displaying photo attached to first record (1997) [/application] error? (1997) Price Change Password (2003) Semi OT: IE losing info from forms when back button is used (2005) UPPERCASE (1997) Max Record length restated as maybe bug (1997) [WebDNA] paypal (2009) WebCat2b13MacPlugIn - [showif][search][/showif] (1997) Sum of Quantities (1997) text size limitation (1997) [index] (1997) I can help! (1996) [url] link (1998) [subtotal] and others (1997) Credit Card Number checking (1997) Re:Merging databases (1997)