Console UTF-8 Greek accent characters

LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
KEYMAP="gr"
CONSOLEFONT="iso07.14"
CONSOLEMAP="8859-7_to_uni"
Having this configuration I can view Greek characters (even accented), switch keyboard from English to Greek (using Alt+Shift) and write Greek characters (example: αβωδσφηξ) but not accented ones (example: άέήίύόώ ϊϋ ΰΐ). Accented characters are produced by first pressing a "dead" key (semi-colon/colon key in my case). I am always referring to console, everything's fine under X.
If I change my configuration to this:
LOCALE="en_US.iso88591"
DAEMON_LOCALE="no"
KEYMAP="gr"
CONSOLEFONT="iso07.14"
CONSOLEMAP=
I can even type accented characters in console but then other issues come up related to the locale not being UTF-8.
Isn't there a way to produce accented characters (multibyte UTF sequences they are) in a UTF-8 console?
I have gone through tons of documentation and sites and still haven't figured this out :-/ Is this a limitation of the kernel not supporting multibyte sequences? (http://www.linuxfromscratch.org/lfs/vie … nsole.html <- see bottom of page)

ksmanis wrote:Having this configuration I can view Greek characters (even accented), switch keyboard from English to Greek (using Alt+Shift) and write Greek characters (example: αβωδσφηξ) but not accented ones (example: άέήίύόώ ϊϋ ΰΐ). Accented characters are produced by first pressing a "dead" key (semi-colon/colon key in my case). I am always referring to console, everything's fine under X.
I have the following configuration and i can properly write accented characters to console (urxvt).
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="yes"
KEYMAP="us"
CONSOLEFONT= <= empty
CONSOLEMAP= <= empty
To properly write greek with alt+shift at keyboard i have this file named "10-keyboard.conf " in /etc/X11/xorg.conf.d/
Section "InputClass"
Identifier "Generic Keyboard"
MatchIsKeyboard "yes"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us,el"
Option "XkbOptions" "grp:alt_shift_toggle,compose:menu,grp_led:scroll"
EndSection
I hope i helped you

Similar Messages

  • [Solved] Greek accented characters and Qt Applications

    Hello.
    This is my first day with Arch linux.
    My problem has to do with greek accented characters like ά, ή, ό etc.
    I can type these characters on my browsers, rox file manager and other applications but not on Qt based applications like Skype and TeXmaker.
    At first when I tried to type ά on skype I got nothing.
    Later I installed ibus-qt and now I get á instead of ά, é instead of έ, etc.
    Thanks in advance for any help.
    PS: I include the results of locale -a and locale commands in case it helps:
    # locale -a
    C
    POSIX
    el_GR
    el_GR.iso88597
    el_GR.utf8
    en_US
    en_US.iso88591
    en_US.utf8
    greek
    # locale
    LANG=C
    LC_CTYPE="C"
    LC_NUMERIC="C"
    LC_TIME="C"
    LC_COLLATE="C"
    LC_MONETARY="C"
    LC_MESSAGES="C"
    LC_PAPER="C"
    LC_NAME="C"
    LC_ADDRESS="C"
    LC_TELEPHONE="C"
    LC_MEASUREMENT="C"
    LC_IDENTIFICATION="C"
    LC_ALL=
    Last edited by Paris (2013-07-22 00:41:19)

    I just created a /etc/rc.conf file and added:
    HARDWARECLOCK="UTC"
    TIMEZONE="Europe/Athens"
    KEYMAP="us"
    CONSOLEFONT="ter-v16b" #it's Terminus font for console, just install terminus-font from community
    CONSOLEMAP=
    LOCALE="en_US.UTF-8"
    DAEMON_LOCALE="no"
    USECOLOR="yes"
    This fixed my problem.

  • Problems with Greek accented characters

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

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

  • Greek language notes display loses accented characters

    I can type in Greek in TextEdit, save the file as Unicode (UTF-16), and drag it into my iPod Notes folder.
    In OS10.4 I can use accented characters in TextEdit but, when the file is loaded onto the iPod, it omits the accented characters. They aren't displayed incorrectly - they simply aren't displayed at all.
    Anyone ever tried uploading Greek to an iPod? Any Greek users out there?
    Martin

    Yes, the accented characters appear OK on my wife's video iPod.
    I suppose there's no chance that Apple will update the software on my not-very-old color iPod?
    No, I thought not. Money-grabbing *****s.
    I love Apple but not ALL the time.

  • Accented characters and UTF-8

    Hi all,
    I have a problem with accented characters. I read that Plumtree 5.0 is completely Unicode enabled and all HTTP responses from remote web services are converted to Unicode (UTF-16). So the portal sends back to the client browser all pages in UTF-8.
    We have a lots of portlet (ASP and JSP) that write data in external DB, for example SQLServer. When I fill an html form with accented characters that have to be saved in our DB, they are saved in UTF-8 because the gateway converts the HTTP response. We want that the data are saved as if we don't use the portal (without conversion). I tried to change the Charset with the ASP code (Response.Charset). This solves only the problem of displaying the right characters in the browser.
    Could you explain me better how the portal make the conversion and how can I solve my problem?
    Thank you very much,
    Alberto Marchiaro

    It might be helpful to clarify a few things first: 1. Both Java and VB Script will store strings in UTF-16/Unicode. If you have some code in your ASP file that looks like this: Dim strDatastrData = Request.Form("SomeName") then if you were to examine memory for the variable strData, you would see 16 bit characters. The same is true for Java. 2. String data is almost never sent over HTTP as UTF-16/Unicode. 3. Both Java and VBScript perform an implicit character set transcoding when reading string data out of a request or when writing string data out to a response. 4. ASP will perform the transcoding according to the value of the Session.CodePage value. If you have Session.CodePage to 65001, then ASP will expect the string data to be in UTF-8 and it will transcode UTF-8 in the request into UTF-16 in VB Script. Similarly, a Session.CodePage value of 65001 will cause "Response.Write" to convert UTF-16/Unicode into UTF-8. 5. All of the above is separate from how Java or VB Script interact with the database. Generally speaking an ASP module will use ODBC to communicate with the database. The ODBC layer knows that VB Script keeps strings in UTF-16/Unicode. The ODBC layer will perform the proper conversion into the database character set. Plumtree always recommends using UTF-16/Unicode in the database. You can do this relatively easily by declaring your database columns using the "N" datatypes such as NCHAR and NVARCHAR. However even if you using some other character set, the ODBC layer should always properly transcode from VBScript. The importantly thing to remember is that data that is sent over HTTP is never written directly to the database without going through some ASP or JSP code. Since the ASP and JSP code always uses UTF-16/Unicode, there should never be any issue with how the data is sent over HTTP. Here is an explanation for how Session.CodePage, Response.CharSet and Session.LCID work in ASP:****************************************************
    1. Response.CharSet
    2. Session.CodePage
    3. Session.LCID
    Here is an explanation of these properties and why they are important to non-English ASP gadget writers:
    1. Response.CharSet
    This property will cause the HTTP contentType header to be set with the specified character set. The HTTP header is the best way to tell the recipient what the character set is. The Plumtree HTTPGadgetProvider will read the ContentType header and then know how to properly trancode the portlet text into UTF-16/Unicode. Here
    is an example of how to set this property:
    Response.CharSet = "UTF-8"
    2. Session.CodePage
    This property tells the ASP engine which character set to send text in. Please remember that all text is encoded in Unicode on the Web Server. It only gets turned into the client character set when it is send down to the client. The Session.CodePage tells the engine which codepage to transcode into when sending down to the client. Please note that this property is an "integer" property not a string. So you have to know the number of the codepage that you would like to transcode into. Here is an example of how to use this property:
    Session.CodePage = 65001
    3. Session.LCID
    This property tells the ASP engine which locale is being used. The locale is used by various VBScript functions such as FormatDateTime in order to format the date correctly for the locale. If the locale is a French locale, then the date will be formatted according to French rules. The locale does not really effect the character set, but if the portlet writer is going to the trouble of setting the other properties, then they should also set the LCID too. Here is an example of how to set this property:
    Session.LCID = 1041
    Please note that the examples that I am using are the appropriate examples for Japanese and UTF-8. The values for these properties are different for different character sets. For example, for ISO-2022-JP, the values would be:
    Request.CharSet = "iso-2022-jp"
    Session.CodePage = 50220
    Session.LCID = 1041
    A very helpful URL to figure out the values to use with Request.CharSet and Session.CodePage is the following:
    http://msdn.microsoft.com/library/default.asp?url=/workshop/Author/dhtml/reference/charsets/charset4.asp

  • When I use Greek accenting and polytonic characters in a title, Final Cut Pro X quits unexpectedly. What should I do?

    When I try to write a title in Greek using the Greek alphabet, Final Cut Pro X quits unexpectedly, the moment I press the button for the Greek accenting (" ' "). This happens only when I press the button. If for example, I write the title in TextEdit and then copy paste it in FCPX then the title is pasted correctly and the program does not quit.
    An example of title: "Εγώ", so as soon as I press the accenting and then "ω", then everything freezes and FCPX quits.
    It must be a bug, but it really causes a problem. Temporarlily, I always c/p to textEdit and then paste it to FCPX. But I am also using Polytonic Greek system (fonts), so it is a bugger to always c/p. Is there a solution to this?
    Thank you.

    This seems to be a bug, as there was another thread that reported this exact same problem but using Finnish (I believe).
    Do you have Motion? You can try doing your titles there and then export/import into FCPX.

  • Exporting accented characters (Unicode) in metadata

    Hi,
    I wrote a little script to export the metadata to an xml file. I am having some problems where the tags contain accented characters (áéö etc.).
    I managed to write the xml file with unicode encoding and the unicode characters contained in the script are transferred correctly.
    However the special characters in the metadata tags are being transformed to some unreadable characters.
    Is there any way to make sure these characters are transferred correctly?
    Thank you
    Balint

    David,
    Thank you for the help.
    I tried setting the output file encoding to UTF-8 or UTF-16, with or without setting the BOM. The accented characters still come out unreadable. I tried the examples that came with the SDK (output set to the console) and they too scramble the accented characters.
    In other cases, where using the iterator function, the fields that contain accented characters are completely ignored.
    Finally i found the .rawData function in Photoshop that could export the accented characters. This is a much slower solution, because Photoshop has to open all the files to read the metadata.
    I also experimented with my own XML files in Bridge. I can open these, do my transformations, save them and all the characters are well preserved.
    Balint

  • 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.

  • Accented characters, XML, Flash

    I have a flash application which is pulling information to
    populate dynamic fields from two XML files. We have three
    languages supported, and have been having problems with the
    non-english accented characters displaying properly
    when they are called from the XML. I have checked that the
    XML files are encoded in UTF-8, and we have also tried writing
    the html code, the unicode code, putting the information in a
    C DATA shell. I'm out of options that I can think of, and I'd
    appreciate if any other folks have some input on this issue.
    I did find this other thread which seems to be about the same
    issue, but there was no resolution given on it.
    http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=15&catid=194&threadid =1212142&highlight_key=y&keyword1=accent%20characters

    So the same questions arise. What happens in the testing
    environment if you trace it or if you go Debug and list variables?
    Also you say they aren't displaying properly. What does that
    mean? Exactly how are they improper?
    PS: I'm absolutely certain that the other thread was not
    correctly saving as UTF-8.

  • Spanish accent characters are not displayed proper in excel file

    Hi
    I have written a program which displays one report file (.xls file ) on the browser.
    This report file is in spanish language and contains few accent characters like
    ("� � � � � � �"). These characters are not displyed properly in that excel file which is opened in the browser. I have used utf-8 encoding method. I tried with some other encoding methods available. But still this problem continues.
    Kindly provide me help as soon as possible.
    Thanks and
    Regards,
    Deval

    File is generated through a java bean at runtime and it is not stored pgysically.
    If I copy these characters from somewhere to new xls file then it will be displayed properly.
    Sample code which is used for setting headers is as below:
         protected void setContentType (
              HttpServletResponse     p_response
         ,     InstanceData          p_instancedata
              p_response.setHeader ("Cache-Control", "no-cache");
              p_response.setHeader ("Cache-Control", "max-age=0");
              p_response.setHeader (
                   "Content-Disposition", "inline; filename="
              +      p_instancedata.userId
              +      "_"
              +      System.currentTimeMillis ()
              +     ".csv"
              System.out.println("Content generator = ");
              p_response.setHeader("charset","utf-8");
              p_response.setContentType (EXCEL_CONTENT_TYPE);
    For generating this xls file, format of data is XML. Means both request and response data will be in XML format.
    Hope this information help in suggesting any solution for this problem.
    Regards,
    Deval

  • Mail with French / Spanish accented characters appear as Question marks

    Hi
    I am facing issues in mails that have French / Spanish accented characters in mail subject.Accented characters appear as Question marks (?) when received in the inbox.Mail subject is read from properties file.
    Please let me know the following
    - Should I have the entries in properties file in Unicode ? For example French accent character � is represented as &#225;
    - Should I replace msg.setSubject(subject); to msg.setSubject(subject,"UTF-8");
    Please suggest.
    Below is code snippet :
         Session session = getSession();
                   // create a message
                   Message msg = new MimeMessage(session);
                   // set the from and to address
                   InternetAddress addressFrom = new InternetAddress(from);
                   InternetAddress[] addressTo = new InternetAddress[recipients.length];
                   for (int i = 0; i < recipients.length; i++)
                        addressTo[i] = new InternetAddress(recipients);
                   msg.setFrom(addressFrom);
                   msg.setRecipients(Message.RecipientType.TO, addressTo);
                   msg.setSentDate(new Date());
    *               msg.setSubject(subject);*
                   MimeMultipart mp = new MimeMultipart("related");

    String subject = "\u00C 9tat de l'inscription en ligne";You need 4 hex digits after \u. You only included 3.
    mailSubject = new String(subject.getBytes(), "UTF-8");
    message.setSubject(MimeUtility.encodeText(mailSubject,"UTF-8", "B"), "UTF-8");Remove the above two lines. You're trying to make
    this much too hard. All you need is:
    message.setSubject(subject, "utf-8");
    Should I use ISO8859_1 as Charset or UTF-8 ?I think the characters you're included are
    representable in iso-8859-1 so you can use
    that.
    I am using Outlook express as my mail client. Do we have to decode it ?No.

  • Accented characters again, this time in WEB module

    Hi,
    today I made an amazing discovery: even if the language and user interface of LR (2.0) is set to German, there is no provision to deal with accented characters (üöä) in the web galleries. These are taken directly into the generated html files.
    Some web servers can deal with that, some can not and need \&\a\u\m\l\; (w/o backslashes) instead of ä. LR does not do the conversion. One could say that now that I know I should just enter directly the html code. Well, the problem with that is that I might have keywords or a caption with accented characters that I want to display in the web gallery. Also, the (next|previous) marks for switching pages are (Weiter|Zurück) in German and there I have the problem. I don't even know, where the HTML templates are hidden, maybe I could change Zurück to html code there.
    What can I do about this? Can anyone help?
    Thanxx, PM

    In article <[email protected]>,
    [email protected] wrote:
    > today I made an amazing discovery: even if the language and user interface of
    > LR (2.0) is set to German, there is no provision to deal with accented
    > characters (üöä) in the web galleries. These are taken directly into the
    > generated html files.
    If the page's encoding is UTF-8 (check the encoding meta tag) there is
    no need for special characters to be converted to html entities.
    If they don't display correctly it's usually the server serving them as
    ISO-something when it shouldn't. That would need to be sorted out with
    the hosting company.
    Cheers Martin

  • Sms with accented characters

    Hi,
    I hope somebody with some SMS/SMPP experience would be able to fix the problem or
    advise as what to do. OK Now we have an application which is supposed to send an
    SMS to a recipient on certain occassions and this SMS might contain accented characters.
    Now in SMPP apparently we have three encoding schemes namely
    1) 7 bit GSM encoding
    2) 8 bit binary
    3) UCS-2
    Now the third one is out of question since it would reduce the size of the message
    to 70 characters which is not acceptable. 2nd one which is 8 bit binary with I assume
    DCS value 4(or at least thats what we are using) seems to support only latin characters.
    It works for latin characters i.e., iso-8859-1 which does have some accented characters.
    however for other than latin we have some problems e.g hex value for small phi in
    greek (iso-8859-7) is f6. If you look at the corresponding value of f6 in Latin 1(iso-8859-1)
    it is �. Now if you send greek characters setting the DCS value to 4 and u send three
    phi's what you would recieve on the recipient device are three �. So it seems that
    the 8 bit binary supports only iso-8859-1.
    Now if I try to do some encoding into GSM 7 bit. and send three phi's thought I dont
    recieve � but not phi's at the recieving end. The DCS value for the purpose I am
    using is 0. How am I encoding it to GSM 7 bit.
    I am creating the following array
    private static final char [] GSM_7Bit_CHARACTERS = {
    '@', '\243', '$', '\245', '\350', '\351', '\371', '\354', '\362', '\307',
    '\n', '\330', '\370', '\r', '\305', '\345', '\u0394', '_', '\u03A6', '\u0393',
    '\u039B', '\u03A9', '\u03A0', '\u03A8', '\u03A3', '\u0398', '\u039E', '\033',
    '\306', '\346',
    '\337', '\311', ' ', '!', '"', '#', '\244', '%', '&', '\'',
    '(', ')', '*', '+', ',', '-', '.', '/', '0', '1',
    '2', '3', '4', '5', '6', '7', '8', '9', ':', ';',
    '<', '=', '>', '?', '\241', 'A', 'B', 'C', 'D', 'E',
    'F', 'G', 'H', 'I', 'J', 'K', 'L', 'M', 'N', 'O',
    'P', 'Q', 'R', 'S', 'T', 'U', 'V', 'W', 'X', 'Y',
    'Z', '\304', '\326', '\321', '\334', '\247', '\277', 'a', 'b', 'c',
    'd', 'e', 'f', 'g', 'h', 'i', 'j', 'k', 'l', 'm',
    'n', 'o', 'p', 'q', 'r', 's', 't', 'u', 'v', 'w',
    'x', 'y', 'z', '\344', '\366', '\361', '\374', '\340'
    Storing all the values in a Map in teh same order and then for each character in the
    message sending the byte value of the index. If I do a snoop in the snoop I see the
    right hex values as per GSM Encoding table but on the recipient device I see garbage.
    Any ideas as to how can greek and other european character set support be added to
    this application?
    Am I using the wrong DCS value or any body with some other ideas.

    I don't know about the exact character sets for the 7 and 8-bit SMS, but I doubt it's any different then character sets for anything else... So, in this case, the 7-bit set will only be able to handle the first 128 chars, which is A-Za-z0-9 and some punctuation. 8-bit would go into the extended ASCII chars in the table here:
    http://www.asciitable.com/
    There might be some restrictions or differences.
    Basically, 7-bit is ASCII. 8-bit is ASCII+Extended or ISO8895-1. The chars your talking about sending get into the other ISO8895-X sets, which I believe would be out of range. The USC-2 should give you these, however. So either you send shorter messages, or you send ASCII text.
    It would also depeend on the device to be able to display those characters in the first place. Just like on any web site, if you don't have a font that has the necessary characters, it just displays as ? or a box or whatever.

  • Converting XML to Spreadsheet - Problem with Accented Characters

    I have a program that uses an external program to gathers user account information from Active Directory. The external program is .Net, and I execute it from my Java app, which then collects the XML output and saves it in a String variable. So far so good.
    Next it parses the XML and retrieves the values for each field for each user 'record' and stores these values in a String member inside of a class I created called "User".
    At the end of the process, the User class data is written to a file in XML format. Still, so far so good. However, using a text editor, any user names that have accented characters in them have an extra space character after the accented character. E.g. accented "e" becomes "e ". At least that is how it appears in the Textpad editor app that I use.
    Next I have a class called "XMLToExcel", that creates a spreadsheet using Apache's POI library, reads in the XML records , and writes the values for each field into a cell. Here the name with an accented character gives the message "[Fatal Error] <file name>:2617:23: Invalid byte 1 of 1-byte UTF-8 sequence."
    I'm not sure what I can to do fix this, or even where to fix it. I wouldn't mind losing the accented characted and replacing it with an un-accented one.
    Any ideas? I can provide code snippets if that would help.
    -John Gooch

    The text looks the same in Notepad and Textpad. However, I manually added the "encoding" tag with the value of "ISO-8859-1", and the converter no longer complains about invalid characters.
    I added the encoding tag to my application's output file, so the converter should not complain about it on the next run. Unfortunately, the names have been fixed in Active Directory ( the special character was there by mistake ), so I cannot do a live test to be sure that it is fix.
    Thanks for the help, Duke points incoming!

Maybe you are looking for