Portuguese characters in IdcCommand

Hi,
When I use the IdcCommand to load files in UCM, and in the metadata I have portuguese characters like ç, á, etc, when I look to this content in UCM the portugueses characters are displayed with "?".
How can I solve this problem?
Thanks

Try using UTF8.
I had problem when I used ANSI.

Similar Messages

Portuguese characters in Command Prompt

Hello.
I have a similar problem but in Portuguese.
I've written an application in LUA connecting to an Oracle 11gR1 database,
running on Windows Vista Business 32.
The database charset is WE8MSWIN1252.
I have a table in which there is a column that have a value of "Manuteção".
When I run a query to the database using SQLDeveloper it works fine.
When the connection is made using LUA it retrieves wrong values. Even
SQL*Plus (DOS) get the values in the wrong way ("ManutenþÒo").
I do not know where should I set up any session parameter to get the
queries working in the same way SQLDeveloper does.
I have read the articles on NLS_PARAMETERS ( FAQ etc ) but I didn't
find any recipe or method to correct the client behavior.
I would appreciate any help on this matter.
Thank you very much
Jayme Jeffman Filho

Your problem is quite different from the original question about length of Spanish characters in AL32UTF8, therefore, I have branched your question into a new thread.
Regarding SQL*Plus Command Prompt (DOS), you need to set NLS_LANG to the OEM code page as follows:
C:\>chcpThis will show:
Active code page: 437or
Active code page: 850Depending on the output, use the following:
C:\>set NLS_LANG=AMERICAN_AMERICA.US8PC437
C:\>sqlplusor
C:\>set NLS_LANG=AMERICAN_AMERICA.WE8PC850
C:\>sqlplusThis should solve the problem for SQL*Plus. Of course, you can use BRAZILIAN PORTUGUESE_BRAZIL in place of AMERICAN_AMERICA:
C:\>set NLS_LANG=BRAZILIAN PORTUGUESE_BRAZIL.WE8PC850
C:\>sqlplusRegarding the LUA application, is it a Command Prompt (character mode) application as well? Do the incorrect characters look the same as in SQL*Plus Command Prompt?
-- Sergiusz

Problem in printing Portuguese characters

Hi ,
We are facing a problem while printing certain Portuguese character . Please guide how to print the PORT characters in SAP script?
Thanks
Saurabh

Hi Saurabh,
Did you [Search|https://www.sdn.sap.com/irj/scn/advancedsearch?query=chinesecharactersin+Script&cat=sdn_all] before posting...
and also refer to this [link|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00adf4da-76f1-2910-43aa-81ad2a67332c]
Regards!

Embedding portuguese characters

Hello Everyone,
I am changing text from english to portuguese in flash template but i can't embed some characters like ç ó õ é à.
The text is coming from xml using cData tag.
Please let me know how i can do this.
Thanks in advance

Thank you again. I remember having a hard time finding a suiteable and working solution to embed the outlines for xml / html text / external css. Somehow all other solutions had some sort of drawback or plainly didn't work. Since I do have the CS4 IDE I would imagine that above solution should work. In the past putting a dynamic text field on the stage and embedding additional characters through the property window would work.
Not sure what to do now...
I guess I can try again to embed the fonts by linking it directly to the font in the Flex IDE and then specify the unicode fonts there. I will give it a shot. If someone knows of a way of making this work in CS4 > export to .swc for Flex (as3 project) please let me know.
Much thanks to everyone.
Regards
sk

Can not recognise portuguese character in weblogic 10

Hello All,
I have Weblogic 10 installed in RedHat Linux and I have deployed a web app in the weblogic server. There are portuguese characters in the web app but we can not see the portuguese characters in the browser. The characters appear as '?'.
Same web app works fine (we can see the portuguese characters) in Tomcat.
I tried adding the param -Dweblogic.webservice.i18n.charset=3Dutf-8 in the startup script but it did not solve the issue.
Chinmoy

Hi shamca,
Its inside.
C:\bea\modules\com.bea.core.utils_1.4.0.0.jar
Hope this helps.
Thanks

Re: How to change the NLS_NCHAR_CHARACTERSET from WE8ISO8859P1 to AL16UTF16 ?

Hi,
Now I have a new problem.
I have a Oracle9i instance, with this configurations.
PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET WE8MSWIN1252
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 9.2.0.1.0
I have a xHarbour DOS Client program that reads, shows in the screen, and write "perfectly fine" a text with Brazilian accentuation stored in a CLOB field.
Following you can see the sample of the text with Brazilian accentuation in my DOS application http://www.screencast.com/t/U5PXwCEo8
In order to my xHarbour DOS Client program works fine with this Brazilian accented characters, I must to set:
SET NLS_LANG=PORTUGUESE_BRAZIL.WE8MSWIN1252
And all is OK from my xHarbour DOS Client program.
My problem is because when I query this data manually using a SELECT from any client DOS/WINDOWS program like SQLPLUS, SQLDEVELOPER, TOAD, etc, I get bad characters instead the correct Brazilian accented characters.
Following you can see the same text into the Toad http://www.screencast.com/t/A1tal2Rtg
(you will see bad characters instead the correct Brazilian accented characters).
Following you can see the result of querying this field using a SELECT from SQLPLUS.
Certifico que por decis„o proferida no processo n§ @@@@@@@@@@@@@@,
foi reconhecida a n„o incidˆncia do ITBI na transa‡„o do(s) im¢vel(is)
abaixo caracterizado(s), com base no art.156, @ 2§, I, da Constitui‡„o
Federal de 1988 e no art.6§, II, da Lei Municipal n§ 1.364 de 19/12/1988.
(you will see bad characters instead the correct Brazilian accented characters).
How to make "SQLPLUS", "TOAD" (and others Windows or DOS Clients programs) show me the Brazilian accented characters correctly?
Thanks in advance,
Luigggye

OK, if you look at the word "decisäo" in your DOS program (shouldn't it be "decisão", by the way?), it is encoded by the following bytes: 64,65,63,69,73,84,6f.
d = 0x64
e = 0x65
c = 0x63
i = 0x69
s = 0x73
ä = 0x84
o = 0x6fSo, the code for "ä" in your database is 0x84. If you look at the definition of the WE8MSWIN1252 character set, for example here: http://msdn.microsoft.com/en-us/goglobal/cc305145 , you will see that the expected code is 0xe4. On the other hand, if you look at the definition of WE8PC850 here: http://msdn.microsoft.com/en-us/goglobal/cc305160 , you will see that the code for "ä" is 0x84 -- the one you have in your database.
This proves my initial diagnosis that you have incorrectly labeled data in your database. By setting the NLS_LANG to the same character set as the database, you created a so-called pass-through configuration. This configuration does not require any character set conversion, hence what you put into the database is what you can retrieve unchanged. As CHCP shows, your DOS program (the correct name is actually "console mode program") works in the Microsoft OEM Code Page 850, which corresponds to the Oracle character set WE8PC850. So this is the character set that your application sends to Oracle and this is what gets stored in the database. If you set the NLS_LANG to .WE8PC850 before inserting data, the database would know that the received data is in WE8PC850 and would convert it properly to the database character set WE8MSWIN1252. This data could then be properly converted as required for other clients such as Toad or SQL Developer. As the NLS_LANG was WE8MSWIN1252, Oracle wrongly assumed that the application data is already in WE8MSWIN1252 and did not do any conversion. You ended up with mislabeled data.
To fix the issue, you should repair the database character set declaration to correspond to the actual database content, i.e. WE8PC850. You should then change the NLS_LANG for the DOS program (and only for the DOS program, not for Toad or other Windows GUI apps) to WE8PC850 as well. I am assuming here, and this is important!, that all non-ASCII (e.g. Portuguese) characters in your database come from this one DOS program.
To repair the database character set declaration:
1) Upgrade to 10g or 11g
2) Run the csscan utility with parameters FROMCHAR=WE8PC850 TOCHAR=WE8PC850. The scan report from the utility (scan.txt) should report only changeless data.
3) After running the scan, execute the ?/rdbms/admin/csalter.plb script in SQL*Plus.
-- Sergiusz

Alt codes not working

I am trying to use alt codes to input spanish and portuguese characters. My laptop has a keypad so I am pressing ALT+!164, for example, but none of the codes works. What could I do to solve this?
Thanks!

I don't believe there is a keycode for the ALT key, but you can apparently determine whether or not it is active (Boolean) using theKeyboardEvent.altKey property. See the following in the help documentation.
http://www.adobe.com/livedocs/flash/9.0/ActionScriptLangRefV3/flash/events/KeyboardEvent.h tml

[URGENT] UTF-8 issue in weblogic SOAP implementation

Guyz,
I am finding an issue with **weblogic.xml.saaj.MessageFactoryImpl** SOAP message factory mplementation class of weblogic. When it creates SOAP from inputstream which includes portuguese characters it does not recognise those characters.
Any idea how to solve this issue?
Chinmoy

Will this really be a problem? UTF-8 is a superset of US-ASCII, I believe,
          so there should be no incompatability. This is assuming that you will only
          be sending latin characters in the form, since the recieving end can only
          accept latin characters. If this is NOT true, then they need to use UTF-8.
          Otherwise, I would test it and see what happens.
          "Volker Mader" <[email protected]> wrote in message
          news:3d3326c4$[email protected]..
          >
          > Hi there,
          >
          > can anybody help me.
          > I have a webapp in wls 6.1 sp2. All of the web is utf-8 based, so i set
          the charset
          > in the page-directive and the html content type to utf-8. Also I set the
          <input-charset>
          > Tag in weblogic.xml to utf-8 for context "/".
          > Problem: I want to send a from out of this webapp to another server which
          serves
          > a iso-8859-1 based application.
          > How can I do that?
          >
          > Thanks for help
          > Volker

Invalid UTF-8 middle byte 0x6f (at char #3309, byte #2895)

Hello Oracle Support/ SOA Experts,
Please guide me on how to resolve this issue.
Issue Description : We are using ATG,Oracle SoA SUite 11g as the Front and Middleware applications for our current website project.The project is basically for latin america(Portuguese Language) and we are facing encoding issue while sending the request from ATG(Front End) to SOA (Middleware).We have an SOA-xsd [customer.xsd) that contains FirstName,LastName,MiddleName as elements.Front End application(ATG) sends the customer xsd in ISO-8859-1 encoding format as we understood that only encoding format for sending the portuguese names is this format.Front is able to send the request to SOA Without any issues however the only format which SOA Suite accepts in our BPEL process is UTF-8 and hence we are seeing this invalid UTF-8 error.Can anyone of you please explain us on how to resolve this issue or please guide us which encoding format can we use for passing portuguese characters from front end to SOA Suite.
*Exception*:
java.lang.RuntimeException: [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6f (at char #3309, byte #2895): [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6f (at char #3309, byte #2895)
What we tried :
Since ATG or front end is using the ISO-8859-1 format to send the request to SOA,we tried to use the encoding format in all the SOA BPEL XSD but we are unable to deploy after changing the encoding and we see the below error :
Exception:
Redeploying on /Farm_soa2_domain/soa2_domain/soa_server1 ...
Redeploying on "/Farm_soa2_domain/soa2_domain/soa_server1" failed!
Error during deployment/undeployment: oracle.mds.transfer.TransferException:
MDS-00001: exception in Metadata Services layer
MDS-00521: error while reading document /deployed-composites/default/ManageCustomerOrderOrchestration_rev1.0/xsd/ManageContract.xsd from metadata repository
IS0-8859-1
IS0-8859-1
MDS-00001: exception in Metadata Services layer
MDS-00521: error while reading document /deployed-composites/default/ManageCustomerOrderOrchestration_rev1.0/xsd/ManageContract.xsd from metadata repository
IS0-8859-1
IS0-8859-1

Hello Oracle Support/ SOA Experts,
Please guide me on how to resolve this issue.
Issue Description : We are using ATG,Oracle SoA SUite 11g as the Front and Middleware applications for our current website project.The project is basically for latin america(Portuguese Language) and we are facing encoding issue while sending the request from ATG(Front End) to SOA (Middleware).We have an SOA-xsd [customer.xsd) that contains FirstName,LastName,MiddleName as elements.Front End application(ATG) sends the customer xsd in ISO-8859-1 encoding format as we understood that only encoding format for sending the portuguese names is this format.Front is able to send the request to SOA Without any issues however the only format which SOA Suite accepts in our BPEL process is UTF-8 and hence we are seeing this invalid UTF-8 error.Can anyone of you please explain us on how to resolve this issue or please guide us which encoding format can we use for passing portuguese characters from front end to SOA Suite.
*Exception*:
java.lang.RuntimeException: [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6f (at char #3309, byte #2895): [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0x6f (at char #3309, byte #2895)
What we tried :
Since ATG or front end is using the ISO-8859-1 format to send the request to SOA,we tried to use the encoding format in all the SOA BPEL XSD but we are unable to deploy after changing the encoding and we see the below error :
Exception:
Redeploying on /Farm_soa2_domain/soa2_domain/soa_server1 ...
Redeploying on "/Farm_soa2_domain/soa2_domain/soa_server1" failed!
Error during deployment/undeployment: oracle.mds.transfer.TransferException:
MDS-00001: exception in Metadata Services layer
MDS-00521: error while reading document /deployed-composites/default/ManageCustomerOrderOrchestration_rev1.0/xsd/ManageContract.xsd from metadata repository
IS0-8859-1
IS0-8859-1
MDS-00001: exception in Metadata Services layer
MDS-00521: error while reading document /deployed-composites/default/ManageCustomerOrderOrchestration_rev1.0/xsd/ManageContract.xsd from metadata repository
IS0-8859-1
IS0-8859-1

Line breaks not passing from flash to asp

Hello,
I've came up with a very anoying problem, and I need it fixed
asap.
The problem is as folows:
I have a form in flash that contains a number of fields. One
of those is a input field with the purpose of capturing the
impressions of the user on a given subject. Needless to say that
that impression may contain paragrafs, and line breaks. I'm using
flash 7 publish settings and passing the values of the fields via
LoadVars. The problem seems to be that no line breaks are passed to
ASP. All the special characters are passed correctly, the HTML is
coded as UTF-8 so that the portuguese characters are correctly
decoded, but no line breaks are shown. I need a quick solution to
solve this problem of the line breaks.
Can someone give me a quick hand on this?
Thx

Thx kglad,
Your solution is very simple... too bad I happened to create
a solution on a much more complicated way... I ended up by escaping
the string, detecting where the %0D was found, and replaced it with
<br>. A much harder way to get to the same result... On
future ocasions im gonna use your solution, which is way much
simpler and doesn't require the number of coding lines that I had
to create for the same purpose.
Thx again m8

Charset in File Adater using ASCII

Hello,
I Have a partner link that uses the file adapter to write ascci files in a directory.
The problem is that when i pass some Portuguese characters into it it writes '?' instead.
Example:
I Pass to the partner link:
<Invoke_PT_118_Put_InputVariable>
<part name="PT_118" >
<PT_118>
<Header>
<Identificador>17708</Identificador>
</Header>
<Detalhe>
<Operacao>a</Operacao>
<Morada>Alameda da Música</Morada>
<NumeroPorta>26</NumeroPorta>
</Detalhe>
<Footer>
<TotalRegistos>2</TotalRegistos>
</Footer>
</PT_118>
</part>
</Invoke_PT_118_Put_InputVariable>
and the File Adapter writes:
Alameda da M?sica;26;;
Any idea to correct this issue?
Tks

Hi,
i had the same problem and solved it setting ( nxsd:encoding="iso-8859-1" ) in .xsd file that describes file format read by inbound file adapter.
my example:
<?xml version="1.0" encoding="iso-8859-1" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"
targetNamespace="http://www.mycompany.com/SRPReadFileInbound"
xmlns:tns="http://www.mycompany.com/SRPReadFileInbound"
elementFormDefault="qualified" attributeFormDefault="unqualified"
nxsd:encoding="iso-8859-1" nxsd:stream="chars" nxsd:version="NXSD">
<xsd:element name="Root-Element">
<xsd:complexType>
hope it helps.
Edited by: pitmarquez on 12-ene-2010 7:26

JVM CodePage

Hi there
When executing an console application, the portuguese characters does not appears correctly. Is there any way to configure JVM code page or anything like that ?
Thanks .
PS: using windows xp

I'd recommend you post this on the I18N forum instead.

SUN JVM CodePage

Hi there
When executing an console application, the portuguese characters does not appears correctly. Is there any way to configure JVM code page or anything like that ?
Thanks .
PS: using windows xp

By console application, I assume you mean an application that displays output on the DOS command prompt on Windows?
If that is the case, then you are seeing a well-known problem - the fact that the JVM codepage is the Windows codepage (for Portuguese it would be 1252), while the DOS command prompt uses codepage 850.
The only way to "fix" that (that I have found) would be to perform a codepage conversion on your own when the application runs as a console application. If that is the only way it executes, you are in luck, since you can just always perform the conversion. You can get the console.encoding value using System.getProperties().

Native2ascii problem

Hello Group,
I have some problem with native2ascii ant task for
non-english languages. When I run native2ascii task through ant task it
generates some junk characters for portuguese characters e.g.
Input char: Efectuar liga��o
Output : Efectuar liga\ufffd\ufffdo
But if I run antive2ascii in commandline without through ant task
then it generates correct characters e.g.
Input char: Efectuar liga��o
Output : Efectuar liga\u00e7\u00e3o
which is correct.
Could you please help me to find out what is the problem when it runs
through ant task?
- BR

Hold on - do you have only languages that can actually be represented in 8859-1? If you do, then you don't even need to run native2ascii, since Java Properties files are expected to be in 8859-1: http://java.sun.com/javase/6/docs/api/java/util/PropertyResourceBundle.html
But if you support 12 languages I would think it highly likely that you actually do have languages that cannot be represented in 8859-1, such as Japanese, Chinese, Russian, etc. In that case you either need to use a different legacy encoding for each distinct script (and therefore run native2ascii with a different encoding option for each group of scripts) or use UTF-8 for all (allowing you to run native2ascii once, on all files. It shouldn't be difficult to choose the best option from those.
With respect to ensuring that the properties files are in the correct encoding: simply saving a file with one of the options you see in Notepad does not convert the file to the encoding in question, it simply saves the bytes as they are - Notepad assumes that you know what kind of text you have in your file. In other words, if you have a file encoded in 8859-1, open it in Notepad and then save it as UTF-8, the bytes in the file are still encoded as 8859-1, and treating it as UTF-8 will just result in errors.
Of the Notepad options 'ANSI' would be the option you would choose for a file encoded in 8859-1 if you are on a system where the default system codepage is 1252 - if you are on a system where the default system codepage is e.g. Russian, however, ANSI would result in the file being saved in the legacy Russian Windows codepage, however. 'ANSI' is a Windows invention, and simply means whatever non-Unicode codepage the Windows box happens to be running in.
To actually convert the file from one encoding to another you need to use a conversion tool such as iconv. In order to use those tools correctly you will still need to know what codepage the file is in, however. So you really need to keep track of the encoding of the files you are dealing with. The easiest way to do that is to always use UTF-8, and these days that is fairly easy.
There are tools that can help you, if you have somehow lost track of the encoding, or the file comes to you from unknown sources, etc. Encoding detection is part of ICU, for instance, and a good Unicode editor like SC Unipad will at least tell you whether the file is encoded in Unicode or not. But none of those methods are work 100%, so again, you are back to keeping track of the encoding yourself if you want to be sure.

How can I display special characters of NonEuropean languages (French, Italian, Spanish, German and Portuguese.) using import string mechanism

I would like to translate the User Interface of my application to French, Italian, Spanish, German and Portuguese.
When I put special characters in the import string file they showed up as ? (question mark)
The import strings file includes the following parameters for each string: font, text, size and style. (but no field for script)
In order to use a unicode font such as Arial I need to select a french script. But this option is not supported bu LabView (As far as I saw)
A) Is there a font which is directly German/ French etc and not regula font + script parameter?
B) Are there another required step
s for special characters support? (When I put speciual characters in the import string file the showed up as ? question mark)

This was discussed last week in this group- read the previous messages.
Look for the thread "Foreign Languages in Labview"
And recite the mantra
ActiveX is good
ActiveX is holy
All Hail Bill
Those who claim otherwise are heretics and not to be trusted
Actually, in this case the non-ActiveX suggestions may be good.
talia wrote in message
news:[email protected]..
> How can I display special characters of NonEuropean languages (French,
> Italian, Spanish, German and Portuguese.) using import string
> mechanism

Portuguese characters in IdcCommand

Similar Messages

Maybe you are looking for