Basically, I've read a few threads when I had trouble getting German special characters like ü,ö,ä,ß to show up when a user uses them in a submission title.   To say the least, they look like this: Ã¼Ã¶Ã¤Ã�  Turns out the database collation was wrong for these types of characters (or so I've read) the collation was latin1_swedish_ci, and I've read to change it to u8_general_ci or utf8_unicode_ci. Well I've tried both but on submission to the database by a user, the title with special characters still shows up the same, all messed up like above.  I guess my question is, what am I doing wrong? Is there an extra step I've missed to get these characters to show correctly? I've never worked with German translation before this particular project, and this is my first time with this. So any help would be fantastic.
326
I'm setting up a new server and want to support UTF-8 fully in my web application. I have tried this in the past on existing servers and always seem to end up having to fall back to ISO-8859-1.  Where exactly do I need to set the encoding/charsets? I'm aware that I need to configure Apache, MySQL, and PHP to do this — is there some standard checklist I can follow, or perhaps troubleshoot where the mismatches occur?  This is for a new Linux server, running MySQL 5, PHP, 5 and Apache 2.
118878
So I have been wondering for a while now what these entries are and what they do, also what the format of them are. They look similar to JSON but are definitely not JSON.   a:1:{s:12:"jetlocations";a:2:{s:5:"label";s:12:"JetLocations";s:4:"type";s:6:"editor";}}   I have searched to try and find out what these might be but come up with nothing.
114295
What are the valid characters to use in labels? I thought that only alphabetic characters were valid, but I tested ' and ! and they work. What are the restrictions to these names?
118141
Too often I messed with bad formated BibTeX files from references databases that are infected with active characters  as % or &amp; (usually in the abstract, that is not printed but produce an error anyway) but I can live with this inconvenient and replace those by with \% or \&amp;.   Also with some input encoding errors due to some UTF8 character that cannot be managed by pdflatex. In references this error is more disturbing that in the main text, but in best cases, is only change some greek letter as γ. In others is the insidious zero width U+200B, but with I can search and replace even this character.    The worse for me is the obnoxious U+301, specially when is not in over a consonant but hiding in vowels as normal acute characters, that are perfectly managed using inputenc, i.e., the   normal e character (U+0065) plus U+301 look exactly like the kind é (U+00E9) and so on with á, Á, í, etc., so if is hard detect the poisonous diacritic mark.   Disappointingly, search U+0065 plus U+301 find also the single character U+00E9 and vice versa in some editors, so I ended with the pain of searching &amp; replacing every accented letter (single or double) with the single character versión.    So the question is specifically is: There are clevers ways to sanitize .bib files with U+301 tildes?   (Of course, a more general answer, covering some automagic cleaning of all unrecognized and active characters will be welcome.)  The minimal (not) working example:   \documentclass{article} \begin{filecontents}{test.bib} @article{xx, author={González, M. and Ruíz, P.} title={Mañana hará calor &amp; bochorno con un 90% de humedad} }    \end{filecontents} \usepackage[utf8]{inputenc} \usepackage[T1]{fontenc} \usepackage[spanish]{babel} \begin{document} Hello  \cite{xx} \bibliography{test} \bibliographystyle{plain} \end{document}
78105
This is what I would like to do:  morekeywords={SENÃO, ENTÃO, FAÇA, ATÉ, ENQUANTO, PARA, SE, DECLARA, DECLARE, E, OU, FIM_ENQUANTO, FIM_PARA}   I'm defining a new language, and I would like to use natural language words as keywords.  The problem is with keywords: SENÃO, ENTÃO, FAÇA, ATÉ.  I have solved the first problem, in showing special chars with:   The alsoletter here, doesn't work for me, I got an error when using it: alsoletter={Ç,É,Ã}.  test.tex  \documentclass{article}  \usepackage[brazilian]{babel} \usepackage[T1]{fontenc}  \usepackage[utf8]{inputenc} \usepackage{listingsutf8}  \usepackage{listings}  \lstset{%         inputencoding=utf8,         extendedchars=true,         literate=%         {é}{{\'{e}}}1         {è}{{\`{e}}}1         {ê}{{\^{e}}}1         {ë}{{\¨{e}}}1         {É}{{\'{E}}}1         {Ê}{{\^{E}}}1         {û}{{\^{u}}}1         {ù}{{\`{u}}}1         {â}{{\^{a}}}1         {à}{{\`{a}}}1         {á}{{\'{a}}}1         {ã}{{\~{a}}}1         {Á}{{\'{A}}}1         {Â}{{\^{A}}}1         {Ã}{{\~{A}}}1         {ç}{{\c{c}}}1         {Ç}{{\c{C}}}1         {õ}{{\~{o}}}1         {ó}{{\'{o}}}1         {ô}{{\^{o}}}1         {Õ}{{\~{O}}}1         {Ó}{{\'{O}}}1         {Ô}{{\^{O}}}1         {î}{{\^{i}}}1         {Î}{{\^{I}}}1         {í}{{\'{i}}}1         {Í}{{\~{Í}}}1 }  \lstdefinelanguage{pseudo} { extendedchars=true, alsoletter={_}, morekeywords={ENQUANTO,PARA,SE,SEN\~{A}O,ENTÃO,ATÉ,FA\c{C}A,DECLARA,DECLARE,E,OU,FIM_ENQUANTO,FIM_PARA,FAÇA}, ndkeywords={NUMERO,TEXTO,LEIA,ESCREVA}, sensitive=true, morecomment=[l]{//}, morecomment=[s]{/*}{*/}, morestring=[b]" }  \begin{document} \lstinputlisting[language=pseudo]{foo.pseudo} \end{document}   foo.pseudo  ENQUANTO nota != -1 FAÇA // Comment example  LEIA nota  SE nota &gt;= 7 ENTÃO    ESCREVA "Aprovado"  SENÃO    ESCREVA "Reprovado"    TEST "Algo mais" /* mais  comentário */  FIM_ENQUANTO    I have seen:
119350
I am writing a new custom keyboard layout for Xorg, but there is one particular glyph which does not exist in Unicode. It is, however, easy to create it by using a standard letter plus a combining diacritic mark.  For example, if I want the letter v with a macron below, the sequence U0073+U0331 creates the character that I want.   In my xkb layout definition, I can specify a single Unicode point (here altgr+d is bound to ḏ and altgr+shift+d to Ḏ):  key &lt;AC03&gt;  { [         d,          D,        U1E0F,        U1E0E ] }; // d with macron below   But I don't seem to be able to specify a 'combined' Unicode glyph for a single key:  key &lt;AB04&gt;  { [         v,          V,  U0076+U0331,  U0056+U0331 ] }; // v with macron below   Is it possible to create a system-wide xkb definition like this?
98690
Let's say I open a webpage with some Unicode characters, say, Cyrillic, in the address like this:        When I try to copy it from the address bar somewhere else, it becomes unreadable rubbish:        I guess this is for compatibility. However for readability I want to copy it straight away with proper Unicode characters.  What and how should I tweak to make that possible?  Edit: The answers are good, but they are hacky. Are there any settings in about:config?
48124
How are people showing keyboard &quot;glyphs&quot; on Super User? I looked at the Markdown help page and it didn't show anything regarding this. Here is  (question has been deleted since this was asked, so an archive link is provided instead):
21330
I work in Linux with the latest TeX Live. The system encoding is UTF-8. It is also the default editor encoding in my TeXstudio 2.12.8.  I have figures in files like σ_1_μ_02_per_5.tikz, and I included them using \input{}.   Now, the most interesting part: it had worked fine (even without inputenc etc), then it just stopped. I have not change a single line in my files. Now I get  Package inputenc Error:  Unicode character σ (U+3C3)(inputenc) not set up for use with LaTeX. ...σ_1_μ_02_per_5.tikz   I have tried:   using babel inputenc with utf8, utf8x, latin1 fontenc with different parameters opening and saving in UTF-8 in other editors   And in this case I get:  Undefined control sequence. ...μ_02_per_5.tikz} Missing $ inserted. ...μ_02_per_5.tikz} Double subscript. ...μ_02_per_5.tikz} Undefined control sequence. ...μ_02_per_5.tikz}   How to fix this?    Minimal not working example:  \documentclass[10pt,a4paper]{article} \usepackage[utf8]{inputenc} \begin{document}     \input{1.tex}     \input{σ.tex} \end{document}
93719
I'm struggling with the design of new database that has to use a different collation (Y Collation) than the SQL Server Instance default collation (X Collation). I'm looking for potential problems.  Temp Tables by default will be created with X Collation so any joins on text data types will fail unless I create temp table with Y collations on columns.  What about SQL Server string functions: REPLACE, SUBSTRING, etc.? Will they always be returned in X collation? What about when I use REPLACE(...) COLLATE Y? Do you see any potential data loss or maybe any different problems?
16765
Trying to find myself on the  I run into weird results. My display name is "Erwin Brandstetter", obviously.  If I type Erwin, I find myself in the search results. If I type Branst, I find myself in the search results. If I type Erwin B or even Erwin Brandstetter, I am not found.  Tried the same with Jon Skeet or Brad Larson and others, no problem. Works either way. Tried the same on a couple of SE sites. Same effects everywhere. Here on meta, too.  Seems broken to me?
30050
I am aware that this might not be the ideal place please move/close this if so.  So since yesterday I run into the following problem:  I use \usepackage[T1]{fontenc} and \usepackage[utf8]{inputenc} in the preamble and save the document in TeXShop accordingly as a UTF-8 encoded file.  As soon as I close the document and open it anew the document is now of type applemac and obviously the special characters are all different. Now this only seems to happen for new document because I wrote my thesis with the same preambel and there when I open it it is still a UTF-8 encoded document.  I really have no idea what's going on. Has anyone ever experienced something similar?
108707
You can search for anything on Google, right? At least, so I thought. I was trying to see how the special characters get encoded in the url, like how &amp; gets converted to %26. I started searching for *. It did not get encoded, but weirdly google didn't tell me that it was an asterisk symbol. All other search engines (yahoo, bing, duckduckgo) did.   See for yourself : . Basically it treats it as a regular expression. So *+* will also not give any results. Still, shouldn't Google at least say that * is the asterisk symbol.  I don't know where else to ask this question, so I came to SO.
28362
I want to have my sections in independent .txt files in the folder of my assignment. So I use \input{text.txt}. The problem is, I write in Danish and we have the 'æ' 'ø' 'å' characters that aren't normally recognized by LaTeX. I fixed it within the master .tex file, so when I write the letters, it shows up nicely in my document. It does not however show up nicely, if I put one of the characters in the file name or within the .txt files. Now, I don't mind that I have to avoid them in file names, but I really need them to be recognized within the file.  \documentclass[10pt,a4paper]{article} \usepackage[danish]{babel} \renewcommand{\danishhyphenmins}{22} \usepackage{lmodern} \usepackage[T1]{fontenc} \usepackage[utf8x]{inputenc} \usepackage[danish=quotes]{csquotes}  \begin{document} æ ø å \input{text.txt} \end{document}   I can't upload the .txt file, but if you copy the three letters, put it in a document called text.txt file and put it in the folder, you'll see what I mean.  If I delete \input{text.txt} from the document, or avoid using those three letters in the input file, everything works perfectly and it writes 'æ ø å' in the output file.  I asked this question on another forum, but they weren't much help. They talked about it being the wrong encoding and told me, that if I saved it as .tex files there would be a dialogue that would enable me to change the encoding of the input document so it would be compatible, however there is no such thing in the 'Save as' dialogues I get from TeXworks. I also have it set to utf8 in my preferences in TeXworks, however that doesn't seem to influence much of anything.
61891
I am trying to get a ẞ in my LaTeX document. How can I do this? I already tried:   Using other fonts: dejavu and libertine Using \MakeUppercase{ß}, which sometimes produces nothing, sometimes produces "SS" Using {\sc ß}, which sometimes produces nothing, sometimes produces "SS" Using XeTeX and lualatex: Just leaves out ẞ and warns about the Glyph that it could not find Using \symbol{"1E9E}, which also produces nothing   How can I do this?
6999
For some strange reason, my computer suddenly doesn't show certain unicode characters anymore! I have no idea what happened.  Affected applications include Windows Explorer (should be Japanese characters), Google Chrome (should be a heart), and Winamp (should be stars):      Russian, German etc. characters are displayed normally. Chrome also displays Japanese script on websites, but not in the GUI. How can I fix it?     TL;DR: A workaround is to put a shortcut with a Unicode name on the desktop so that explorer.exe is the first process to display a Unicode string after booting.     Update: I have tried to use System Restore to fix it. I needed to go back in time quite a while because the most recent restore points didn't solve it so I used one from the middle of November. After that restore, Unicode symbols were displayed again. Then I updated my system with Windows Update again because those were removed during the restore. After that, the error occurred again! I then did a restore to a point before my new updates, but the error persists, and the old restore point (which I used before) is gone and there are currently no other snapshots of the system. Any suggestions on what to do now?  Update 2: I could find a workaround:      Control Panel → Region and Language → Administration → Change Language for Unicode-incompatible programs to Japanese (Japan).    All mentioned programs display their symbols correctly again. However, I don't consider this a fix because these programs are not usually Unicode-incompatible, and it also leads to some (non-serious) artifacts in some programs. I still welcome an answer that tells me what went wrong here and how to fix the issue.  Update 3: I think I have isolated the particular Windows Update which causes the error. It is . I have installed all other updates except this one, and the error did not occur again.  Update 4: The true origin of this problem was Chrome, see accepted answer. Workaround: put shortcut with Unicode name on desktop so that explorer.exe is the first process to display a Unicode string after booting.
44199
I'm in Belgium (french part) and I cannot find the proper keyboard layout in Settings > Region and Languages > Input Sources.  the closest I found is the french (AZERTY) one but for the symbols such as ! and _ it's not the same keys...  what can I do to solve it ?  Thank you.