I agree that the number of encodings makes a full proof transparent solution
impossible to implement.
I still think that some simpler text file handling out of the box should exist
on the JVM to read utf files.
Utf-8 is kind of natural within the JVM.
Exposing all this BOM machinery every time
Assume that charset is the same, even this case, there're many types of
encoding scheme for it and for portability,
you have to consider both input and output encoding. On Mac OS X or Linux,
this is controlled by locale system,
on windows 1. you can force encoding system using control panel or you
I cannot remember the details but in 2010 I had similar problem in a
cross-platform project
using Clojure. And problems earlier in another cross-platform/cross-language
project.
So it's the reverse way, no BOM at all...
Can't believe we are in 2015 still struggling with character set issues.
> * On Notepad++ went to the Encoding menu and selected "Encoding in UTF-8
> w/o BOM". Saved the file. When running "lein run" on the cmd.exe console it
> works but it outputs garbage instead of any non-ascii character (see
> http://i.imgur.com/H0rngyq.png)
>
This is as expected.
Garbage character
On Mon, Jul 13, 2015 at 2:52 PM, Luc Préfontaine <
lprefonta...@softaddicts.ca> wrote:
> BG is right on it. I hit this problem a decade ago (roughly :)).
> UTF-8 files with no BOM are not handled properly on windows.
> It assumes that they are ASCII coded. That works partially (both character
> se
BG is right on it. I hit this problem a decade ago (roughly :)).
UTF-8 files with no BOM are not handled properly on windows.
It assumes that they are ASCII coded. That works partially (both character sets
have the same
encoding for many characters) but eventually fails.
Make sure that the files
Of course not. My files do not have BOM. So the problem lies in the
BOM thingy?
On Mon, Jul 13, 2015 at 10:07 AM Baishampayan Ghose
wrote:
> Hi,
>
> IIRC Windows requires UTF-8 encoded files to have the BOM (Byte Order
> Mark).
> Can you verify that your file has the BOM?
>
> Regards,
> BG
>
> O
I followed steps described by Denis Fuenzalida in my Windows 7 machine and
I can completely reproduce the results.
So, in Windows 7, the solution is the .clj files must be saved with UTF-8
without BOM encoding.
On Sunday, 12 July 2015 08:57:59 UTC+7, Denis Fuenzalida wrote:
>
> I was able to re
Hi,
IIRC Windows requires UTF-8 encoded files to have the BOM (Byte Order Mark).
Can you verify that your file has the BOM?
Regards,
BG
On Thu, Jul 9, 2015 at 8:03 AM, Alex Woods wrote:
> clojure don't support .clj source code file by utf-8.
> it's ok when the .clj source code files by ascii
>
Windows a problem ?
N, impossible :)))
Luc P.
Sent from my iPhone
> On Jul 12, 2015, at 19:39, Sungjin Chun wrote:
>
> On Mac OS X (Yosemite) and Linux (Ubuntu), this code works well (I'm using
> en_US.UTF-8 as
> charset and encoding for my system).
>
> I suspect that the OS (Windows) o
On Mac OS X (Yosemite) and Linux (Ubuntu), this code works well (I'm using
en_US.UTF-8 as
charset and encoding for my system).
I suspect that the OS (Windows) or its configuration is the source of the
problem.
On Sunday, July 12, 2015 at 10:57:59 AM UTC+9, Denis Fuenzalida wrote:
>
> I was abl
I was able to reproduce an error involving Windows 7 and UTF-8 in a virtual
machine with VirtualBox 4.3 (not sure if it is the issue that Alex
experienced though):
* Installed Windows 7, then used Ninite.com to install Notepad++ (text
editor), Oracle JDK 8 (1.8.0_45). Installed Leiningen 2.5.1
Hi Alex
You'll need to give us some more information about this to help us
troubleshoot what's going on. Can you share the file with us?
On Fri, 10 Jul 2015 at 3:59 AM Alex Woods wrote:
> clojure don't support .clj source code file by utf-8.
> it's ok when the .clj source code files by ascii
>
13 matches
Mail list logo
