Entering accented characters via Simulator

I turned on international keyboard support in Simulator. I can switch to French keyboard. I can hold down 'e' to show me the options for 'e' (é,è,ê,ë...), but I can pick any of them. The keys for r,t,y...are highlighted instead.
This a bug? Anyone get it to work?

Follow up....I can enter accented characters into the contact app in the simulator so it's not keyboard related as I thought. But, I can't enter the characters if I'm running the SQLiteBooks example Apple posted today.

Similar Messages

ATV entering accent characters?

Trying to add a flickr contact whose name included an accented a character (ie á). Since flickr distinguishes between a and á, how do I enter that on ATV? There doesn't seem to be the same hold down the key trick that works for iPhone?

In those now-rare instances where a font lacks an accented character, you
can create one similar to the way you did formerly by using kerning. Of
course, you run into those cases where the accent just won't fit the letter
properly and you end up spending time adjusting the size and baseline shift
of the accent. I suppose if it is a long composition you could record a
macro and assign a shortcut -- but I'd rather choose a font with true
accented glyphs whenever possible.
Trez

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?

French accented characters in a barcode are being dropped when scanned by a handheld scanner

We have an issue when our pdf417 barcodes contain french accented characters é,à,è, etc and are scanned by a handheld scanner. As a result Montréal is decoded as Montral (the é is dropped). We are using the Datalogic PowerScan 7000 and a Motorola Symbol DS6608 handheld scanners. We currently have a ticket open with Datalogic.
The problem does not exist when the barcode is decoded by LC Barocded Forms.Decode.
Talking to someone, they indicated that this is pretty common with handhelds. However, I did find this old post from lee sutton http://forums.adobe.com/thread/332743 where he uses a keyboard wedge?
Has anyone had to deal with a similar issue (non-english chars) via handheld?
Can anyone recommend a handheld that does read non-eng characters without the wedge?
Is there something in the encoding from Designer that i can do?

When you're decoding with the hand-held scanner, you'll need to ensure that the decoder itself supports the scanning of extended characters AND if it's a keyboard-wedge scanner, ensure that your keyboard is in French or Canadian-French mode or the simulated typing won't happen.

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 in Word for Mac: Option-i doesn't work

I am trying to type an accented character (e.g., a circumflex over a letter). Everything I find online says type and hold "OPTION-i", release, then type the letter, but it doesn't work. Instead I get the accent over empty space, next to the letter. This is MS Word for Mac 2008 software on a MacBook Pro. Any ideas?

> the problem is that I'm trying to put a "hat" over a consonant
I suspect you'll find that, the more precise and specific your question, the more greater the likelihood of getting a speedy and helpful answer.
> Looks like the software only allows the circumflex over vowels.
> Option-i does work on my computer for vowels. (Built-in
> keyboard).
Nonsense. Nothing to do with your keyboard. Btw, you still haven't told us what character you're trying to insert.
> I guess I will have to use the Equation Editor.
That's an option, but not the only one. Just for the sake of argument, let's assume it's p-hat (not the party hat, but the symbol for sample proportion).
(1) Specifically in Word, you can use fields (overstrike). Go to Insert > Field… > Equations and Formulas > Eq; then type
EQ \O (p,^)
and confirm. (Note that "EQ" will be inserted by Word automatically, you don't need to type it again.)
Once you get the hang of it, you won't need to insert it using menu & submenu commands, but by typing and applying styles.
(2) The right way is Unicode. Currently, Unicode defines >100k codepoints, so, for obvious reasons, it's neither necessary nor practical for most keyboard layouts to be able to access anything but a small subset. You can enter Unicode characters using Character Viewer (aka Special Characters), or, more efficiently, using the Unicode Hex Input keyboard layout.
If the character is already defined as such in Unicode, eg, for all (upside down A), then hold down Option and type its Unicode hex code, ie 2200 -- ∀. However, p-hat isn't defined as such, so it must be entered as a combining character sequence. The sequence is ((Latin small letter p) + (combining circumflex accent)), or (p + 0302) -- p̂.
Unfortunately, all is not sweetness and light. Although this is how it should be done, the display may disappoint. Questions 12b and 12c in the respective Unicode FAQ explain what happens and why.

Accented Characters and Diacritic folding flag

Hi,
When using "--diacritic-folding" flag in dgidx, is there a way to ignore certain characters from mapping accented characters to simple ASCII equivalents?
For e.g, i have this flag enabled but i need "ñ" and "n"to behave as two different characters.
Is this possible?
Thanks
Edited by: mk.s on Apr 12, 2013 5:33 AM

There is no out of the box capability for this that I am aware of. You could raise a feature request via support.oracle.com to allow you to be able to define exceptions, and if you do so I'd recommend including some use cases to explain the business requirement.
The only way I can think of doing this with the current software is a workaround - you would have to have a pre-processing step to map the character to a different code point, then when you submit your search apply the same translation. I've done this previously to get around issues with unsupported (in older Endeca releases) code points in the Thai language, and it does work but you have to add a manipulator to your pipeline (or do the transformation in the data extract) and have some simple code before you send the query on to Endeca (before ENEQuery if via the API).
Thanks
Michael

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

Accented characters do not display correctly

Hello,
I created a report in CR with an Oracle8i ODBC connection (version 8.01.74.00). The strange thing is that accented characters are displayed weird in the report although the characters are just fine when I look at them via sqlplus. At first I thought it was a CR problem but I got the same results in Access.
Eg. in sqlplus I see this:
user comment :"Veuillez faire réparer dès que possible la photocopieuse
But in the report I see this:
user comment :"Veuillez faire rÃ©parer dÃ¨s que possible la photocopieuse
I already played around with the NLS_LANG setting in the registry but this didn't help.
Does anybody has an idea how I can solve this?
Thx,
Geert

One possibility is that the Windows regional settings on your machine may be conflicting with your NLS settings. Access and Crystal Reports probably look there exclusively, recent versions of Oracle ODBC driver and SQL*Plus will look exclusively to your NLS settings, while the 7.3 era ODBC driver probably looks to the Windows regional sessings.
Justin

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

Accented characters in exported images getting munged

Lightroom 2.x, OS X 10.5.6, G5, Nikon D80, Raw/NEF/DNG
I'm trying to sort out a problem I'm having that looks similar to other issues with international characters, but is a little different. My problem is specific to keywords.
I don't think this should matter, but I generally import as DNG and never save metadata to XMP. I mainly export to JPEG (to a folder that I zip up) in order to upload photos (outside of Lr) to a sharing site.
What I'm finding is that if I tag my photos (in Lr) with keywords that have accented characters (which I use a fair amount because I often travel to Francophone areas to take photos, and my IPTC data and keywords use correct French spelling) upon upload to any photosharing site I try, the keywords will be munged, duplicated and/or generally messed up. For example, I have a keyword "café". Upon export I can see this correctly in the IPTC Keyword metadata (via a third party EXIF/IPTC viewer, and also using "Get Info" in the Finder). However, as soon as I upload this JPEG to any photo sharing site the photo will end up with a series of keywords applied to it: "caf, cafe, cafã©"
Similarly, a keyword like "naïve" will end up as two keywords: "naã¯ve, nave" I get similar results with HTTP uploaders as well as uploader plugins inside Lr. And so on for è, ô &etc. In the case of Flickr, there will be one "copy" of the keyword that is correct. The others will still be present.
I've read hints that suggest that the IPTC metadata stored in the exported file by Lr might not be Unicode-clean, which causes anything that parses and normalizes select metadata (as all online sharing sites will want to do) to choke. I've heard rumours that the XMP data is properly Unicode clean, but most sharing sites ignore that data, since they are pretty much interested only in EXIF or IPTC metadata (and rightly so, I suppose.)
Is this a defect in the way Lr creates metadata in exported images? Or is is a problem with the way all these sites suck in and normalize the metadata stored in the image? Or is it a subtle interaction between the two that results in incompatibilities?
I haven't tried experimenting with creating or finding a JPEG with no keywords at all and manually inserting IPTC keywords with accents, just to see what Flickr (et al) do upon upload. I've also tried various permutations of the keyword options in the Lr export dialogue with no significant change in behaviour.
I'm interested in who else might be seeing this problem. Is it a Lr only thing, or is it Lr-on-Mac? Or something specific to the two sites I upload photos to?
I should point out that I've been seeing this behaviour since Lr 1.x.

(Jao, AdobeRGB is an experiment. I have a colour managed browser, so I wanted to see if I could tell the difference. This is a test photo from my junk pile.)
I think I see the problem. With something like ExifTool you can see that the keywords are stored in a number of places in the EXIF/IPTC header: Keywords, Subject and Hierarchical Subject. It is the Keywords section that is not Unicode clean, apparently. This is even more apparent if you show the output encoded in HTML entities:
Keywords : Franais, Test Shots, Wings of Paradise Butterfly Conservatory, butterfly, cafŽ, l'h™tel, na•ve, tests
Subject : Français, Test Shots, Wings of Paradise Butterfly Conservatory, butterfly, café, l'hôtel, naïve, tests
Hierarchical Subject : Français, Test Shots|tests, Wings of Paradise Butterfly Conservatory, butterfly, café, l'hôtel, naïve
So, it depends on what section the keywords are taken from. It appears that both Flickr and 23 will try to find the keywords in as many places as possible. This explains the many duplicates I am seeing.
So, now I just have to figure out why Subject is so wrong, and how to correct it (or leave it blank.)

Accented characters in LR for mac.

Hi all:
I'm having problems with pictures with "accented characters" in the name. I can work with these pictures, no question mark is shown, and LR can show where the actual file is located. The problem is as following: if I try to sync a folder, then LR says there are x missing files and the same x new files. If I tell LR to proceed, then the "new" pictures loose keywords, tags, edits, etc.
I have the same pictures and catalog both in windows and in mac (both version 4.4), as I'm trying to swicht, and in windows there is no problem. So it is a particular mac version problem. I tried to check the problem: if I delete these accented characters, then no new nor missing files are detected in sync, but this is not a solution (I have thousends of pictures and I want to keep the accented characters).
Is there any other solution?
This same problem has been mentioned several times, but nobody find a good solution. For example in
http://forums.adobe.com/thread/608096 and in http://lightroomkillertips.com/?p=2778
Thanks in advance.

> the problem is that I'm trying to put a "hat" over a consonant
I suspect you'll find that, the more precise and specific your question, the more greater the likelihood of getting a speedy and helpful answer.
> Looks like the software only allows the circumflex over vowels.
> Option-i does work on my computer for vowels. (Built-in
> keyboard).
Nonsense. Nothing to do with your keyboard. Btw, you still haven't told us what character you're trying to insert.
> I guess I will have to use the Equation Editor.
That's an option, but not the only one. Just for the sake of argument, let's assume it's p-hat (not the party hat, but the symbol for sample proportion).
(1) Specifically in Word, you can use fields (overstrike). Go to Insert > Field… > Equations and Formulas > Eq; then type
EQ \O (p,^)
and confirm. (Note that "EQ" will be inserted by Word automatically, you don't need to type it again.)
Once you get the hang of it, you won't need to insert it using menu & submenu commands, but by typing and applying styles.
(2) The right way is Unicode. Currently, Unicode defines >100k codepoints, so, for obvious reasons, it's neither necessary nor practical for most keyboard layouts to be able to access anything but a small subset. You can enter Unicode characters using Character Viewer (aka Special Characters), or, more efficiently, using the Unicode Hex Input keyboard layout.
If the character is already defined as such in Unicode, eg, for all (upside down A), then hold down Option and type its Unicode hex code, ie 2200 -- ∀. However, p-hat isn't defined as such, so it must be entered as a combining character sequence. The sequence is ((Latin small letter p) + (combining circumflex accent)), or (p + 0302) -- p̂.
Unfortunately, all is not sweetness and light. Although this is how it should be done, the display may disappoint. Questions 12b and 12c in the respective Unicode FAQ explain what happens and why.

Deleting text in a file dialog box via simulated keyboard strokes

I am trying to delete text in a file dialog box via simulated keyboard strokes, but the key combination of SHIFT down - HOME - END - SHIFT up does not highlight the text as expected. I attach an example vi that opens its own file open box, enters a text string, which it should subsequently delete. But it is not deleting the text as expected. What do I need to change?
Attachments:
Test_Delete_Text_in_File_Dialog_Box.vi ‏40 KB

Pbuerki,
It looks like you are doing all the keystrokes correctly. My only guess as to why it is not highlighting is that the keybd_event function does not support advanced key code commands. The function is outdated and has been superseded. See the follow MSDN link for more information: MSDN keybd_event.
There are probably some easier ways to accomplish your overall objective. What are you trying to do? Do you simply want to programmatically open a file?
Have a nice day!
Robert Mortensen
Applications Engineer
National Instruments
Robert Mortensen
Software Engineer
National Instruments

Entering extended characters?

As a recentish switcher I'm completely stumped by how I can enter extended characters. I need to enter the character code 0239 to get a special character in a font I'm using. On a PC I'd simply type 0239 on the numeric pad while holding down the Alt key. But that doesn't work on the Mac.
Any help much appreciated. GeoffT.

Most apps have an item in the "Edit" menu called "Special Characters..." which brings up a palette with just about every conceivable character set you could want. That should do the trick, unless the app is so old that it doesn't enable this system-level item. Assuming it works, once you've found the character you want, just click the "Insert" button in the lower-right of the palette to insert it into the active text field.
Here's Apple's description of the same feature:
http://docs.info.apple.com/article.html?path=Mac/10.5/en/8164.html
There are also many longstanding tricks to enter the more common special characters such as curly quotes, emdashes, and accented characters. Here's a very old but still valid cheat sheet:
http://home.earthlink.net/~awinkelried/keyboard_shortcuts.html

French accented characters not translated during decodeIncomingMessage

Hello,
Our b2b.log displays the correct French syntax during the decryption process after receiving message from our partner.
"oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:decryptAndVerify Enter"
example = È
But the French characters translate to ? during the
"oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:decodeIncomingMessage" and
"oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:getPayload"
I tried setting a unix environment variable on the B2B server NLS_LANG=CANADIAN FRENCH_CANADA.WE8MSWIN1252
But this did not help.
Should I also ask the NLS_LANG be set on the database server?
thanks in advance,
Ken

Hello Anuj,
It takes awhile to arrange a change configuration with our IT section and arrange a test message with our partner.
But we did arrange a test a few minutes ago.
The b2b_2.log tip.properties reads as:
-bash-3.00$ grep encoding tip.properties
oracle.tip.adapter.b2b.encoding=ISO-8859-1
#oracle.tip.adapter.b2b.encoding=Cp1252
#oracle.tip.adapter.b2b.encoding=UTF-8
But the b2b.log contains:
-bash-3.00$ grep encoding b2b_2.log
<?xml version="1.0" encoding="utf-8" ?>
2009.10.30 at 15:27:23:186: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.callout.B2BCalloutHandler:processIncomingCallout payload after callout: <?xml version = '1.0' encoding = 'UTF-8'?>
2009.10.30 at 15:27:23:358: Thread-13: Repository - (INFORMATION) BIND VARS = (7720B238D6E7808EE0430AFA0B04808E-11-1, 11, 1, N, , 1070, clob, <?xml version = '1.0' encoding = 'UTF-8'?>
<?xml version="1.0" encoding="utf-8" ?>
<?xml version="1.0" encoding="utf-8" ?>
2009.10.30 at 15:30:59:311: Thread-13: B2B - (DEBUG) oracle.tip.adapter.b2b.callout.B2BCalloutHandler:processIncomingCallout payload after callout: <?xml version = '1.0' encoding = 'UTF-8'?>
2009.10.30 at 15:30:59:368: Thread-13: Repository - (INFORMATION) BIND VARS = (7720B238D6F2808EE0430AFA0B04808E-11-1, 11, 1, N, , 1070, clob, <?xml version = '1.0' encoding = 'UTF-8'?>
<?xml version="1.0" *encoding="utf-8"* ?>
Does this indicate that the encoding did not take effect?
Do we need to remove the commented lines in the tip.properties file?
The accented characters translated to ? in this test (in b2b.log)
thanks
Ken

Entering accented characters via Simulator

Similar Messages

Maybe you are looking for