Character encoding problem. Question mark in a diamond??

I have gotten this a few times before, but it usually fixes when I switch the encoding. This time absolutely nothing is working. In browsers like Safari, you can see what the black diamond and question mark really is. It's just supposed to be an alt-bullet. If I copy and past it, it turns out fine. I included the url of the site affected. My encoding is currently on Western (ISO-8859-1) and the auto detect is on universal. Anyone have a solution

I assume hat you mean this character: • (&#x2022;)
http://en.wikipedia.org/wiki/Bullet_%28typography%29
If you see a Question mark in a diamond then that means that the font that Firefox uses doesn't map that character.
It is in a code block with: font-family: courier new,Verdana,Arial;<br />
You can check those fonts

Similar Messages

Question Mark in black diamond in Safari and Adobe Lightroom

I have a problem with the “question mark in black diamond” phenomenon noted elsewhere in these forums. My problem is different in certain aspects, though, and I’ve found nothing which suggests a way forward in other threads.
I get the “? in black diamond” appearing in two contexts:
(1) in the UI of the Web Module in Adobe Photoshop Lightroom when using the LRG One with PapPal Template (from lightroomgalleries.com), and selecting a currency symbol other than $ (i.e. when using £, EUR, or the Yen symbol)
(2) when viewing web pages generated by the Lightroom Web Module with the PayPal template in Safari
In both these contexts, the currency symbol is displayed as “? in black diamond” in place of the "£" symbol.
The strange thing about this is that when I view the output in other browsers (I’ve tried IE5 for Mac, Camino, Firefox, OmniWeb and Opera), the “£” currency symbol shows up ok. However, it can’t just be a Safari issue, as the “?” shows up in the Lightroom Web Module interface as well.
I’ve posted a screenshot of the Lightroom interface here: http://www.lochaberphoto.co.uk/currency.html , and an example of gallery output here: http://www.lochaberphoto.co.uk/test2/index.html (click on the left-hand thumbnail to bring up the image page and check out the dropdown menu beneath the image).
Before posting here, I’ve tried various forums relating to Lightroom (Adobe Lightroom U2U, lightroomgalleries.com, luminouslandscape.com) but to no avail.
So this is a last chance post: hopefully one of the OS X experts here may be able to suggest a reason for this (is it a font issue? or something to do with UTF-8, or Safari’s default encoding? – I’m not a coder, but I really want to find the answer so I’ll try just about anything…), and maybe a way to solve it. BTW, I get the same experience on my G4 iMac and my MacPro, so I guess it’s not an Intel-specific issue.
Thanks in anticipation for any answers, or follow-up questions
Jim

Hi Tom
Thanks for this. I've tried previously changing the Default encoding in Safari Prefs to Western (ISO Latin 1), but found that did not help.
Following your advice I tried changing encoding from the View menu, and find that the £-sign displays correctly in both ISO Latin 1 and MacRoman (though not in UTF-8). The odd thing about this is that with Default Encoding in the Prefs set to either of those, I still get the ? until I go into the View menu and change from Default to Latin 1 or MacRoman, whereupon the £-sign shows up! Can't imagine how that can be. Tried closing and re-opening Safari after setting Pref to Roman 1, but still need to use the View menu to get the £-sign. Restaring the Mac doesn't help either.
So, Tom, with your help I now have a viable workaround, but as this is going to remain an issue for other Mac/ Safari users visiting my site, I'd like to find a way of preventing it happening. Can you suggest how it can be that Safari needs to be told twice (in Prefs and in View menu) to use ISO Latin 1 or MacRoman before it does so?
Look forward to any further comments
Jim
(P.S.: It seems to me this must be linked to the fact that the ? shows up in the Lightroom interface, and that the fault lies with the PayPal gallery Template I'm using. So I'm wondering if there's anything you - or anyone else - can suggest that I can put to the developer of the Template which will enable him to resolve the issue - he's a Windows user, but has made one suggestion that I adapt the encoding in a file called transformer.xslt from it's default of ISO_8859-15 to UTF-8. I've tried that and tried also ISO_8859-1, but the issue persists regardless.)

Character encoding problem by Gmail set up as exchange account on IOS mail

It was maybe asked before but I could not find any solution. If someone can help I would appreciate it...
If I set up my gmail, which I use very heavily, as Gmail on the IOS mail installation it would be set up as IMAP and does not push the emails. If I choose it to install as exchange account via m.google.com everything is OK and I get my mails instantly. But the way over exchange disturbs because of the character encoding problem. IOS mail does not show me the turkish or some german characters like "ü" and the mail is almost not readable... By version 1 also as IMAP there is no problem with the characters but I must start IOS mail everytime to see if I have new mail...
Does anyone know a solution for it?
Thanks...
Mel

But I cannot set the the gmail app as standart email program, or? I mean if I want to send a page on safari and click send via email, the mail.app would start and not the gmail.app.... I am using Iphone since a few weeks and as far as I know a customisation is not possible.

Apostrophe etc converting to question mark in black diamond

I have read the related threads and do not see an actual answer to the problem other than the suggestion that I turn off Straight Quotes with Smart Quotes which does not make sense as everyone else here has it turned on. I am one user of many on
our system and only a few have this problem. When I send an email it looks fine. When I receive the reply back my apostrophes and 3 dots etc are replaced with a question mark inside a black diamond.

It's related to the character set and character encoding you are using and the easiest, sure-fire fix is to disable smart quotes. Using ISO-8859-1 encoding and a standard font should fix it too, but it may still be a problem for a few recipients. Using the
basic ACSII characters will guarantee it doesn't happen.
What encoding are you using? Look in File, Options, Advanced - near the bottom. Try Western European (ISO), not UTF-8.
What font do you use? Stick with one of the standard fonts.
Diane Poremsky [MVP - Outlook]
Outlook & Exchange Solutions Center
Outlook Tips
Subscribe to Exchange Messaging Outlook weekly newsletter

Why are some websites displayed with added question marks inside black diamonds

Numbers are displayed with question marks inside black triangles before and following, possibly as column separators.
== This happened ==
Every time Firefox opened
== I attempted to access financial websites

Can you post a link?
You can try a few different encoding settings: "View > Character Encoding" like Western ISO-8859-1 or another Western encoding or UTF-8
You can also try to switch on Auto-Detect: "View > Character Encoding > AutoDetect > Universal"
A diamond with a '?' usually indicates that a character is missing in the font that is used on a website or the wrong encoding is used.
You get the '?' on websites that use an 8 bit encoding like ISO-8859-1 or a Windows encoding like Windows-1252.
This issue can happen if content was copied from one 8 bit or Unicode encoding to another encoding.

CF8 MySQL character encoding problems

Having worked with a MySQL 5 database (latin1 charset) with
CF5 with no problems for a long time.
After migrating to CF8 I get question marks ("?") instead of
extended characters (like umlauts ÄÖÜ) when printing
database content to my web page.
The following commands are set in my Application.cfm:
<cfset SetEncoding("form", "ISO-8859-1")>
<cfset SetEncoding("url", "ISO-8859-1")>
<cfcontent type="text/html; charset="iso-8859-1">
My HTML content starts as follows:
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN" "
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="de" xml:lang="de" xmlns="
http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type"
content="text/html;charset=iso-8859-1" />
Environment is WinXP, CF8, default JVM, MySQL3 driver coming
with CF8. Tables are MyISAM format with latin1 character set and
collation.
I cannot use the MySQL4/5 driver so far, since this driver
seems to enforce the STRICT database mode, which collides with some
database content (NULL values got saved as 0000-00-00 etc. as this
project has startet as a MySQL3 database many years ago). (BUT:
MySQL4/5 driver seems to work fine with above settings
I've already tried several combinations of
useUnicode=false;characterEncoding=iso-8859-1;characterSetResults=iso-8859-1
parameters in the "connection string" box of the data source (with
either ";" or "&" as separator) - to no avail.
Any chance I get it up running with the MySQL3 driver?
thanks for any help
Bernhard

quote:
Originally posted by:
brahms_x01
We have the same problem since upgrading to CF 8. I have
found out, that it seems to depend on the encoding type of the
form. <cfform action="rezensent_update.cfm" method="post">
works fine but as soon as we use <cfform
action="rezensent_update.cfm" method="post"
enctype="multipart/form-data"> we get the same problem.
while searching for a solution to my problem came across a
possible solution to your problem: Adobe somewhere writes that you
have to add some encoding information to the enctype parameter. I
don't know the URL of the article anymore, but IIRC it was an
official bulletin of Adobe for internationalization of ColdFusion
projects. Have a google for it.
Bernhard

Elements Organizer Problem - Question Marks and Application Won't Quit Cleanly

I recently upgraded from Photoshop Elements/Premier Elements 11 to version 13 on a Mac. After the upgrade, my elements organizer is experiencing some issues.
1. When I click on a double click on a thumbnail, I am taken to screen that has a large question mark on it. (Not the photo) Elements organizer knows exactly where the file is on my hard drive though as I can edit it in photoshop elements. In addition, I can right click on the thumbnail and select show file Info -> Double click on Location. When I do this I am taken do the correct file in finder.
2. My other issue is that the program doesn't close properly. If I choose Quit from the menu bar, the program GUI closes, but it stays resident in my dock. I have to force close in order to open the organizer again.
Any help would be greatly appreciated.
Thanks!
Ben

Trying renaming your contacts.xml file. To access the file, you need to go - Macintosh HD/Library/Application Support/adobe/elements organizer/organizer/settings I just named it "renamedfile.xml". A new contacts file will appear after you reopen the program.
I've had this problem a few times and renamed this file (after a support person from Adobe told me to the first time). It opens after I remaned it.
The contacts function of the organizer doesn't seem to be a stable. It always deletes entries that I want to add in.
Hope this helps

Character encoding problem using XSLT and Tomcat on Linux

Hi,
I have an application running on a Tomcat 4.1.18 application server that applies XSLT transformations to DOM objects using standard calls to javax.xml.transform API. The JDK is J2SE 1.4.1_01.
It is all OK while running on a development enviroment (which is Windows NT 4.0 work station), but when I put it in the production enviroment (which is a red hat linux 8.0), it comes up with some kind of encoding problem: the extended characters (in spanish) are not shown as they should.
The XSL stylesheets are using the ISO-8859-1 encoding, but I have also tried with UTF-8.
These stylesheets are dynamicly generated from a JSP:
// opens a connection to a JSP that generates the XSL
URLConnection urlConn = (new URL( xxxxxx )).openConnection();
Reader readerJsp = new BufferedReader(new InputStreamReader( urlConn.getInputStream() ));
// Gets the object that represents the XSL
Templates translet = tFactory.newTemplates( new StreamSource( readerJsp ));
Transformer transformer = translet.newTransformer();
// applies transformations
// the output is sent to the HttpServletResponse's outputStream object
transformer.transform(myDOMObject, new StreamResult(response.getOutputStream()) );Any help would be appreciated.

Probably you need to set your LANG OS especific environment variable to spanish.
Try adding this line:
export LANG=es_ES
to your tomcat/bin/catalina.sh, and restart tomcat.
It should look like this:
# OS specific support. $var _must_ be set to either true or false.
cygwin=false
case "`uname`" in
CYGWIN*) cygwin=true;;
esac
export LANG=es_ES
# resolve links - $0 may be a softlink
PRG="$0"
.(BTW, keep using ISO-8859-1 encoding for your XSL)
HTH
Un Saludo!

c:import character encoding problem (utf-8)

Aloha @ all,
I am currently importing a file using the <c:import> functionallity (<c:import url="module/item.jsp" charEncoding="UTF-8">) but it seems that the returned data is not encoded with utf-8 and hence not displayed correctly. The overall file header is:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=E67F9DAF44C7F96C0725652BEA1713D8;
Content-Type: text/html;charset=UTF-8
Content-Length: 6861
Date: Thu, 05 Jul 2007 04:18:39 GMT
Connection: close
I've set the file-encoding on all pages to :
<%@ page contentType="text/html;charset=UTF-8" %>
<%@ page pageEncoding="UTF-8"%>
but the error remains... is this a known bug and is there a workaround?

Partially, yes. It turns out that I created the documents in eclipse with a different character encoding. Hence the entire document was actually not UTF-encoded...
So I changed each document encoding in Eclipse to UTF and got it working just fine...

Character encoding problem

          We are using WebLogic 7.0 SP4 on Solaris 8 w/ jdk131_10. By default we don't specify
          the "encoding" jsp-param of the jsp-descriptor in the weblogic.xml. The BEA documentation
          says "If not set, this parameter defaults to the encoding for your platform."
          Without setting this value, certain characters in our JSPs are converted just
          fine in our test environment but become "weird" characters in our production environment.
          Question 1: Where exactly is the encoding of the "platform" specified?
          So I figured we just had to specify the encoding to be UTF8, right? Well when
          we do that, everything is still fine in test but in production we get the following
          exception when WebLogic tries to compile a JSP.
          weblogic.utils.ParsingException: nested TokenStreamException: antlr.TokenStreamIOException
          at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:964)
          at weblogic.servlet.jsp.JspParser.doit(JspParser.java:90)
          at weblogic.servlet.jsp.JspParser.parse(JspParser.java:213)
          at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:119)
          at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
          at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:356)
          at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:214)
          at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:164)
          at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:534)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:364)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:462)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
          at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
          at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
          at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
          at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
          Question 2: Any ideas why this exception is happening?


Conrad Armstrong wrote:
          >
          > We are using WebLogic 7.0 SP4 on Solaris 8 w/ jdk131_10. By default we
          > don't specify the "encoding" jsp-param of the jsp-descriptor in the
          > weblogic.xml. The BEA documentation says "If not set, this parameter
          > defaults to the encoding for your platform." Without setting this value,
          > certain characters in our JSPs are converted just fine in our test
          > environment but become "weird" characters in our production environment.
          >
          > Question 1: Where exactly is the encoding of the "platform" specified?
          >
          > So I figured we just had to specify the encoding to be UTF8, right? Well
          > when we do that, everything is still fine in test but in production we get
          > the following exception when WebLogic tries to compile a JSP.
          >
          > weblogic.utils.ParsingException: nested TokenStreamException:
          > antlr.TokenStreamIOException
          > at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:964)
          > at weblogic.servlet.jsp.JspParser.doit(JspParser.java:90)
          > at weblogic.servlet.jsp.JspParser.parse(JspParser.java:213)
          > at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:119)
          > at
          >
          weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
          > at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:356) at
          > weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:214) at
          > weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:164) at
          >
          weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:534)
          > at
          >
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:364)
          > at
          >
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:462)
          > at
          >
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
          > at
          >
          weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
          > at
          >
          weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
          > at
          >
          weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
          > at
          >
          weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
          > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
          >
          > Question 2: Any ideas why this exception is happening?
          The platform encoding is the one returned by the system property
          file.encoding => System.getProperty("file.encoding")
          Probably you are developing on windows and deploying ('production') on
          solaris? In that case the default file encodings on each os are different
          and that may be causing the problem here. (On windows the default is cp1252
          i think)
          Typically, are all your jsps more or less iso-8859-1? then you can set this
          encoding in weblogic.xml. I believe the default encoding on solaris is
          "ISO-8859-1" (You can check this by writing a simple jsp which prints out :
          Encoding : <%= System.getProperty("file.encoding") %>
          Hope that helps.
          Do let me know what you find
          --Nagesh

Character encode problem

how can i encode turkish character �� .in j2me. � can connect my xm l file via IIS server by using inputStream class. but when � use readUTF() method in DataInputStream class to read file ,null pointer execption occur but not read method in Data�nputStream. thanks for advance

here is my code ;
StreamConnection c=(StreamConnection) Connector.open(URL);
InputStream is=c.openInputStream();
StringBuffer buffer = new StringBuffer();
int ch;
while ( (ch = is.read()) != -1) {
buffer.append((char)ch);
is.close();
wordsXML=buffer.toString();
i can not read turkish character truely . can you give sample code to overcome this problem.

XML special character/encoding problem

Hi
I would like to store XML in a MSSQL database into a column with the datatype xml.
It seems like the xml datatype in an xMII transaction allways is stored with encoding type UTF-8
and the MSSQL xml datatype is UTF-16. This gives me some problem with special characters when inserting into the MSSQL database (in the example below is the MSSQL datatype xml):
INSERT INTO
VALUES
The error returned is this:
"com.microsoft.sqlserver.jdbc.SQLServerException: XML parsing: line 1, character 62, illegal xml character"
If I replace the 'ä' with a normal 'a' the command executes ok.
I am currently using a workaround that looks like this, when setting the parameter in my transaction:
stringreplace(Local.test, " encoding=" & doublequote & "UTF-8" & doublequote, "")
But I was hoping I could get rid of the stringreplace.
Is there a solution / recommended way of doing this?
Best Regards
Simon Bruun
Edited by: Simon Bruun on Mar 4, 2011 10:43 AM

I solved this. I convert to Unicode UTF-8

Character encoding problem in deployed version

Hello,
I developed an ADF/jspx application in JDeveloper. When I'm running it in the embedded OC4J or the stand-alone OC4J, everything works well.
But when I deploy it into OAS 10.1.3 and run it, the special characters (in my german case for example "ü", "ö" and so on) are not shown. Instead some kind of place holder is displayed.
I checked the project's settings and parameters in web.xml and the jspx's, and all are set same to windows-1252. The NLS-LANG parameter in the registry of the server is also set to WE8MSWIN1252 (seems to be ok in my opinion).
Is there any further "place" for me to check the used encoding of OAS when displaying deployed pages?
Thank you very much!
Sebastian

I have just solved the problem.
In my servlet I had to add :
request.setCharacterEncoding("UTF-8");And thats it.

Character encoding problems with weblogic stax implementation?

Hello all,
While using Stax to parse some XML, we encounter the following exception when the processor reaches the UTF-8 character C3 B1, ('ñ'):
Caused by: Error at Line:1, token:[CLOSETAGBEGIN]Unbalanced ELEMENT got:StudentRegistration expected:LastName
at weblogic.xml.babel.baseparser.BaseParser.parseSome(BaseParser.java:374)
at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:199)
We suspect that the processor's encoding might somehow be set to ANSI instead of UTF-8. I have read, in other posts, of a startup property related to web services:
-Dweblogic.webservice.i18n.charset=utf-8
However, this XML is not a web service request, but rather a file being read from disk after an MDB's onMessage() method is called.
Could this setting be affecting stax parsing outside of webservices? Any other ideas?
Thanks!

As far as I know, we don't support changing outbound message encoding charset in 9.x. Both 8.x and 10.x support it. Check [url http://docs-stage/wls/docs100/webserv/client.html#wp230016]here

Character encoding problem (I think)

Hello everyone! I hope you can help me out with this problem:
I have noticed just today that my RSS feeds in Safari come out gibberish, almost like the font Helvetica fractions, and changing the encoding does not fix it.
I thought I can live with that for now, but I noticed the same problem in Mail as well, but only characters in the message window. When I get a mail or when I compose one. Any ideas of what to reset? I ran permissions repair and no fix. I'm totally stumped!
Thanks

UPDATE: It is using Helvetica Fractions! The setting in MaiI preferences is the default and ok, but I clicked Command+T and noticed it had Helvetica Fractions selected. I changed it and it is ok for composing messages, has not fixed what the text is in some of my in box messages.
I use Linotype Font ExplorerX but have not since this problem occured. My RSS feeds are still unreadable, as are some web pages. I have cleared out the old feeds but that did nothing.

Character encoding problem. Question mark in a diamond??

Similar Messages

Maybe you are looking for