Help with French Accent Characters Corrupted

Hi, All.
I am developing a Flex Front end connect with Java back-end.
The back-end sends data retrieved from XML file to the Flex
front-end; displays it in an TextArea, and allow user to change.
After user changes the data, hit "Save" button, then Flex sends the
data to the back-end.
I check with the back-end, make sure the data was correct
when sending out to Flex, and the French accented characters gets
corrupted when sending back from Flex. However, in Flex side, this
change cannot be awared. (i.e. The French accents characters
display correctly in Flex, but sending wrong character back). I'm
guessing that might be something related to character sets.
However, I cannot find anywhere to set character sets in
HTTPService. Anybody has idea?

Use Ariel MS Unicode font.

Similar Messages

Problem loading Image data with French accent in file name

We have a very complex commercial application that has been working perfectly in English for over a year. We have now localized it to French and Spanish, and discovered a serious show-stopping problem. We need help fast, with the scheduled release being less than 2 weeks away...!
We iterate over a folder to find all the images in it, then display those in a user window. The code for loading the images is:
            for each (var name:String in filenames){
                var image:SmoothImageTransformable = new SmoothImageTransformable();
                var imagePath:String = dir + "/" + name;
                image.source = imagePath;
                trace("Adding Item to picture carousel with url " + image.source);
                image.data = {directory:dir, filename:name};
                image.isDragEnabled = true;
                image.setStyle("horizontalCenter", 0);
                image.setStyle("verticalCenter", 0);
                _images.push(image);
Our SmoothImageTransformable class is an internal class that inherits from Image. This all works fine for image names like 'myFavoritePhoto', 'test', 'photo346', etc. However, it fails to load the data if the file name is something like 'caméra' Any name with a UTF-8 character causes the data load to fail.
To be sure we weren't doing a load somewhere else in the code that I had overlooked, I added a "image.autoLoad = false' line in there. That did exactly as expected -- all image squares then show a grey blank, with no image shown. Removing that line (reverting to the original code, as shown above) causes all the images to work perfectly, except for those with French accent characters like the é.
HELP! Is this a known bug? Is there some additional setting I need to make it understand the extended character set? I can't find any mention about this at all in the documentation.

@markerline:
We have a fix! Almost... I don't understand one aspect of what I am seeing though.
We have one test file named "camèra.jpg" that is an example of what I am unable to load into an Image. I decided to examine the character codes at each letter, and this is what Flex has as the string:
name = cam?ra.jpg
   [0] = c; 0x99
   [1] = a; 0x97
   [2] = m; 0x109
   [3] = ?; 0x232
   [4] = r; 0x114
   [5] = a; 0x97
   [6] = .; 0x46
   [7] = j; 0x106
   [8] = p; 0x112
   [9] = g; 0x103
Note that the è prints as gibberish in the trace statement, and shows a numeric encoding of 0x232. According to
     http://docstore.mik.ua/orelly/web2/action/appb_01.htm
The unicode equivalent of Latin1 for è is 0xE8, which is equivalent to 0x232. That implies that the string is already Latin1, which I would think would mean that Windoze would recognize the file name and open it properly -- but it does not.
I then tried taking the "camèra.jpg" string, pasting it into NotePad++ in a UTF8 document, then telling NotePad++ to display as ASCII. The result is "camÃ¨ra". I then tried just forcing the file name within Flex to this new mangled string. The result then is:
MAGIC name = camèra
   [0] = c; 0x99
   [1] = a; 0x97
   [2] = m; 0x109
   [3] = ?; 0x195
   [4] = ?; 0x168
   [5] = r; 0x114
   [6] = a; 0x97
   [7] = .; 0x46
   [8] = j; 0x106
   [9] = p; 0x112
[10] = g; 0x103
Note this time the trace statement looks proper. More important, the IMAGE DOES LOAD! (Our display of the name to the user now looks like crap, but that just means I need to modify our class to have a separate 'name' property, rather than extracting it from the 'image.source')
So... my remaining question -- what encoding did I just do through that NotePad++ incantation? That site I quoted above said that it was already Latin1, which is what I thought I was trying to get to. I clearly need to write a method to map from incoming (UTF8 I thought, but maybe Latin1?) to Windows file system (Latin1 I thought, but maybe ASCII).
In other words, I am not sure what charcter set to come from or go to... It turns out the code was already in the character set I had been trying to go to (which is why it wasn't working) and the set I seem to need to go to is not the one I thought...

Transfer/Reply to emails with french special characters - BB 9360

Hi,
I've got a problem when I reply/transfer to mails with french special characters (such as "é" "è" "ç" etc..) => all the special characters are replaced with strange characters such as chinese letters or others.
No problem when I send an email with those same characters, it appears only when transfer or reply and only on special characters contained in the original mail I transfer/reply to.
is there a way to solve this issue?
thanks

while pressing the 'e' key, scroll your trackball side to side, you will find the various e variations.
You can do that with most keys to get special characters.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

French accented characters in a barcode are being dropped when scanned by a handheld scanner

We have an issue when our pdf417 barcodes contain french accented characters é,à,è, etc and are scanned by a handheld scanner. As a result Montréal is decoded as Montral (the é is dropped). We are using the Datalogic PowerScan 7000 and a Motorola Symbol DS6608 handheld scanners. We currently have a ticket open with Datalogic.
The problem does not exist when the barcode is decoded by LC Barocded Forms.Decode.
Talking to someone, they indicated that this is pretty common with handhelds. However, I did find this old post from lee sutton http://forums.adobe.com/thread/332743 where he uses a keyboard wedge?
Has anyone had to deal with a similar issue (non-english chars) via handheld?
Can anyone recommend a handheld that does read non-eng characters without the wedge?
Is there something in the encoding from Designer that i can do?

When you're decoding with the hand-held scanner, you'll need to ensure that the decoder itself supports the scanning of extended characters AND if it's a keyboard-wedge scanner, ensure that your keyboard is in French or Canadian-French mode or the simulated typing won't happen.

ITunesU - Tags name with french accents (é,è,à,ê,...)

Every time I try to upload files in iTunesU with french accent in the tag, I found after the upload some characters I never write in the tags.
For example, if the name of the artist is «Hélène David» after the upload the name in tags is «Hélène DavidTS». I do not understand why the letters «TS» appear in the name.
Samething happen if I write in the tag Name «L'intégrité à l'Université de Montréal : pour une vraie réussite» after the upload the new name is «L'intégrité à l'Université de Montréal : pour une vraie réussiteTALB». Same problem with the the name of the album. I wrote «Les grandes conférences du CEFES» and this text appear in the tag «Les grandes conférences du CEFEST».
How to fix this problem ?

You might want to ask in a forum specific to the Forefront server.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Iweb with french accents.

Hi all, I'm using the great IWeb in french... I have found that when i create a new page with french accents IWEB creates a stange file name , but when this new web page have no french accents the name becomes ok. My Os X 10.4.8 is in french and my Iweb is in french to. By the way i'm not from France . I am from Québec Canada. I say that because we do not use the same keyboard configuration nor the same french language.
The question is , Is this phenomenone normal or is there something i can do to correct it.
My version of IWEB is 1.1.2 wish, i think, is the latest version of the product.
Thank in advance.
Mac Book Mac OS X (10.4.8) processor 1.83 GHz Intel Core Duo

It's a known issue. Anytime you use characters outside the plain alphanumeric characters, iWeb will generate a more complex address and corresponding file/folder names. It may be as simple as replacing the characters with their hex/ascii codes or you may get a string of random characters.
My iWeb 2.0 wish is that we are allowed to make pagenames that are separate from the URLs. That would do away with some of the constraints like you describe in naming your page correctly and still having valid and legal URLs.

Access denied - Password with french accent

hello,
we meet a problem of access via ActiveSync
on our mobile phone for people with
a password with french accents.
the connection is no longer.
to access our CAS server, we go through
a Forefront server registered
DMZ. If we do not go
through this Forefront server, the problem
disappears ...
Anyone have any ideas??
thank you in advance to all!

Hi,
We need your detailed information, do you use TMG or FPE? it sounds like the TMG has published your server.
Do you see any error information?
Best Regards
Quan Gu

Muse and the beyond annoying and awkward menus help with French titles with accents that don't work?

I am doing a French/English site. The only way I can do this is do two sites and then do creative linking. That sucks. Go Live allowed me to have as many pages as I wanted and Menu Machine worked pretty decently as it allowed me to have different menus so a bilingual site was a piece of cake. Now I have to do two different sites and the problem is some of the page names in french have accents as needed in that language. The village idiots at adobe did not take that into account and now of couse I have an issue and will need to create navigation for the french elsewhere and import as a graphic. This is beyond stupid. Anybody have a solution. Adobe told me too bad so sad the software is in its' infancy. Well then why the hell did they get rid of Golive which worked well for designers. Because Muse is so dumbed down I am not able to do anything about the menus as the menus are dictated by the page names. If you decide to do a manual menu you can not have just words with state changes as the bloody menus sytem will not allow that. The design requires just the words having state changes this is not abnormal. REALLY. I am beyond frustrated and pissed off and equally pissed off Adobe hangs us out to dry not even having phone contact just some dudes in Inia on the chat which sucked. Any solutions? Anybody at Adobe actually understand this is a problem and might suggest it will be fixed in updates but in the meantime help me solve th eproblem easily. I can live without stupid scrolling I would rather have solid software that is easy to use and some degree of fleixibility if you are a seasoned designer who does a lot of web. But dumbed down for the folks who just want to do a simple site. Yikes this is frustrating. Any help would be appreciated.

Village idiot here, apparently...
In Page Properties you can independently set the page name (used in menu widgets), the page title (displayed in the browser tab) and the file name for the .html file for the page.
To create a menu where only the appearance of the text change across states:
1) select a menu item
2) select each state in the State panel and click the trash can to clear all pre-existing state-specific formating
3) choose the Normal state and set all the text formatting that will be the same across all states
4) select mouse down, roll over or active state
4) set the text properties you want for that state in the Text Panel
5) repeat for the other two states
6) you may want to set the fill and stroke on the menu item Normal state to none, so only the text of the menu items is visible
The automatic "All Pages" and "Top Level" pages menu functionality is currently limited to being site-wide, so for the multi-lingual site you describe your choices are to have one automatic and one manual menu, two manual menus, or create two sites. It depends on the size of your site, the complexity of your menu and your personal preference which is best for your case.
If accents are not being preserved through your workflow, please share:
1) URL for an example page that demonstrates mangled accents
2) How you're uploading your site? Publish to BC? File > Upload to FTP Host? Export and external FTP client?
3) If you're not hosting with Adobe (BC), who's your hosting provider.
If accents are not being preserved that generally indicates a problem with how the files are being transferred to the server and/or a problem with how the server is configured. The output of Muse fully supports accented characters throughout the workflow.
Many members of the user community are active here, along with the technical support team and several members of the development team, like myself. We generally respond most effectively to clear questions with screenshots, URLs of example page, etc.
There are a lot of tutorials, videos, templates, widgets, etc. available online from Adobe and other sources:
http://muse.adobe.com
http://lynda.com
http://muse-themes.com
http://musegrid.com
http://qooqee.com
http://muselayers.com
http://museresources.com
http://museworld.com
etc.

French accented characters not translated during decodeIncomingMessage

Hello,
Our b2b.log displays the correct French syntax during the decryption process after receiving message from our partner.
"oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:decryptAndVerify Enter"
example = È
But the French characters translate to ? during the
"oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:decodeIncomingMessage" and
"oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:getPayload"
I tried setting a unix environment variable on the B2B server NLS_LANG=CANADIAN FRENCH_CANADA.WE8MSWIN1252
But this did not help.
Should I also ask the NLS_LANG be set on the database server?
thanks in advance,
Ken

Hello Anuj,
It takes awhile to arrange a change configuration with our IT section and arrange a test message with our partner.
But we did arrange a test a few minutes ago.
The b2b_2.log tip.properties reads as:
-bash-3.00$ grep encoding tip.properties
oracle.tip.adapter.b2b.encoding=ISO-8859-1
#oracle.tip.adapter.b2b.encoding=Cp1252
#oracle.tip.adapter.b2b.encoding=UTF-8
But the b2b.log contains:
-bash-3.00$ grep encoding b2b_2.log
<?xml version="1.0" encoding="utf-8" ?>
2009.10.30 at 15:27:23:186: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.callout.B2BCalloutHandler:processIncomingCallout payload after callout: <?xml version = '1.0' encoding = 'UTF-8'?>
2009.10.30 at 15:27:23:358: Thread-13: Repository - (INFORMATION) BIND VARS = (7720B238D6E7808EE0430AFA0B04808E-11-1, 11, 1, N, , 1070, clob, <?xml version = '1.0' encoding = 'UTF-8'?>
<?xml version="1.0" encoding="utf-8" ?>
<?xml version="1.0" encoding="utf-8" ?>
2009.10.30 at 15:30:59:311: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.callout.B2BCalloutHandler:processIncomingCallout payload after callout: <?xml version = '1.0' encoding = 'UTF-8'?>
2009.10.30 at 15:30:59:368: Thread-13: Repository - (INFORMATION) BIND VARS = (7720B238D6F2808EE0430AFA0B04808E-11-1, 11, 1, N, , 1070, clob, <?xml version = '1.0' encoding = 'UTF-8'?>
<?xml version="1.0" *encoding="utf-8"* ?>
Does this indicate that the encoding did not take effect?
Do we need to remove the commented lines in the tip.properties file?
The accented characters translated to ? in this test (in b2b.log)
thanks
Ken

Problems with Greek accented characters

After the update to AIR 2.0.2 I cannot input into any application greek with accented characters.
Tried TweetDeck and Twhirl and neither work (used to before the update)
Is this a bug or it needs some configuration
I am working on Fedora13 but heard the same problem reported on Ubuntu.
Have not tried on MS Windows or MacOSX

Hi,
I'm using Adobe AIR 2.0.3 on Windows machine. I wrote an app in Aptana Studio (build: 2.0.5.1278522500) with ExtJS library and I found the problem with polish national characters like ż and Ż (all the other national characters like ą, ę, ń are possible to input).
In order to reproduce, here you have the sample code in ExtJS:
http://dev.sencha.com/deploy/dev/examples/form/anchoring.html
As you will see - it is possible to input ż and Ż in text fields.
Now, use the same code to build AIR applicaton and then run the application. It is not possible to input those characters in Air window. Right Alt+z acts like undo operation - it removes last entered text. All the other characters work fine.
Here is the code I used:
<html>
    <head>
        <title>New Adobe AIR Project</title>
        <link rel="stylesheet" type="text/css" href="lib/ext/resources/css/ext-all.css" />
        <link rel="stylesheet" type="text/css" href="lib/ext/air/resources/ext-air.css" />
        <script type="text/javascript" src="lib/air/AIRAliases.js"></script>
        <script type="text/javascript" src="lib/ext/adapter/ext/ext-base.js"></script>
           <script type="text/javascript" src="lib/ext/ext-all.js"></script>
        <script type="text/javascript" src="lib/ext/air/ext-air.js"></script>
        <script type="text/javascript">
        Ext.onReady(function(){
    var form = new Ext.form.FormPanel({
        baseCls: 'x-plain',
        labelWidth: 55,
        defaultType: 'textfield',
        items: [{
            fieldLabel: 'Send To',
            name: 'to',
            anchor:'100%' // anchor width by percentage
            fieldLabel: 'Subject',
            name: 'subject',
            anchor: '100%' // anchor width by percentage
            xtype: 'textarea',
            hideLabel: true,
            name: 'msg',
            anchor: '100% -53' // anchor width by percentage and height by raw adjustment
    var window = new Ext.Window({
        title: 'Resize Me',
        width: 500,
        height:300,
        minWidth: 300,
        minHeight: 200,
        layout: 'fit',
        plain:true,
        bodyStyle:'padding:5px;',
        buttonAlign:'center',
        items: form,
        buttons: [{
            text: 'Send'
            text: 'Cancel'
    window.show();
        </script>
    </head>
    <body>
    </body>
</html>
Is it possible to input those characters or is there a workaround for this (disable undo operation or so) ?
I really appreciate any help.
Kind regards,
Marcin.

Web Service response from XMLA (using BW SAP) returns french Accent characters as question marks '?'

I am using .Net Framework 4 C# web service project.
I am connecting with XMLA service (using as web reference) in my C# project. The issue seems to be able to handle the French characters once i am getting response back from the XMLA execute method.
At this moment the data is coming back as '??' whenever it contains french special characters.
I am pasting the code below and would appreciate help at earliest.
sapqasbwi.MsXmlAnalysis _sMxlA = new sapqasbwi.MsXmlAnalysis(); // Create XMLA reference object.
System.Net.NetworkCredential _nc = new System.Net.NetworkCredential(); // Creating Network credentials object
_nc.UserName = userid;
_nc.Password = _password;
_sMxlA.Credentials = _nc.GetCredential(new System.Uri(url), "Basic");
_sMxlA.Url = url;
sapqasbwi.ExecuteCommand cmd = new sapqasbwi.ExecuteCommand();
cmd.Statement = stText; // sText contains the query
_bwPropertyList.DataSourceInfo = "default";
_bwPropertyList.Format = "Tabular";
_bwPropertyList.AxisFormat = "ClusterFormat";
_bwPropertyList.Content = "SchemaData";
_bwParameters.PropertyList = _bwPropertyList;
_sMxlA.RequestEncoding = System.Text.Encoding.GetEncoding("ISO-8859-1"); // already tried utf 8
//Execute BW Query
System.Xml.XmlElement returnXML;
returnXML = _sMxlA.Execute(cmd, _bwParameters); // Execute method only returns an XML element object.
This particular object is containing the '??' whenever a french character is found
The output i am receiving is as follows
<MainServiceAndStatuses>
<MainService>Entreposage ?? long terme</MainService>
<MainServiceStatus>Service Termin??</MainServiceStatus>
<TransactionID>1000006216_10_Cde client standard</TransactionID>
</MainServiceAndStatuses

Hi
Can you please send me the direct link for C# forum, i cannot find it on this forum.
thank
TheNauman

How to import a csv with French accents in it ?

Hello to all,
It's been a while that everytime I import a participant csv in Adobe Connect, if I have French accents (example : é, è, ô...), the name imported with the accents comes out with white on black questions marks at the place of the original accentuated letter.
I have tried different methods to conturn this : using Notepad++ with UTF8 with or without BOM, OEM863 (French)... Nothing seems to do the trick.
Would anyone know how to do this in a import without having to go all through the procedure of either creating my participants manually or changing manually the names after the import, please ?
Thank you very much for your help !
Abigail

I am working on this same issue and doing some small tests. I have saves my file as Unicode text (txt) and that seems to solve the issue with accents not saving. I will need to try larger files.

Problems with input accented characters after moving JInitiator to JDK 1.5

After upgrading from JInitiator 1.3.1.18 to JDK 1.5.0_06 (jdk plugin in IE), the input of accented characters (in our case portuguese) isn't working anymore in text areas on the forms (Forms 10g).
So, if you push first the "´" key and then the "a" key, you should get as result "á" (worked correctly with JInitiator), but after upgrading to JDK 1.5 you will get simply a letter "a".
Pressing Alt + 160 shows correctly "á".
Somebody can give a clue about this problem please?
Downgrading again to JInitiator is no option for us, as we need a more modern JVM (for a Dicom viewer applet we developed), and IE crashes if you have an Oracle form running with JInitiator, and then try to open another IE page with an applet requesting JVM 1.5 ...
Thanks a lot for your comments.
Alberto A.Smulders
HostDat Lda. - Portugal

In IE, the server must be in the Trusted Sites list & the security for Trusted Sites set to low
Tools -> Internet Options
Security Tab
Sites button
Add all Forms servers, or use a wildcard to get your entire domain. If you are not using SSL, uncheck the "Require server verification (https:) for all sites in this zone"
Set the Security Level for this zone to Low. If the slider bar is not there, click the Default Level button, then slide the security setting to low.

Problem with French accents

Hi,
I'm using B2B to transform HL7 v2.x messages from text to xml. The messages include many French accents and are misinterpreted by B2B. Is there a way to set the character set in an HL7 over MLLP setup?

Thanks Ramesh,
There is no BPEL involved at this point. Did you mean the xsd file generated by EDIfecs? It does actually contain the UTF-8 encoding. As for the ecs file, I would not know how to ensure the encoding:
<?xml version="1.0" encoding="UTF-8"?>

<xsd:schema xmlns="urn:oracle:integration:b2b:361B7F53AD2940EB92FB9BBD2424389B" targetNamespace="urn:oracle:integration:b2b:361B7F53AD2940EB92FB9BBD2424389B" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="1.0" elementFormDefault="qualified">
<xsd:element name="OUL_R21" type="OUL_R21.CONTENT"/>
<xsd:complexType name="OUL_R21.CONTENT">
<xsd:annotation>
Thanks,
Francois

Interactive report : issue with french special characters

Hi,
We have many interactive reports and we can't use any french special characters in the filter clauses. For example, Montréal becomes montrÃ©al.
What parameters do we have to change to make it work?
Thanks.

I found the answer in this thread : Interactive Report Character Set Issue

Help with French Accent Characters Corrupted

Similar Messages

Maybe you are looking for