> > Do you relly know that there is no 8859 encoding? > The standards go from ISO-8859-1 to ISO-8859-16 and you would need to > have collations for all of them and a way to let the user choose which > one is the right one for them (including regional variations). >
For me I just need the 8859-1. What I really need is a single byte storage because it is ease and simple to handle. 8859-1 is just the perfect choice among the all single byte encoding available. To clarify my requirements: I need SQLite to be lite working with accented characters. App and database (storage file) lite. Utf16 would be more simple than utf8 but I would get the database unnecessarily bloated. > There are so many things wrong with this kind of reasoning I prefer to > not say more. > It's a pity. You're helping a lot. > My guess is that you are assuming your text is ISO-8859-1 (commonly > called Latin-1). There are many problems with this, like for example > the fact ISO-8859-15 -- Latin-9 -- being the replacement, with the € > (euro) sign added, but Windows decided to invent it's own encoding and > it's "Latin" it's not exactly the same (the Euro sign is the symbol > which usually get's corrupted). > This is another problem that not affects me. Anyway, for me 8859-1 is not the requirement, but a single byte with latin accented character. 8859-1 just fit this requirement. > Don't assume a case insensitive match it's easy if done right. Read > about the Unicode collations and you will understand why -- there > doesn't exist a single generic upper/lower case function that works > for all. > Exactly! Using utf8 it's not ease. It could be simplified at the cost of the correctness. I don't need correctness. In fact I don't need multi byte, but I can do nothing to change this. SQLite is a multi byte database and I need to handle it with this constraint. What you stated it's a very important reason to a database not choose just one encoding (or tree counting with utf16be and le). One encoding doesn't works to all. > It's very easy to replace the SQLite functions with user-defined ones, > so if someone wants to go the easy way (partial support for just the > common western scripts) it's easy. And already done by many, if you > search the mailing list. > It's exactly what I'm looking for. It could be my mistake but I searched the list and I couldn't find it. If not asking too much, can you suggest better terms to use in my search? Many thanks. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
