Print Accented Characters in UTL_FILE

Hi All,
I am trying to write a .csv file in to server path. everything is working fine.
my problem is that when I try to write some accented characters , it was not written into the file properly.
here is what I needed.
MON-MONTRÉAL but instead it is written as MON-MONTREAL, Let me know how to print É using UTL_FILE
below is the code which  I am using.
UTL_FILE.put_raw (l_utl_file, UTL_I18N.string_to_raw ('|'|| c_vendor_rec.remitto,'WE8MSWIN1252'));
my database characterset is showing as
select value from NLS_DATABASE_PARAMETERS where parameter='NLS_CHARACTERSET';
'UTF8'
when I use the same UTL function to convert the characterset from DB, the file is getting generated in the server with the translated value.
but when I run the same as a concurrent program, it is not working properly , it just prints E instead of É. let me know how to resolve this.
Thanks,
Ragul

Hi Sybrand,
my database characterset is showing as
select value from NLS_DATABASE_PARAMETERS where parameter='NLS_CHARACTERSET';
'UTF8'
when I use the same UTL function to convert the characterset from DB, the file is getting generated in the server with the translated value.
but when I run the same as a concurrent program, it is not working properly , it just prints E instead of É. let me know how to resolve this.
Thanks,
Ragul

Similar Messages

  • Reading of accented characters in US-ASCII format in Exchange 2010

    I finished a migration from Exchange 2003 to Exchange 2010.
    I have one unsolved problem. An internal application generates and sends automatically reporting mails using the US-ASCII format through an anonymous Exchange 2010 Receive connector. This connector was configured following the Microsoft recommandations (article
    "Allow Anonymous Relay on a Receive Connector",
    http://technet.microsoft.com/en-us/library/bb232021(printer).aspx).
    The problem is that accented characters like "é", "è" or "à" are converting in "?" when the reporting mails arrive in the user mailboxes in Exchange 2010.
    I made the following test :
    1. When I generate from the shell in Powershell a mail in US-ASCII format, the accented characters are converted to ?
    $encoding = [System.Text.Encoding]::ASCII
    Send-MailMessage -To '[email protected]' -Subject 'Test' -Body 'Test mail avec des é è à et @' -SmtpServer '172.16.3.55' -From
    '[email protected]' –encoding $encoding
    2. When I generate from the shell in Powershell a mail in UTF7 format, the accented characters remains unchanged in the mailbox :
    $encoding = [System.Text.Encoding]::UTF7
    Send-MailMessage -To '[email protected]' -Subject 'Test' -Body 'Test mail avec des é è à et @' -SmtpServer '172.16.3.55' -From
    '[email protected]' –encoding $encoding
    Is there a solution to keep the accented characters without changing the US-ASCII message format in the reporting application ?
    Best regards,
    Pascal

    hi,
    I think it is by design.
    In an Exchange Server 2010 organization, content conversion is handled by the categorizer on a server that has the Hub Transport server role installed. Categorization on each message happens after a newly arrived message is put in the Submission queue. In
    addition to recipient resolution and routing resolution, content conversion is performed on the message before the message is put in a delivery queue.
    Please see this link:http://technet.microsoft.com/en-us/library/bb232174.aspx
    thanks,
    CastinLu
    TechNet Community Support

  • URL Access Scripting & accented characters

    I'm trying to write a small iTunes script that checks whether track titles of an album match those in the MusicBrainz database. But I'm running into a small problem when I try to retrieve the album information when it's title has accented characters.
    Here's a snippet of code:
    property baseURL : "http://musicbrainz.org/ws/1/release/"
    property tempFile : "Data:temp:tempAlbumInfo.xml"
    property albumTitle : "með suð í eyrum við spilum endalaust"
    set queryURL to "?type=xml&releasetypes=Official&limit=10&title=" & albumTitle
    set the clipboard to (baseURL & queryURL)
    -- Fetch the releases info from musicbrainz
    tell application "URL Access Scripting"
    download (baseURL & queryURL) to tempFile replacing yes
    end tell
    This gives me a 503 error from URL Access Scripting, but when I paste the variable just copied to the clipboard into Firefox, the page loads perfectly. Pasting it into Safari, it doesn't work.
    I'm guessing it has something to do with either the way URL Access Scripting and Safari rawurlencode their URLs, or some Unicode / Latin-1 problems.
    Oh, and for album titles without accented characters it all works perfectly. Any idea why this is happening? Thanks!

    Hello
    I think you need to escape URI string properly.
    Try replacing the line:
    set queryURL to "?type=xml&releasetypes=Official&limit=10&title=" & albumTitle
    with these two lines:
    set escapedTitle to do shell script "echo " & quoted form of albumTitle & " | perl -Mutf8 -MURI::Escape -lne 'print uri_escape($_);'"
    set queryURL to "?type=xml&releasetypes=Official&limit=10&title=" & escapedTitle
    Hope this may help,
    H
    Message was edited by: Hiroto (fixed typo: URI::Escape is the correct module.)

  • How to print Arabic characters in Oracle BI Publisher report

    Dear Experts,
    Kindly suggest me how to print arabic characters in BI Publisher.
    Regards,
    Mohan

    see link
    https://blogs.oracle.com/BIDeveloper/entry/non-english_characters_appears

  • How to print Special Characters in Sap-Scripts

    How to print Special Characters in Sap-Scripts
    Thanks,
    Ravi

    Hi
    if u want print special characters we can use hot codes i.e '  '  (single inverted commas). in between these hot codes insert u r special characters.
    write    '    !@#$%^&*( )  '.
    for the above write statement output is
    output is   !@#$%^&*( )

  • Photoshop CS3 printing garbage characters on HP LaserJet 1300

    After installing CS3, Photoshop prints garbage characters on my HP LaserJet 1300.
    Yes, I have tried printing as ASCII, ASCII85, Binary and JPEG - nothing helps (plus the settings won't stick even after holding down Alt and clicking the Remember button).
    The only way to print right now is to choose Save as PDF in the print dialogue, open the PDF in Adobe Reader and print from there.
    Any ideas?

    tzw - I responded about this on another forum. I talked to technical support at Adobe about this exact issue about 2 months ago - can't print photoshop CS3 on any of my three HP printers. ( I have a HP1200, an HP 2550 and a HP photosmart 7660) (CS2 works fine) They worked with me for about an hour - called me back and worked some more, and then decided to send it up to the programmers (or engineers or whatever) The programmers called me and worked with me for another hour - trying different set-ups etc., but the conclusion by them was that this was a huge problem in that there were a lot of HP printers out there - that they were going to give this their top priority - and that there would be a fix for this soon. (I have yet to see a fix.)

  • When i print a pdf from preview it prints strange characters - it looks fine on screen

    when i print a pdf from preview it prints strange characters - it looks fine on screen

    You can also try opening the PDF with preview, then doing a copy and paste to TextEdit and printing from there.
    Adobe makes it easier, but you do have software to accomplish this.
    Only download Adobe reader from this site, to avoid "fakes/spoofs/malware" that will cause damage to your machine.
    http://www.adobe.com/support/downloads/product.jsp?platform=macintosh&product=10
    Hope this helps

  • How can I disable the accented characters from popping up on the iPad?

    Hello all,
           I work with clients who are unable to talk due to various developmental delays. We use the Proloquo2go app which uses the regular iPad keyboard for communication. Is there a way to disable the accented characters from popping up when typing on the keyboard? This is very distracting for some of our clients. Thanks in advance for any advice.
    Nikki

    I don't use an external keyboard but I wonder if you would have any different functionality with one. I'm sorry that I cannot recommend anything but have you thought about that approach?
    http://mashable.com/2012/05/11/ipad-special-needs/

  • How to load CSV with accented characters?

    Hi,
    I have a database instance with NLS_CHARACTERSET = 'AL32UTF'. I upload a csv file with APEX into WW_FLOW_FILES table and then parse it with dbms_lob.instr. The problem that I am facing is that if I save the CSV file in UTF8, then this works fine, if I save it in any other encoding then it's displaying 'funny' characters when I try to parse it and display the parsing result and the source data contains some accented characters, like, á, é, ő etc,
    I am not sure if this is an APEX issue or I rather be turning to NLS forum. TIA.
    Tamas
    Edited by: Tamas Szecsy on Jan 30, 2011 6:34 PM

    Did you every find a resolution to this issue on importing with accented characters?

  • Printer has been setup in one server but it's printing Junk characters

    Printer has been setup in one server but it's printing Junk characters
    Pdf file's sent from server and from local machine are printing fine..But prints sent from Oracle Reports are not getting printed, instead it is printing some garbage contents.

    Forgot to mention it's  10gAS (10.1.2.3) forms & reports

  • 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

  • Printing Turkish Characters in SAP Script

    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, How did you manage to get this done?

  • Accented characters in tagged text

    I normally write copy in a text editor (TextPad), paste into InDesign, and format in the Story Editor. Now I want to format in TextPad and import tagged text. But I am finding that accented characters from the numeric keypad as well as other more frequently used characters - €, £ - are being misinterpreted. For instance R$8·25 million (about €3 million) comes in as R$8·25 million (about €3 million) and  Fundação de Amparo à Pesquisa do Estado de São Paulo is rendered as Fundação de Amparo à Pesquisa do Estado de São Paulo.
    I have the options to format the text file as ANSI or DOS, and I have used the headers <ASCII-WIN> and <ANSI-WIN>, but there seems to be no combination that brings the text in cleanly.
    Substituting Unicode values for these characters gives me what I want and I can build a library of them to add in TextPad, but this is counter to my aim of more productivity.
    Can anyone give me a the formatting options to enable me to use the numeric keypad to generate the extended character set in a form that will import as tagged text?
    k

    Yes, sorry, it had to be somewhere from InDesign to InDesign. What I actually meant was that your tagged text started life in InDesign. My tagged text is starting life in TextPad.
    TextPad can save text in DOS (I guess that means ASCII), ANSI and UTF-8. It's possible that the text in the file I was importing wasn't actually in ANSI. I've restructured it now and it is importing accented characters correctly except, bizarrely, for the Euro symbol (yes, there is a € in the font - Myriad Pro). If I use Alt0128 to create the symbol - or the keyboard AltGr4 - import stops at the last complete line before the € would be encountered, and nothing more is imported. If I use <0x20AC> the symbol imports properly and the whole file is placed.
    I also worked with two identical (except for the substitution of some Unicode characters) versions of the same file. Both were ANSI, and both were headed with <ANSI-WIN> and no other definition information. One file picked up the definitions from the InDesign decument and rendered correctly, the other ignored all the paragraph styles and simply imported text at the default paragraph style.
    So please accept some points for your collection Ken for leading me to re-check the actual code set in the document.
    If you have any ideas about the € problem or why one version of the file would not pick up style definitions I would be intrigued to hear.
    k
    As an afterthought, I've attached a chunk of each file to show one that picks up definitions and one that doesn't. My initial thought was that the one that does pick up definitions would bleat about them being missing, while the other wouldn't. But if I place them in a blank file, both complain that the definitions are missing. However, If I make an appropriately named definition to match one in the file, the version that picks up definitions will match it and only bleat about the other missing definitions. The file that isn't picking up definitions will fail to honour the paragraph style, and will complain that the remainder are missing.

  • Problem with base64 encoding an xml file with accented characters

    Oracle 10.2.0.1.0 Enterprise Edition running under windows 2003 server
    DB Characterset UTF-8
    I have a routine which takes an xml file and base64 encodes it, and the base64encoded text is stored in a clob column of a table.
    The xml file is stored in UTF-8 format.
    The routine works correctly, except when there are accented characters.
    I am using dbms_lob.loadclobfrom file to load the file.
    DBMS_LOB.OPEN(src_clob, DBMS_LOB.LOB_READONLY);
        DBMS_LOB.LoadCLOBFromFile(
              DEST_LOB     => dest_clob
            , SRC_BFILE    => src_clob
            , AMOUNT       => DBMS_LOB.GETLENGTH(src_clob)
            , DEST_OFFSET  => dst_offset
            , SRC_OFFSET   => src_offset
            , BFILE_CSID   =>dbms_lob.default_csid
            , LANG_CONTEXT => lang_ctx
            , WARNING      => warning
        DBMS_LOB.CLOSE(src_clob);base 64 encoded xml with accented character -- incorrect
    PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCjxncDpBcHBs
    aWNhdGlvblByb2ZpbGUgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAx
    L1hNTFNjaGVtYS1pbnN0YW5jZSINCiAgICB4c2k6c2NoZW1hTG9jYXRpb249Imh0
    dHA6Ly9uYW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9zeXN0ZW1zLXByb2Zp
    bGVzLzEuMS4wIGh0dHA6Ly9uYW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9z
    eXN0ZW1zLXByb2ZpbGVzLzEuMS4wL0dQLnN5c3RlbXMucHJvZmlsZXMuMS4xLjAu
    QXBwbGljYXRpb25Qcm9maWxlLnhzZCINCiAgICB4bWxuczpncD0iaHR0cDovL25h
    bWVzcGFjZXMuZ2xvYmFscGxhdGZvcm0ub3JnL3N5c3RlbXMtcHJvZmlsZXMvMS4x
    LjAiDQogICAgVW5pcXVlSUQ9Ik1FIiBQcm9maWxlVmVyc2lvbj0iMS4xLjAiIEVy
    cmF0YVZlcnNpb249IjAiPg0KICAgIDxncDpEZXNjcmlwdGlvbj5Gb3J1bSBUZXN0
    PC9ncDpEZXNjcmlwdGlvbj4NCiAgICA8Z3A6RGF0YUVsZW1lbnQgTmFtZT0iw6Fj
    Y2VudCIgRXh0ZXJuYWw9InRydWUiIFR5cGU9IkJ5dGVTdHJpbmciIEVuY29kaW5n
    PSJIRVgiIEZpeGVkTGVuZ3RoPSJmYWxzZSIgTGVuZ3RoPSIxNiIgUmVhZFdyaXRl
    PSJ0cnVlIiBVcGRhdGU9InRydWUiIE9wdGlvbmFsPSJ0cnVlIiAvPiAgICANCjwv
    Z3A6QXBwbGljYXRpb25Qcm9maWxlPg0Kbase 64 encoded xml without accented character -- correct
    PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4NCjxncDpBcHBs
    aWNhdGlvblByb2ZpbGUgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAx
    L1hNTFNjaGVtYS1pbnN0YW5jZSINCiAgICB4c2k6c2NoZW1hTG9jYXRpb249Imh0
    dHA6Ly9uYW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9zeXN0ZW1zLXByb2Zp
    bGVzLzEuMS4wIGh0dHA6Ly9uYW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9z
    eXN0ZW1zLXByb2ZpbGVzLzEuMS4wL0dQLnN5c3RlbXMucHJvZmlsZXMuMS4xLjAu
    QXBwbGljYXRpb25Qcm9maWxlLnhzZCINCiAgICB4bWxuczpncD0iaHR0cDovL25h
    bWVzcGFjZXMuZ2xvYmFscGxhdGZvcm0ub3JnL3N5c3RlbXMtcHJvZmlsZXMvMS4x
    LjAiDQogICAgVW5pcXVlSUQ9Ik1FIiBQcm9maWxlVmVyc2lvbj0iMS4xLjAiIEVy
    cmF0YVZlcnNpb249IjAiPg0KICAgIDxncDpEZXNjcmlwdGlvbj5Gb3J1bSBUZXN0
    PC9ncDpEZXNjcmlwdGlvbj4NCiAgICA8Z3A6RGF0YUVsZW1lbnQgTmFtZT0iYWNj
    ZW50IiBFeHRlcm5hbD0idHJ1ZSIgVHlwZT0iQnl0ZVN0cmluZyIgRW5jb2Rpbmc9
    IkhFWCIgRml4ZWRMZW5ndGg9ImZhbHNlIiBMZW5ndGg9IjE2IiBSZWFkV3JpdGU9
    InRydWUiIFVwZGF0ZT0idHJ1ZSIgT3B0aW9uYWw9InRydWUiIC8+ICAgIA0KPC9n
    cDpBcHBsaWNhdGlvblByb2ZpbGU+DQo=the xml file in use is
    <?xml version="1.0" encoding="UTF-8"?>
    <gp:ApplicationProfile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://namespaces.globalplatform.org/systems-profiles/1.1.0 http://namespaces.globalplatform.org/systems-profiles/1.1.0/GP.systems.profiles.1.1.0.ApplicationProfile.xsd"
        xmlns:gp="http://namespaces.globalplatform.org/systems-profiles/1.1.0"
        UniqueID="ME" ProfileVersion="1.1.0" ErrataVersion="0">
        <gp:Description>Forum Test</gp:Description>
        <gp:DataElement Name="áccent" External="true" Type="ByteString" Encoding="HEX" FixedLength="false" Length="16" ReadWrite="true" Update="true" Optional="true" />   
    </gp:ApplicationProfile>The file is being loaded from a windows xp professional 32 bit system.
    If I just convert the xml text of the file using
    select utl_raw.cast_to_varchar2(
    utl_encode.base64_encode(
    utl_raw.cast_to_raw(
    '<?xml version="1.0" encoding="UTF-8"?>
    <gp:ApplicationProfile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://namespaces.globalplatform.org/systems-profiles/1.1.0 http://namespaces.globalplatform.org/systems-profiles/1.1.0/GP.systems.profiles.1.1.0.ApplicationProfile.xsd"
        xmlns:gp="http://namespaces.globalplatform.org/systems-profiles/1.1.0"
        UniqueID="ME" ProfileVersion="1.1.0" ErrataVersion="0">
        <gp:Description>Forum Test</gp:Description>
        <gp:DataElement Name="áccent" External="true" Type="ByteString" Encoding="HEX" FixedLength="false" Length="16" ReadWrite="true" Update="true" Optional="true" />   
    </gp:applicationprofile>'
    ))) from dual;I get the following
    PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPGdwOkFwcGxp
    Y2F0aW9uUHJvZmlsZSB4bWxuczp4c2k9Imh0dHA6Ly93d3cudzMub3JnLzIwMDEv
    WE1MU2NoZW1hLWluc3RhbmNlIgogICAgeHNpOnNjaGVtYUxvY2F0aW9uPSJodHRw
    Oi8vbmFtZXNwYWNlcy5nbG9iYWxwbGF0Zm9ybS5vcmcvc3lzdGVtcy1wcm9maWxl
    cy8xLjEuMCBodHRwOi8vbmFtZXNwYWNlcy5nbG9iYWxwbGF0Zm9ybS5vcmcvc3lz
    dGVtcy1wcm9maWxlcy8xLjEuMC9HUC5zeXN0ZW1zLnByb2ZpbGVzLjEuMS4wLkFw
    cGxpY2F0aW9uUHJvZmlsZS54c2QiCiAgICB4bWxuczpncD0iaHR0cDovL25hbWVz
    cGFjZXMuZ2xvYmFscGxhdGZvcm0ub3JnL3N5c3RlbXMtcHJvZmlsZXMvMS4xLjAi
    CiAgICBVbmlxdWVJRD0iTUUiIFByb2ZpbGVWZXJzaW9uPSIxLjEuMCIgRXJyYXRh
    VmVyc2lvbj0iMCI+CiAgICA8Z3A6RGVzY3JpcHRpb24+Rm9ydW0gVGVzdDwvZ3A6
    RGVzY3JpcHRpb24+CiAgICA8Z3A6RGF0YUVsZW1lbnQgTmFtZT0iw6FjY2VudCIg
    RXh0ZXJuYWw9InRydWUiIFR5cGU9IkJ5dGVTdHJpbmciIEVuY29kaW5nPSJIRVgi
    IEZpeGVkTGVuZ3RoPSJmYWxzZSIgTGVuZ3RoPSIxNiIgUmVhZFdyaXRlPSJ0cnVl
    IiBVcGRhdGU9InRydWUiIE9wdGlvbmFsPSJ0cnVlIiAvPiAgICAKPC9ncDphcHBs
    aWNhdGlvbnByb2ZpbGU+Edited by: Keith Jamieson on Jul 13, 2012 9:59 AM
    added code tag for last base64 encoded object

    Not sure if utl_i18n is already there in version prior to 11.2.0.2.
    But on above mentioned version I can do the simplified method
    SQL> SELECT utl_i18n.raw_to_char (
             utl_encode.base64_encode (
               xmltype (
                 '<?xml version="1.0" encoding="UTF-8"?>
    <gp:ApplicationProfile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://namespaces.globalplatform.org/systems-profiles/1.1.0 http://namespaces.globalplatform.org/systems-profiles/1.1.0/GP.systems.profiles.1.1.0.ApplicationProfile.xsd"
        xmlns:gp="http://namespaces.globalplatform.org/systems-profiles/1.1.0"
        UniqueID="ME" ProfileVersion="1.1.0" ErrataVersion="0">
        <gp:Description>Forum Test</gp:Description>
        <gp:DataElement Name="áccent" External="true" Type="ByteString" Encoding="HEX" FixedLength="false" Length="16" ReadWrite="true" Update="true" Optional="true" />   
    </gp:ApplicationProfile>').getblobval (
                 NLS_CHARSET_ID ('utf8'))),
             'utf8')
             x
      FROM DUAL
    X                                                                                                                                                    
    PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPGdwOkFwcGxp                                                                                     
    Y2F0aW9uUHJvZmlsZSB4bWxuczp4c2k9Imh0dHA6Ly93d3cudzMub3JnLzIwMDEv                                                                                     
    WE1MU2NoZW1hLWluc3RhbmNlIiB4c2k6c2NoZW1hTG9jYXRpb249Imh0dHA6Ly9u                                                                                     
    YW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9zeXN0ZW1zLXByb2ZpbGVzLzEu                                                                                     
    MS4wIGh0dHA6Ly9uYW1lc3BhY2VzLmdsb2JhbHBsYXRmb3JtLm9yZy9zeXN0ZW1z                                                                                     
    LXByb2ZpbGVzLzEuMS4wL0dQLnN5c3RlbXMucHJvZmlsZXMuMS4xLjAuQXBwbGlj                                                                                     
    YXRpb25Qcm9maWxlLnhzZCIgeG1sbnM6Z3A9Imh0dHA6Ly9uYW1lc3BhY2VzLmds                                                                                     
    b2JhbHBsYXRmb3JtLm9yZy9zeXN0ZW1zLXByb2ZpbGVzLzEuMS4wIiBVbmlxdWVJ                                                                                     
    RD0iTUUiIFByb2ZpbGVWZXJzaW9uPSIxLjEuMCIgRXJyYXRhVmVyc2lvbj0iMCI+                                                                                     
    CiAgPGdwOkRlc2NyaXB0aW9uPkZvcnVtIFRlc3Q8L2dwOkRlc2NyaXB0aW9uPgog                                                                                     
    IDxncDpEYXRhRWxlbWVudCBOYW1lPSLDoWNjZW50IiBFeHRlcm5hbD0idHJ1ZSIg                                                                                     
    VHlwZT0iQnl0ZVN0cmluZyIgRW5jb2Rpbmc9IkhFWCIgRml4ZWRMZW5ndGg9ImZh                                                                                     
    bHNlIiBMZW5ndGg9IjE2IiBSZWFkV3JpdGU9InRydWUiIFVwZGF0ZT0idHJ1ZSIg                                                                                     
    T3B0aW9uYWw9InRydWUiLz4KPC9ncDpBcHBsaWNhdGlvblByb2ZpbGU+Cg==                                                                                         
    1 row selected.which encodes and decodes properly on my system even with accented characters.

  • Portuguese Accent characters in file name

    Hi,
    I have a created web role with a web application containing HTML files. The HTML file names contains portuguese accent characters. When i publish from visual studio to azure the accent characters change to some different symbol. How do i make visual studio
    to publish the file names with accent characters correctly.
    Thank You

    hi,
    Did you check your accent characters file from instances? I suggest you could login on RDP and check the file name whether is same as your local. You could find file follow this way:
    login on VM==>>open the local Disk==>>siteroots>>0
    Also, you could add the Portuguese language into your isntacnes language list. And change your VM page name as your local page name . And then try to visit using the
    accent characters file name. Please try it.
    Also, you could try to install the language pack for azire (http://social.technet.microsoft.com/Forums/windowsazure/en-US/75d5c1c8-31bb-4431-97ae-a8b80098a9c6/net-framework-45-language-pack-for-azure-web-role-os-family-3-windows-server-2012?forum=windowsazuretroubleshooting ).
    Any update info, please let me know free.
    Regards,
    Will
    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.

Maybe you are looking for

  • Importing outside of API / Open Interface supported?  Partial Workflow ?

    Hi there I've been asked to find out if importing data not using the API or Open API is supported by Oracle? There is a proposal to import orders into Order Management from a legacy database. Some of these orders may be partially through the workflow

  • Transport for ECC and PI for proxy communication

    We have both Outbound and Inbound scenarios between ECC and PI and developed accordingly. We also created both client and server proxy in ECC system. While transporting to the next system is there any dependency that first we need to transport the PI

  • Problems with Menu Bar after recent security update

    Ever since installing yesterday's security update I have been having problems with the menu bar. When clicking on the blue Apple in the upper left hand corner, no drop-down menu appears as it should. This problem also occurs in the drop-down menu nam

  • Is it possible to use repository variable in conditional formatting

    Is it possible to use repository variable in conditional formatting . if no then is there any workaround for implementing the same.... Also i came across a sql of an init block.. which goes like 'exec OracleBi..procedure_name' Is 'OracleBi..' a keywo

  • Sync notes with iMac, iPhone, and MacBook

    My calendar and contacts are in sync for my iMac, iPhone, and MacBook. I can not figure out how to sync my notes on these machines. Any suggestions on how to  do this?