Dear Anise and Chiara,
I just had a look on the Mac issue. It seems that Mac does need to be told
this is an executable.
The "technical" option would be to go to a terminal and run "chmod +x
path/to/NautilusApp". The Icon then changes to some kind of terminal icon
and can be run by double clicking.
I would believe there is a better option in MacOS but I am definitely not
familiar with this system. If anyone is willing to give the trick, that
would be awesome ;)
Best,
Thibault
2017-05-20 20:23 GMT+02:00 Anise <[log in to unmask]>:
> Hi all,
> What happened to Chiara happened to me too. Since I'm not an expert on
> that, just an 'explorer', probably I didn't understand the instructions.
> So, whoever answers to Chiara, please, answers to me too.
> Thanks🙏
> Anise
>
>
> 2017-05-20 7:10 GMT-03:00 [log in to unmask] <[log in to unmask]>:
>
>> Dear all,
>> I have been following the interesting discussion on Perseids and the
>> Captains framework. I tried to download NautilApp for Mac, but once I
>> download it, what I have is not an app, but a reading file opened by Text
>> Editor where I can find this error message:
>>
>> Contents.
>> Cannot open archive file
>> Could not allocate read buffer
>> Could not read from file
>> Error decompressing %s
>> %s could not be extracted!
>> Failed to write all bytes for %s
>> Could not allocate buffer for TOC. Could not read from file. Error on
>> file MEI
>> Error allocating decompression buffer
>> 1.2.5 Error %d from inflate: %s
>> Error %d from inflateInit: %s
>> rb __main__ Could not get __main__ module. Could not get __main__
>> module's dict. .py __file__ Failed to unmarshal code object for %s
>> Failed to execute script %s
>> %s%s%s%s%s / Error coping %s
>> %s%s%s%s%s%s%s .. %s%s%s.pkg %s%s%s.exe %s%s%s Archive not found: %s
>> Error extracting %s
>> Error allocating memory for status
>> Error opening archive %s
>> : Cannot allocate memory for ARCHIVE_STATUS
>> _MEIPASS2 Cannot open self %s or archive %s
>> PATH System error - unable to load! .pkg Py_DontWriteBytecodeFlag Cannot
>> dlsym for Py_DontWriteBytecodeFlag
>> Py_FileSystemDefaultEncoding Cannot dlsym for Py_FileSystemDefaultEncoding
>> Py_FrozenFlag Cannot dlsym for Py_FrozenFlag
>> Py_IgnoreEnvironmentFlag Cannot dlsym for Py_IgnoreEnvironmentFlag
>> Py_NoSiteFlag Cannot dlsym for Py_NoSiteFlag
>> Py_NoUserSiteDirectory Cannot dlsym for Py_NoUserSiteDirectory
>> Py_OptimizeFlag Cannot dlsym for Py_OptimizeFlag
>> Py_VerboseFlag Cannot dlsym for Py_VerboseFlag
>> Py_BuildValue Cannot dlsym for Py_BuildValue
>> Py_DecRef Cannot dlsym for Py_DecRef
>> Py_Finalize Cannot dlsym for Py_Finalize
>> Py_IncRef Cannot dlsym for Py_IncRef
>> Py_Initialize Cannot dlsym for Py_Initialize
>> Py_SetPath Cannot dlsym for Py_SetPath
>> Py_SetProgramName Cannot dlsym for Py_SetProgramName
>> Py_SetPythonHome Cannot dlsym for Py_SetPythonHome
>> PyDict_GetItemString Cannot dlsym for PyDict_GetItemString
>> PyErr_Clear Cannot dlsym for PyErr_Clear
>> PyErr_Occurred Cannot dlsym for PyErr_Occurred
>> PyErr_Print Cannot dlsym for PyErr_Print
>> PyImport_AddModule Cannot dlsym for PyImport_AddModule
>> PyImport_ExecCodeModule Cannot dlsym for PyImport_ExecCodeModule
>> PyImport_ImportModule Cannot dlsym for PyImport_ImportModule
>> PyList_Append Cannot dlsym for PyList_Append
>> PyList_New Cannot dlsym for PyList_New
>> PyLong_AsLong Cannot dlsym for PyLong_AsLong
>> PyModule_GetDict Cannot dlsym for PyModule_GetDict
>> PyObject_CallFunction Cannot dlsym for PyObject_CallFunction
>> PyObject_SetAttrString Cannot dlsym for PyObject_SetAttrString
>> PyRun_SimpleString Cannot dlsym for PyRun_SimpleString
>> PyString_FromString Cannot dlsym for PyString_FromString
>> PyString_FromFormat Cannot dlsym for PyString_FromFormat
>> PySys_AddWarnOption Cannot dlsym for PySys_AddWarnOption
>> PySys_SetArgvEx Cannot dlsym for PySys_SetArgvEx
>> PySys_GetObject Cannot dlsym for PySys_GetObject
>> PySys_SetObject Cannot dlsym for PySys_SetObject
>> PySys_SetPath Cannot dlsym for PySys_SetPath
>> PyEval_EvalCode Cannot dlsym for PyEval_EvalCode
>> PyMarshal_ReadObjectFromString Cannot dlsym for
>> PyMarshal_ReadObjectFromString
>> PyUnicode_FromString Cannot dlsym for PyUnicode_FromString
>> Py_DecodeLocale Cannot dlsym for Py_DecodeLocale
>> _Py_char2wchar Cannot dlsym for _Py_char2wchar
>> PyUnicode_FromFormat Cannot dlsym for PyUnicode_FromFormat
>> PyUnicode_Decode Cannot dlsym for PyUnicode_Decode
>> PyUnicode_DecodeFSDefault Cannot dlsym for PyUnicode_DecodeFSDefault
>> Error loading Python lib '%s': %s
>> out of memory
>> Fatal error: unable to decode the command line argument #%i
>> Failed to convert progname to wchar_t
>> base_library.zip Failed to convert pypath to wchar_t
>> Failed to convert pyhome to wchar_t
>> Error detected starting Python VM. Failed to get _MEIPASS as PyObject.
>> _MEIPASS marshal loads s# y# mod is NULL - %s %s?%d %U?%d path Installing
>> PYZ: Could not get sys.path
>> Failed to append to sys.path
>> Failed to convert argv to wchar_t
>> pyi- Failed to convert Wflag %s using mbstowcs (invalid multibyte string)
>> _MEIXXXXXX INTERNAL ERROR: cannot create temporary directory!
>> WARNING: file already exists but should not: %s
>> wb DYLD_FRAMEWORK_PATH DYLD_FALLBACK_FRAMEWORK_PATH
>> DYLD_VERSIONED_FRAMEWORK_PATH DYLD_LIBRARY_PATH DYLD_FALLBACK_LIBRARY_PATH
>> DYLD_VERSIONED_LIBRARY_PATH DYLD_ROOT_PATH -psn . TMPDIR TEMP TMP /tmp
>> /var/tmp /usr/tmp ? 4 4 —X !
>>
>> I know the software is new, but Is there anything I should do that I am
>> not doing, before downloading the app? Maybe something related with Python?
>> Thanks for the work on the CTS Perseids web site. It is helpful to
>> understand how the framework behind it works, concerning the communication
>> method between its users.
>> Regards,
>> Chiara Salvagni
>>
>> On 20 May 2017, at 01:02, DIGITALCLASSICIST automatic digest system <
>> [log in to unmask]> wrote:
>>
>> There are 4 messages totaling 618 lines in this issue.
>>
>> Topics of the day:
>>
>> 1. Linking to the Perseus Digital Library (3)
>> 2. Standalone CapiTainS Corpora Reader for Windows, Ubuntu and Mac
>> (Looking
>> for Beta Testers and Collaborators)
>>
>> ----------------------------------------------------------------------
>>
>> Date: Fri, 19 May 2017 12:56:31 +0100
>> From: Yiannis Doukas <[log in to unmask]>
>> Subject: Re: Linking to the Perseus Digital Library
>>
>> Dear all,
>> my thanks to everybody for getting back to me off- and on-list, for all
>> the
>> helpful suggestions and solutions provided and for the discussion that
>> followed.
>> All the best,
>> Yiannis
>>
>> 2017-05-18 15:35 GMT+01:00 Thibault Clérice <[log in to unmask]>:
>>
>> Hi everyone,
>> I am the developer behind the framework used in http://cts.perseids.org
>> and http://cts.dh.uni-leipzig.de/ (which unfortunately is suffering from
>> memory issues lately). The framework is Capitains ( http://capitains.org/
>> ) if any of you were interested to dig deeper.
>>
>> We do not provide, through CapiTainS, access to word level tokens, while
>> we accept these identifiers. There is few reasons behind it including the
>> status of the corpora and some problems tied to the standard. Though,
>> Yiannis, for your original purpose, I would just like to mention the
>> OpenAnnotation standards that aims at providing solid text selectors for
>> chunks and that is more vastly supported by the IT community (
>> https://www.w3.org/TR/annotation-model/#text-quote-selector )
>>
>> I hope to have provided an answer to your question
>>
>> Best,
>> Thibault
>>
>>
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source
>> =link&utm_campaign=sig-email&utm_content=webmail> Garanti
>> sans virus. www.avast.com
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source
>> =link&utm_campaign=sig-email&utm_content=webmail>
>> <#m_8435294108183331065_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>>
>> ------------------------------
>>
>> Date: Fri, 19 May 2017 15:06:04 +0200
>> From: Thibault Clérice <[log in to unmask]>
>> Subject: Standalone CapiTainS Corpora Reader for Windows, Ubuntu and Mac
>> (Looking for Beta Testers and Collaborators)
>>
>> Dear all,
>>
>> After the talk yesterday on identifiers of Perseus, I would like to
>> promote
>> a small portable software I wrote to help people run their own reading
>> environment based on CapiTainS corpora (To learn more about CapiTainS :
>> http://capitains.org and a blog post about the future of it
>> http://capitains.org/milestones/2017/04/28/2.0.0 )
>>
>> You can find the software here https://github.com/Capitains/nautilapp
>>
>> *Be careful using this software, it is possible it would crash. Only use
>> if
>> you know how to kill a process on your system.*
>>
>> Here is a list of know CapiTainS Corpora :
>>
>> - https://github.com/OpenGreekAndLatin/First1KGreek
>> - https://github.com/OpenGreekAndLatin/csel-dev
>> - https://github.com/PerseusDL/canonical-latinLit
>> - https://github.com/PerseusDL/canonical-greekLit
>> - https://github.com/nevenjovanovic/cts-croala (While the Reading
>> Interface
>> might not work for this one, the API should.)
>>
>> A little warning : while I have some experience in web design and python
>> programming, I was totally new to GUI TK development still yesterday
>> afternoon. The interface that helps you run the whole thing is pretty ugly
>> and - I am sure - could be enhanced a lot ( See
>> https://github.com/Capitains/nautilapp#developers if you want to
>> contribute
>> :) )
>>
>> This is the first time I compile something for Windows, Ubuntu and Mac, so
>> it's possible you'd find bugs. If you find some, you can write me a mail
>> or
>> simply enter an issue on Github ( https://github.com/Capitains/
>> nautilapp/issues ). I'd be happy if other people take on the GUI
>> improvement, now that the basis is done.I am looking forward your
>> feedback,
>>
>> Kind regards,
>>
>> Thibault Clérice
>>
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source
>> =link&utm_campaign=sig-email&utm_content=webmail>
>> Garanti
>> sans virus. www.avast.com
>> <https://www.avast.com/sig-email?utm_medium=email&utm_source
>> =link&utm_campaign=sig-email&utm_content=webmail>
>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>> ------------------------------
>>
>> Date: Fri, 19 May 2017 16:42:48 +0200
>> From: Neven Jovanovic <[log in to unmask]>
>> Subject: Re: Linking to the Perseus Digital Library
>>
>>
>> Hi Yiannis,
>>
>> may I just point out another approach -- through Perseids it is now
>> possible to annotate either a chosen passage or its selection by choosing
>> the "Annotate in Perseids" link. On the page that will open (after you
>> login to Perseids; best to create an account beforehand at the
>> <http://sosol.perseids.org/sosol/signin>), you can either annotate with
>> some pre-existing categories ("Has Translation", "Has Classification") or
>> you can add your own URI (Uniform Resource Identifier) for the type of
>> relationship that you want to annotate. If you choose to add your own URI,
>> you are responsible for publishing something at the other end of the
>> identifier -- but this might be just what you need.
>>
>> The publishing side of Perseids is, I think, not completely ready (or
>> perhaps even conceptualized) yet, so you cannot refer to the annotation
>> you've made directly from the outside: you should submit the annotation to
>> a board (if you ask the administrators, they will gladly create a board
>> for you and your team), and, after an annotation is reviewed and finalized
>> (by yourself, if you're the board as well), you should probably export it
>> and publish it somewhere on your own (see the examples here:
>> <http://sites.tufts.edu/perseids/publications/student-publications/>).
>> The
>> important thing is that all identifiers are prepared for you -- but you
>> have to make them accessible (and stable). (This is, after all, more in
>> line of creating a scholarly publication, like writing a book, carefully
>> checking each note and quotation -- but that's just my opinion.)
>>
>> The important thing is that it is the users who push Perseids forward and
>> make it grow (I'm speaking from my own experience), so try to contact
>> Bridget Almas, who is the lead developer of Perseids
>> <http://www.perseus.tufts.edu/hopper/about/who/bridgetAlmas>, and see how
>> Perseids can serve what you want to do.
>>
>> And best of luck with your Ph. D!
>>
>> Neven
>>
>> Neven Jovanovic
>> Zagreb, Croatia
>>
>>
>>
>>
>>
>> On Sri, svibanj 17, 2017 6:49 pm, Yiannis Doukas wrote:
>>
>> Dear all,
>>
>> I am working on a digital intertextuality project as part of my Ph.D. In
>> this, I will present late Greek epic texts along with a commentary
>> focusing
>> on sources and parallels.
>>
>> I?m planning to cross-reference to the texts as they are included in the
>> Perseus Digital Library, by using the Citation URI stable identifier
>> provided. My problem is that, in most cases, I only need to link to short
>> passages, of two or three lines, or even specific words, while (if I am
>> not
>> mistaken) the citation URIs correspond to larger chunks of text (or even
>> whole poems).
>>
>> My question then: is it possible to manipulate the URI or is there some
>> other way available in order to link to a specific line in a text of the
>> Perseus Digital Library?
>>
>> Thanking you in advance,
>>
>> Yiannis Doukas
>>
>>
>> ------------------------------
>>
>> Date: Fri, 19 May 2017 11:28:40 -0400
>> From: Bridget Almas <[log in to unmask]>
>> Subject: Re: Linking to the Perseus Digital Library
>>
>>
>> Hi all
>>
>> Sorry for the delay in chiming in on this very interesting topic.
>>
>> A few points
>>
>> 1) Neven is correct that you can annotate textual passages in Perseids.
>> As for the publication of these annotations, we are currently working on
>> a few things that will make this a bit more organized, including
>> implementing the RDA Collections API
>> (https://www.rd-alliance.org/groups/pid-collections-wg.html) to enable
>> us to better manage annotations produced on the platform (including
>> giving you the ability to refer to it from outside the platform) and
>> enabling users to download their annotations as structured BagIt
>> archives that could be preserved in institutional repositories or
>> deployed in other applications. We are also working on a individual
>> publishing solution for treebank data which will work with GitHub pages.
>> We won't get to the point where that sort of individual publishing
>> solution is available for all types of annotations on Perseids, at least
>> not under current funding, but maybe what we do get done can inspire
>> future work.
>>
>> 2) As for the annotations themselves, the current Perseids annotation
>> interface that Neven refers to should eventually be replaced with the
>> much nicer Plokamos semantic annotation tool, which we are currently
>> using for Social Network annotations but which we designed with the
>> intent that it could be used much more widely than that. (See
>> http://sites.tufts.edu/perseids/2016/12/16/announcing-plokam
>> os-a-semantic-annotation-tool/).
>> An important difference between Plokamos and the older Perseids
>> annotation editor is that Plokamos uses Open Annotation Text Selectors
>> to reference individual words in the text, rather than the CTS URN
>> subreferences. Our experience with the subreferences is that it's very
>> difficult to support those at scale, especially when you are dealing
>> with texts which are still in the process of curation.
>>
>> So, to make that difference more concrete:
>>
>> The original version of the Perseids Annotation Editor saves an
>> annotation that has a triple something like this:
>>
>> <anno1> a oa:Annotation ;
>> oa:hasBody <http://example.org> .
>> oa:hasTarget <urn:cts:greekLit:tlg0085.tlg003.opp-grc3:1-20@τηλουρὸν[1]>
>> .
>>
>>
>> Plokamos instead uses an OA Text Selector as the target, e.g something
>> like
>>
>> <anno1> a oa:Annotation ;
>> oa:hasBody <http://example.org> .
>> oa:hasTarget <sptarget1> .
>>
>> <sptarget1> a oa:SpecificResource ;
>> oa:hasSource <urn:cts:greekLit:tlg0085.tlg003.opp-grc3:1-20> ;
>> oa:hasSelector <selector1> .
>>
>> <selector1> a oa:TextQuoteSelector ;
>> oa:exact "τηλουρὸν" ;
>> oa:prefix "Χθονὸς μὲν ἐς"
>> oa:suffix "ἥκομεν πέδον" .
>>
>> OpenAnnotation (now Web Annotation) allows for multiple selectors, so an
>> approach which combined both might give the best of both worlds. 3) For
>> all of these annotations though, the use of the CTS URN, with or without
>> subreference, is problematic because it is not by itself web resolvable.
>> It's okay if these all come from one repository or CTS API endpoint such
>> as cts.perseids.org, but that is increasingly not the case. I will be
>> posting more soon about a new effort to research use of the Handle
>> System to offer the community one approach to solving that. All the best
>> Bridget
>> On 05/19/2017 10:42 AM, Neven Jovanovic wrote:
>>
>> Hi Yiannis,
>>
>> may I just point out another approach -- through Perseids it is now
>> possible to annotate either a chosen passage or its selection by choosing
>> the "Annotate in Perseids" link. On the page that will open (after you
>> login to Perseids; best to create an account beforehand at the
>> <http://sosol.perseids.org/sosol/signin>), you can either annotate with
>> some pre-existing categories ("Has Translation", "Has Classification") or
>> you can add your own URI (Uniform Resource Identifier) for the type of
>> relationship that you want to annotate. If you choose to add your own URI,
>> you are responsible for publishing something at the other end of the
>> identifier -- but this might be just what you need.
>>
>> The publishing side of Perseids is, I think, not completely ready (or
>> perhaps even conceptualized) yet, so you cannot refer to the annotation
>> you've made directly from the outside: you should submit the annotation to
>> a board (if you ask the administrators, they will gladly create a board
>> for you and your team), and, after an annotation is reviewed and finalized
>> (by yourself, if you're the board as well), you should probably export it
>> and publish it somewhere on your own (see the examples here:
>> <http://sites.tufts.edu/perseids/publications/student-publications/>).
>> The
>> important thing is that all identifiers are prepared for you -- but you
>> have to make them accessible (and stable). (This is, after all, more in
>> line of creating a scholarly publication, like writing a book, carefully
>> checking each note and quotation -- but that's just my opinion.)
>>
>> The important thing is that it is the users who push Perseids forward and
>> make it grow (I'm speaking from my own experience), so try to contact
>> Bridget Almas, who is the lead developer of Perseids
>> <http://www.perseus.tufts.edu/hopper/about/who/bridgetAlmas>, and see how
>> Perseids can serve what you want to do.
>>
>> And best of luck with your Ph. D!
>>
>> Neven
>>
>> Neven Jovanovic
>> Zagreb, Croatia
>>
>>
>>
>>
>>
>> On Sri, svibanj 17, 2017 6:49 pm, Yiannis Doukas wrote:
>>
>> Dear all,
>>
>> I am working on a digital intertextuality project as part of my Ph.D. In
>> this, I will present late Greek epic texts along with a commentary
>> focusing
>> on sources and parallels.
>>
>> I?m planning to cross-reference to the texts as they are included in the
>> Perseus Digital Library, by using the Citation URI stable identifier
>> provided. My problem is that, in most cases, I only need to link to short
>> passages, of two or three lines, or even specific words, while (if I am
>> not
>> mistaken) the citation URIs correspond to larger chunks of text (or even
>> whole poems).
>>
>> My question then: is it possible to manipulate the URI or is there some
>> other way available in order to link to a specific line in a text of the
>> Perseus Digital Library?
>>
>> Thanking you in advance,
>>
>> Yiannis Doukas
>>
>>
>> ------------------------------
>>
>> End of DIGITALCLASSICIST Digest - 18 May 2017 to 19 May 2017 (#2017-56)
>> ***********************************************************************
>>
>>
>>
>
