RE: [WebDNA] multi-language sites in current versions of webdna?
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105669
interpreted = N
texte = Govinda, You can use one database if you like. I think using one per language is easier to manage. When we first started to use WebCat for multilingual websites we used one database. That is all WebCat had at the time! We literally had multiple sites in multiple languages all running off of the one database. Keep in mind these site were all eCommerce sites... Eventually when we had unlimited databases we separated everything and then made a multilingual content management solution using WebDNA. This CMS also managed each language version and had an interface for translators to translate, edit and proof the content in context as well as many other things. Olin, who you may know from this list, was the head programmer for that solution. Mike -----Original Message----- From: Govinda [mailto:govinda.webdnatalk@gmail.com] Sent: Friday, July 23, 2010 6:00 PM To: talk@webdna.us Subject: Re: [WebDNA] multi-language sites in current versions of webdna? 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 --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
Govinda, You can use one database if you like. I think using one per language is easier to manage. When we first started to use WebCat for multilingual websites we used one database. That is all WebCat had at the time! We literally had multiple sites in multiple languages all running off of the one database. Keep in mind these site were all eCommerce sites... Eventually when we had unlimited databases we separated everything and then made a multilingual content management solution using WebDNA. This CMS also managed each language version and had an interface for translators to translate, edit and proof the content in context as well as many other things. Olin, who you may know from this list, was the head programmer for that solution. Mike -----Original Message----- From: Govinda [mailto:govinda.webdnatalk@gmail.com] Sent: Friday, July 23, 2010 6:00 PM To: talk@webdna.us Subject: Re: [WebDNA] multi-language sites in current versions of webdna? 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 --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug 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:
Cart # Starting at 1000 (2000)
[OT] Domain Name Scam (2000)
Putting & into a database (1999)
Re:Signal Raised (1997)
syntax question, not in online refernce (1997)
[lookup] again... *solved* (2003)
two unique banners on one page (1997)
quotation marks needed? (2000)
Some ThankYou page problems (1997)
setitems, one more thing (1997)
can pull down menu do a ONCHANGE= without Java script? (2000)
Calendar (1997)
[date format] w/in sendmail (1997)
Thanks for tips, more quest (1997)
[OT] MacWorld Expo (2004)
writefile, csv, tab and excel import behavior (2004)
Bug Report, maybe (1997)
Re:Merging databases (1997)
[WebDNA] Setting up a new server, hierarchy question (2014)
Date Range Sorting (1997)