RE: [WebDNA] multi-language sites in current versions of webdna?
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105665
interpreted = N
texte = We were using WebCat in the late 90's to serve multi-lingual websites. Itwas the only thing we could find that could handle the double-byte charactersets. We progressed to the point of developing sites in multiple languagesfor Disney, Lazard, Daimler Chrysler, Kodak etc. We used language tags todenote the duplicate files, databases, photos, etc throughout the site.Something like logo_EN, logo_ES, logo_JA, etc. for the same file indifferent languages. Then we used different charsets in the header to denotewhich language. These days you just use Unicode. We also had a "sourcelanguage" 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 usethe translations for double-byte languages like Japanese and Thai inPhotoshop and Illustrator without messing up the encoding when you copy andpaste the text from the translations. There are other issues.....feel freeto contact privately if you need some more pointers.I know there are others on the list that currently do this with much lesseffort than we used in the 90's. With the use of Unicode thing have beengreatly simplified. Hopefully they will chime in here with some updatedinfo.Mike-----Original Message-----From: Govinda [mailto:govinda.webdnatalk@gmail.com] Sent: Friday, July 23, 2010 3:03 PMTo: WebDNA talkSubject: [WebDNA] multi-langauage sites in current versions of webdna?Hi AllI have a new client who will need me to make the same site in several languages (more than a few languages)... and my very first thought about how to approach this was to make mirror databases with the very same content (whose records will populate the text blocks).. but just make one mirror db for each language, where all the fields and records are the same, with the only difference being that each db is a language-translation of the other. (I.e. "content_english.db", "content_spanish.db", "content_hindi.db", etc. )I have never before had to pay much attention to char encoding.. and I am expecting this is suddenly going to be a big issue, and so i want to start by asking you who have worked on multi-language *Webdna* sites -- What did / do you experience?- What are the issues I should be aware of as a newbie multi-lingual website webmaster? ... And specifically to my initial idea of how to best approach this project,- Can webdna store other languages' characters in its native db format? ...Even if the character belongs to a charset that is not a single-byte encoding? (not sure if I said/understood that right ;-) .And/Or.. what better/other question(s) should I be asking?Thanks for any feedback/guidance!------------Govindagovinda.webdnatalk@gmail.com---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list
.To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
We were using WebCat in the late 90's to serve multi-lingual websites. Itwas the only thing we could find that could handle the double-byte charactersets. We progressed to the point of developing sites in multiple languagesfor Disney, Lazard, Daimler Chrysler, Kodak etc. We used language tags todenote the duplicate files, databases, photos, etc throughout the site.Something like logo_EN, logo_ES, logo_JA, etc. for the same file indifferent languages. Then we used different charsets in the header to denotewhich language. These days you just use Unicode. We also had a "sourcelanguage" 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 usethe translations for double-byte languages like Japanese and Thai inPhotoshop and Illustrator without messing up the encoding when you copy andpaste the text from the translations. There are other issues.....feel freeto contact privately if you need some more pointers.I know there are others on the list that currently do this with much lesseffort than we used in the 90's. With the use of Unicode thing have beengreatly simplified. Hopefully they will chime in here with some updatedinfo.Mike-----Original Message-----From: Govinda [mailto:govinda.webdnatalk@gmail.com] Sent: Friday, July 23, 2010 3:03 PMTo: WebDNA talkSubject: [WebDNA] multi-langauage sites in current versions of webdna?Hi AllI have a new client who will need me to make the same site in several languages (more than a few languages)... and my very first thought about how to approach this was to make mirror databases with the very same content (whose records will populate the text blocks).. but just make one mirror db for each language, where all the fields and records are the same, with the only difference being that each db is a language-translation of the other. (I.e. "content_english.db", "content_spanish.db", "content_hindi.db", etc. )I have never before had to pay much attention to char encoding.. and I am expecting this is suddenly going to be a big issue, and so i want to start by asking you who have worked on multi-language *Webdna* sites -- What did / do you experience?- What are the issues I should be aware of as a newbie multi-lingual website webmaster? ... And specifically to my initial idea of how to best approach this project,- Can webdna store other languages' characters in its native db format? ...Even if the character belongs to a charset that is not a single-byte encoding? (not sure if I said/understood that right ;-) .And/Or.. what better/other question(s) should I be asking?Thanks for any feedback/guidance!------------Govindagovinda.webdnatalk@gmail.com---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us
"Michael A. DeLorenzo"
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:
do you have a webcatalog tool you want to sell? (1999)
Not really WebCat (1997)
Count how many items in a summ total (2003)
Location of Webcat site in folder hierarchy (1997)
How do I get WebCatalog to interpret WebDNA tags in .html files? (1997)
Snake Bites (1997)
Showing unopened cart (1997)
passing large amount of text in post form (2005)
.. more on sliding discounts... (1997)
more cookie crumbling (1999)
charging? (2001)
Bug or syntax error on my part? (1997)
Error Lob.db records error message not name (1997)
t or f (1997)
Help! WebCat2 bug (1997)
emailer w/F2 (1997)
2.0Beta Command Ref (can't find this instruction) (1997)
Separate SSL Server (1997)
Testing band width (2002)
Webcatalog error, Plug-in for Webstar (1996)