Using accented characters in text

I'm trying to create a document using text for the Czech republic.
I only need "dead" text to be in the Czech language, so am using text objects. Every time I try to paste the Czech words in (via notepad to clear any background Java), LiveCycle crashes with a C++ runtime error.
Any help or advice appreciated...!

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!

Similar Messages

How to exclude accent characters in Text components

How can I exclude accent characters in Text components. I
just want the keystroke do nothing for accent characters.

I assume you mean TextInput.
Easiest way? You may want to do something like this, it
restricts input to only the provided characters, so you'd have to
add any others that you DO want:
restrict="ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz"
Harder way? Extend TextInput (but it only stops `):

Poor keyboard when used in foreign languages using accented characters

I'm looking for a replacement to the built-in virtual keyboard of the iPad (same thing for the iPod or the iPhone). This keyboard is fun to use in english but carry lot of problems for someone who want to write in foreign languages, where accented characters are used. Those characters are available, but in such way that they are unusable for someone who need to do serious work, let say in french, german or spanish.
I can't find an App that do this job. Is there one?
(By the way, the best will be that Apple offer this choice in the next iOS...)
Thanks

Sorry, there will be no immediate or short-term fixes through an app.
Those who need or want to do "... serious work..." on the iPad, by which I guess you must mean a lot of typing, need to get a keyboard to do it with, the current choice being between the Keyboard/Dock and a selection of wireless BT models. I'm going to assume that using one of those will give you as close to the functionality of a 'normal' setup as you're likely see on the iPad.
As for some fix in a future iOS release, you should first think out exactly how you would like them to fix this issue, describe it in some detail, and then forward it along to Apple via their established
FEEDBACK FORM — http://www.apple.com/feedback/ipad.html

HTML + using spanish characters

Hi
If this is a dumb question - forgive me.
Note this is for a site that will be in English & Spansih
(translated pages
in Spanish)
But if I want to include spanish characters on a site do I
need to replace
each spanish character with ascii code or is there another
way to get the
characters to display
e.g.
resúmenes - do i have to enter it into the html as
resúmenes
also
When I view the pages on my pc the spanish characters display
correctly.
Once the pages are uploaded the spanish characters do not
display - why
would this happen?
Thanks
B
www.visit-the-coqui.com/
If you are thinking of a vacation to Puerto Rico
http://gadgetgrapevine.blogspot.com
Latest gadget and other news here

Thanks david for the explaination.
So now I need to figure out how I can save my html as utf-8
without using
notepad (I don't have dreamweaver and have used up my trial
period).
Any one know of any other way of creating a utf-8 html file?
thanks
B
www.visit-the-coqui.com/
If you are thinking of a vacation to Puerto Rico
http://gadgetgrapevine.blogspot.com
Latest gadget and other news here
"David Powers" <[email protected]> wrote in message
news:[email protected]...
>B wrote:
>> could you explain the difference in 'laymans terms'
>
> UTF-8 (Unicode) is designed to handle virtually all
writing systems,
> including Arabic, Japanese, Chinese - and English.
ISO-8859-1 is Western
> European encoding, which handles only those characters
used in Western
> European languages. ISO-8859-1 actually supports the
accented characters
> used in Spanish, but older browsers weren't always
capable of displaying
> them, which led to the use of HTML entities, such as
ñ.
>
> If you select ISO-8859-1 (Western European) in
Dreamweaver, it
> automatically converts all accented characters, such as
those used in
> Spanish, into entities, which makes the code very
difficult to read. If
> you select UTF-8, the accented characters are preserved.
Since English
> doesn't have any accented characters, the encoding is
identical in
> ISO-8859-1 and UTF-8.
>
> If you're working with a database, though, it's very
important not to mix
> the two types of encoding for data that uses accented
characters. If you
> do, the accented characters will be garbled.
>
>> also I posted another ? regarding a BOM warning that
I now get after
>> saving as utf-8 - is this an issue?
>
> I saw that, but didn't reply because you said you used
Notepad. I have no
> idea how Notepad handles the BOM (if I remember
correctly, it stands for
> Byte Order Mark). As the validation warning told you,
older browsers can't
> handle the BOM, so it's best to omit it. Dreamweaver
Preferences let you
> determine whether to add the BOM or leave it out of
UTF-8 pages. By
> default, Dreamweaver omits the BOM.
>
> --
> David Powers, Adobe Community Expert
> Author, "The Essential Guide to Dreamweaver CS3"
(friends of ED)
> Author, "PHP Solutions" (friends of ED)
>
http://foundationphp.com/

Accented characters showing up as ? in JRE1.3 but ok in 1.2

I'm implementing a database web interface product that utilizes JSPs (on SunOS 5.7).
The problem is in the search form. When using accented characters (French language), the JSP calls on URLEncode, but all accented characters show up as '?'.
However, when editing a record, using accented characters is not a problem (i.e., the accented characters are properly stored in the fields).
Back on the server, I ran a small program to output accented characters and also to call java.net.URLEncoder to convert the characters.
The default JDK is J2SE (1.3.1). Compiliing and running the program results in question marks.
Using JDK 1.2, the accented characters show up fine.
It would appear that URLEncoder is not at fault, but instead, JDK 1.3.1 doesn't seem to handle the accented characters.
I figure there must be a setting somewhere, but I'm not sure where.
Here's the program I used (written in Win98, using standard Win-based character set and Unicode format \u00xx; in Unix, "more" displays the Win accented characters fine but "vi" displays them as \xxx; compiles and displays perfectly when using JDK 1.2):
import java.net.*;
class mine {
public static void main(String args[]) {
System.out.println("��") ;
System.out.println(URLEncoder.encode("��")) ;
System.out.println("\u00e0\u00e2\u00e4");
System.out.println("\351");
System.out.println("\351\347\356\364\373\340\350\342\344\374\357") ;
The output with JDK 1.2 is:
��
%E9%E7%EE%F4%FB%E0%E8%E2%E4%FC%EF
��
The output with JDK 1.3.1 is:
%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F

Between jdk1.2 and jdk 1.3 the default encoding of the vm changed.
You can get it by executing:
System.out.println("Default Encoding:" + System.getProperty("file.encoding"));
or
System.out.println("Default Encoding:" + (new java.io.InputStreamReader(System.in)).getEncoding());
The default encoding is used during the conversion of bytes to strings and vice verca.
Assume your default encoding is ISO8859_1. Then calling new String(byte[]) is equivalent to calling
new String(byte[], "ISO8859_1")
Now if you are converting a character from one encoding scheme to another and there is no mapping
for this character in the target scheme. Then the character will be replaced by a default character
which is (quite often) the question mark.
You can set the default encoding for a vm by passing it as a command line parameter
java -Dfile.encoding=ISO8859_1
java -Dfile.encoding=Cp1252

Accented characters

I use accented characters - à, è, ù for example - by pressing and holding the corresponding key to chose the right character that appears in the balloon. This will usually work. Occasionally, it won't work though. When I hold a key - a, e, u, for example - I will get aaaaa, eeeee, etc. To fix the issue, I usually restart the system and the problem is fixed. Is there a more convenient way to fix this rather than restarting the Mac?
MacBook Air mid 2012
Yosemite 10.10.2
Safari Version 8.0.3 (10600.3.18)

hello,
you have a Help application on your device, that can be accessed easily :
home screen >> Help
for example the information you need can be seen in three clicks :
Help >> Typing >> Typing basics >> Type an accent or special character
for convenience, the help is also available on the internet, it's here :
http://na.blackberry.com/eng/deliverables/2596/Type_an_accent_or_special_character_28280_11.jsp
The search box on top-right of this page is your true friend, and the public Knowledge Base too:

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.

Pages breaks words using "Justify text" on certain accented characters

I'm working on a document in Hungarian, and it seems that when I use the "justified text" setting, this puts extra white space around certain accented characters.
Please see these screenshots:
http://www.kkovacs.hu/~kkovacs/Pages-bug-with-accented-words.jpg
In this case, "időszak" should be a single word, and it is, when I write it as "Idõszak" (using õ instead of ő, but this is not the character that is needed there). The problem seems independent of the font that I use (Big Caslon, in the example above).
Is there a way to work around this?
Thanks in advance,
Kristóf

Hello
My old eyes fooled me.
I saw a "lowercase o with a tilde" when it was a "lowercase o with double acute"
With your font which is a bit more recent than mine, the missing glyph is grabbed from an other font (I didn't search which one it is).
I didn't got what was in your original screenshot.
I just get a character with a fully different drawing.
It's funny because it's the kind of problem RC-R and me where exchanging about in:
http://discussions.apple.com/thread.jspa?threadID=1644259&tstart=0
Given what I get, I will not call that a bug but a feature that many users (most of them ?) are unaware of.
The operating system does its best to display the character we are asking for even if it is not built in the used font.
This trickery has PROs and CONs.
For your use, I'm afraid that CONs are the most important and that you will have to search for a font embedding the needed characters.
To scan the contents of a font, I uses the free Linotype FontExplorer which displays the defined glyphs in black and the missing ones in red so, it's easy to see if a font fit our needs.
Yvan KOENIG (from FRANCE mardi 5 août 2008 16:01:46)

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.

Problems with input accented characters after moving JInitiator to JDK 1.5

After upgrading from JInitiator 1.3.1.18 to JDK 1.5.0_06 (jdk plugin in IE), the input of accented characters (in our case portuguese) isn't working anymore in text areas on the forms (Forms 10g).
So, if you push first the "´" key and then the "a" key, you should get as result "á" (worked correctly with JInitiator), but after upgrading to JDK 1.5 you will get simply a letter "a".
Pressing Alt + 160 shows correctly "á".
Somebody can give a clue about this problem please?
Downgrading again to JInitiator is no option for us, as we need a more modern JVM (for a Dicom viewer applet we developed), and IE crashes if you have an Oracle form running with JInitiator, and then try to open another IE page with an applet requesting JVM 1.5 ...
Thanks a lot for your comments.
Alberto A.Smulders
HostDat Lda. - Portugal

In IE, the server must be in the Trusted Sites list & the security for Trusted Sites set to low
Tools -> Internet Options
Security Tab
Sites button
Add all Forms servers, or use a wildcard to get your entire domain. If you are not using SSL, uncheck the "Require server verification (https:) for all sites in this zone"
Set the Security Level for this zone to Low. If the slider bar is not there, click the Default Level button, then slide the security setting to low.

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.

Accented characters on E70

Does anyone know if there's an easy way to input accented characters (like é en ä) on the E70 with the phone folded open? I would have expected that switching to Dutch would change the input mode such that pressing for instance e and ' consecutively would give an é, but no such luck. Right now, the only way of entering accented characters that I know of using the full keyboard is holding the control key while pressing the ascii code of the desired character, which is inconvenient even for the few characters for which I know the ascii code by heart. Alternatively, one can close the full keyboard and use the numerical keypad to cycle through the available characters, but constantly switching between the full keyboard and the numerical keyboard is'n really my idea of convenient text input. Thanks, René (that would be Ren<CTRL><233> :-) )

The capitalization help is a feature I'd like to turn off.
It hinders me a lot more than it helps.
The first line of any SMS or email I send always begins with a lowercase letter - very unprofessional - because the UI has already pressed the shift key. When I press the shift key, to capitalize, it un-capitalizes for me.
I can't correct this habit of hitting the shift key each time I want to capitalize a letter - no other GUI does this to me. Normally, when you begin a sentence, you type a capital letter. But if the phone's UI sees a period, it automatically presses Shift for you.
This means every time you abbreviate something and use a period midsentence in an SMS, the next leter is capitalized, viz. This example.
or "it hinders my typing in emails, sms, etc. And is really annoying. this uncapitalized sentence would be another example."
Anyway how do I turn the thing off because it only wastes my time.
I find myself trying to outwit and predict this auto-cap behavior and I'm tired of it.
How do I turn it off?

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

Help!!!! Accented characters lost!

Hi,
I have a DOS aplications connected to Oracle. This app. inserts accented characters into a table. When I connect to oracle in SQL PLus, or other GUI Tool, accented characters are lost. How can I solve this problem? ANSI
to OEM conversion?
This also happens with a text file created with DOS text editor, when opened on notepad. When I use Ultraedit (a enhanced GUI text editor), it's possible to use "OEM character set", then accented characters are shown correctly.
Are there anything like this on Oracle?
Thank's

Probably the characters are not lost, but they just are not shown because your client uses different language settings.

Using accented characters in text

Similar Messages

Maybe you are looking for