[poppler] PDF 2.0 Spec

[Leonard Rosenthol]

> The exception is citing - e.g. if you want to 
>    copy paragraphs word by word into source code or issue comments, you 
>    need a copy of the standard.
>
You can't do that with an ISO document.  ISO does not permit copying of their material.   You can, of course, cite the section (and paragraph, note, etc.) in code - for which you would need the PDF standard itself.

Leonard


On 11/29/18, 9:46 AM, "poppler on behalf of Tobias Deiminger" <poppler-bounces at lists.freedesktop.org on behalf of haxtibal at posteo.de> wrote:

    Am 28.11.2018 23:18 schrieb Albert Astals Cid:
    >> a) "I won't do any poppler patches during the next 6 months
    >> and won't need the copy during that time. You can give the
    >> copy to someone else during these 6 months."
    > 
    > Sorry for being annoying here, but what happens after those 6 months?
    > can he contribute back without needing a "license"?
    
    No problem, let's try to figure it out. IANAL, but as far as I 
    understand contributing to poppler is generally not related to owning a 
    copy of the PDF standard. The exception is citing - e.g. if you want to 
    copy paragraphs word by word into source code or issue comments, you 
    need a copy of the standard. Considering the 6 months example above, if 
    you want to contribute a bugfix after you gave the copy away, you just 
    do it. But if you need to cite the standard or need to learn something 
    new from it, you write KDE and say "can you please reassign a copy to 
    me". If you have different opinion or doubts, please explain a bit, then 
    I can ask DIN again.
    
    > I mean i very seldom read the PDF spec since most of the times bugs i'm
    > fixing are just that bugs, not missing spec features or misimplemented 
    > spec
    > features that actually need me to read the spec.
    
    My primary use case of the standard is learning, i.e. I often have 
    poppler source code on the left and the standard on the right, because 
    the code is closely written along the standard wrt. terminology, data 
    structures and algorithms. Imo it's good practice, new code should also 
    follow it. However using the standard for that purpose is just my 
    preferred method, one could use books or years of experience instead.
    
    > You can do it. You're as much a KDE developer as I am :)
    
    Ok, will CC you then. Any idea how much copies would be appropriate?
    
    Cheers
    Tobias
    _______________________________________________
    poppler mailing list
    poppler at lists.freedesktop.org
    https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Fpoppler&data=02%7C01%7Clrosenth%40adobe.com%7C045d9bf7e7854de97f7508d65609673f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636790995747619288&sdata=0Udj0Pj%2BnfDeaD8TB35UCMyBbJO1bi0B5rZHvdLq2MQ%3D&reserved=0