Non English BW Upgrade

Hi Gurus,
Please share your experiences on -
When I am upgrading Non-English BW system ( from 3.x to3.5) what is special care if any should be taken or how is it different from normal BW (English) upgrade?
thanks
Vikash

Vikash
if u have started this upgradation project, i hope by now u might have revealed dificulty in reading the non-english scripts. U can use transaction like SE63 for translation and probably u will use english as your language and user will use his own official language, where SAP has provided language/login support.
Please look for some PDFs in Service.sap for non-english upgradation matter as this is quite normal as many of our indian consultants have worked on projects in other language like German, chinese, arabian, spanish etc. Probabaly sharing their experince will help a lot in this matter.

Similar Messages

Problem: Adding support for non-english charachter sets in UCCX 8.0

We have just moved from windows-based UCCX 7.0 to UCCX 8.0, the upgrade process went successfully so far, but for some reasons, Cisco Agents are experiencing problems displaying non-english charachter sets, everything was working fine prior to upgrading to the new version.
Is there a way to add support for these character sets?
Thanks in advance.

Hi Bala,
Follow the command. I believe that the space is normal.
This command can take significantly long time,
and can also effect the system wide IOWAIT on your system.
Continue (y/n)?y
Filesystem            Size Used Avail Use% Mounted on
/dev/sda6              90G   46G   41G 54% /common
8.0K    /var/log/inactive/
admin:
admin:
admin:show diskusage activelog
This command can take significantly long time,
and can also effect the system wide IOWAIT on your system.
Continue (y/n)?y
Filesystem            Size Used Avail Use% Mounted on
/dev/sda6              90G   46G   41G 54% /common
8.0K    /var/log/active/mgetty
0       /var/log/active/sa
4.0K    /var/log/active/platform/snmp/sappagt/sappagt.index
4.0K    /var/log/active/platform/snmp/sappagt/sappagt.log
4.0K    /var/log/active/platform/snmp/sappagt/startup.txt
16K     /var/log/active/platform/snmp/sappagt
4.0K    /var/log/active/platform/snmp/hostagt/hostagt.index
Thanks,
Wilson

Non-English fonts problems.

Hello guys,
I have a problem with non-English (well Cyrillic) font. I faced this problem 3 days ago when was working in iDVD trying to type text there. The problem is if I type in Russian with chosen font it does no appear as its english counterpart. I have tried many of them but it seems all of them (except may be two or three) work same (wrong) way. I have also checked them in other programms and got the same result. I have even checked this in Photoshop CS2 but... guess.. the same!
I have read lot's of topics but did not find a suitable solution for me although I used some of tips while working on the problem. For example I checked everything in System Preferences and Fonts folders. Everything is ticked/unticked there as appropriate.
Hope you'll give me a solution.
Thanks a lot!

Hello Tom,
thank you for your reply and for dealing with my problem. I am sorry for not being understandable. It may be because English is not my first language. I'll try to explain it in a different way. I was working on iDVD project and tried different fonts. As I was doing the project in both languages (English and Russian) because I wanted them to look the same. For English version I took Monotype Coursiva font (hope I spell right) as it was suitable to the whole theme of the project. When I typed with the same font in Russian it did not look like its English version but still readable (it is not the case of encoding problems when a text you have typed looks as the set of strange symbols). Then I tried Lucida Handwriting and oher having the same result. I have tried CY fonts as well but it was difference in appearence between letters and digits (I typed chapter names like this January 2007 and so on). Digits appeared different to russian letters, actually they were similar to English version.
I switched to Mac a year ago from Windows and absolutely love it. In Windows I mostly used Word and Power Point to work with text and did not have such problems (hope windows users are not reading this now).
I think it is related to Apple fonts because I noticed that all the applications share the same Font Book. I have tried different applications on my Mac in order to track the problem down and even Microsoft Office's Word for Mac which I use sometime was not able to do the job I requested. In other words I have same problem. May be my Font Book is not full? May be I need to update or upgrade it?
Thanks.
P.S. It's possible that my explanation is a bit complicated and you still cannot understand what the problem is. If so, would it be a good idea to send you some screenshots to be able to show you what I mean?
If answer is "yes" will you give me your e-mail, please?

Is Lightroom intentionally made difficult for non-English users?

Could it be that Lightroom is intentionally made difficult for the non-English user? I came to this forum today hoping to find an answer and all I see is problems when I try searching the forum, and complicated instructions on how to, supposdely, solve this issue. The issue I am facing has to do with localization, compatibility, interoperability and compliance. The problem is that I can't use many of the Lightroom shortcuts. Many of the ones that require the use of a modifier key on my keyboard just don't work. So what if I have a Swedish keyboard? Sweden is one of the most computer literate contries in the world, and Sweden has played a major role in the development of early computers and new technologies. Adobe has a presence in this country, and I'm quite sure Sweden is an important market for Adobe. So why not make Lightroom compatible with the Swedish keyboard? Why should I care to go through complicated instructions on how to hacktivate my keyboard by the means of editing config or script files? Why can't it just work out of the box?
I feel like this is intentional. Could it be that Lightroom users are only to be found in English speaking countries like USA, UK, New Zealand and Australia? I don't think so.
Swedish user:
http://forums.adobe.com/message/1459525#1459525
Swiss user:
http://forums.adobe.com/message/4375318#4375318
German user:
http://forums.adobe.com/message/3588746#3588746
http://forums.adobe.com/message/3817657#3817657
How about the ability to change keyboard shortcut bindings, i.e. custom shortcuts? I just found that this is not even possible in Lightroom! That explains why people take these strange measures and kludgy ways of making custom shortcuts in Lightroom. Changing shortcuts is often times tricky business because you have to change them in respect to other shortcuts. It's likely that one will have to change several keyboard shortcuts to avoid conflicts, etc. Lightroom needs a shortcut editor!
One should really not even have to change the default shortcuts, Adobe should choose some intelligent key combinations that make sense, and they should just work on any keyboard. I've tried changing the language from English to Swedish in Lightroom settings. The result of this is that nearly all shortcuts are changed to something else, so I would have to re-learn some of the shortcuts I have already learned using Lightroom in English, and of course this also changes the language of the interface which is not something I want. I will have to change my keyboard layout to English to make this work, or get a secondary keyboard, one with English layout. This is something I will only have to do when I work in Lightroom, because many of the professional programs that I use are working just fine with my keyboard. Perhaps Adobe can make the keyboard localization (shortcut maps) as an option, separate from the interface language setting? And for God sake integrate a keyboard shortcut editor for once!

Another Swiss user on Lightroom forums:
http://www.lightroomforums.net/showthread.php?6867-Flippy-Key-Using-Lightroom-in-english-w ith-a-non-english-keyboard-layout
I ended up removing the Keyboard Tamer plugin and then manually adding following strings to C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\en\TranslatedStrings.txt. This is by the way something that the Keyboard Tamer plugin does as well, because when I removed it I found two files named TranslatedStrings.txt in the Recycle Bin. The Keyboard Tamer is just supposed to save you the time and effort of manually manipulating these strings.
"$$$/AgLibrary/Menu/View/ZoomIn=Zoom In"
"$$$/AgLibrary/Menu/View/ZoomIn/Key=Cmd+."
"$$$/AgLibrary/Menu/View/ZoomInMinor=Slow Zoom In"
"$$$/AgLibrary/Menu/View/ZoomInMinor/Key=Cmd+Shift+."
"$$$/AgLibrary/Menu/View/ZoomOut=Zoom Out"
"$$$/AgLibrary/Menu/View/ZoomOut/Key=Cmd+-"
"$$$/AgLibrary/Menu/View/ZoomOutMinor=Slow Zoom Out"
"$$$/AgLibrary/Menu/View/ZoomOutMinor/Key=Cmd+Shift+-"
I found this thread helpful:
http://forums.adobe.com/message/1459525#1459525#1459525
I just replaced AgDevelop with AgLibrary. This of course only changes the key binding for Zoom In and Zoom Out in the Library module. Is there perhaps a document somewhere that explains the structure of the TranslatedStrings.txt file? There seems to be one of these files in each of the language specific folders under the Resources folder.
This file is known to be found in:
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources>dir /b /s TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\de\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\en\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\es\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\fr\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\it\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\ja\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\ko\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\nl\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\pt\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\sv\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\zh_cn\TranslatedStrings.txt
C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\zh_tw\TranslatedStrings.txt
I will study the structure of this file in Resources\sv\ and try to understand it. And as I find new "flaws" in the shortcut key bindings I will make new edits to the file I saved in Resources\en\ accordingly.
Here's an idea: those of you who don't mind re-learning all the shortcuts - the localized shortcuts for Swedish keyboards - simply copy the TranslatedStrings.txt file from C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\sv\ and paste it in C:\Program Files\Adobe\Adobe Photoshop Lightroom 4\Resources\en\. What this does it allows you to keep English as your interface language, but it changes the shortcut map to something that's more adopted for the Swedish keyboard layout. You get the same shortcut key bindings as the ones you see when you change the language to Swedish in the settings. But this way you are preventing Lightroom from changing the interface language.
Either that, or add new strings to an empty Resources\en\TranslatedStrings.txt file for each key binding you find to be broken and not compatible with your keyboard. This way you are only making changes to the key bindings that don't work very well for your keyboard, you are not chaning all of the shortcut key bindings. The other key bindings stay the same, the default key bindings found in the English version of Lightroom (or with English as language settings).
This is a way to adapt Lightroom for your own environment. But this is still too complicated and unncessary. A simple shortcut editor built into Lightroom would have solved this. But what are we going to do?... this is up to Adobe... Lightrooms have been complaining about the lack of a shortcut editor since at least Lightroom 2 and Adobe has not listened. So I don't expect to see this feature in the following years to come. It might just come along in maybe Lightroom version seven or something... but who cares?... At that time I might even ditch Lightroom altogether.
Ligthroom 5 upgrade...
I just found out that the new Lightroom 5 is not compatible with Windows Vista. I have the Vista Ultimate 64-bit on my desktop where I use Lightroom. This was not made very clear by Adobe. They simply state that Lightroom 5 works on Mac and on Windows. You have to read the fine print. I almost purchased the upgrade. I'm glad I didn't. I won't upgrade from Vista to Windows 7 just to run Lightroom 5! We, the early Windows Vista adapters, got screwed by Microsoft. Now, we are getting screwed by Adobe too! I see no reason not to support Windows Vista as it is pretty much the same system as Windows 7, and one would expect Adobe to support them both. I found a thread about it where one user asked why Vista was not supported and Adobe failed to give any explanation. They just silently dropped the OS support.
I guess they can do whatever they want. They are Adobe.
But I will not upgrade to Windows 7 because of Lightroom, so I won't upgrade to Lightroom 5. This is a great oppertunity for Phase One to strike with a good deal, such as a discounted migration upgrade for Capture One. I am sure many Lightroom 4 users would be happy to leave the Lightroom ship in favor of Capture One. At the end of life of Lightroom 4 I will probably just go to Capture One, even if I have to pay full price. At least they support Windows Vista.

HT201407 my Iphone stopped enabling none English keyboard and I can't unlock it

My iphone 3 was recently upgraded to OS 6.1
My daughter use a none english Keyboard for the passcode.
After connecting it for sync with I-tunes the none english keyboard option disappeared.
Would appriciate an advice.

It's not possible to update an iPhone 3G to iOS 6.1
If you locked yourself out your iPhone read here > http://support.apple.com/kb/HT1212

Non-English characters

Hello, I have read several times that since Java uses Unicode, it solves the problems of non-English characters automatically or something like that.
But my app is not working as expected. Would someone help please?
I have a client/server combo written in Java. The server can send messages in English or Japanese. The Japanese messages are hard-coded as String literals in the server source code. On the client side, they are displayed on a JEditorPane. But the Japanese characters are all garbled. The OS on the server side and client side are, of course, different.
My supposition, which is obviously wrong as it is not working, is that since both ends of communication are Java app, I need not worry about any encoding conversions for String literals.
Suggest me what is wrong here?

How is the required encoding/decoding supposed to be done?
When I didn't worry about non-English characters, I did the following, which WORKED.
// SENDER side
Socket socket ;
PrintWriter out = new PrintWriter(socket.getOutputStream(),true);
String outMessage = "my message";
out.println(outMessage);//RECEIVER
Socket socket ;
BufferedReader in = new BufferedReader(new InputStreamReader(socket.getInputStream()));
String inMessage = in.readLine();When non-English characters are involved, I did the following, which DID NOT WORK. Please someone correct me.
// SENDER side
Socket socket ;
PrintWriter out = new PrintWriter(socket.getOutputStream(),true);
String outMessage = "my message";
String utfString = new String(outMessage.getBytes(),"UTF-8");
out.println(utfString);//RECEIVER
Socket socket ;
InputStreamReader ins = new InputStreamReader(clientSocket.getInputStream(),"UTF-8");
BufferedReader in = new BufferedReader(ins);
String inMessage = in.readLine();The received message is still garbled.

Non-english character display as square box

Hi all,
I'm not very sure if this question should be asked here or in the JRE board, thus I'm trying here also
I have been trying an opensourced application called Alliancep2p (could be obtained from www.alliancep2p.com) using JRE 1.6 on an English Windows XP Pro machine.
The problem:
all chinese input are displayed as "square box". It looks like the programme "gets" the correct character, only that everything is displayed as "square box".
It looks like a font issue, though I'm not that sure. Is there anyway the default fonts could be changed, or to get the characters correctly displayed?
Note: I have east asian fonts installed, and the Java config panel can display chinese or other non-english characters correctly.
I tried the same application under GNU/Linux (locale is UTF-8) and chinese input/display correctly without any problem at all. Does it mean that it is not the problem of the application, or?
The original question in the JRE board:
http://forum.java.sun.com/thread.jspa?threadID=5265369&tstart=0
Thanks for all the input.

I'm not really sure if it's a problem of the application or not. But the fact that it works perfectly under Linux makes me think maybe it's not the problem of the program, and actually their developers said that unicode is being used all over the program and seems like they're not CJK users also.
I'm not a java guru so I can't really tell from the source if there's anything wrong.

Non English characters in FTP transport

Hi gurus,
I have this kind of problem: I need to create text file from internal table (table of 10000 charactes lines) , the file should be created in given ftp server (currently using FM FTP_R3_TO_SERVER).
But, and here is the problem, the text file contains some non English character (Czech to be specific) and after the file is created in ftp server the non English character are replaced by #, characters are fine in the table, even after creating the file on local system everything is fine.
I checked rfc connections, their are Unicode, file is sending in bin mode of ftp (ascii mode had no change, only acsii mode cuts the line to 256 character which is not enough) and parameter of fm FTP_R3_TO_SERVER character_mode is checked.
I will appreciate any help or "kick" in right direction.
Thanks
Martin

Hi Salehashaikh,
I'm not using the FM 'FTP_R3_TO_SERVER' any more to transfer the internal table to ftp, so I do not have the code. Sorry,
but i will try to answer the question.
when you are using function module 'FTP_R3_TO_SERVER' to transfer internal data to ftp the parameter fname should be the name or path of the file you are creating. If you only put file name there for example:
     CALL FUNCTION 'FTP_R3_TO_SERVER'
       EXPORTING
       handle = w_hdl
       fname = 'test_file.txt'
     character_mode = 'X'
this will create file test_file.txt in root directory on ftp.
You could also put there whole path on the ftp for example
      fname = '/directory/test_file.txt'
Other approach will be to change to the directory with function module 'FTP_COMMAND' with parameter command set to cd /directory/ code will look like this:
data: lv_command type string,
         lv_path type string.
constants: lc_change_dir type string value 'cd'.
*body of the program including calls of FM to connect to ftp
concatenate lc_change_dir lv_path into lv_command sepparated by space.
CALL FUNCTION 'FTP_COMMAND'               "this FM will execute any ftp command on ftp server
EXPORTING
   HANDLE                = lv_handle
    COMMAND               = lv_command
TABLES
    DATA                  = lt_result
CALL FUNCTION 'FTP_R3_TO_SERVER'
       EXPORTING
       handle = w_hdl
       fname = 'test_file.txt'
      character_mode = 'X'.
this "code" will create file test_file.txt in the ftp server on given directory from internal table passed to fm ftp_r3_to_server.
list of ftp commands could be found http://www.cs.colostate.edu/helpdocs/ftp.html
good explanation of ftp is here http://wiki.sdn.sap.com/wiki/display/Snippets/ABAPsolutiontoimplementFTP+transactions
I hope this is understandable and helps to solve your problem
Martin
Edited by: Martin Gabris on Feb 3, 2011 1:38 PM

Non english characters in DN cannot be retrieved

We are using Netscape directory server 4, protocal V3. We have a problem related to non-english characters appearing in RDN.
We publish to Ldap entries using the values from database. For example, we have pubulished an entry to Ldap, based on DB values, the entry should have a DN like: ou=Liege BELGIUM ... LGG1a, <other components of DN>. However, when we call netscape search API (search against uid attribute which does not have non-english characters), the search return the entry, but when further call getDN() method on the returned Ldap Entry, it only returns Li, instead of the complete DN value.
It seems the entry is corrupted in Ldap. I wanted to delete the corrupted entry and re create new one to test. I tried many ways, but none of them worked, I think it is because DN is corrupted, there is no key value to identify the Ldap entry for any operation(modify, delete).
You help and insights are much appreciated.
Thanks.
Han Shen

LDAP uses the UTF8 encoding. You must store data in the directory using the UTF8 encoding. This includes DN values. This also means that if you want to be able to view the values in your native character set and font, you must use an application that can convert the UTF8 LDAP data back to the native character encoding. The directory console by default should work for LATIN-1 (ISO 8859) languages if the LOCALE is set correctly.

Non English characters in BIP email

Hi, my report contains Japanese characters, when I view the output in HTML format. It is displayed properly. But when I click on send button , enter email parameters like to, cc, bcc, subject , etc and send it, in the mail I receive, the japanese characters are not getting displayed properly. The same problem occurs for spanish and portugese texts-in general to all non english characters. I am using Oracle Business Intelligence Publisher Release 10.1.3.4. If someone has faced a similar issue, kindly help. Thanks in advance

Suggestions
1) Try with NLS_LANG as
SWEDISH_SWEDEN.WE8DEC
2) Make a paramform and enter via paramform (unencoded)
(This is just for testing purpose)
3) Change machine locale to swedish and try
4) Which reports version is this ?
Please see
BUG 2713695 - NLS CHARACTERS FOR PARAMETERS CHANGE TO QUESTION MARKS WHEN PASSED ON URL BAR
Get in touch with Support to see if this is the issue and if "yes" get a one-off patch.
[    All Docs for all versions    ]
http://otn.oracle.com/documentation/reports.html
[     Publishing reports to web - 10G ]
http://download.oracle.com/docs/html/B10314_01/toc.htm (html)
http://download.oracle.com/docs/pdf/B10314_01.pdf (pdf)
[   Building reports - 10G ]
http://download.oracle.com/docs/pdf/B10602_01.pdf (pdf)
http://download.oracle.com/docs/html/B10602_01/toc.htm (html)
[   Forms Reports Integration whitepaper 9i ]
http://otn.oracle.com/products/forms/pdf/frm9isrw9i.pdf
---------------------------------------------------------------------------------

"Program files" directory problem during Microsoft Office Customization Installer in non-English versions of Windows

We have a document-level customization solution for Word and are experiencing problems during deployment in an environment running on terminal services. The OS (Windows 2012) is English and Word (2013) is non-English (German).
Installation is done into the "Program Files" folder correctly. But when trying to start a word document linked to the specific template. The "Microsoft Office Customization Installer" pops up with the error.
"There was an error during installation"
From: file:///C:/Programme/[CompanyName]/[Productname]/[Productname].vsto
Downloading file:///c:/Programme/[CompanyName]/[Productname]/[Productname].vsto did not succeed.
Exception: ....
System.Deployment.Application.DeploymentDonwloadException: Download file:///C:/Programme/[Companyname]/Productname]/[Productname].vsto did not suceed. ---> System.Net.WebException: Could not find a part of the path 'C:\Programme\[Companyname]\[Productname]\[Productname].vsto'.
---> System.Net.WebException: ...... ---> System.IO.DirectoyNotFoundException......
The problem seems to be that the installer is looking for C:\PROGRAMME instead of C:\PROGRAM FILES. C:\PROGAMME is the German localized name of PROGRAM FILES (http://en.wikipedia.org/wiki/Program_Files).
The installer installs the solution correctly deployed into c:\program files, but when the later a user tries to start it and the Microsoft Office Customization Installer is called, it tries to access the non-existing "c:\programme" folder. This
doesn't exist, because Windows is English.
Is there any thing related to deploying solutions on a platform which has different languages (mixing/matching of OS language and Office language?)
Thank you for your help

Hello,
1. First, I would confirm with you whether you dealt with the localization for your document-level add-in?
2. Did you use this way to define the Create a class that defines the post-deployment action part of Put the document of a solution
onto the end user's computer (document-level customizations only) and did you get the path with Environment.SpecialFolder enum?
To handle this, I would recommend you consider using Environment.SpecialFolder to set that property.
Regards,
Carl
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Oracle 10g - Defining the column name in Non English

Hi Experts,
I have an exisitng application which is developed on Windows using ASP Technology and uses Oracle 10g 10.1.0.2.0.
The application is supported with an instance of Data Base within which multiple tablespaces are created for different clients. The application is developed in such a way that some of the tables arecreated dynamically and the columns are named using the data entered through the UI.
This application needs to be globalized now. The problem is, the column name entered through the UI can be in any language based on the client's settings and those values in turn will be used for naming the columns in the tables.
1) Can I have the column names to be named using non english characters in Oracle 10g DB? If so,
1.1) what should I do to configure the exisiting Oracle instance to support it?
1.2) To what level is that configuration possible, is it per DB instance level (or) can it be done at Tablespace level. I would like to configure each tablespace to host tables with columns defined with different languages, say for example, tablespace 1 will have tables with Japaenese column names and tablespace 2 will have tables with German column names?
2) What should I do to make my entire DB to support unicode data i.e., to accept any language strings. Currently all strings are declared as VarChar2, should I change all VarChar2 to NVarChar2 (or) is there a way to retain the VarChar2 as is and make some database wide setting?
Please note that I do not have an option of retaining the column in English as per the Business Requirement.
Envionment:
OS - Windows 2003 32 bit
Oracle 10g 10.1.0.2.0
UI forms in ASP
TIA,
Prem

1. Yes, you can.
SQL> create table ÜÝÞ( ßàá number(10));
Table created.
SQL> insert into ÜÝÞ values (10);
1 row created.1.1 and 1.2 and 2. You can choose UTF as your default character set. It allows the user of non-English characters in VARCHAR columns in your whole database. It is not per tablespace.
SQL> create table ÜÝÞ( ßàá varchar2(100));
Table created.
SQL> insert into ÜÝÞ values ('âãäçìé');
1 row created.

English reviews in non English app stores

In the past it was possible to see the English / American reviews in non-English app stores. It would be more than nice to get that ability back. In small countries there are often not that many reviews and also English speaking people in non-English countries should be able to read reviews.

Are you referring to the Customer Reviews? iTunes doesn't distinguish which language is used by the customer in writing the review so it can't filter out those you don't want to see. In fact someone could write one review and use many languages in it, but it seems those that speak German are the most vocal in the Swiss store.
This is also a user forum. Responses are from other users of Apple products. It is mainly for other users helping you with a problem that they can fix. If you want to give feedback to Apple select Provide iTunes Feedback from the iTunes menu from within the iTunes application.

Non-English characters not displaying correctly - Serious Issue

My corporate email is on a Lotus Domino server with Lotus Traveler installed.
I have set my PlayBook (with OS 2) up to syncronize with the corporate email trough Active Sync (see http://alturl.com/qh3nn), which works perfectly.
I have however noticed that in some emails special non-english characters are displayed correctly but in some emails special non-english characters are displayed as a black diamond with a question mark inside.
This is of course a serious issue as most non English speaking countries use some special characters.
When trying to understand this problem how can I analyse the emails and see what character set is being used?
And of course better; has someone solved this?

I am having the same problem. Is there any update available?

Problem with Non-English Fields Output to PDF by JASPER in JDev10.1.3

I am using jsprx files(designed in i-report) to generate pdf reports out of an oracle database.
The non-English fields are shown correctly when I output the report into an HTML or when I view it with JasperView.
If I try making PDF files (JasperExportManager.exportReportToPdfFile) the static fields containing e.g.Arabic/Chineese characters won't be displayed and dynamic fields from the database with non-English contents will be shown as ??? or null.
I received some suggestions about using PARAMETERS to feed the report instead of FIELDS, which I think can not be helpful in this case and in general.
I think this should be a common problem. These are the components I am using:
itext-1.4.7. jar
commons-digester- 1.7.zip
jasperreports- 1.2.8.jar
Any comment or help is appreciated.
Thanks
Farbod

I am using jsprx files(designed in i-report) to generate pdf reports out of an oracle database.
The non-English fields are shown correctly when I output the report into an HTML or when I view it with JasperView.
If I try making PDF files (JasperExportManager.exportReportToPdfFile) the static fields containing e.g.Arabic/Chineese characters won't be displayed and dynamic fields from the database with non-English contents will be shown as ??? or null.
I received some suggestions about using PARAMETERS to feed the report instead of FIELDS, which I think can not be helpful in this case and in general.
I think this should be a common problem. These are the components I am using:
itext-1.4.7. jar
commons-digester- 1.7.zip
jasperreports- 1.2.8.jar
Any comment or help is appreciated.
Thanks
Farbod

Non English BW Upgrade

Similar Messages

Maybe you are looking for