Re: [WebDNA] multi-language sites in current versions of webdna?
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 105667
interpreted = N
texte = Hi I have recently done a 9 language, CMS based site and basically = everything was using utf-8, I did have separate db's, no reason it = wouldn't have worked all in one though. I didn't seem to need any = particular special treatment when it came to reading or writing to db so = it should be easy enough. Cheers =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Steve Craig - Asylum Interactive Ltd Tel +44 1330 860550 Fax +44 1330 860880 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D http://www.asylumweb.com Email: steve@asylumweb.com Skype: s.craig - iChat: steve.craig =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D On 23 Jul 2010, at 22:59, Govinda wrote: > Thanks for replying Mike! >=20 > 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). >=20 > For now let me just ask - >=20 > 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).. > ? >=20 > Thanks for writing, > -G >=20 > On Jul 23, 2010, at 5:09 PM, Michael A. DeLorenzo wrote: >=20 >> 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. >>=20 >> 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. >>=20 >> Mike >=20 > --------------------------------------------------------- > 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:
Hi I have recently done a 9 language, CMS based site and basically = everything was using utf-8, I did have separate db's, no reason it = wouldn't have worked all in one though. I didn't seem to need any = particular special treatment when it came to reading or writing to db so = it should be easy enough. Cheers =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Steve Craig - Asylum Interactive Ltd Tel +44 1330 860550 Fax +44 1330 860880 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D http://www.asylumweb.com Email: steve@asylumweb.com Skype: s.craig - iChat: steve.craig =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D On 23 Jul 2010, at 22:59, Govinda wrote: > Thanks for replying Mike! >=20 > 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). >=20 > For now let me just ask - >=20 > 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).. > ? >=20 > Thanks for writing, > -G >=20 > On Jul 23, 2010, at 5:09 PM, Michael A. DeLorenzo wrote: >=20 >> 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. >>=20 >> 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. >>=20 >> Mike >=20 > --------------------------------------------------------- > 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
Steve Craig
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] Encryptng a password (2016)
WebCat B13 Mac CGI -- Frames question (1997)
Search anomaly aaarrgghh! (2000)
Choices (2000)
Help name our technology! I found it (1997)
Encrypt & SetHeader Length Problem (2000)
Too Much Rootbeer Free Offer (1997)
Logical and or in [hideif] (1997)
Installing 4.5 under 10.2 (2002)
New commands in Final candidate (1997)
2.1 release (1998)
[append] vs. [appendfile] delta + question? (1997)
WC TableGrinder (1997)
Building Calendars (1997)
Nested tags count question (1997)
Adding up line items. (2000)
form image (2000)
adding time (2003)
WebDNA hosting? ... (2004)
WebCatalog/Mac 2.1b2 New Features (1997)