Guys, leave
>>22 alone/ignore him. He's pretty "obvous"ly an Adobefag, thinking of "read-only" digital files (retarded and contradictory). Failing to notice I already knew KPDF can search, though not with regular expressions. Not realizing that files in someone's computer are soemone's files in someone's computer, thus subject to alteration. Not realizing one can hack PDFs too if he so desires, so PDF doesn't give any extra security anyways; never anything except for signed files, for which you don't need PDFs. Or that people will get fucked over by lawyers if they steal shit from others and try to make money from it anyways (this is an important issue in fucking with people). For not noticing that, he thinks he owns files in everybody else's computers. Give the dumbass a break. He lives in America - lots of lawyers, patents, DRM, DMCA and "rights-management" dumbshits there.
>>23
PDF has an additional con. It sucks for office work, because review and commentary works better when you can just edit a file and add comments. Any half-popular rich text editor supports it as well. diff is an excellent tool, just you need to RTFM.
>>24
I know the difference Adobefags make from "typesetting" to "editing an octet-stream", but I make none. Any operation I perform of my files is octet-stream editing. I want the most versatile high-level and low-level editing. I want to be able to do something useful with the data I have. That's why I prefer it text/plain, but I'll take other things I can process to do something useful with them.
For fuck's sake, not everything can or should be designed with HTML and CSS.
If there's something that, regardless of being possible or not with HTML and CSS, has you thinking about how to do it, then you need to rethink it as a whole: you are doing something wrong. Information should be easy to access and easy to lay out. Easy to access information is easy to lay out. Easily layed out information is almost always easy to access.
By deliberately avoiding PDFs and converting them to text, of which you seem so proud, you have no sense of what a properly typeset article should look like.
Oh, it's not text anymore, it's an
article! Fap fap fap lol documents. Fuck that. My "articles" read pretty well in my console. That's right, I even prefer fixed-width fonts to variable-width fonts. But it's just my preference. You want to read tiny Times text with goatse-anus-sized margins? You can. Or you should be able to, if, of course, you can transform text. I'll make it easy by keeping it text/plain.
I will allow you to read text I send to you (becoming YOUR file, not MINE, though it may be my text and my idea) in any way, because I understand and respect your possible need to use gay "designer" fonts and gay "designer" styles. Even if you like Comic Sans MS (lots of "designers" do). Why won't you understand and respect my need to browse my files in my preference?
Also, if you're a "designer", what the fuck are you doing in /prog? Go suck some Adobe cock elsewhere. We're Haskell/Python/Ruby/* trolls here, not "designers".
If you break the formatting of my article and then redistribute it, you make me look like an idiot.
No. If I don't understand your article, then I'm the idiot, not you. And if you used proper formats, then it'd be readable with any display options.
If you change the content of my contract, you can legally fuck me over.
And I can change it in a PDF file too. Except if signed. I can sign text/plain files too.
You've been dealing with text for 20 years, and you get frustrated because you can't edit the PDFs your clients send you.
11 years, and yes, I get frustrated. I'm used to process text files with perl, sed, grep, etc. Anything that allows me to use data in a creative, flexible way. Not a stupid "look mom, it looks like paper lol lol it's eazy lol lol" read-only browser.
>>26
Truth
>>27
HTML and CSS have their place. That place is in webpages on the internet
Then why do you "designer" fags keep offering PDF shit on MY Internet?
>>30
I'll second that.
>>31
Granted. As long as I get useful delicious plain text I'm ok.
>>32
I'm used to prefix or infix notation, even for complex Maths. I could take other formats though. Not PDF though.