I tried to upload issues 1, 3, 4, 5, 7, 16, & 17, but have no perms to push. EOM

[philgoetz]

I tried to upload issues 1, 3, 4, 5, 7, 16, & 17, but have no permission to push.

[macterra]

Please accept the collaborator invitation and try again, thanks

[giulioprisco]

Great! I look forward to reading those missing issues! G.

…

On 2019. May 16., Thu at 5:56, David McFadzean ***@***.***> wrote: Please accept the collaborator invitation and try again, thanks — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3?email_source=notifications&email_token=AAGSI6B4NMFYK43EZ4QQC63PVTLNXA5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVQST2I#issuecomment-492906985>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGSI6B7LZTJ7YE7ISJKUATPVTLNXANCNFSM4HNIDG2A> .

[philgoetz]

I didn't do any OCR on them. Perhaps I should do that first. On Thu, May 16, 2019 at 2:55 AM Giulio Prisco <notifications@github.com> wrote:

…

Great! I look forward to reading those missing issues! G. On 2019. May 16., Thu at 5:56, David McFadzean ***@***.***> wrote: > Please accept the collaborator invitation and try again, thanks > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > < #3?email_source=notifications&email_token=AAGSI6B4NMFYK43EZ4QQC63PVTLNXA5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVQST2I#issuecomment-492906985 >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AAGSI6B7LZTJ7YE7ISJKUATPVTLNXANCNFSM4HNIDG2A > > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3?email_source=notifications&email_token=AAVE7BGUW677W7I5CV2HVY3PVUAO5A5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVQ3KFQ#issuecomment-492942614>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAVE7BBFYEGQEUY5WOVHUU3PVUAO5ANCNFSM4HNIDG2A> .

[giulioprisco]

Perhaps the software you use to scan to pdf already includes OCR?

…

On 2019. May 16., Thu at 16:05, philgoetz ***@***.***> wrote: I didn't do any OCR on them. Perhaps I should do that first. On Thu, May 16, 2019 at 2:55 AM Giulio Prisco ***@***.***> wrote: > Great! I look forward to reading those missing issues! > G. > > On 2019. May 16., Thu at 5:56, David McFadzean ***@***.*** > > wrote: > > > Please accept the collaborator invitation and try again, thanks > > > > — > > You are receiving this because you are subscribed to this thread. > > Reply to this email directly, view it on GitHub > > < > #3?email_source=notifications&email_token=AAGSI6B4NMFYK43EZ4QQC63PVTLNXA5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVQST2I#issuecomment-492906985 > >, > > or mute the thread > > < > https://github.com/notifications/unsubscribe-auth/AAGSI6B7LZTJ7YE7ISJKUATPVTLNXANCNFSM4HNIDG2A > > > > . > > > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > < #3?email_source=notifications&email_token=AAVE7BGUW677W7I5CV2HVY3PVUAO5A5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVQ3KFQ#issuecomment-492942614 >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AAVE7BBFYEGQEUY5WOVHUU3PVUAO5ANCNFSM4HNIDG2A > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3?email_source=notifications&email_token=AAGSI6AZDSTKKDATA6WQ4ITPVVSZVA5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVR5IAI#issuecomment-493081601>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGSI6ESSUXVZBT6N4TSJV3PVVSZVANCNFSM4HNIDG2A> .

[philgoetz]

No, it doesn't. The scans aren't great--they're all a bit skewed, and some have vertical lines from dust on the sensor. On Thu, May 16, 2019 at 10:22 AM Giulio Prisco <notifications@github.com> wrote:

…

Perhaps the software you use to scan to pdf already includes OCR? On 2019. May 16., Thu at 16:05, philgoetz ***@***.***> wrote: > I didn't do any OCR on them. Perhaps I should do that first. > > On Thu, May 16, 2019 at 2:55 AM Giulio Prisco ***@***.***> > wrote: > > > Great! I look forward to reading those missing issues! > > G. > > > > On 2019. May 16., Thu at 5:56, David McFadzean < ***@***.*** > > > > wrote: > > > > > Please accept the collaborator invitation and try again, thanks > > > > > > — > > > You are receiving this because you are subscribed to this thread. > > > Reply to this email directly, view it on GitHub > > > < > > > #3?email_source=notifications&email_token=AAGSI6B4NMFYK43EZ4QQC63PVTLNXA5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVQST2I#issuecomment-492906985 > > >, > > > or mute the thread > > > < > > > https://github.com/notifications/unsubscribe-auth/AAGSI6B7LZTJ7YE7ISJKUATPVTLNXANCNFSM4HNIDG2A > > > > > > . > > > > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, view it on GitHub > > < > #3?email_source=notifications&email_token=AAVE7BGUW677W7I5CV2HVY3PVUAO5A5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVQ3KFQ#issuecomment-492942614 > >, > > or mute the thread > > < > https://github.com/notifications/unsubscribe-auth/AAVE7BBFYEGQEUY5WOVHUU3PVUAO5ANCNFSM4HNIDG2A > > > > . > > > > — > You are receiving this because you commented. > > > Reply to this email directly, view it on GitHub > < #3?email_source=notifications&email_token=AAGSI6AZDSTKKDATA6WQ4ITPVVSZVA5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVR5IAI#issuecomment-493081601 >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AAGSI6ESSUXVZBT6N4TSJV3PVVSZVANCNFSM4HNIDG2A > > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3?email_source=notifications&email_token=AAVE7BHWS56ZBMPHFVBOYIDPVVU3JA5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVR67QI#issuecomment-493088705>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAVE7BHOK45RSXVY5JKLHDTPVVU3JANCNFSM4HNIDG2A> .

[Famicoman]

@philgoetz I just stumbled upon this open issue. I would suggest uploading the missing issues now and worrying about OCR later. That can always be added later, and in the meantime these issues are not accessible.

I'm personally very interested in your contribution, and if you are reluctant to add them here, I'd love to acquire the files from you in another way.

[o-Epictetus-o]

I just found this, I don't know if it can be of any help though. http://fennetic.net/irc/extropy/

[macterra]

I'll check it out, thanks

…

On Tue, Jul 30, 2019 at 6:22 PM Kartereo ***@***.***> wrote: I just found this, I don't know if it can be of any help though. http://fennetic.net/irc/extropy/ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3?email_source=notifications&email_token=AADKDVCNQAURCCRQQKKWRELQCC5LXA5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3FPRSA#issuecomment-516618440>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADKDVARFBJ5XUQIDSQBHIDQCC5LXANCNFSM4HNIDG2A> .

[drannex42]

@philgoetz any updates on those uploads?

[philgoetz]

Hi--You've all expressed interest in getting my scans of early Extropy issues. (I don't know if my response will get to Macleod Sawyer and David McFadzean; the mailing list hid their email addresses from me.) I finally got my OCR program working--turned out all I had to do was validate my copy of Windows--and began running it on them, and found out it's a lot of work! Clean scans work well, but some of the issues were themselves printed very poorly, such as issue 7, and my OCR software (Omnipage) has a terrible user interface for correcting errors. What I'd really like is an editor that lets me go through the OCR results and edit them. (Omnipage does this by presenting one suspected error at a time, which is incredibly time-consuming and error-prone, since you can never see what it did with your edits, and it's impossible to edit some things. It's also impossible to add words to the dictionary while editing; the "add" key is always greyed out. This is a big problem with Extropy, which is full of words not in Omnipage's dictionary, like "meme", "transhuman", and many more.) If you know of any way to edit the OCRed text in a PDF, please let me know. Or if you know of any OCR program that will replace the scanned image with the inferred text in a similar font. Some of those Extropy back-issues have been OCRed with such a program, and it did a fantastic job--even producing perfect geometric figures to replace the ones in the original. I don't know if it's better for me to run an error-riddled OCR on them and post that, or just post the raw images without OCR. I don't know if a document can be run through a better OCR process, by someone more patient than me, once it's had OCR info attached to it. Please advise if you have an opinion on this. (Max never got back to me about permissions. I think it will be easier to get forgiveness.) At this point I'd like to just post most of them without any OCR. But I've lost my emails with information on where the website to post them to is, and I expect that I still don't have permission to post there. - Phil

…

[macterra]

@philgoetz You should have write access to the repo. LMK if you don't.

[macterra]

@giulioprisco Can you offer any OCR advice? Did you scan the issues that have been uploaded already?

[giulioprisco]

I would suggest that Phil uploads the raw scans first, and then we think of how to correct OCR errors. Phil, before OCRing did you produce raw scans in PDF or DJVU format? That would be better than nothing. G.

…

On Mon, Feb 24, 2020 at 2:18 AM David McFadzean ***@***.***> wrote: @giulioprisco <https://github.com/giulioprisco> Can you offer any OCR advice? Did you scan the issues that have been uploaded already? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3?email_source=notifications&email_token=AAGSI6BN5GUMZZRQZZQKZY3REMN5XA5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMWNJZQ#issuecomment-590140646>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGSI6B5URBEQR32D7K43DTREMN5XANCNFSM4HNIDG2A> .

[philgoetz]

Realistically, I'm not going to have time for weeks to OCR these myself, so I just posted issues 1, 3-5, and 7-17, plus one 1997 newsletter, to https://github.com/Extropians/Extropy. All without OCR. Sorry; I could've done this months ago. - Phil

…

[giulioprisco]

Thanks Phil! This step is much better than nothing, and I could finally read Extropy #1! Now only #2 is missing. I'll hunt for it. When we have the complete collection we can OCR everything and maybe produce a single PDF with the complete archive. Best - Giulio

…

On Thu, Feb 27, 2020 at 8:34 PM philgoetz ***@***.***> wrote: Realistically, I'm not going to have time for weeks to OCR these myself, so I just posted issues 1, 3-5, and 7-17, plus one 1997 newsletter, to https://github.com/Extropians/Extropy. All without OCR. Sorry; I could've done this months ago. - Phil > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3?email_source=notifications&email_token=AAGSI6GZW4BT664TEQ53NGLRFAITRA5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENFVCKQ#issuecomment-592138538>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGSI6AT2J2QRHMI3T4EG5LRFAITRANCNFSM4HNIDG2A> .

[macterra]

I've located my copy of issue 2. I'll see if I can get it scanned and converted to pdf...

[macterra]

Extropy #2 uploaded! Many printing defects in the original hardcopy unfortunately.

[philgoetz]

Thanks! Reading it now.

…

On Sat, Feb 29, 2020 at 10:26 AM David McFadzean ***@***.***> wrote: Extropy #2 <https://github.com/Extropians/Extropy/blob/master/Extropy%2002%201989.pdf> uploaded! Many printing defects in the original hardcopy unfortunately. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3?email_source=notifications&email_token=AAVE7BCPUUL5TPTY5245IHDRFEUMFA5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENL4X4Y#issuecomment-592956403>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAVE7BE2GXOUTSWSRQW2IQTRFEUMFANCNFSM4HNIDG2A> .

[giulioprisco]

Great! We have the complete collection now!

…

On 2020. Feb 29., Sat at 17:12, philgoetz ***@***.***> wrote: Thanks! Reading it now. On Sat, Feb 29, 2020 at 10:26 AM David McFadzean ***@***.*** > wrote: > Extropy #2 > < https://github.com/Extropians/Extropy/blob/master/Extropy%2002%201989.pdf> > uploaded! Many printing defects in the original hardcopy unfortunately. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > < #3?email_source=notifications&email_token=AAVE7BCPUUL5TPTY5245IHDRFEUMFA5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENL4X4Y#issuecomment-592956403 >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AAVE7BE2GXOUTSWSRQW2IQTRFEUMFANCNFSM4HNIDG2A > > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3?email_source=notifications&email_token=AAGSI6AUMVTQEL7PWC7BNVDRFEZWHA5CNFSM4HNIDG2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENL54FA#issuecomment-592961044>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGSI6ETK4OART6WDRILPITRFEZWHANCNFSM4HNIDG2A> .