As you mentioned, you’d have to know the encoding of the file to read the encoding attribute. However, there is a heuristic that can easily get you close enough to the “real” encoding to allow you to read the encoding attribute. This works, because the <?xml part by definition can only contain characters in the … Read more
UPDATED: Since Java11 there is a specific method to write strings using java.nio.file.Files: Files.writeString(Paths.get(file.toURI()), “My string to save”); We can also customize the writing with: Files.writeString(Paths.get(file.toURI()), “My string to save”, StandardCharsets.UTF_8, StandardOpenOption.CREATE, StandardOpenOption.TRUNCATE_EXISTING); ORIGINAL ANSWER: There is a one-line solution, using Java nio: java.nio.file.Files.write(Paths.get(file.toURI()), “My string to save”.getBytes(StandardCharsets.UTF_8), StandardOpenOption.CREATE, StandardOpenOption.TRUNCATE_EXISTING); I have not benchmarked this … Read more
iconv -f WINDOWS-1252 -t UTF-8 filename.txt
Java stores strings as UTF-16 internally. “default encoding” isn’t quite right. Java stores strings as UTF-16 internally, but the encoding used externally, the “system default encoding”, varies from platform to platform, and can even be altered by things like environment variables on some platforms. ASCII is a subset of Latin 1 which is a subset … Read more
ASCII is fundamental Originally 1 character was always stored as 1 byte. A byte (8 bits) has the potential to distinct 256 possible values. But in fact only the first 7 bits were used. So only 128 characters were defined. This set is known as the ASCII character set. 0x00 – 0x1F contain steering codes … Read more
If you’ve got files encoded in a particular way, it’s probably best to tell javac that rather than forcing the whole JVM to use a particular encoding. The javac task has an encoding attribute for this reason. <javac srcdir=”${src.dir}” destdir=”${build.classes.dir}” encoding=”iso-8859-1″ /> But really, you should just convert the source files to UTF-8. Everything tastes … Read more
Jersey should always produce utf-8 by default, sounds like the problem is that your client isn’t interpreting it correctly (the xml declaration doesn’t “make” it utf-8, just tells the client how to parse it). What client are you seeing these problems with? Valid JSON is only supposed to be Unicode (utf-8/16/32); parsers should be able … Read more
I have found following way to fix this issue… I hope this can help you. json_encode($data,JSON_UNESCAPED_UNICODE|JSON_UNESCAPED_SLASHES);
import codecs f=codecs.open(“test.html”, ‘r’) print f.read() Try something like this.
Did you “get things right”? Yes, Except that I think that French accents are ‘correctly’ compared in utf8mb4_unicode_520_ci. Your two SELECTs will both to a full table scan, thereby be inefficient. The reason is that you are overriding the collation (for #1) or hiding the column in a function (LOWER, for #2) or using a … Read more