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:

[WebDNA] When was autonumber added? (2010) weird user / authenticate happenings (2003) HELP! 10K hits per hour for pages that no longer exist! (2000) Help with update to 2.11 (1998) Problems searching from a FORM (1997) Any help gratefully appreciated (2001) WebCatalog for guestbook ? (1997) Upgrade to WebCat2 from Commerce Lite (1997) [WebDNA] Fails to recognize comma-separated db (2010) Freeze (2003) searching by date (1998) Unique SKU Numbers (2000) formula.db problem (1999) Refering page (1998) Review comparison by PC Magazine: Open for On-line Business (1997) Error:Too many nested [xxx] contexts (1997) Search design (1997) Multiple ShipTo Addresses (2003) OK, here goes... (1997) Webstar 1.3.1 PPC (1997)