[WebDNA] character encodings in linux

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 107304
interpreted = N
texte = Since I've begun to transfer sites over to my linux server, I've found = there's a few differences with the way WebDNA behaves compared to the = other OS's I've used. One of the important functions I was using was a character converter = that would remove special characters from strings to create web-friendly = urls. Now, special characters like =99(trademark) show up as those nice = black diamonds with question marks. =20 All of my files are UTF-8 LF encoded (created on a mac), and I'm using: [convertchars db=3D^xxx.db]Some Item=99 300 Series (10lb)[/convertchars]=20= to take a user-inputed, dbfield record value and convert it to: "some-item-300-series-10lb" This was previously hosted on a windows box, and nearly all files are = UTF-8 LF In a nutshell, what's the fastest route to regaining the same = functionality I had prior to the linux box? =20 Might changing the character encoding be all it requires? (there's a = lot of scripts and dbs!) Any advice on practices to improve compatibility for the future? Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] character encodings in linux (Tom Duke 2011)
  2. [WebDNA] character encodings in linux (aaronmichaelmusic@gmail.com 2011)
Since I've begun to transfer sites over to my linux server, I've found = there's a few differences with the way WebDNA behaves compared to the = other OS's I've used. One of the important functions I was using was a character converter = that would remove special characters from strings to create web-friendly = urls. Now, special characters like =99(trademark) show up as those nice = black diamonds with question marks. =20 All of my files are UTF-8 LF encoded (created on a mac), and I'm using: [convertchars db=3D^xxx.db]Some Item=99 300 Series (10lb)[/convertchars]=20= to take a user-inputed, dbfield record value and convert it to: "some-item-300-series-10lb" This was previously hosted on a windows box, and nearly all files are = UTF-8 LF In a nutshell, what's the fastest route to regaining the same = functionality I had prior to the linux box? =20 Might changing the character encoding be all it requires? (there's a = lot of scripts and dbs!) Any advice on practices to improve compatibility for the future? aaronmichaelmusic@gmail.com

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:

Ok here is a question? (1997) New One (for me).... Error type 12 (1999) Size limit for tmpl editor ? (1997) What does this error mean? (2000) Founditems Add/remove graphic display problem (1999) how do you and/or in a search? (1997) [WebDNA] v7 help (2012) carriage returns in data (1997) Reversed words (1997) Looking up two prices in database? (1997) OT: javascript help (2003) Resume Catalog ? (1997) OS X problem: when using [ShowCart] or [orderfile]... (2000) ColdFusion (2006) Math with Time (1997) READFILE command? (1998) SQL db type (2006) WebCatalog 2.1b4/Mac available (1997) Locking up with WebCatalog... (1997) Date field search needs ... (1998)