Character encoding in unix environment.

Hi,
Users try to download files from my application. These files are uploaded by others. They may contain characters from foreign languages as well. The file names are displayed properly on the screen, but when the user clicks on the link to download the file, the servlet set-up to read the file path is unable to read the file name on UNIX with jdk1.5.0_06. The same piece of code works perfectly well on windows with same jdk.
This is how i get the file name from the request:
String filePath = new String((httpRequest.getServletPath() + httpRequest.getPathInfo()).getBytes("ISO8859_1"), "UTF-8");
Same line of code throws out junk characters in unix.
Please advice
~sandeep

I would like to add that in the windows environment, the application is deployed on tomcat 5.x, but on the production (unix) machine, the request is routed through apache http server onto the tomcat server. Does this make any difference?

Similar Messages

Force same character encoding in UNIX as in Windows

My program reads a simple text file and outputs the same on the console. The file contains special characters like àéèéàöäül etc. The goal of this exercise is to make java recognize special characters both on the UNIX and on the Windows system in the same manner.
I wrote the program on a Windows machine and then transferred the class file to the UNIX system and ran it there. It is giving two different outputs for the different systems.
Here is the code
public class LocaleFile {
public static void main(String [] args ) throws IOException{
System.out.println("Deafult Locale :: "+Locale.getDefault());
System.out.println("Deafult Characterset :: "+Charset.defaultCharset());
System.out.println("Resetting defailt local to de_DE ... ");
Locale newLocale=new Locale(Locale.GERMAN.toString(), Locale.GERMANY.toString());
Locale.setDefault(newLocale);
System.out.println("After resetting Locale :: "+Locale.getDefault());
BufferedReader bufferedReader=new BufferedReader( new InputStreamReader( new FileInputStream("helloworld.txt"), "ISO-8859-15"));
String line=bufferedReader.readLine();
do{
System.out.println(line);
line=bufferedReader.readLine();
while(line!=null);
bufferedReader.close();
Windows Output
Deafult Locale :: de_CH
Deafult Characterset :: ISO-8859-1
Resetting defailt local to de_DE ...
After resetting Locale :: de_DE_DE
Character set 1: Arijit
Character set 2: è!éà£
Character set 3: ü?öä$
Character set 4: []{}
End of Test
UNIX Output
bash-3.00$ java LocaleFile
Deafult Locale :: en
Deafult Characterset :: US-ASCII
Resetting defailt local to de_DE ...
After resetting Locale :: de_DE_DE
Character set 1: Arijit
Character set 2: ?!???
Character set 3: ????$
Character set 4: []{}
End of Test
bash-3.00$
*Structure of helloworld.txt*
Character set 1: Arijit
Character set 2: è!éà£
Character set 3: ü?öä$
Character set 4: []{}
End of Test
Hope to hear from you soon guys.
Thanks
Arijit

gimbal2 wrote:
Just a thought, but I'd say that it is the character encoding of the command/bash prompt that is misleading you here. It probably actually has nothing to do with the code or the data, just the way the OS is displaying it.
edit: ninja'd by Baftos. :)*@gimbal2*
Well, thank you. That did raise a doubt. I changed the program slightly to write to a file say "recorded.txt" instead of printing it to the console.
Code
BufferedReader bufferedReader=new BufferedReader( new InputStreamReader( new FileInputStream("helloworld.txt"), "ISO-8859-15"));
BufferedWriter bufferedWriter=new BufferedWriter( new OutputStreamWriter(new FileOutputStream("recorded.txt")));
String line=bufferedReader.readLine();
do{
bufferedWriter.write(line.toString());
System.out.println(line);
line=bufferedReader.readLine();
while(line!=null);
bufferedReader.close();
bufferedWriter.close();
However the output remained the same

Character Encoding question

I'm helping another group out on this so I'm pretty new to this stuff so please go easy on me if I ask anything that is obvious.
We have a J2EE web application that is sitting on a Red Hat Linux box and is being served up by OAS 10.1.3. The application reads an xml file which contains the actual content of the page and then pulls in the navigation and metadata from other sources.
Everyone works as it should but there is one issue that has been ongoing for a while and we would like to close it off. In my content source xml file, I have encoded special characters such as é as & amp;#233; - when I view the web page all is well (I see the literal value of é but when I do a view source, I see & #233;
If I put & #233; into the source xml file, the page still displays with é but when I do a view source on the web page, I see literal é value in the source which is not what we want. What is decoding the character reference? While inserting & amp;#233; into the xml source file works, we do not want to have to encode everything that way we would prefer the have & #233;. Is it a setting of the OS, the Application Server or the Application itself?
When I previewed this post, I noticed that by typing & amp;#233; as one solid word, it gets decoded as is seen as é so I had to put a space between the & and the amp to get my properly explain myself.
Any help would be appreciated!
Thanks,
/HH

There are a lot of notes on MetaLink about character encoding. I wrote Note 337945.1 a while ago, which explains this into more detail. I will quote some relevant to your situation:
For the core components, there are three places to set NLS_LANG:
- in the system environment (this is obvious)
- in the file opmn.xml
- in the file apachectl
A. Changing opmn.xml
- go to $ORACLE_HOME/opmn/conf and edit the file opmn.xml
- Search for the OC4J container your application runs in.
- Within the <process-type.... > </process-type> section, add an entry similar to:
(1) OracleAS 10g (10.1.2, 10.1.3):
<environment>
<variable id="NLS_LANG" value="ENGLISH_UNITED KINGDOM.AL32UTF8"/>
</environment>
B. Changing apachectl (Unix only)
- Go to $ORACLE_HOME/Apache/Apache/bin
- Open the file 'apachectl'
- search for NLS_LANG
e.g.
NLS_LANG=${NLS_LANG=""}; export NLS_LANG
Verify if the variable is getting the correct value; this may depend on your environment and on the version of OracleAS. If necessary, change this line. In this example, the value from the environment is taken automatically.
There is more on this topic in the mod_plsql area but since you do not mention pulling data from the database, this may be less relevant. Otherwise you need to ensure the same NLS_LANG and character set is used in the database to avoid conversions.

Crystal Reports with Java in Unix Environment

We have Crystal Enterprise Professional Edition and Embedded Edition v10 with us.We want to use them for generating reports in our development project.
We have to generate reports as batch jobs ( scheduled jobs) for which we will have a Java Application running in Z/OS (Unix zSeries). This Java Application will connect to our database(DB2) and retrieve data which should be filled in the report design(template).
1.Can the .rpt file have the design alone(without the data from database).?
2.Can we fill the data from the database using the .rpt file in a Java Application using an API ?
3.Can we export this file(report with data) to a text file with a specific character encoding.?
All the above has to be done using a Java Application that will run in a Z/OS(Unix Environment).
4.Is Java API for the above operations available as a .jar file that can be included in our classpath in UNIX Environment ?
I request you all to help me with these queries as soon as possible.
Million Thanks in Advance.

Hi,
It seems that you are having issue with Crystal reports Java SDK's.
Post your question in Java Development - Crystal Reports forum.
That forum is monitored by qualified technicians and you will get a faster response there. Also, all Java Development queries remain in one place and thus can be easily searched in one place.
Thank you for your understanding
Amit
Edited by: Amit Singh on Dec 2, 2008 2:55 PM

Writing to file with specific encoding in unix

hi,
I want to write html files which contain Turkish characters in unix operating system.
I'm currently using FileWriter to write the files.
I'm getting the file content from the database and I can see that the characters seem to be fine but when I write them into an html file, they are displayed with the question mark character (?).
What can I do about this?
Thanks

FileWriter uses the default character encoding of whatever platform your program is running on. Beside the fact that the default encoding may vary from one machine to another, it may not be suitable for storing non-ASCII (Turkish) characters.
Rather than using FileWriter, you can use an OutputStreamWriter and a FileOutputStream, which allows you to specify the character encoding you want. UTF-8 is generally a good choice, since it can encode just about anything. For example:FileOutputStream fos = new FileOutputStream("/some/file/name");
OutputStreamWriter osw = new OutputStreamWriter(fos, "utf-8");
osw.write("your text with Turkish characters...");Geoff

Wrong character encoding from flash to mysql

Hi, im experiencing problems with character encoding not
functioning correctly when sending from flash to mysql. What i am
doing is doing a contact form in flash which then sends the value
to a php file which takes the values and inserts them into a table.
As i'm using icelandic charecters i need the char encoding to be
either latin1 or utf8 in mysql, or at least i think so. But it
seems that flash or the php document isn't sending in the same
format as i have selected in mysql because all special icelandic
characters come scrambled in the mysql table. Firefox tells me
tough that the html document containing the flash movie is using
utf-8.

I don't know anything about Icelandic characters, but Flash
generally really likes UTF-8. So it should be sending that if that
is what it is starting with.
You aren't using any kind of useCodePage? That will mess it
up.
Are you sure that the input method is Icelandic?
In the testing environment can you list variables (from the
debug menu) and see if they look proper? If they do then Flash is
readying them correctly and the problem must be coming in further
down stream.

How to set the system default file character encoding to UTF-8?

Hi all. This is driving me nuts, on both my Windows box and Snow Leopard; I figure much more chance of finding the answer for OS X.
My language and locale are set to Australian English. $LANG=en_AU.UTF-8
However, as I believe is expected, OS X (and Windows for that matter) will create files by default with character encoding of Cp1252 (Latin-1). That is, the FILE encoding in the file metadata - the Byte Order Mark I believe. The file itself, not the characters written to it.
This, in a word, bites. I don't want to be restricted to only ASCII by default, and it is causing me problems with certain software (a Firefox plugin) that creates text files, passing in UTF-8 encoded content, which is then mangled because the file encoding itself is still Cp1252. (I know, I've tested this by changing the file encoding manually and having it overwritten again by the plugin: works correctly.)
As a simple example, just `touch somefile` from terminal creates a file in Cp1252 -- I'm obtaining that info by opening in jEdit by the way (anyone know of something better?).
In other locales that are not English-based, I believe the default file encoding is UTF-8. But surely this can be controlled independently? There must be a system configuration value somewhere that specifies file encoding default. Can someone please tell me what it is?
Thanks!

However, as I believe is expected, OS X (and Windows for that matter) will create files by default with character encoding of Cp1252 (Latin-1). That is, the FILE encoding in the file metadata - the Byte Order Mark I believe. The file itself, not the characters written to it.
Apps like TextEdit and Mail have settings that let you determine the encoding of text produced. The default would normally depend on the character content of the file, ranging from ASCII for basic English to Windows Latin-1 (Win 1252) or ISO Latin -1 (ISO 8859-1) to UTF-8 for other content.
Win 1252 is not ASCII, but has twice the number of characters in the latter.
Byte Order Mark is something totally different --it's a particular character used to signal certain encodings.
http://en.wikipedia.org/wiki/Byteordermark
As a simple example, just `touch somefile` from terminal creates a file in Cp1252 -- I'm obtaining that info by opening in jEdit by the way (anyone know of something better?).
For what Terminal does and how to change it, it might best to post in the Unix forum:
http://discussions.apple.com/forum.jspa?forumID=735
For problems with a FireFox plugin, it might be good to ask on their own forums as well.

Character encoding again

Hi, i havent got any answer so i try to ask again...
I have created a page from Data Controls.
I have created parameter form. And table. Detail is showed at the bottom of page (there is shown current row through #bindings. . .
Everything works fine when i fill something into parameter form table is filtered by that criteria, when current row is changed, the detail is also changed. But when i fill some czech character into parametr form it works pretty bad.
The table is correctly filtered but when i make any other action after filtering, the table shows no rows.
I found what cause this problem. It is the Property in bindings that holds value for this parameter. When i first call bindings.findXXX.execute the Propertys value is "č" for example. That is correct and table shows filtered rows. After i perform another action (i think it is not dependent what the action is, but change current row fow example) the value in that Property has changed to "?" instead of "č" and because of this filter is applied again and table shows no rows. I have checked all encoding and character encoding is set to utf-8. Is this the problem and i miss some settings ?
1) menu tools-preferences-Environment
2) project properties- compiler-character encoding
3) in jspx
<?xml version='1.0' encoding='UTF-8'?>
<jsp:directive.page contentType="text/html;charset=UTF-8"
pageEncoding="UTF-8"/>
<afh:head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</afh:head>
is there other ? i dont know i set this settings long ago ...
Please if someone know, give me some hint , thanks for help.
Jdeveloper 10.1.3.0.4(SU5)

check regional language settings on your machiner where u r application server is running. I faced this problem but was able to resolve by modifying the
NLS_LANG = AMERICAN_AMERICA.WE8ISO8859P1
NLS_LANG is under HKEY_LOCAL_MACHINE==>ORACLE
WE8ISO8859P1 is the standard encoding for my application developed in local indian language and works fine for me
THIS can help check out
Amit

Could not deploy my project in unix environment

I am using windows for development environment, my code was deploying fine in windows environment. But when i tried to deploy in unix environment I got this error
bpel_IRobo_Workflow1_1.0.jar failed to deploy.
Error while loading process. The process domain encountered the following errors while loading the process "IRobo_Workflow1" (revision "1.0"): BPEL validation failed. BPEL source validation failed, the errors are: [Error ORABPEL-10902]: compilation failed [Description]: in "bpel.xml", XML parsing failed because "undefined part element. In WSDL at "file:/u01/app/oracle/product/AS10.1.3.3.0/bpel/domains/default/tmp/.bpel_IRobo_Workflow1_1.0_e580208857197172fe72bbfca5d9d8b6.tmp/workflow2.wsdl", message part element "{http://schemas.xmlsoap.org/ws/2003/03/addressing}RelatesTo" is not defined in any of the schemas. Please make sure the spelling of the element QName is correct and the WSDL import is complete. ". [Potential fix]: n/a. . . If you have installed a patch to the server, please check that the bpelcClasspath domain property includes the patch classes.
Can any one knidly help. I have to fix this thing in a day so any help would be of great use thanks

bpel.xml
<?xml version = '1.0' encoding = 'UTF-8'?>
<BPELSuitcase>
<BPELProcess id="IRobo_Workflow1" src="IRobo_Workflow1.bpel">
<partnerLinkBindings>
<partnerLinkBinding name="client">
<property name="wsdlLocation">IRobo_Workflow1.wsdl</property>
</partnerLinkBinding>
<partnerLinkBinding name="combtecbsnk03NetworkInstallationsService">
<property name="wsdlLocation">combtecbsnk03NetworkInstallationsServiceRef.wsdl</property>
</partnerLinkBinding>
<partnerLinkBinding name="fr_pots_dj_schedule">
<property name="wsdlLocation">fr_pots_dj_schedule.wsdl</property>
<property name="retryInterval">60</property>
</partnerLinkBinding>
<partnerLinkBinding name="fr_staa_response">
<property name="wsdlLocation">fr_staa_response.wsdl</property>
<property name="retryInterval">60</property>
</partnerLinkBinding>
<partnerLinkBinding name="fr_jumper_info">
<property name="wsdlLocation">fr_jumper_info.wsdl</property>
<property name="retryInterval">60</property>
</partnerLinkBinding>
<partnerLinkBinding name="eet_mismatch_correction">
<property name="wsdlLocation">eet_mismatch_correction.wsdl</property>
<property name="retryInterval">60</property>
</partnerLinkBinding>
<partnerLinkBinding name="TaskService">
<property name="wsdlLocation">TaskServiceWSIF.wsdl</property>
</partnerLinkBinding>
<partnerLinkBinding name="IRobo_Workflow2">
<property name="wsdlLocation">workflow2.wsdl</property>
</partnerLinkBinding>
</partnerLinkBindings>
</BPELProcess>
</BPELSuitcase>
Workflow2 WSDL
<?xml version="1.0" encoding="UTF-8"?>
<definitions
name="IRobo_Workflow2"
targetNamespace="http://xmlns.oracle.com/IRobo_Workflow2"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://xmlns.oracle.com/IRobo_Workflow2"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:client="http://xmlns.oracle.com/IRobo_Workflow2">
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/IRobo_Workflow2" schemaLocation="IRobo_Workflow2.xsd"/>
</schema>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://01hw127125.India.TCS.com:8888/orabpel/xmllib/ws-addressing.xsd"/>
</schema>
</types>
<message name="IRobo_Workflow2ResponseMessage">
<part name="payload" element="tns:IRobo_Workflow2ProcessResponse"/>
</message>
<message name="IRobo_Workflow2RequestMessage">
<part name="payload" element="tns:IRobo_Workflow2ProcessRequest"/>
</message>
<message name="WSARelatesToHeader">
<part name="RelatesTo" element="wsa:RelatesTo"/>
</message>
<message name="WSAReplyToHeader">
<part name="ReplyTo" element="wsa:ReplyTo"/>
</message>
<message name="WSAMessageIDHeader">
<part name="MessageID" element="wsa:MessageID"/>
</message>
<portType name="IRobo_Workflow2Callback">
<operation name="onResult">
<input message="tns:IRobo_Workflow2ResponseMessage"/>
</operation>
</portType>
<portType name="IRobo_Workflow2">
<operation name="initiate">
<input message="tns:IRobo_Workflow2RequestMessage"/>
</operation>
</portType>
<binding name="IRobo_Workflow2CallbackBinding" type="tns:IRobo_Workflow2Callback">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="onResult">
<soap:operation style="document" soapAction="onResult"/>
<input>
<soap:header message="tns:WSARelatesToHeader" part="RelatesTo" use="literal" encodingStyle=""/>
<soap:body use="literal"/>
</input>
</operation>
</binding>
<binding name="IRobo_Workflow2Binding" type="tns:IRobo_Workflow2">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="initiate">
<soap:operation style="document" soapAction="initiate"/>
<input>
<soap:header message="tns:WSAReplyToHeader" part="ReplyTo" use="literal" encodingStyle=""/>
<soap:header message="tns:WSAMessageIDHeader" part="MessageID" use="literal" encodingStyle=""/>
<soap:body use="literal"/>
</input>
</operation>
</binding>
<service name="IRobo_Workflow2CallbackService">
<port name="IRobo_Workflow2CallbackPort" binding="tns:IRobo_Workflow2CallbackBinding">
<soap:address location="http://set.by.caller"/>
</port>
</service>
<service name="IRobo_Workflow2">
<port name="IRobo_Workflow2Port" binding="tns:IRobo_Workflow2Binding">
<soap:address location="http://01hw127125.India.TCS.com:8888/orabpel/default/IRobo_Workflow2/1.0"/>
</port>
</service>
<plnk:partnerLinkType name="IRobo_Workflow2">
<plnk:role name="IRobo_Workflow2Provider">
<plnk:portType name="tns:IRobo_Workflow2"/>
</plnk:role>
<plnk:role name="IRobo_Workflow2Requester">
<plnk:portType name="tns:IRobo_Workflow2Callback"/>
</plnk:role>
</plnk:partnerLinkType>
</definitions>
James I am making the endpoint reference available at run time so I think I need not change it while deploying.I think this is the problem the problem.
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://01hw127125.India.TCS.com:8888/orabpel/xmllib/ws-addressing.xsd"/>
</schema>

Wrong character encoding in error messages

The Java compiler can be adjusted to source file encoding with the option javac -encoding ...
The Java runtime can be adjusted to terminal encoding with java -Dfile.encoding=...
While this appears somehow inconsistent, it works and can be used e.g. when running the tools from Cygwin (the POSIX layer on Windows) which uses UTF-8 by default, while Java, following the Windows mechanism, uses some other character encoding by default (this works more seemlessly on Unix/Linux, by the way).
Now if I compile UTF-8 source with non-ASCII characters, and there is an error message related to them, the error message printed to the console will not be UTF-8 encoded, resulting in mangled text output.
(Arguably, source and terminal encoding could be different, but then there is no option available to the compiler to adjust this;
it does not accept -Dfile.encoding=....)
Example: Error message looks like this:
FM.java:1: error: class, interface, or enum expected
b▒h
While the string is actually "bäh" in the source.
This is a bug. Any proper place to actually report a bug?
Edited by: 994195 on 15-Mar-2013 09:42

I'll ignore you just blatantly assuming it is a bug because you say so, you did not think to type "java report bug" into Google?

How to use the character encoding model to use ' �' in java

hi
I have to use the special characters like '�' using java.but when '�' character is transferred to data base or is displayed in my form,it is shown as '?'.but i need to display the original characters in the form of what it is.
what can i do as i expects the result .i needs it very urgently.so reply to me as soon as possible.
advance thank you
rgds
Oasisdeserts

Java stores all characters as 16 bit UNICODE (which has plenty of room far more exotic characters than Greek). Every time character data is brought into, or stored from the Java environment it passes through a specific character encoding. If you don't state the encoding explicitly it uses the default encoding of the machine it's running on (which is typically oriented to the language set in the locale.).
With a database the database driver is supposed to do any necessary translation. The non-latin character could be stored wrongly, the database could be returning it wrongly or whatever's creating your form could be interpretting it wrongly, or lack the capacity to display the character.
If it's, say, a JSP try setting the page encoding to UTF-8. Try dumping the characters read from the database in HEX and look them up at www.unicode.org.
Take a look at the database setup information, some have an option of storing characters as UNICODE or ASCII.
The "?" is substituted whenever a codec can't make sense of the codes it's translating, either the byte array is invalid or the UNICODE character can't be represented.

Problem using character encoding....

Hi,
I have written an app which constructs an email and sends it to subscribers. The data is read from the database (oracle 9) and its running on UNIX.
The subject title (read from the email) however does not appear correctly in the email. I think the encoding character set is incorrect.
When my subject title (a string) is:
test � $
i get something like this
test =?ANSI_X3.4-1968?Q?
I checked and the data is stored correctly in the database.
So i changed my method which reads the subject title from the database to:
for (int i = 0; i < o.length; i++) {
strArray[i] = new String(((String) o).getBytes(), "ISO-8859-1");
which basically changes the character encoding to ISO-8859-1 for the text. But now in the subject title i get
test $��
(the � shouldnt be there)
Any ideas? Which character set should i use?

You should use the character set that the database uses. Looks like it could be UTF-8.

Autonomy Character Encoding

I'm sorry if this is not the right place to ask, but it seems to be the less inappropriate place XD
I'm working with the Search Engine that is shipped with WebLogic Portal(Autonomy Idol), and I'm having some problems with character encoding, in the server where the Autonomy installation is running I have no access to the Internet so I cannot run the spider to search any website... so I ran a spider into my computer and It worked fine... then I exported the INDEXED data into an idx file which I uploaded into the production server and then I indexed, the problem is that some characters aren't shown correctly in my portlet, executing an action command such as /action=query&text=something_here I can see that the generated xml has this wrong characters, so definitely this is not a problem with my porltet, executing the same action in my local autonomy installation everything goes well so the questions are...
Why Autonomy is not indexing correctly the special characters into my production environment?? and
Why it happens only with some of them? for example the word Ingeniería is indexed correctly in some entries and not in some others, and both entries comes from the same idx file
Thanks in advance
P.S

Sorry, in the example I gave, the none-english letters looks like this:
&# 1490;&# 1497;&# 1488;(I made the space between the # and the number delibertly to prevent it from being presented as a letter ...).

Upload a file from unix environment

hi
does anybody know which fm to use to upload a file from unix environment?
anjali

hi sia,
try this.
parameters: p_file like rlgrap-filename obligatory
default '/usr/sap/upload.xls'.
types: begin of t_data,
vbeln like vbap-vbeln,
posnr like vbap-posnr,
matnr like vbap-matnr,
werks like vbap-werks,
megne like vbap-zmeng,
end of t_data.
data: it_data type standard table of t_data,
wa_data type t_data.
open dataset p_file for output in text mode encoding default.
if sy-subrc ne 0.
write:/ 'Unable to open file:', p_file.
else.
do.
read dataset p_file into wa_data.
if sy-subrc ne 0.
exit.
else.
append wa_data to it_data.
endif.
enddo.
close dataset p_file.
endif.
rgds
anver

Why does Firefox 18 ignore the specified character encoding for websites?

We are developing a page on our website that will have the page crawled and a newsletter generated and sent out to a mailing list. Many email packages default to character encoding of iso-8859-1 so we have set our character encoding to this on the page via the standard meta tag.
We have a problem on the newsletters that we had until now been unsuccessful to replicate. Though now I know why.... I have just discovered that in Firefox 18, the specified character encoding is being completely ignored. It is rendering the page in UTF-8 even though we specified ISO-8859-1. Firefox 3.6 however, renders the page with the proper encoding (thank god for keeping an old version for testing).
Can anyone explain why the new Firefox is completely ignoring the meta tag? Both browsers are using the factory default (I even opened FF18 in safe mode)...

Thanks for letting me know that Firefox 18 ignores everything but the server headers... but it doesn't help me much. Our website is in UFT-8... but this page is a newsletter, one that is crawled and saved into an email and sent out to a mailing list (by a third party newsletter program) and many email readers use ISO-8859-1 hence why we want to have the page rendered in that encoding so that we can actually test the newsletter properly. We can't test through the third party software as our testing environment is behind a firewall, and you can't change the server headers for a single page... hence the meta tag.
If you explicitly choose to render a page in a specific encoding, that shouldn't be ignored by the browser. It's not a big deal, but now every time we make a code change in our test environment and reload the page we have to force the encoding manually in the browser which is a pain.
The problem is, the newsletter is already live and we have some users complaining because some characters aren't displaying properly in their email packages (Entourage for Mac is one of them), all our testing (which is encoding using UTF-8) looks fine.

Character encoding in unix environment.

Similar Messages

Maybe you are looking for