Live data from Hacker News

PEP – An open source PDF editor for Mac

macpep.org

41–50 of 113 posts

Re: PEP – An open source PDF editor for Mac

#41

Earlier quoted context omitted.

> I wish that once people do name their project, they would assign it a 128-bit random number in lower case hex We already have something similar: URLs.

Yeah but urls and names might need to change due to marketing. A hash would uniquely id the project and let the marketing aspect be dynamic. Although if the actual project name, authors, and codebase changes is it even still the same project?

Then maybe what really needs to happen is we burn all marketers in a pyre? So they quit fucking up things that ain’t fucked up?

Re: PEP – An open source PDF editor for Mac

#42
post #14

Earlier quoted context omitted.

I wish that once people do name their project, they would assign it a 128-bit random number in lower case hex, and include that number on any web page that they would like people searching for their project to find. That way once I know that say PEP the PDF editor exists and find its 128-bit number (let's say that is 379dd864b16eaca3ce94c15a6bdfcc73), at least I can subsequently toss a +379dd864b16eaca3ce94c15a6bdfcc…

8 bit ascii could work. 8^256 is a huge number.

A 256 bit number is 2^256 possible combinations. 8^256 is the same as (2^3)^256 (or 2^768)

Re: PEP – An open source PDF editor for Mac

#43
post #14

Earlier quoted context omitted.

I wish that once people do name their project, they would assign it a 128-bit random number in lower case hex, and include that number on any web page that they would like people searching for their project to find. That way once I know that say PEP the PDF editor exists and find its 128-bit number (let's say that is 379dd864b16eaca3ce94c15a6bdfcc73), at least I can subsequently toss a +379dd864b16eaca3ce94c15a6bdfcc…

> I wish that once people do name their project, they would assign it a 128-bit random number in lower case hex We already have something similar: URLs.

tzs is proposing URNs rather than textual program names. A URL is unnecessarily specific (though I suppose you could anycast URL resolution)

Re: PEP – An open source PDF editor for Mac

#44
post #9

I have a dream... that one day people will name their projects with names that don't exist on google yet. If you search for PEP now you'll find python enhancement proposals, and the "Philippine Entertainment Portal" and the stock code for PepsiCo.

PEP is also "Politically exposed person" in anti money launcering circles, and often the lists we get are PDFs.

Seems like PEP is used for more things too :)

Re: PEP – An open source PDF editor for Mac

#45
post #8

Hi, developer of a PDF scanning app for macOS (PDFScanner) here. I always toyed with the idea of developing a PDF engine from scratch but the spec scares me. Kudos for being that brave! Just curious: Why did you choose Objective-C for a new lib?

I am a happy user of PDFScanner. How are you doing the OCR?

I use the hocr feature of tesseract and parse the resulting xml that contains all the text with bounding boxes.

Re: PEP – An open source PDF editor for Mac

#46

Earlier quoted context omitted.

> I wish that once people do name their project, they would assign it a 128-bit random number in lower case hex We already have something similar: URLs.

Except a URL only points to one resource. The idea here is that this identifier would exist on any resource related to PEP (maybe even in URLs).

[deleted]

Re: PEP – An open source PDF editor for Mac

#47
post #44
post #9

I have a dream... that one day people will name their projects with names that don't exist on google yet. If you search for PEP now you'll find python enhancement proposals, and the "Philippine Entertainment Portal" and the stock code for PepsiCo.

PEP is also "Politically exposed person" in anti money launcering circles, and often the lists we get are PDFs. Seems like PEP is used for more things too :)

I study biochemistry, so “phosphoenolpyruvate” was the first thing to come to mind, ha.

Re: PEP – An open source PDF editor for Mac

#48

A GUI app for manually crafting PDFs is one thing, but a library instead would enable countless developers to create software capable of producing PDF deliverables as output, possibly improving the accessibility situation too. I would gladly sponsor the development of a reliable library that allows to programmatically produce compliant, accessible tagged PDFs with arbitrary layout[0], correctly printable and viewable…

I would expect other apps to use the core of PEP, Gene. Which will be easy to use as dragging and dropping Gene folder into other projects in Xcode. Gene is a stand alone lib, and is licensed in GPL2.

Re: PEP – An open source PDF editor for Mac

#49
post #14
post #9

I have a dream... that one day people will name their projects with names that don't exist on google yet. If you search for PEP now you'll find python enhancement proposals, and the "Philippine Entertainment Portal" and the stock code for PepsiCo.

I wish that once people do name their project, they would assign it a 128-bit random number in lower case hex, and include that number on any web page that they would like people searching for their project to find. That way once I know that say PEP the PDF editor exists and find its 128-bit number (let's say that is 379dd864b16eaca3ce94c15a6bdfcc73), at least I can subsequently toss a +379dd864b16eaca3ce94c15a6bdfcc…

That's actually a pretty solid idea. A meta tag for topics.

Only issue would be handling inevitable "SEO-ified" abusers of it.

Re: PEP – An open source PDF editor for Mac

#50
post #14

Earlier quoted context omitted.

I wish that once people do name their project, they would assign it a 128-bit random number in lower case hex, and include that number on any web page that they would like people searching for their project to find. That way once I know that say PEP the PDF editor exists and find its 128-bit number (let's say that is 379dd864b16eaca3ce94c15a6bdfcc73), at least I can subsequently toss a +379dd864b16eaca3ce94c15a6bdfcc…

That's actually a pretty solid idea. A meta tag for topics. Only issue would be handling inevitable "SEO-ified" abusers of it.

Simple solution: 379dd864b16eaca3ce94c15a6bdfcc73™
Post reply on HN