Turkish characters display '#'

Hi,
I am having a problem with the BEx Analyzer tool. I want to display Turkish characters correctly when running the report but I notice there is a '#' symbol for a specific turkish character (I with a dot on the top).
It's represented correctly in SAP BW when I view the master data text values. It is even displayed correctly when I execute the report via the web interface. The only problem is the BEx Analyzer tool.
Is this a regional setting for laptops? Does Microsoft have some support for BEx so that it can display all Turkish characters correctly? Does SAP have some additional language support for BEx Analyzer?

Hi,
will be displayed for Characteristcs when there is no data...if diplay properties of characteristic are set to 'key'.
if display propety is 'Text',then 'not assigned' will be displayed instead of #.
don't want to display # ?
regards
Message was edited by: C C

Similar Messages

Upgarded Oracle database works incorrect with Turkish Characters

Hi All,
I have upgarded my database from oracle version 7.3 to 8.0.6.
My new database in oracle 8.0.6 works incorrect with Turkish Characters, displays incorrect.
I tried creating new oracle database in oracle 8.0.6, not upgrading as above, this database works well with Turkish Characters.
Please help me to fix above problem in my upgraded database.
Thanks in advance.
Thuong Tran.
null

Use Ariel MS Unicode font.

CR4Ev2 problem exporting to PDF containing Turkish characters

I know there are other threads with similar topics but I also know some people get irritated when people jump onto their threads with their own problems.
I am using CR4Ev2 and on my machine which I have installed Eclipse on I have no problems
exporting my reports to PDF, I have Turkish characters which display perfectly (they did not with
CR4Ev1 so thanks so much for that)
I have now exported my project as a WAR file and am trying to run it on another machine with the same
Tomcat and Java versions.
If I view the report via the CrystalReport Viewer the Turkish characters display with no hassel.
But if I try export the report to PDF all the Turksh characters now display as ?, (as they did in CR4Ev1)
Am I missing something, is there something that I am not including in my project that I need
when exporting the PDF.
I have installed Adobe Reader 9 on this new machine incase the Turkish langauge fonts were not in
my version 8, but still get funny ? characters, I even installed the Turksih version of Adobe 9 and still nothing. Is there some other files that I could have installed on my Eclipse machine that I have not installed
on the second machine.
I have tried both the following commands to export to PDF
CRJavaHelper.exportPDF(clientDoc, response, true);
and
CRJavaHelper.exportPDF(clientDoc, response, false);
both dont work.
I have also tried the following (which I used before with CR4Ev1)
ByteArrayInputStream byteArrayInputStream = (ByteArrayInputStream)clientDoc.getPrintOutputController().export(ReportExportFormat.PDF);
writeToFileSystem(byteArrayInputStream, EXPORT_OUTPUT); // EXPORT_OUTPUT = "c:\test.pdf"
private void writeToFileSystem(ByteArrayInputStream byteArrayInputStream, String exportFile) throws Exception {
          //Use the Java I/O libraries to write the exported content to the file system.
          byte byteArray[] = new byte[byteArrayInputStream.available()];
          //Create a new file that will contain the exported result.
          File file = new File(exportFile);
          FileOutputStream fileOutputStream = new FileOutputStream(file);
          ByteArrayOutputStream byteArrayOutputStream = new ByteArrayOutputStream(byteArrayInputStream.available());
          int x = byteArrayInputStream.read(byteArray, 0, byteArrayInputStream.available());
          byteArrayOutputStream.write(byteArray, 0, x);
          byteArrayOutputStream.writeTo(fileOutputStream);
          //Close streams.
          byteArrayInputStream.close();
          byteArrayOutputStream.close();
          fileOutputStream.close();
But that also does not work.
Please can someone tell me what they think I am missing.
Oh, another note with the CRJavaHelper.exportPDF(clientDoc, response, false); command
It does work but I do get the following error in my console (both the Eclipse machine and the new one).
org.apache.jasper.JasperException: java.lang.IllegalStateException: getOutputStream() has already been called for this response
06-Feb-2009 15:06:52 org.apache.catalina.core.ApplicationDispatcher invoke
SEVERE: Servlet.service() for servlet jsp threw exception
java.lang.IllegalStateException: getOutputStream() has already been called for this response
     at org.apache.catalina.connector.Response.getWriter(Response.java:610)
     at org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:198)
     at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:125)
     at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:118)
     at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:188)
     at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:118)
     at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:77)
     at org.apache.jsp.Report_002dviewer_jsp._jspService(Report_002dviewer_jsp.java:263)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:374)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:630)
     at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:436)
     at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:374)
     at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:302)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
     at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
     at java.lang.Thread.run(Thread.java:619)
But as I said it seems to work fine apart from the Turkish character issue on the new machine)
Is this part of the problem or a seperate issue??
Thanks all for looking at this.
Darren

Ted,
I have double checked the Java version and infact reinstalled jdk6u7 (multilanguage version) just to be
100% sure, but that did not help.
ON my Eclipse machine the Fonts are as follows
Verdana(Embedded Subset)
     Type: TrueType
     Encoding: Built-In
but on the other machine it is different
Verdana
    Type: TrueType
    Encoding: Ansi
    Actual Font: Verdana
    Actual Font Type: TrueType
So that does appear to be the problem, but the question is what controls this?
As I said the project is exactly the same (same WAR file) so what I have done differently or what am I
missing in the new enviroment.
I set the "Text file encoding" for the whole project to UTF-8 before I exported the project (in Eclipse)
but that didnt help. I even set the properties of each report to UTF-8.
I am sure I am missing something simple.
The only other difference is Im running XP Pro on Eclipse machine but W2KSP4 on the other, but
surely that is not the issue.
Cheers
Darren

Problems with Turkish characters not displaying correctly

A user is having problems with certain Turkish characters in particular fonts not displaying correctly (as shown below).
The two fonts (Gill Sans and Helvetica LT CondensedLight) are used for English language marketing material. Ideally, for continuity, the same font would be preferred for our Turkish language marketing material rather than changing it to a similar font.
Helvetica LT CondensedLight
Turkish character “ İ ” does not display correctly in either Word or InDesign.
Gill Sans
Turkish characters “ ş ” and “ ğ ” display correctly in Word but not InDesign.
My questions are:
1. For Gill Sans, why are the characters not displaying in InDesign but are in Word?
2. I've noticed here: http://www.webtype.com/font/gill-sans-family/#glyphs-tab that the required characters are available within the Gill Sans font. Is this because the font is newer and includes the additional characters? Would this work in InDesign?

One of the big differences between InDesign and Word is that Word will happily substitute glyphs without telling you. So, unless your installs of Word and of InDesign are using different versions of Gill Sans (which is possible, BTW) then your s-with-cedilla and your g-with-macron are actually not in Gill Sans but in some other font. I'm guessing Arial.
It's possible that you have more than one Gill Sans installed (e.g. one in your Document Fonts folder and another in your system fonts folder) that have different glyph complements. Gill Sans has been around a long time, and the version I have from the 90s has no Turkish support whatsoever.
As far as the capital-I-with-dot, you can check your glyph coverage in a variety of ways. In both InDesign and Word, you can open up a window that shows you all of the glyphs in a font. In InDesign, find it in Type -> Glyphs. In Word, it's called "Insert Symbol" and you can find it in Word 2010 by going to Insert -> Symbol -> More Symbols. I am guessing that the answer to this question is simply that your cut of Helvetica LT has no cap-I-with-dot. You'd need to pick a font that actually has support for Turkish. On WIndows, I use a very full-featured freebie called BabelMap to check font coverage. They have a Web version here:
http://www.babelstone.co.uk/Unicode/babelmap.html
but I personally prefer the downloadable .exe file.

PDF Output Not Displaying Turkish Characters

Hi,
We've configured BI 7.0 System with an Standalone Portal+BI Java System running both on SP11 Stack without problem.
For BI Web Reports, we're taking PDF Outputs and getting Turkish Character Problems. On the screen we can see everything correct, even Excel Export displays Turkish Characters without problem but PDF Export is wrong. I've checked the "<b>Note 1007116 - Form output in incorrect language</b>" but not sure whcih form to check? And also if this is the problem?
If anyone can help us, it'll be great

Hi Ade,
I tried all possible combinations of fetching the data. Writing a PL/SQL function and assigning the data to placeholder in before report trigger. Also, tried to use a query and then assign the data to placeholder through formula column. Directly assigining the database column on field without using placeholder.
While trying all the above options, I ensured that width is set to 4000 characters.
But all in vain. It works fine for 2000 characters but not able to print 4000 characters.
Regards,
Mitiksha

Error in display of Turkish Characters in BEx Report

Hi Experts,
I am facing an issue while running one of reports in BEx in place of Turkish Characters i am getting #.whereas same report if run over Web is giving Turkish characters showing "I" in place of #.
Please provide any pointers on this.
Thanks
Nilesh

As mentioned above - check the OSS notes - this problem is one of the main reasons for upgrading a BEx front end to 7 or moving to the web
However there is a workaround - you can broadcast queries in xls format and email them - this gets around the problem - but no user interaction is possible and you cannot format the xls (is you wanted to format the xls you would use the precalc service but this then would turn the characters back into #)

Printing Turkish Characters in SAP Script Form

Hi I want to print a Form where I need to Print Turkish characters from Database. Its Print Preview is coming absolutely right but there is some problem while printing. I shows # symbol in places of Turkish Characters. I have checked the printer and drivers and they are absolutely fine. Printer is printing other documents in Turkish Language but not the form. System has Turkish fonts installed. Kindly help. Thanks in advance.

Hi
See this OSS note for your problem
OSS Note: 776507
Symptom
Documents printed via SAPscript or SmartForms do not print with correct special characters, e.g. ### prints instead of Japanese or Russian characters. What to do?
Other terms
SAPscript, SmartForms, printing, device types, OTF
Reason and Prerequisites
Help required to choose proper fonts in a SAPscript or SmartForm
Solution
When using SAPscript or SmartForms to print (or email or fax) a form from a business application, many factors influence the outcome of the actual text within the form. All these factors must be checked in order to ensure a correct printout:
1) The language version of the form used to produce the printout.
Example: If you want to print a French invoice, you need to have a FR version of your SAPscript or SmartForms invoice form RVINVOICE01. And the application program must specify the corresponding language key (FR) when calling the SAPscript or SmartForms API.
2) The font selections specified in the form (possibly also in a SAPscript style or SmartStyle used in a form).
Example: In a SAPscript form or a SmartStyle you need to specify HELVE if you want to print German text in Helvetica (or similar) font. If you want to print Japanese text, HELVE is not a valid choice but you need to specify a Japanese font like JPMINCHO in your Japanese form.
3) The output character set of the device type
Every printer in transaction SPAD has a "device type" assigned. Device types used by the spooler for printing support only one single specific output character set. All text from the form has to be converted (using SAP's built-in character conversion mechanism) to this output character set.
A character set can typically support either a single language (e.g. Shift-JIS which supports only Japanese) or a set of languages (e.g. ISO 8859-1, which supports Western-European languages). It is possible that a given language (such as German) can be supported by several output character sets, e.g. you may use either ISO 8895-1 (Latin-1) or ISO 8859-2 (Latin-2) to represent German text. This is so because both character sets contain the special characters used in German.
Example: HPLJ4000 is a HP LaserJet device type supporting the ISO 8859-1 (Latin-1) character set. ISO 8859-1 can be used to represent e.g. Dutch, English, French, German, Spanish, Swedish but NOT Russian or Japanese.
As a consequence, it is ok to use HPLJ4000 to print English, German French etc. but not for Japanese or Russian.
4) The set of available printer fonts for a given device type
When formatting a document, SAPscript and SmartForms perform an automatic mapping of the font definitions in the form (e.g. "HELVE 14 point bold") and the available printer fonts of the device type. A replacement printer font is chosen, should the specified font selection not be available in the device type. Now this replacement can be problematic if a language-specific font, such as Chinese CNSONG, is specified in a form and it gets replaced by a font which does not support this language, e.g. COURIER.
To solve this problem, font families in SE73 have language attribute assigned, e.g. some fonts are characterized as being suitable only for certain languages. And when a replacement has to be chosen because the original font from the form is not available in the device type, a replacement font is chosen which has the same language attributes.
If no fonts for the language in question exist in the device type, the resulting font will not be able to print the special characters and you will see "wrong" output characters in the printout.
Note on SAPscript/SmartForms Print Preview:
The OTF Print Preview available in Windows GUI (e.g. from transaction SP01) will sometimes not show the "wrong" characters which appear on the final printout. Here is the reason: since the Print Preview runs in Windows environment, it will use Windows fonts to represent the actual printer fonts. A Windows font typically has more available characters (i.e. covers more character sets) than are actually available in a printer's resident font.
A typical example where the Print Preview will differ from the printout is here: if you have a Chinese PCL5 printer such as CNHPLJ4 and use the Western Latin font COURIER in your document, the print preview will show you Chinese characters if you (by accident) tried to format Chinese characters in COURIER font. This is because Windows will automatically choose a font that can output Chinese characters (which is actually not Courier). But when you print the job on an actual PCL5 printer with resident Western and Chinese fonts, the Courier font will not print any Chinese characters but Western special characters instead, because the printer's resident Courier font does not include Chinese characters.
Rule of thumb: all Asian device types (e.g. CNHPLJ4, JPHPLJ4, JPPOST, KPHPLJ4) support not only Asian fonts but also COURIER, HELVE and TIMES fonts. But these Latin fonts can only be used to print English text, not Chinese/Japanese/Korean characters.
Which fonts are suitable for a given language?
Language(s):            Font family to use in a form:
Latin-1 (Western Europe/Americas) *******
DE,EN,FR,ES,NL,SV       COURIER, HELVE, TIMES
                        (LETGOTH, LNPRINT)
Latin-2 (Central Europe) ****************
PL, CZ                  COURIER, HELVE, TIMES
ISO 8859-4 (Baltic) *********************
ET, LT, LV              COURIER, HELVE, TIMES
ISO 8859-5 (Cyrillic) *******************
BG, RU, SR, UK          COURCYR, HELVCYR, TIMECYR
ISO 8859-7 (Greek) **********************
EL                      COUR_I7, HELV_I7, TIME_I7
ISO 8859-8 (Hebrew) *********************
HE                      COURIER, HELVE, TIMES
ISO 8859-9 (Turkish) ********************
TR                      COURIER, HELVE, TIMES
Simplified Chinese **********************
ZH                      CNHEI, CNKAI, CNSONG
Japanese ********************************
JA                      JPMINCHO, DBMINCHO, DBGOTHIC
Korean **********************************
KP                      KPBATANG, KPDODUM, KPGULIM
                        KPGUNGSE, KPSAMMUL
Traditional Chinese *********************
ZF                      TWDPHEI, TWMING, TWSONG
Thai ************************************
TH                      THANGSAN, THDRAFT, THVIJIT
Arabic (Unicode systems only) ***********
AR                      ANDALE_J
Verify your output by examining the OTF data
When analysing printing problems of this type, be sure to check the OTF data which gets produced by SAPscript or SmartForms. OTF or "Output Text Format" is the intermediate page-description format generated from SAPscript or SmartForms. OTF will contain the final printer font names and character set/language identifiers which help to solve the problem. OTF will even name the form and the language of the form used to create the output.
The easiest way to do this is to create a spool request from your application, run transaction SP01, use menu
Goto->Display Requests->Settings
and choose
Display Mode: Raw
Now display your spool request. If this is a SAPscript or SmartForms spool request, you will see OTF data. Each line represents one OTF command, every command starts with a 2-character cmd identifier and possibly some cmd parameters follow.
Here is an excerpt from a sample OTF file where we highlight the most interesting commands:
//XHPLJ8000    0700 00000000001
IN04EALEXTEST_ZEBRA
IN05%PAGE1
OPDINA4 P 144 240 1683811906000010000100001
IN06%WINDOW2
MT0024401289
CP11000000E
FCHELVE 120 00109XSF100SF101110000067E X
UL +0000000000000
SW00067
CT00000000
ST0453037Dieses SF hat Stil ALEXTEST_ZEBRA mit
The 1st line with the // (Control) command reveals the device type usedto print: HPLJ8000
//XHPLJ8000    0700 00000000001
The 2nd line (IN = Info command) shows the name and (internal 1-char)language key of the form:
IN04EALEXTEST_ZEBRA
In this case it is the English (E = EN) SmartForm ALEXTEST_ZEBRA
The OP-line (OP = Open Page) gives the page format used in the form, it is DINA4 Portrait orientation:
OPDINA4 P 144 240 1683811906000010000100001
The CP (CodePage) cmd shows the SAP system codepage used to code the text and the active language. In our case it is codepage 1100 and language E = EN = English.
CP11000000E
Finally, the FC-cmd (Font Call) lists a printer font selected within SmartForms. Please note that every SmartForm has a designated default SmartStyle under "Form Attributes->Output Options". In addition, every text node can have a SmartStyle attached (which will override the definitions from the default style for the text). In our case the resulting printer font that was selected is HELVE 12.0 pt bold-off, italic-off.
FCHELVE   120 00109XSF100SF101110000067E X
Header Data
Release Status: Released for Customer
Released on: 22.08.2005 09:57:20
Priority: Recommendations/additional info
Category: Customizing
Primary Component: BC-CCM-PRN Print and Output Management
Secondary Components: BC-SRV-SCR SAPscript
BC-SRV-SSF Smart Forms
<b>
Reward points for useful Answers</b>
Regards
Anji

Turkish Character - Display Problem

Hi,
Recently we upgraded our systems, ECC 6.0 from 4.7, and now using Integrated ITS with NetWeaver 2004. Eventhough turkish characters like "ş ğ ı" was correctly displayed in early version, standalone ITS 6.20, when we included charset=UTF-8 or charset=ISO-8859-9 in the meta tag of the file, in new version Explorer 7.0 cannot display same turkish characters.
Without these characters the words become unreadable,
Waiting for your comments and help,
Best Regards.
Utku Ates

Hello Utku,
it sounds as you have changed a file to include those charset attributes into a meta tag in ITS 6.20. Can you tell me what file did you change?
However, I would expect the WebAS to insert the correct charset based on the login language automatically. Do you have a tool to watch the HTTP protocol? What charset is set, if any, in the HTTP header?
With best regards,
T. J. Domsalla

Reg: Turkish characters issue on BW 3.10 Bex level and RSRT

Hi,
We are facing the same problem with the turkish characters, Our system is BW 3.10 (3.30 Cont) and ECC 6.0. The turkish characters are displaying correctly at the table level, but not at the RSRT or the Bex level.
The turkish characters are displaying correctly at the table, RSRT and Bex level if we load the same record from the Non-unicode Prod system to the Non-unicode BW Dev system, but if we load from the unicode QA system the same record is not displaying correctly.
Has anybody got a solution for this issue
thanks
Kalyan

Hi,
Yes, we installed transport request, which came with Integration Kit in our BW System.
We are also facing another issue,
ISSUE 2:
We have another publication with oracle DataSource , where we need to publish report(personalized) for 200 users.
Even we configured dedicated processing server for that publication and setting maximum no of connection to 250, it is throwing error like maximum no of concurrent connection reached.
Previously it was working with just 50 connections.
Now we are running this report by setting max no of connection to 500, and doing service restart after each publication.
Otherwise next publication will throw same error again.
Guide me on this also.
Regards
Baby

Text characters displayed as # on Bex analyzer (excel)

Hi all,
I am having issues with Turkish Charaters displayed on the report output on Bex analyser.
The Turkish text characters in the fields like Name 1, Name 2, city are displayed in # format.
This is happening only when the report is executed on Bex analyzer (excel). In BW system I can see the turkish characters properly. There is no # symbol anywhere when i check in cube or master data.
The # sign is not shown when the query is executed on internet explorer(web report). This issue is only with Bex analyzer(excel).
Some sample data is as below.
Correct data in BW cube or master data: ÜCRETLI ÜRETICISI TÜ
The same is displayed when executed the report over web.
But when executed on BEX analyzer(Excel) it shows as: #CRETLI #RETICISI T#
This was not happening last month. I was able to see the turkish characters last month properly on BEX analyzer.
Now we are having this # issue.
Can anyone suggest what could be the problem with? and how we can rectify this?
Thanks in advance

Hi Maddy,
I also think it is a front-end issue.
The texts look fine in RSA1 and in Web Analyzer.
The problem with the codepage variable is that as far as i know it can have only one value.
On my report I have a list of purchase orders with the vendors.
The vendors come form different countries and are maintained by the country's affiliate in their native language.
The user needs to see the texts for all displayed vendors regardless the language and alphabet.
Right now I have probelms with Greek, Bulgarian and Serbian.
But next month the report may contain the vendors from other countries.
Therefore I would have to add all languages to codepage variable.
In fact in my system it doesn't even work for one value.
I also added other languages to windows regional settings but it didn't help.
Do you have any tips on that?
Thanks,
Marek

Turkish Characters Encoding Problem

Hi,
My java code is not going into if statement because of the Turkish characters which are fetched from database. When i printed the result value, it displays Turkish characters as question marks "?". In debug mode i can see the result variable displays correct characters.
            BindingContainer bindings = BindingContext.getCurrent().getCurrentBindingsEntry();
            OperationBinding operationBinding = bindings.getOperationBinding("getLovValue");
            operationBinding.getParamsMap().put("valueId", valueChangeEvent.getNewValue());
            String result = (String)operationBinding.execute();
            System.out.println("Result:"+result.toString());
            System.out.println("KİŞİ".equals(result));
            if(result != null) {
                if ("KİŞİ".equals(result)) {
                    setAdiRequired(true);
                    setSoyadiRequired(true);
                    setSirketAdiRequired(false);
                else if ("ŞİRKET".equals(result)) {
                    setAdiRequired(false);
                    setSoyadiRequired(false);
                    setSirketAdiRequired(true);
                else {
                    setAdiRequired(false);
                    setSoyadiRequired(false);
                    setSirketAdiRequired(false);
            }Console:
Result:K???
false
I really need help about this issue.
Jdeveloper version: 11.1.2.2
My JDeveloper Environment Encoding Setting is "UTF-8"
Regards,
Anil

Hi,
I have already told JDev version in my first post. Nevermind, I just solved problem by setting JDeveloper encoding settings to ISO-8859-9. I don't know why it is not working with UTF-8.
Edited by: AnilA on 18.Eki.2012 11:10

Turkish characters in Bex reports

Hello Experts,
I have a problem viewing Turkish characters in Bex reports. In place of Turkish characters I get some invaild characters. This problem is only with Bex reporting (Via excel).
Web reporting, RSRT (Bex) everywhere it is showing properly, only in Bex (via excel) I am having this problem.
I checked for OSS too, but not much help.
Any help is appriciated.
Thanks
VJ

Hello Green,
we have solved our problem. Actually we have written to SAP and they said that currently with Bex (EXCEL only) may not support all the characters. So they asked us to 1) install SAP GUI Patch version 44 logon as english and
2) Windows -> Start -> Control Panel -> Regional and Language Settings
Select Turkish on the first Drop Down Box, on the tab Regional Options as well as on the Advanced options. Then the specified characters as well as the English characters will display properly
This worked for us....
hope this helps
VJ

Turkish Character displayed as # in Smartforms

Hi ,
I am unable to show the turkish characters in my smartforms , when I try to display 'Sipariş No ' it displays it as 'Sipari# No' .
Even when I enter 'Sipariş No' in the text editor it automatically converts it to 'Sipari# No' when I save the form.
The system in UniCode one and in ECC 5.0 .
I have checked theTransalte section of language attirbutes in Form attributes but it did not help.
Do let me know what needs to be done to solve the issue.
Regards,
Senthil

Hi Senthil,
Do you use the MS Word editor as the graphical editor for smartforms? The old graphical editor is not unicode enabled.
You can activate the MS Word editor for smartforms and sapscipt via the report RSCPSETEDITOR. After this try again to enter te characters in the smartform editor and it should worrk ok.
Regards,
Aidan

How to change the size of the characters displayed on GUI screen?

Hi All,
My problem is : the characters displayed on GUI screen are smaller than other associates when we are in same condition.
Can anyone tell me what i should do to change the size?
Thank you very much.
Regards,
Fiona

hi,
click on the layout menu button at the end of standard tool bar.
select visual settings. there u will get font size options.
u can manage through this your font size.
and this will effective with the first front end mode u start.
layout menu button >> visual settings >>general tab>> font size
hope it will help you.
Edited by: Sachin Gupta on Jul 15, 2008 9:42 AM

Not all chinese characters display correctly with non-embedded text

Hi all,
I've updated to the last beta 2 of Flash Player 10.1 (10,1,51,66) and compiled this simple Flex application to illustrate the fact that not all chinese characters can be displayed correctly with non-embedded text (device font).
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
               xmlns:s="library://ns.adobe.com/flex/spark"
               xmlns:mx="library://ns.adobe.com/flex/halo"
               minWidth="1024" minHeight="768"
               creationComplete="resourceManager.localeChain = ['zh_CN'];"
               layout="{new VerticalLayout()}">
    <fx:Script>
        <![CDATA[
            import spark.layouts.VerticalLayout;
        ]]>
    </fx:Script>
    <s:Label text="伜-伞伟传伡伢伣伤伥伦伧伨伩伪伫伬伭-伝">
    </s:Label>
    <mx:Label text="伜-伞伟传伡伢伣伤伥伦伧伨伩伪伫伬伭-伝"/>
</s:Application>
Notice that characters from the Unicode range 0x4F1E .. 0x4А2D are not displayed within <s:Label> component that uses Flash Text Engine (FTE) by default to display the text, but at the same time those characters display just fine within older <mx:Label> component that relies on flash.text.TextField instance to render the text.

    OK, did not know that "Arial Unicode MS" font is only distributed with Microsoft Office, was looking into relying on this font in case if "simsun.ttc" font is not available at the user's system, by using the following:
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
               xmlns:s="library://ns.adobe.com/flex/spark"
               xmlns:mx="library://ns.adobe.com/flex/mx"
               minWidth="1024" minHeight="768"
               creationComplete="resourceManager.localeChain = ['zh_CN']"
               layout="{new VerticalLayout()}">
    <fx:Style>
        @namespace s "library://ns.adobe.com/flex/spark";
        @namespace mx "library://ns.adobe.com/flex/halo";
        s|Label {
            fontFamily: "Arial Unicode MS, SimSun, Arial";
    </fx:Style>
    <fx:Script>
        <![CDATA[
            import spark.layouts.VerticalLayout;
        ]]>
    </fx:Script>
    <s:Label id="sparkLabel" text="伜-伞伟传伡伢伣伤伥伦伧伨伩伪伫伬伭-伝"/>
</s:Application>
Tough decision ahead, but accordingly to the survey at codestyle.org (2000 participants from 2007 year and onwards), Arial Unicode MS is present at 62.53%% system surveyed.
ps
   My current install of Windows XP already includes the install of Microsoft Office 2007 and I've also enabled/disabled the support of East Asian languages, thus the content of my "fonts" folder differs now significantly from "clean" Windows XP install version.
Nevertheless I found the page with comprehensive lists of standard fonts installed with different releases of Windows that looks viable here: http://www.kayskreations.net/fonts/fonttb.html

Turkish characters display '#'

Similar Messages

Maybe you are looking for