Search the accented characters

Hello everyone,
We have a column, which has the accent. But when we do the search we'd like to use the unaccented character.
For example, when we type in "ALKARAKPEI", we want to get "ALKARAKPEI" and "ALKARAKPËI".
ALKARAKPËI => ALKARAKPEI
DIKPÖR => DIKPOR
Please give me some suggestion and ideal...
Thanks in Advance!!!

another way,you won't get exact results this way:
SQL> with t as (select 'ALKARAKPËI' str from dual
           union all
           select 'DIKPÖR' str from dual)
select str
from t
where (soundex (str) = soundex ('ALKERAGPEI'))
       or (soundex (str) = soundex ('DOKPUR'))
STR
ALKARAKPËI
DIKPÖR
2 rows selected.

Similar Messages

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

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

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

Accented characters on windows the mac way

It took me a while to write the accented characters in mac. For instance, option-E for acute, then vowel: like, opt-e then a= á
Now, I need windows for a series of reasons. However, I cannot make windows behave like this. I want windows to show the exact same behavior. What can I do?

You can't do it exactly like the Mac, but pretty close. You have to switch your keyboard layout to US International: http://support.microsoft.com/kb/97738

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

Portuguese Accent characters in file name

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

hi,
Did you check your accent characters file from instances? I suggest you could login on RDP and check the file name whether is same as your local. You could find file follow this way:
login on VM==>>open the local Disk==>>siteroots>>0
Also, you could add the Portuguese language into your isntacnes language list. And change your VM page name as your local page name . And then try to visit using the
accent characters file name. Please try it.
Also, you could try to install the language pack for azire (http://social.technet.microsoft.com/Forums/windowsazure/en-US/75d5c1c8-31bb-4431-97ae-a8b80098a9c6/net-framework-45-language-pack-for-azure-web-role-os-family-3-windows-server-2012?forum=windowsazuretroubleshooting ).
Any update info, please let me know free.
Regards,
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Accented characters do not display correctly if there is a variable beside it

Hello,
We are experiencing a problem when we have text with accented characters an a variable beside it within the same text box.
The problem is that the accented characters in the text do not display correctly in the preview or publised course to Flash9
These characters display correctly in Captivate in edit mode.
This is the process we have followed:
Export to XML
Translated
Import XML
Publish to Flash9
Captivate version: 4
OS: Windows Vista SP2
We have tried to work with locale in Spanish with no luck, the only solution we have found is to put the text and the variable in different text boxes
I have pasted an image of the preview and also of the text in Captivate edit mode.
Any help will be very welcomed !
Tess

Hi there
I agree with Lilybiri that you should definitely file a Bug Report.
However, a thought occurs here. Have you tried placing the accented text in a User Defined variable?
Assuming this is a workaround, my thought is that you could then just have a caption with two variables. The User Defined variable containing the accented text followed immediately by the system variable providing the Project Name.
Cheers... Rick
Helpful and Handy Links
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcerStone Blog
Captivate eBooks

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

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.

Migrating from MySQL to Oracle 11gR2 containing accented characters

Hello Gurus,
I am going to migrate a MySQL database that contains accented characters. The collation of the tables holding these data is utf8_unicode_ci.
I used SQLDeveloper to generate data migration scripts. After a test migration run, the web pages displays "?" instead of the accented character.
I am currently tracing where the problem is.
From what I have read, mysqldump uses utf8 as the default character set, so I assume the accented characters in <tablename>.txt files are in tact.
Could the problem be on sqlldr? Has anyone come across this problem?
I really would appreciate any help.
Thanks

Hi Srini, thanks for the reply.
here is the result of select * from nls_database_parameters;
PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET AL32UTF8
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 11.2.0.1.0

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.

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

WE + CE cause problem with accented characters

While creating a CFF font which contains the WE as well as the CE character set, it causes problems with most of Adobe programs (Photoshop 7, Illustrator 10, Photoshop Elements 2.0) under Mac OS X. Problem: the accented characters get replaced by Helvetica (Photoshop) or Myriad (Illustrator). Only InDesign treats it right.
I tested under Mac OS X 10.2 as well as 10.3; no difference. I tested on 'old machines', but fresh machines as well (machines which didn't have the fonts installed before); no difference. All the same problem.
Deleting the CE characters solves the problem, but yeah, I want to create a CFF font which contains both character sets.
Generating the font in FontLab or FDK doesn't make any difference.
So, what's the solution? Sounds like a mystery.
Bas

Two comments:
OpenType/CFF fonts should work to some degree on versions of Mac OS from 8.x on. "Some degree" means that pre-Mac OSX, you need ATM for them to work, and you only get the Roman char set. On Mac OSX, Unicode savvy apps will give you access to the entire charset, but at the moment only Adobe apps support any OpenType features.
About your problem with CE charset: this is a known problem, and is still a mystery. Adam Twardoch has reported the same problem and has supplied some test fonts. I have spent over a day looking over the fonts, and looking into old code, and can't find any problem in the font data. Investigating further is likely to be a several day effort, and will happen, but not soon.

Accented characters copied into design view not converting in code mode?

Hello!
I just upgraded from Dreamweaver MX to CS6 (patched to v12.0.3) and am having a problem with French characters. In the past, I copied text that contained accented characters like "é" and, when I pasted it into the Design window, I could see in the Code window that the accented characters would be converted into "& eacute;" (without the space) so that it would show up properly in all broswers. This doesn't seem to be the case with CS6 - it is just pasting the "é". This is a very large problem for me - does anyone know how I can restore whichever setting it is that will cause the paste function to work the same way it did in DW MX?
I've tried playing with the settings in Edit --> Preferences --> Code Rewriting and with New Document --> Default Encoding, but I guess I just haven't found the right combo to get it to work.
Any help would be appreciated!
Thanks,
-Cherie

If I understand it correctly, it doesn't. I know that modern browsers would be able to understand the characters if it is encoded with UTF-8, but I need older browsers and adaptive technologies to be able to understand the accented characters, so I don't think I can go with UTF-8 yet.

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

Issue with ENEQuery java api and searching terms with accented characters

Hi,
we are using ENEQuery to query the mdex engine. When search terms contain accented characters (like á,í etc), even though the terms are decoded (using java.net.URLDecoder), the term gets send to dgraph is encoded. for e.g a search for "sofá", from the dgraph logs "sof%c3%a1" and fetch in 0 results
ENEQuery query = new ENEQuery();
final ERecSearchList searches = new ERecSearchList();
final ERecSearch eRecSearch = new ERecSearch("search interface name", "term");
searches.add(eRecSearch);
query.setNavERecSearches(searches);
Any suggestions?
Thanks

Hi,
Does your indexed data (which you hope to match) contain "sofá" or "sofa" (no diacritic)? If the latter, and in-general, you may benefit from the dgidx flag --diacritic-folding* as described in documentation "Mapping accented characters to unaccented characters". If you are running the latest version, this is all that should be required to generate a match.
Best
Brett

Search the accented characters

Similar Messages

Maybe you are looking for