Hi Yes, the problem with Eclipse was related to the Character set of the files. Because my files are stored on a Windows Server. And I can't save those files as UTF-8 because I have to change a lot of files, and also because those files will become incompatible with simple editors like notepad on the windows side :)
The best scenario for me should be that the files remain encoded with ISO 8859-1, and the server response were UTF-8. I tryed to do this, but I could not make this possible. This is why I have to change everything into ISO 8859-1. Dante On 6 mayo, 09:22, Andy Wu <[email protected]> wrote: > Dante, there are 2 encodings you should concern yourself with - the > encoding of the cfm file and the encoding of the response. > > What Marcel described in his email is in relation to the encoding of the > cfm file. The other ways that OpenBD determines the file encoding is by > looking for a cfprocessingdirective tag in the body of the cfm page, > then failing that it resorts to the default file encoding. That default > file encoding was set with the argument that you passed into Tomcat but > normally it defaults to the OS based default which in your case must not > have been ISO-8859-1. > > Note that the encoding that you changed in the bluedragon.xml is in > relation to the response. It need not match the encoding of the cfm file > and I'd certainly recommend leaving it as UTF-8 to be international > friendly. > > HTH > Andy > > Dante wrote: > > Hi > > > Today I resolved a problem with the enconding charset and I wish to > > share my experience to you. > > > I have an Open Blue Dragon installed with Tomcat 6.0 on Ubuntu 8.04. > > > The problem was that I can't view the latin characters like "á" or > > "ñ" on any .cfm page. > > > I changed the character encoding on the bluedragon.xml file to > > ISO-8859-1 without success. > > > If I called getPageContext().getResponse().getCharacterEncoding() I > > received "ISO-8859-1" > > > But I always saw "?" signs instead of the required characters. > > > So, I thinked that the problem was related with a Java issue (because > > I already had a similar fight in my Eclipse installation) :) > > > Basically the solution was to add a parameter into the java call to > > the Tomcat server. > > > Just edit the /etc/init.d/tomcat6.0 file and put > > > CATALINA_OPTS="$CATALINA_OPTS -Dfile.encoding=ISO8859_1" > > > before the following lines > > > # Define other required variables > > CATALINA_PID="$CATALINA_BASE/temp/$NAME.pid" > > > After this, just restart your Tomcat server :) > > > I read that this kind of changes can also be done in another file call > > "setenv.sh". If someone know about that, please tell me. > > > Dante > > --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
