I am using a  that fixes encoding issues with the text. It has been working great until I deal with a curly apostrophe ’.  Sometimes in my database, a column field will contain words with these curly apostrophes instead of straight ones. The UTF8 converter I am using for whatever reason will convert it from  you’ll   to  you?ll   Anyone have any wisdom that points me in the right direction as to why this is happening. I am not that familiar with encoding issues.
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.
105397
I use some packages with require utf8. Here is the main file:  \documentclass[a4paper,titlepage]{report}  \usepackage[utf8]{inputenc} \usepackage[T1]{fontenc} \usepackage[american]{babel} \usepackage{csquotes} \usepackage[backend=biber,style=alphabetic]{biblatex} \addbibresource{refs.bib}  \begin{document} \nocite{*} \printbibliography[heading=bibintoc] \end{document}   And here is the reference file:  @MISC{Example,     author = {Author with spec\'{\i}al character},     title = {Title} }   I have no issues with composing special characters like \H{o} (ő) or \k{a} (ą). However, when I try to compose \'{\i} (í), I get the following inputenc error: "not set up for use with LaTeX". It seems like double compositions are not allowed. A solution is to use \'{i} instead, but not removing the dot is ugly. Surely there must be a better way?  Note: I have tried to add \DeclareUnicodeCharacter{00ED}{\'{\i}} to the preamble, but it doesn't help either.
69352
Hi I was translating one of my plugins in "CodeStyling Localization". when I update my plugin my translation erased. Is there anyway to find it ? And How can I backup my translation (I don't want to waste my time next time :))
112694
What mysql functions are there (if any) to trim leading zeros from an alphanumeric text field?    Field with value "00345ABC" would need to return "345ABC".
87083
Here's the problem:  In C# I'm getting information from a legacy ACCESS database. .NET converts the content of the database (in the case of this problem a string) to Unicode before handing the content to me.  How do I convert this Unicode string back to it's ASCII equivalent?   Edit Unicode char 710 is indeed MODIFIER LETTER CIRCUMFLEX ACCENT. Here's the problem a bit more precise:     -> (Extended) ASCII character ê (Extended ASCII 136) was inserted in the database.  -> Either Access or the reading component in .NET converted this to U+02C6 U+0065     (MODIFIER LETTER CIRCUMFLEX ACCENT + LATIN SMALL LETTER E)  -> I need the (Extended) ASCII character 136 back.    Here's what I've tried (I see now why this did not work...):  string myInput = Convert.ToString(Convert.ToChar(710)); byte[] asBytes = Encoding.ASCII.GetBytes(myInput);   But this does not result in 94 but a byte with value 63... Here's a new try but it still does not work:  byte[] bytes = Encoding.ASCII.GetBytes("ê");    Soltution Thanks to both  and  for pointing in the right direction I solved the problem .
99906
One of the responses to  suggested that I should make sure my database can handle UTF-8 characters correctly. How I can do this with MySQL?
103952
I sometimes see weird characters on some websites instead of what they're meant to display. I've attached an image below as an example. In IE the site displays correctly but on Chrome there are weird characters instead.  My encoding settings on Chrome are set to Auto detect/Unicode UTF-8. I've tried reinstalling all my Windows default fonts too but no success.  Does anyone have a fix for this? Most solutions I've looked at haven't been successful
61185
I'm trying to remove some characters from file(UTF-8). I'm using tr for this purpose:   tr -cs '[[:alpha:][:space:]]' ' ' &lt;testdata.dat    File contains some foreign characters (like "Латвийская" or "àé"). tr doesn't seem to understand them: it treats them as non-alpha and removes too.  I've tried changing some of my locale settings:  LC_CTYPE=C LC_COLLATE=C tr -cs '[[:alpha:][:space:]]' ' ' &lt;testdata.dat LC_CTYPE=ru_RU.UTF-8 LC_COLLATE=C tr -cs '[[:alpha:][:space:]]' ' ' &lt;testdata.dat LC_CTYPE=ru_RU.UTF-8 LC_COLLATE=ru_RU.UTF-8 tr -cs '[[:alpha:][:space:]]' ' ' &lt;testdata.dat   Unfortunately, none of these worked.  How can I make tr understand Unicode?
17694
I can read the MySQL documentation and it's pretty clear. But, how does one decide which character set to use? On what data does collation have an effect?  I'm asking for an explanation of the two and how to choose them.
63011
I have a few shapefiles where some of the attributes contain the non-English characters ÅÄÖ. Since some queries doesn't work with these characters (specifically ), I tried to change them in advance with a simple script and add the new strings to another field.  However, change in characters works fine but not updating the field with arcpy.UpdateCursor.   What is an appropriate way of solving this?  I have also tried to do this via the Field Calculator while posting "code" to the codeblock, with the same error.  Error message: Runtime error  Traceback (most recent call last):   File "", line 1, in    File "c:/gis/python/teststring.py", line 28, in      val = code(str(prow.Typkod)) UnicodeEncodeError: 'ascii' codec can't encode character u'\xc4' in position 3: ordinal not in range(128)  Code:  # -*- coding: cp1252 -*- def code(infield):     data = ''     for i in infield: ##        print i         if i == 'Ä':             data = data + 'AE'         elif i == 'ä':             data = data + 'ae'         elif i == 'Å':             data = data + 'AA'         elif i == 'å':             data = data + 'aa'         elif i == 'Ö':             data = data + 'OE'         elif i == 'ö':             data = data + 'oe'         else:             data = data + i     return data   shp = r'O:\XXX\250000\DB\ArcView\shape.shp'  prows = arcpy.UpdateCursor(shp)  for prow in prows:     val = code(unicode(str(prow.Typkod), "utf-8"))     prow.Typkod_U = val     print val     prows.updateRow(prow)   The values of Typkod are of the type: [D, D, S, DDRÄ, TRÄ] etc.  I use ArcMap Basic (10.1) on Windows 7.    New Error message:  Runtime error  Traceback (most recent call last):   File "", line 1, in    File "c:/gis/python/teststring.py", line 29, in      val = code(unicode(str(row.Typkod), "utf-8")) UnicodeEncodeError: 'ascii' codec can't encode character u'\xc4' in position 3: ordinal not in range(128)  &gt;&gt;&gt; val 'DDRÄ' &gt;&gt;&gt; type(val) type 'str'      It appears as if the output from the function is wrong somehow. When there's ÅÄÖ involved it returns data = u'DDR\xc4' and not (as was my intention) data = 'DDRAE'. Any suggestions on what might cause this?
38016
I try to make a table for language manual. Could anybody help me to manage curly brackets in the cells of a table?  Like this:    I tried to do it like  but I could't manage it.
105734
In my web app, I submit some form fields with jQuery's $.getJSON() method. I am having some problems with the encoding. The character-set of my app is charset=ISO-8859-1, but I think these fields are submitted with UTF-8.   How I can set encoding used in $.getJSON calls?
76738
I have a webserver administration question. In this website:   All PHP generated pages contain the following line:  &lt;meta http-equiv="Content-Type" content="text/html; charset=iso-8859-2" /&gt;   But this is somehow disregarded probably via the php-apache processing and the page displays in browsers with an UTF-8 header. As a result of that question marks (�) are shown in the page text instead of accented characters (éáöőóüűúí). I tested this in Firefox, IE, Chrome and Seamonkey.  The strangest in this phenomenon, that this symptom started only yesterday, after I upgraded my server to Debian 8.0 Jessie from 7.0 Wheezy. During the upgrade I also upgraded all other packages as well, including apache, php, and so on, and selected "yes" for overwriting config files with factory default ones. After this I fine-tuned my config files to have everything the way I like, but I did not find a way to fix this. Before the upgrade, the page displayed just fine.  Here is a screenshot, where you can see that Firefox sees the "charset=iso-8859-2" definition, but still displays the page with UTF-8 encoding.    My suspicion is, that this is a server configuration issue, but it could also be, that one part of the processing component (Apache, php) changed due to the upgrade in some way, resulting this strange behavior. The problem is, I can't pinpoint, what could possibly cause this problem.  Can anyone solve this mistery? What could be possibly going wrong during the processing of the page?
93446
I have just changed computers, and running Biber 2.11 now produces this error:  Utils.pm:209&gt; ERROR - Data file ... cannot be read in encoding 'UTF-8':  Can't decode ill-formed UTF-8 octet sequence &lt;96&gt; at C:\ ... Slurper.pm line 63   My .bib file is huge, having accumulated over years.  Thus, I suspect that there's something malformed in it.  Is there any rapid way to trouble-shoot it?  The new machine runs Win 10, Biber 2.11, XeLaTeX 2018.10.31, LaTeX2e 2018-04-01 and TeXLive 2018.  The old machine ran Win 7 and slightly earlier versions of all of the above.  A MWE of the driver .tex file:  \documentclass{article} % also with beamer  \usepackage[utf8]{inputenc} % problem arises whether or not include this \usepackage[backend=biber,bibencoding=utf8]{biblatex} %  problem arises whether or not include this \addbibresource{bib-mwe.bib}  \begin{document}  cite reference \cite{mal-rwws}  \printbibliography  \end{document}    Thanks!
73925
Earlier today a question was asked regarding .  The top answer, at time of writing, suggests in PHP just using htmlspecialchars and mysql_real_escape_string.   My question is: Is this always enough? Is there more we should know? Where do these functions break down?
44716
I have a shapefile with names for Regions. These don't seem to contain special characters "Ä", "Ü", "Ö", "ß" but ugly hieroglyphs.  What can I do to display them correctly. If I import the shape as UTF-8 it doesn't work.  The names are in a dbase table. So is it possible to save a dbase table in UTF-8 or is there a different way of dealing with it?
25069
I'm having exactly the same issue as , also using Biber 2.14, albeit I didn't upgrade, downgrade, change TexLive version, change encoding or (seemingly) do anything. It's like Biber suddenly quit parsing dates on me.  Whether the bibfile is encoded in ASCII or UTF-8 makes no difference. Whether the date is a short format or the full YYYY-MM-DD makes no difference. I'm not sure what else to test.  Here's a MWE and the associated .blg file:  \begin{filecontents}{mwe.bib}     @Article{JD2020,         author       = {John Doe},         title        = {A Title},         date         = {2020-01-01},         %date       = {2020}         journaltitle = {Journal},     } \end{filecontents}  \documentclass{article} \usepackage{biblatex} \addbibresource{mwe.bib}  \begin{document}     test\autocite{JD2020}     \printbibliography \end{document}   [1] Config.pm:304&gt; INFO - This is Biber 2.14 [1] Config.pm:307&gt; INFO - Logfile is 'mwe.blg' [154] biber-darwin:322&gt; INFO - === Thu Apr 30, 2020, 11:04:33 [185] Biber.pm:415&gt; INFO - Reading 'mwe.bcf' [354] Biber.pm:943&gt; INFO - Found 1 citekeys in bib section 0 [384] Biber.pm:4256&gt; INFO - Processing section 0 [385] Utils.pm:75&gt; INFO - Globbing data source 'mwe.bib' [385] Utils.pm:91&gt; INFO - Globbed data source 'mwe.bib' to mwe.bib [401] Biber.pm:4455&gt; INFO - Looking for bibtex format file 'mwe.bib' for section 0 [402] bibtex.pm:1653&gt; INFO - LaTeX decoding ... [406] bibtex.pm:1471&gt; INFO - Found BibTeX data source 'mwe.bib' [437] Utils.pm:304&gt; WARN - Entry 'JD2020' (mwe.bib): Invalid format '2020-01-01' of date field 'date' - ignoring [457] UCollate.pm:68&gt; INFO - Overriding locale 'en-US' defaults 'normalization = NFD' with 'normalization = prenormalized' [457] UCollate.pm:68&gt; INFO - Overriding locale 'en-US' defaults 'variable = shifted' with 'variable = non-ignorable' [457] Biber.pm:4084&gt; INFO - Sorting list 'nty/global//global/global' of type 'entry' with template 'nty' and locale 'en-US' [457] Biber.pm:4090&gt; INFO - No sort tailoring available for locale 'en-US' [461] bbl.pm:652&gt; INFO - Writing 'mwe.bbl' with encoding 'UTF-8' [463] bbl.pm:755&gt; INFO - Output to mwe.bbl [463] Biber.pm:128&gt; INFO - WARNINGS: 1   The \printbibliography output actually looks like this: [1] John Doe. “A Title”. In: Journal ().  In my actual thesis, all the dates are gone from the pdf output.