bert db wrote: > I just found a solution, well sort of a hack. I found out that when I wrote > the "â¬" directly in a text field in the builder it prints okay (whichever > encoding I use (cp1252 or identity-H). I then isolated the value of the > character returned by the database for this sign ( 128 for the encoding iso > 8859-1, but for whatever reason it is 191 for the cp1252 (hex(80)= 191 ?? > ;-)) ) and transform all of these characters to the ⬠sign with a simple > replace.
there's no euro char in the iso-8859-1 (latin-1) charset, it came out well before the existence of the euro. the euro is found in iso-8859-15 (AKA latin-9, don't ask) where it's at decimal 164 codepoint or in unicode at decimal 8364. hex 80 *is* decimal 128. decimal 191 (hex BF) is an inverted question mark ¿ in windows-1252 (ditto for unicode). i suggest you front-to-back review your data entry process & make sure the encodings are all the same for every part of your app. also make sure that the oracle charset is exactly the same the cf ones, especially as oracle likes to name it's own charsets the same as ISO/IEC ones even though they are slightly different. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:313919 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
