Accented characters don't display

Forum search yielded somebody advising ttf-bitstream-vera, so I installed that and restarted X, but the problem persists.
Any ideas?
Last edited by henrysmith (2007-07-15 18:12:22)

DejaVu didn't fix it.
[henry@arch ~]$ locale
LANG=en_US.utf8
LC_CTYPE="en_US.utf8"
LC_NUMERIC="en_US.utf8"
LC_TIME="en_US.utf8"
LC_COLLATE=C
LC_MONETARY="en_US.utf8"
LC_MESSAGES="en_US.utf8"
LC_PAPER="en_US.utf8"
LC_NAME="en_US.utf8"
LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT="en_US.utf8"
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=

Similar Messages

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

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

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

Math fonts don't display in mail messages?

For some reason when I receive a mail message with math - fractions, equations, etc. these characters don't display. My husband has an iPhone 4 and this isn't a problem on his phone. I am wondering how I can get these characters to display?
Thanks

Hi markatos
Hi Rick Van Vliet
I have the same problem, and I can also (only) underline text.
Since upgrading to Tiger (10.4.8) from Panther 10.3.9, I have experienced a few daft functional problems, eg the 'Enter' key not working on the calculator (the standard one, not the Dashboard version). This turned out to be a '.plist' problem.
Mail was marking all outgoing mail as 'Junk' ... '.plist' problem again.
But I cannot see how to sort this one ... at the moment I am having to format text on a Stickie then paste it into a Mail message in order to do simple things like bold headings (I don't need any more than this really). So the 'Font' palette is working. Message format is set to 'Rich Text'.
Any ideas anyone?
Help will be appreciated.
Thanks in advance.
Paul

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

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.

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

Chinese characters are not displayed in the Firefox bookmarks

Chinese characters are not displayed in the Firefox bookmarks. The name looks like e.g. "??????? ???? cn.nytimes.com"
Chinese character of the site name is displayed ok in the head of the browser window and there is no problem reading chinese web content. I use Firefox Portable 11 /English from portableapps.com in Windows XP.
I googled and got some tips:
1) Set your browser to recognise Chinese language internet sites.
Windows users: Under "Tools - Options" on your browser's menu-bar add Chinese to the languages list.
- I did this.
2) Set your browser's "Character Set" or "Encoding" to UTF-8 (sometimes also called Universal Alphabet or Unicode).
Encoding settings can be changed under the "View" option in your browser's menu-bar.
- It was already set to UTF-8.
3) Windows users: If Chinese text still does not display correctly, East Asian language support may need to be enabled.
- This has been done when I installed Windows.
I still don't get any Chinese fonts in the bookmark names. I can edit the bookmark name with chinese characters and then save the bookmark, it works fine. But why does not Firefox recognize the characters when saving bookmarks? Help is appreciated.

No I didn't change anything deep beneath the hood. My problem didn't apply to the URL, but to the name of the link or bookmark header or whatever you would like to call it. (When hitting Ctrl + D there is a Name field). I only got ???????? instead of chinese characters in the name. Also for e.g. www.cntv.cn ...but maybe all China is not in the whitelist either. ;-) But anyway, this was not the real problem for me.
Apparently I was wrong as after a reboot of the computer it worked. The solution seemed to be to add Chinese to the language list. I don't know why it was not enough to restart Firefox?
Now I only have problems to show chinese characters in the name field of my external link manager... But I guess it is not an issue for Mozilla.

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

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

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

How to load CSV with accented characters?

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

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

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 don't display

Similar Messages

Maybe you are looking for