Edit jars on 5.6.1.0.5 (margins, font sizes) -- and non-jb fonthack

[NiLuJe]

Some things are more tolerant to CR/LF than others, but it's just bad practice to mix line-endings, and most everything we do here is guaranteed to expect/work with unix line-endings, while it might only once in a blue moon tolerate CR/LF without ill effect.
Hence the go-to recommendation is unix line-endings and a decent editor, because we're sure *that* expected setup will work. Anything else would just add 'noise' and complicate support. Better eliminate potential issues early, where we can.
Plus, one byte less per line, win/win ^^.

One of the many things that will not ever bear CR/LFs are shell scripts, for instance.

[shalym]

Originally Posted by NiLuJe

Some things are more tolerant to CR/LF than others, but it's just bad practice to mix line-endings, and most everything we do here is guaranteed to expect/work with unix line-endings, while it might only once in a blue moon tolerate CR/LF without ill effect.
Hence the go-to recommendation is unix line-endings and a decent editor, because we're sure *that* expected setup will work. Anything else would just add 'noise' and complicate support. Better eliminate potential issues early, where we can.
Plus, one byte less per line, win/win ^^.

One of the many things that will not ever bear CR/LFs are shell scripts, for instance.

Well, then, notepad must not use CR/LFs, then, since I've written shell scripts using notepad.

Shari

[knc1]

Originally Posted by shalym

Well, then, notepad must not use CR/LFs, then, since I've written shell scripts using notepad.

Shari

Bad guess.

How did you transfer the script from the Windows machine you wrote it on to the Linux (or other *nix) system you ran it on?

[shalym]

Originally Posted by knc1

Bad guess.

How did you transfer the script from the Windows machine you wrote it on to the Linux (or other *nix) system you ran it on?

FTP. How do you transfer files from one system to another?

Shari

[NiLuJe]

By "how", knc1 meant both over which protocol, but most importantly, via which software, because some are known to silently (or not so silently) fudge with line-endings.

We've already had a couple of interesting and excruciatingly long & pointless debugging back-and-forth sessions simply because an unarchiver or a file transfer program was trying to be cute.

[shalym]

Originally Posted by NiLuJe

By "how", knc1 meant both over which protocol, but most importantly, via which software, because some are known to silently (or not so silently) fudge with line-endings.

We've already had a couple of interesting and excruciatingly long & pointless debugging back-and-forth sessions simply because an unarchiver or a file transfer program was trying to be cute.

I usually use filezilla, but I have used WsFtp and (rarely) CuteFTP or even the built in FTP client in Windows Explorer. I've also (in a pinch) done it using the command line from Dos, but that is a horrible memory from the long ago dark days.

Shari

[eschwartz]

Originally Posted by shalym

Actually, I see references to this all the time, and I just don't understand what the issue is. I use notepad. not Notepad++, just the regular notepad that comes with Windows. I've edited config files for my Kobo and my Kindle, and edited html, vbscript, javascript and probably many other things I'm not remembering, all using plain old vanilla notepad. I've never had a problem with any system not recognizing the line endings.

Maybe people who are having problem are using either Wordpad or MS Word instead of notepad? Neither of those will work for working in code, but again...I've been working with scripts and devices for years, and never had a problem with notepad.

Shari

The tests conclusively point to the issue of using CRLF, insomuch as there are utilities or manual editing for switching to *nix line endings, and that is the specific action that gets things working.

Regardless, if you create or edit a file using Windows' built-in Notepad, you will be working with CRLF. That may or may not blow up on you. I have no idea whether this specific file must use *nix line endings (I was not the one who said it was required), but of a surety, there are things that do depend on it.
(As for html and javascript, line endings are optional, so naturally there would be no problem either way. vbscript is a Windows thing, so if it depends on anything it will be DOS line endings...)

One way to test your claim (since it runs contradictory to the experience of, well, every other test by any other human being on the planet) would be to open one of those files with Notepad++, which will tell you whether the file uses *nix or DOS line endings.


And check the manual for the transfer program you use, to find out if it has the helpful feature of auto-correcting line endings. I am pretty sure Filezilla at least does that. EDIT: Yup -- https://wiki.filezilla-project.org/Data_Type

[knc1]

Originally Posted by shalym

I usually use filezilla, but I have used WsFtp and (rarely) CuteFTP or even the built in FTP client in Windows Explorer. I've also (in a pinch) done it using the command line from Dos, but that is a horrible memory from the long ago dark days.

Shari

Ah, there you go - -
Big Daddy B. Gates is holding your hand in the background -
and translating line endings for you.

[shalym]

Originally Posted by eschwartz

The tests conclusively point to the issue of using CRLF, insomuch as there are utilities or manual editing for switching to *nix line endings, and that is the specific action that gets things working.

Regardless, if you create or edit a file using Windows' built-in Notepad, you will be working with CRLF. That may or may not blow up on you. I have no idea whether this specific file must use *nix line endings (I was not the one who said it was required), but of a surety, there are things that do depend on it.
(As for html and javascript, line endings are optional, so naturally there would be no problem either way. vbscript is a Windows thing, so if it depends on anything it will be DOS line endings...)

One way to test your claim (since it runs contradictory to the experience of, well, every other test by any other human being on the planet) would be to open one of those files with Notepad++, which will tell you whether the file uses *nix or DOS line endings.


And check the manual for the transfer program you use, to find out if it has the helpful feature of auto-correcting line endings. I am pretty sure Filezilla at least does that. EDIT: Yup -- https://wiki.filezilla-project.org/Data_Type

Ok...so I've downloaded notepad++ and looked at 5 different scripts that I've either created or edited using notepad.

What am I supposed to be seeing? As far as I can tell the only difference is that it adds pretty colors to highlight different elements of the script, kind of like other script editors do. I see nothing to indicate anything about what kind of line endings the file is using. Where would I see that?

Shari

[eschwartz]

In the status bar at the bottom, it should indicate DOS or Unix.

The other great feature is that if the file you open is using *nix line endings, it will read it as a DOS file.

Rather than treating everything as one giant line, which I do promise you will happen if you copy *nix files from a linux computer to a flashdrive to a Windows computer instead of using FileZilla... and then try to open that file in the default Notepad.

[thomass]

Originally Posted by shalym

I see nothing to indicate anything about what kind of line endings the file is using. Where would I see that?

use this option:

[odamizu]

Thank you again everyone for all your help, with a special to ecostin for finding and sharing this hack. It works great!

Originally Posted by tono1020

... Default values are: 7.13 7.81 8.49 9.17 10.53 12.56 16.98 29.2 ...

I calculated few value sets for myself, but only those values [7.49 8.43 9.37 10.31 11.25 12.19 13.13 14.07] worked for me. Don't know why.

This article explains how to calculate those values: http://www.the-ebook.org/forum/viewt...424889da87d14b. Article is in russian language, but you can "google translate" it.

That's interesting. I wonder why some of your sets didn't work and what criteria the numbers need to follow in order for them to work. I went to the Russian forum, but I didn't really understand it, even with the help of Google Translate

There was something in there about increments of .34, and indeed the default settings increase by multiples of .34 (.68, 1.36, 2.03, 4.42, 12.22). Though I notice you increased each setting by .94 and it worked, so clearly the .34 thing isn't required.

In any case, I played with the numbers (using multiples of .34 for each increment), mostly because I like the first 4 or 5 default settings; it's the upper range that I wanted to adjust. If anyone's interested, these sets all worked on my KV (default settings in black, my adjustments in blue):

7.13 7.81 8.49 9.17 9.85 10.53 11.21 11.89

7.13 7.81 8.49 9.17 10.19 11.21 12.23 13.25

7.13 7.81 8.49 9.17 10.53 11.89 13.25 14.61

7.13 7.81 8.49 9.17 10.53 12.56 13.92 15.28

7.13 7.81 8.49 9.17 10.53 15.28 16.64 18.0

[odamizu]

P.S. re: all this talk of line endings (and thank you eschwartz for the amusing overview), I feel like a child sitting at the grown-up's table struggling to understand what you're all talking about!

I edited the text files using an HTML editor on Mac OS X, then saved the file in "plain text" format, and it worked nicely on my Kindle.

I'm curious: Did it work because I saved it as plain text (i.e., does plain text = *nix line endings?) or did it work because I'm on a Mac and OS X is Unix-based?

[knc1]

Originally Posted by odamizu

- - - -
I'm curious: Did it work because I saved it as plain text (i.e., does plain text = *nix line endings?) or did it work because I'm on a Mac and OS X is Unix-based?

Both (saved as plain text and your on a *nix based system).
Plain text != type of line endings.
It was the Mac OS (prior to OS X) that used CR for line endings.

(Darn. Some good must have come from living with a roomful of computers for over a 1/2 century.)

[thomass]

Originally Posted by odamizu

I'm curious: Did it work because I saved it as plain text (i.e., does plain text = *nix line endings?) or did it work because I'm on a Mac and OS X is Unix-based?

The file on this zip has no line ending in it (ie it contains only 1 line of text) I think for this particular file editing software does not matter. (also pay attention to the extension of the resulting file.)