There is no need for any e-book format besides pdf, prove me wrong

This is when we know you've never used an e-reader.
PDF works well with documents that are supposed to be printed, because you already know the size and aspect ratio of the support (for instance, A4). Not all e-readers have the same size nor the same aspect ratio, and reading PDFs on them is utter shit.

Fuck no. Also
Another fuck no. Pdf is only okay

As an avid reader of manga I disagree. Simple folders full of jpegs or pngs is far superior in every way, shape, and form to a packaged pdf. Mostly because pdf readers are all pure cancer.

How about .cbr/.cbz
Sumatra seems very nice. Apart from .pdf it also reads .chm, .djvu, .mobi, .epub, .cbr and .cbz.

Enjoy your 0.0034% extra storage usage from slack space. I bet you don't even optimize your images faggot.

Attached: folder vs zip.png (249x30, 345)

Plain ASCII master race. For stuff that really neads "muh formatting", Markdown or (rarely) HTML+CSS will suffice. For manga, plain JPG/PNG (encapsulated in .cbz or .tar) is better.

well it sure looks like .pdf wins on that chart because it has the most green boxes next to it

I bet you haven't heard of "storage" compression level, which is basically zero compression. Archive file formats have other purposes besides reducing used storage space by means of compression, such use is to aggregate other files inside one file. Filesystem images are somewhat similar.
rude and mean

In other words: useless, redundant shit which is best supplanted with `tar`. Do one thing and do it well: either compress or aggregate.
Faggot. Get out of here before you give us all AIDS.

FB2 is the least cancer of all these, judging by the table.
a book should not have fucking sound, or interactivity. it's also not infested with DRM.

Show me, without googling, how to make a tar without storing absolute paths (which could be an embarrassing information leak).
After that we can talk about it.

Storing text as images? Are you stupid?

Don't talk to Windows users.png

$ tar -cf archive.tar directory

you failed.
absolute paths are default behavior and these options do not change that.

Oops, me failed.
I forgot it's about a different thing: the username and file permissions. Tar stores them by default, leaking your username.

and the answer is here
unix.stackexchange.com/questions/278011/anonymous-tarballs
totally not easy to find, and totally not obvious that tar is non anonymous by default.

not the fun part:
`--numeric-owner` is silently ignored and 2 other options are unsupported

$ tar --version
bsdtar 2.8.3 - libarchive 2.8.3

so, it seems, on some systems it's not even possible to create anonymous tarballs with the tool that's intended to create them.

also it stores the path without normalizing.

tar -cf benis.tar test
tar -cf benis.tar /test

these 2 commands produce DIFFERENT FILES although they refer to the same directory
that's visible if you look at the file in hex editor that the argument is stored as is

forgot the dot

Now it's time to the Unix hating quote guy to step in and say something interesting about why tar is so shit

it's called Digital Restrictions Management
are you a cuck or why are you using the cucked naming?

Why, exactly, is this a problem? 'test/' and './test/' will cause exactly the same results if extracted. No problem there.

it can sometimes help connect some dots, you know, it's called fingerprinting (unless you use the default one, but on many systems there's no default username, and on others, it could be unique to the distro, and then there are also potentially distinct user/group IDs)
and the worst part is that this is the default behavior and most of the users have no idea that it happens

it's useless information about whether I used a dot, and it can also add a bit of fingerprinting.

remember kids, there's no excuse for leaking more data than necessary to achieve the goal.

It is what it is. Digital Rights Management.

The cuck, it is what you are.

“Digital Rights Management” (abbreviated “DRM”) refers to technical mechanisms designed to impose restrictions on computer users. The use of the word “rights” in this term is propaganda, designed to lead you unawares into seeing the issue from the viewpoint of the few that impose the restrictions, and ignoring that of the general public on whom these restrictions are imposed.

Good alternatives include “Digital Restrictions Management,” and “digital handcuffs.”

Please sign up to support our campaign to abolish DRM.
defectivebydesign.org/

defectivebydesign.org/what_is_drm_digital_restrictions_management

You have valid points there. However, I think I'll continue using tar for most things: the most severe problem in my opinion is the username (which can fairly easily be fixed with --numeric-owner), just because it's easier to manage the compression separately from the archiving. (and can be pipelined) For example, recompressing in a superior compression format:

$ pv tarball.tar.gz | gzip -dc | lzip > tarball.tar.lz

Or extract an archive while it's downloading.

$ curl ftp.gnu.org/gnu/something/something-latest.tar.xz | tar -xJ

it doesn't work, at least on some flavors of tar, and it is silently ignored in that case.
you should at least test it by inspecting the result in a hex editor.

normal archives can be pipelined too.
it's just not supported by the fatally impotent pipelining convention of UNIX — it has no convention for structured data.
but you can write code in something like Python or whatever language you know, to stream individual files from an archive and send them immediately to the compression program.
if it was not a fringe use case, perhaps it could be released too.

...

It's fuckin yuge, epub is like 1/20th the size
Fuck you

Also on many desktop systems it's possible for a bystander to see your username even if your session is locked.
So, it's enough for it to be something unique to let a certain subset of human population deanonymize you.

No need for that.
gzip -dc archive.tar.gz | dd bs=512 count=1 | grep $USER && echo "fix your shit" || echo "all good"
What kind of bullshit is this. Unixhaters are actually fucking retarded.
Yes, of course, because the shell and the operating system have to be aware of every possible file format so it can be "aware of structured data". Right?

On an unrelated note, how fucking new are you. You double- and triple- and often even quadruple-post when one post could suffice, because you can't be patient enough to wait until all your thoughts have gathered. This behaviour is indicative of redditors who can EDDIT their posts billions of times (and piss off other redditors in the process).

I don't usually do that when I am in a good thread.
This thread is low value.

Who said writing a new script every time?

No.
There could be just one standard simple format for sending nested lists and that would be enough.
And it doesn't even need to be serialized to a file, so we're adding zero file formats.
In other words, right now streams have "lazy sequence of bytes" type, and after this change the type will be T = "lazy sequence of (lazy sequence of bytes | T)"

Right. It's low value because you're shitting it up with your 6,000,000 short replies which each contain almost nothing of value.
You would need to write new scripts whenever any new compression format was released. You would need to update your software EVERY TIME you became aware of some obscure compression format with edge case use.
This isn't necessary when doing it the Unix way.
I do not understand how this would improve pipelining of ZIP files to the compressor.
Even if it did, it's not necessary because we have formats (such as tar and gzip) which are stream-oriented rather than having some kind of tree structure (which requires additional memory for caching and cannot load the CPU evenly).

let's see
high value threads aren't like that

Yes, OP is a faggot as is usual here. However, this thread does contain interesting discussion regarding ebook formats, which then diverged into a discussion about archive formats (punctuated with 6,000,000 badly formatted posts by you). This isn't really related to the OP, but it is not what I'd call "low value". There are a lot of things which I learned on this board only because a thread derailed and went into a really obscure topic. Sure, derailed threads can sometimes be total shit. But sometimes they are not.

yeah you have a point here.
but other than a little distraction thrown in between, these posts are still the same amount of text.

nah. if any compression tool follows a convention of accepting inputs/writing outputs, then it won't need to be modified.

you would be able to directly send a tree structure with file paths and contents, and it will be transparently handled by the OS, that's it.
in this alternate universe, each archiver/unarchiver would be able to write/read these trees completely lazy, and you could do things like
unzip benis.zip | 7z -o benis.7z
to

what is stream-oriented about tar and gzip?
most sane archive formats are also streamable. the difference is that you must deal with structured data.

tar will also never be as friendly to compression, because when the compressor deals with individual files, it may choose the best method per file by a clever heuristic. (7z does that, for example).
if you try to do this for tar, you end up duplicating complexity in the compressor to parse it back again, and then it doesn't make sense to use tar anymore.

Ultimately the cbx file extensions were just made up to tell your OS, that these archives should be opened with a comic book reader. Zip (.cbz) and RAR (.cbr ) might be the most commonly used formats on piracy sites, but you can also create 7z (.cb7), ACE (.cba) and tarball (.cbt) files, to open them with you comic book software.

fug
why cannot I forget this shit

What are some decent comic book readers? I was using CDisplay for a while, but my PDF reader ended up doing the job better. Still doesn't have support for some zip (don't blame me, that's the method the scanners use) layouts though. I haven't tested too thoroughly, but it's either unicode text, or nested subfolders, can't really change the files because most of them are from torrents, and I don't really have the space to keep two copies of everything.

because you're a fucking degenerate who watches jewish porn and engages in jewish fantasies

mount them with fuse-zip and view the files individually

heh..

┌───────────┬───────────────┬───────────┬────────┐│ Format │ Open Standard │ Word Wrap | Tables |├───────────┼───────────────┼───────────┼────────┤│ plaintext │ Yes │ Yes | Yes |└───────────┴───────────────┴───────────┴────────┘

I'm using Comix. Don't know much about it, but I can read comicbooks.

┌───────────┬───────────────┬───────────┬────────┬────────┐│ Format │ Open Standard │ Word Wrap | Tables | Images |├───────────┼───────────────┼───────────┼────────┼────────┤│ plaintext │ Yes │ Yes | Yes | Yes |└───────────┴───────────────┴───────────┴────────┴────────┘

▓▓▓▓▓▓▀▀░░░░░░▀▀▓▓▓▓▓▓ ▓▓▓▀░░░░░▄██▄░░░░░▀▓▓▓ ▓▓░░░░░▄▄██▀░░░░░░░░▓▓ ▓░░░░░▄██▀░░░▄█▄░░░░░▓ ▌░░░░░▀██▄▄▄█████▄░░░▐ ░░▄▄▄░░░▀████▀░▀▀██▄░░ ░░▀██▄░▄▄████▄░░░▀▀▀░░ ▌░░░▀█████▀▀▀██▄░░░░░▐ ▓░░░░░▀█▀░░░▄██▀░░░░░▓ ▓▓░░░░░░░░▄██▀░░░░░░▓▓ ▓▓▓▄░░░░░▀█▀▀░░░░░▄▓▓▓ ▓▓▓▓▓▓▄▄░░░░░░▄▄▓▓▓▓▓▓

Let's try that again shall we.

┌───────────┬───────────────┬───────────┬────────┬────────┐│ Format │ Open Standard │ Word Wrap | Tables | Images |├───────────┼───────────────┼───────────┼────────┼────────┤│ plaintext │ Yes │ Yes | Yes | Yes |└───────────┴───────────────┴───────────┴────────┴────────┘

▓▓▓▓▓▓▀▀░░░░░░▀▀▓▓▓▓▓▓ ▓▓▓▀░░░░░▄██▄░░░░░▀▓▓▓ ▓▓░░░░░▄▄██▀░░░░░░░░▓▓ ▓░░░░░▄██▀░░░▄█▄░░░░░▓ ▌░░░░░▀██▄▄▄█████▄░░░▐ ░░▄▄▄░░░▀████▀░▀▀██▄░░ ░░▀██▄░▄▄████▄░░░▀▀▀░░ ▌░░░▀█████▀▀▀██▄░░░░░▐ ▓░░░░░▀█▀░░░▄██▀░░░░░▓ ▓▓░░░░░░░░▄██▀░░░░░░▓▓ ▓▓▓▄░░░░░▀█▀▀░░░░░▄▓▓▓ ▓▓▓▓▓▓▄▄░░░░░░▄▄▓▓▓▓▓▓

┌───────────┬───────────────┬───────────┬────────┬────────┬────────────┐│ Format │ Open Standard │ Word Wrap | Tables | Images | Executable |├───────────┼───────────────┼───────────┼────────┼────────┼────────────┤│ plaintext │ Yes │ Yes | Yes | Yes | Yes |└───────────┴───────────────┴───────────┴────────┴────────┴────────────┘

cs.cmu.edu/~tom7/abc/

What a surprise

I tried to use the aa tag (because it's for "ascii art") and it failed. So, code tag. Stay triggered leftyshit

I only heard about this shit fortunately.
Which porn is not jewish? How do you know?
hmm

I had to search it up to understand your reference.

so, if I need to check something, I need to ask you if you know about it and if you don't, then it's jewish?
do you have an email/XMPP to be asked privately?
I'm into relatively obscure shit that will get me deanonymized probably lol

Comics are meant to be read in pages of 2. It's not just some shitty ORIGINAL PAPER-LIKE EXPERIENCE meme, the amount of content you can see at once is considered by the artists, and they can basically time surprising shit to happen the next page over.

Used the Comix fork Mcomix, it was basically way better than I could even imagine. Just disable the sidebar, ignore the library functions, and you've basically got a version of CDisplay that doesn't trip up on weird filepaths, and goes through pages in order when the scanners fuck up the numbering and don't use any leading "0"s.
Since scanners all have their own opinions as to whether completely blank pages should be put after the title page, or since they sometimes do stupid shit like get a full scan of both covers across the spine, one thing you're going to occasionally want to do is hold the Control key as you're going over the page sometimes. Irons out page desyncs, which become very obvious with Japanese comics. I'm not a fan of some of the default keybindings, but then can all be changed, which is a lot more than SOME monstrosities allow for. You might also want to change the default scroll/turn page settings.
Anyway, 10/10, even my autistically particular eye couldn't find a single real fault about it.

plain text is fine.
PDF really pisses me off because my government releases protected forms that only work in adobe.

why didn't it replace html?

It is starting to look more like an interactive novel/text adventure kind of language.

PDF is fixed. It still relies on paper formats in a digital age. I may like reading a PDF on my PC or laptop, during the day, but when I'm on a train reading something on my phone I want something that adjusts to fit the screen without getting tiny letters. Also, especially if it's getting dark, then I'd like to adjust colors if necessary.

Yes, exactly!

This is an excellent example of what I meant when calling most texts blobs. Their logical, narrative structure, situational relationships, are concretized in human language and unparseable, effectively inoperable. When we mark human languages up, we open the text in question to modification, literally decompiling it. A novel, when it is broken up in its constituent logical, topographical, strategic/tactical, cost-analysis, decision-making units that are typically hidden behind English verbalization, opens itself to recreation, or analysis and re-synthesis as a parallel work in the same universe, for instance.

I wish I hadn't accidentally sent that first post too early; maybe I would be able to express my point better. But you understood it very well. Yes, a narrative format could represent knowledge, for instance so:

...

All major porn hosts are Jewish.
Jap porn though? Not really

This OP is blatant bait.

CBR:

✔️ Good Encryption Support
NO OTHER FORMAT HAS THIS

✔️ Superior to DRM, only tech savvy can copy-paste. Think of it as IQ-DRM.

✔️ Supports Anything you can put in an image:
✔️ Images
✔️ Tables
✔️ Word wrap

✔️ Doesn't make noise - ever.
✔️ Doesn't run scripts - ever.
✔️ Doesn't get scribbled on - ever.
✔️ Never get Rick-Rolled.
IT'S A BOOK, FAGGOT

✔️ Bookmarking support app-dependent, as it should be

✔️ Fast
PDF, I'M LOOKING AT YOU
✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️✔️ Super-fast: Extract, view with QuickVirwer

CBR: It's a book, improved.

PDF: It's like a book, only with CIA inside!!!

It's a good topic, though. Adobe owns business books, documents.

Say a company has a white paper for you to download. Place your bets, will it be:
1. CBR
2. ePub
3. Kindle
4. mobi
5. PDF

Place your bets now.

...

Let me join the compression debate:
gzip can't compress multiple files and tar was used for fucking cassettes if I remember correctly which were cheap at the time but mostly just corrupted data.
* gzip for single files when the program which uses the format supports it (like GIMP, it's really useful in this case WHY IS THIS NOT THE DEFAULT OPTION? IT'S PROBABLY FASTER THAN SAVING TO A HARDDRIVE DIRECTLY)
* zip for accessibility
* 7zip for compression
* rar for spreading files over multiple downloads with as much links as required which can all be downloaded with a download manager and then reconstructed into the actual files
(checked)
Companies know nothing about tech but used PDF to print so it will be PDF. Not because it's good but because they don't know any better.

Ignore him. He adopted the poisonous XML-mindset the plan 9 dev warned us about. Better JSON, INI or fucking anything else

Except CBR/CBZ is bitmaps (compressed, but bitmaps still) in an archive container. PDF is a vector format, a large document will be much larger in CBR and have a fixed resolution.

The CB* formats are literally just compressed archives, put vector support in your reader and you'll read vector CB*s all day

HTML my manz. pdf is only used because in academia it's standard practice among all the "prestigious" groups. it's literally less aids to just embed your math crap in images in HTML. yes HTML is shit but these alternatives are strictly worse

non-ASCII characters
lol are you using the Windows codepage with blocks or utf-8?
both are shit

Why is RAR's multipart better than anyone else's?

Ups. Didn't know other formats supported that.
Never made multipart stuff myself but I only ever saw it compressed to rar.

It may be because of this:
menga.net/why-i-still-use-rar-instead-of-7z

But you're right: RAR might be obsolete

This is new to me, last time I've dealt with RAR multiparts they were r00, r01 and so forth.
Double-clicking is gay in any case, and 7-Zip's context menu recognizes them.

This doesn't work in 7-Zip, but I don't see why would it be very useful. You need all parts to extract anyway.

I like .djvu but ti is poorly supported.

You might already know, but it turns out part of the PDF format is turing complete. It can't be safely parsed.

I wish I would know why goodolddownloads and so on still use rar instead of 7zip.
Sage because offtopic

In the context of this thread, I have absolutely zero preference between JSON, XML, ini files or any other format.

Habit, probably.

If you are in fact referring to TeX, there is nothing -- NOTHING -- better for typesetting math. Nothing else even comes close. But by all means continue to poke around in your gui "equation editor" like a nigger.

I prefer plain ASCII, so I can read it fine with a pager like 'less', or on an old 80's computer, or my Nintendo DS Lite with Moonshell.
If there are some illustrations or diagrams, then just supply them as GIFs in a zip file along with the plain text, or an HTML document that preserves their location in the text. But I'll probably just run "lynx -dump" to extract just the plain text.

Is there a format which allows text formatting without imitating paper with retarded borders and XML? I don't know why all word processors fell to fucking paper no one prints out anyways and compressed XML no one would ever touch.
And a proper editor? (Something like MS Wordpad without the paperborders with a more unicode alternative than RTF?)

LMAO JUST USE POSTSCRIPT MY DUDE