eeditiones / tei-publisher-app Goto Github PK

If you browse into a collection, view a document and then want to go back to the collection, you don't have a way to do it directly. Would be nice to have a separate button in the toolbar (or menu) to bring you back into the collection you were browsing previously.

• View a document and use sidebar to switch to a different ODD
• Reload the page: ODD is set back to teipublisher.odd

I was following the YouTube workshop to learn how to use TEI-publisher.
When I was editing ODD for a file I uploaded in the "playground" section, I had to log out, log in, then click the "save" button at the left-top corner. Otherwise, an error window would jump out, with only Error-undefined-CLOSE as a message. After a day, even this method didn't work anymore. No matter using the tei-demo account or a user account I created myself in User Manager in eXist-db dashboard, I can not save any element after creating/modifying a model or a model sequence. The error message itself does not give me any useful information.

Suggestion:
The page templates seem to get different general page margins and display rules. This should be unified as it makes it much easier to style all pages consistently and control the responsive behavior.
This can be achieved either by generally using a grid system like css-grid / flex, or by stacking elements in rows and columns by following a consistent padding / margin rule in the correct order.

Example:
To demonstrate the current styling by just adding a pink background-color, this is how a <h1> element is nested in the index.html. You see that the main wrapper is shrinking the content by adding a margin, which leaves a gap between "screen" and inner element.

If the page margins (padding) were set correctly, the h1 element or its wrapping section could fill the screen. This is crucial for controlling a responsive behavior of the elements, or be able to set custom backgrounds for example.

Also, when planning a grid as a default layout, consider fallbacks when not all elements are implemented as intended but customized, so that the layout will always be "stable" and gaps will be filled.

Probably only Chrome requires shadowRoot.getSelection.

Reporting here on Git as several months since first report on Slack and others also reporting as bug in 7.0 after upgrading from earlier versions of TEI Publisher (where the navigation for their works functioned fine).

Here is description of issue as it manifests in a specific example:

Document comprised of 40 categories. For nearly all categories, the category is further divided into two parts (main and addenda). Each part has a number of entries ranging from 1 to 100+. These are encoded as nested divs.

Here is a simplified representation of my document structure:

Link becomes undefined/49548.xml

Yesterday I tried to update Tei-Publisher from 7 to 7.1 in my test environment running with docker. The app was updated by the documents were not displayed and I got "the server did not return any content/The request to the server failed.: The request to the server failed." repeated in the page. I decided to stop the container, remove it and pull the new image. It seemed all fine, until my ssh session crashed and the container stopped (I had not started it as permanent). When I restarted the container, the error appeared again, so I deleted it and restarted from the beginning, I even deleted the image, but nothing fixed it. Please note that I can upload files, and even edit them in exide, but I sill have the error in display.
I checked again from the virtual machine and it all works on localhost and by using the ip and port, but not when I call it with the external url, so there must be something wrong there. Please not that 7 run with no problem and Shakespeare Plays are perfectly healthy. I am unsure if this is a bug or a configuration problem in docker.

When uploading a docx to teipublisher 7.2.0 I get:

Type error: the given string '[trash]' cannot be cast to xs:anyURI [at line 201 of /exist/etc/../data/expathrepo/tei-publisher-lib-2.9.0/content/docx.xql

The docx file contains a directory named "[trash]" which causes this problem.

Full stacktrace:

exerr:ERROR Type error: the given string '[trash]' cannot be cast to xs:anyURI [at line 201, column 13, source: /exist/etc/../data/expathrepo/tei-publisher-lib-2.9.0/content/docx.xql] In function: docx:mkcol-recursive(item()*, item()*) [188:29:/exist/etc/../data/expathrepo/tei-publisher-lib-2.9.0/content/docx.xql] docx:unzip-file(xs:string, xs:anyURI, xs:string, item()?, item()*) [-1:-1:/exist/etc/../data/expathrepo/tei-publisher-lib-2.9.0/content/docx.xql] partial1400441619(xs:anyURI, xs:string, item()?, item()*) [175:13:/exist/etc/../data/expathrepo/tei-publisher-lib-2.9.0/content/docx.xql] docx:unzip(xs:string, xs:string) [31:26:/exist/etc/../data/expathrepo/tei-publisher-lib-2.9.0/content/docx.xql] docx:process(xs:string, xs:string, function(*), xs:string?) [61:33:/exist/etc/../data/expathrepo/tei-publisher-lib-2.9.0/content/docx.xql] (item()*, item()*) [49:46:/db/apps/tei-publisher/modules/lib/api/collection.xql] capi:upload(item()*, item()*, item()*) [45:17:/db/apps/tei-publisher/modules/lib/api/collection.xql] capi:upload(map(*)) [176:30:/db/apps/tei-publisher/modules/lib/api/collection.xql]. Type error: the given string '[trash]' cannot be cast to xs:anyURI [at line 201 of /exist/etc/../data/expathrepo/tei-publisher-lib-2.9.0/content/docx.xql]```

App generation produces a modules/pm-config.xql limited to a single app. It is unclear to users how to extend it for multiple ODDs.

After using the upload panel to upload an ODD file, you get an error if you select the ODD for the first time to display a document. This happens because the ODD is not compiled automatically.

An app updated to 6.0.0 about a week ago, issue noticed on 2020-08-27. ODD file is attached.

kivi.zip

Any changes made to any model in the visual ODD editor of 6.0.0, e.g. changing a rendition slightly, and saving changes appears to screw up the way the element is displayed, as if the element had no rendition set at all. Any subsequent changes, including undoing the change made earlier, have no effect. Looking at the css file corresponding to the ODD file under /transform, the css classes for the edited models appear with :null, e.g.: .tei-note2:null {...}. Removing the :null manually causes the changes to take effect and the display of the elements to be otherwise restored. But if one then goes back to the visual ODD editor and simply presses save again, the issue comes back, with the :null in the css classes visible again. The issue does not occur when editing the ODD file in eXide.

I am not sure this is the correct repository to raise this issue but I would deeply appreciate built-in support for right-to-left languages based on the @xml:lang attribute. Currently, none of the built-in ODDs correctly renders Arabic as right-aligned. This could be done by a simple CSS instruction for all block-level XML elements that carry a limited range of values in their @xml:lang attribute. The CSS would be something like

/* render Arabic, Ottoman, Persian, and Hebrew as rtl */
[lang = "ar"],
[lang = "ota"],
[lang = "fa"],
[lang = "he"],
[lang *="-Arab-AR"]{
    direction:rtl;
    text-align:right;
}
/* render languages in Latin script as ltr */
/* this is not strictly necessary as the behaviour defaults to ltr */
[lang = "en"],
[lang = "fr"],
[lang = "de"],
[lang = "it"],
[lang *="ar-Latn-"],
[lang *="ota-Latn-"]{
    direction:ltr;
    text-align:left;
}

In addition, it would make sense to change the default font based on the script family as the default fonts aren't very legible for Arabic script.

In the default view with three panels, if one switches the third panel to facsimile view, image navigation controls show but images do not, until one adds a fourth panel. In the fourth panel, neither navigation controls nor images then load until one reloads the page.

The issue is present with other applications that use a similar template to the Van Gogh demo, i.e. a grid with ability to add and remove panels, both in TEI Publisher 6.x and 7.x. The issue does not seem to be browser related, as it is present both in Chrome and Firefox.

After clicking App Generator , filled the table, and clicked SAVE/GENERATE button, then I went to the dashboard, opened the app, logged in, uploaded exactly the same .xml file I used with creating odd and template earlier, the following error message showed up without conveying any useful information.

We keep getting the following error message after trying to generate an application:

This XML file does not appear to have any style information associated with it. The document tree is shown below.

/db/apps/siegedantioch-beta3/modules/lib/api.xql
err:XQST0059 error found while loading module dapi: Error while loading module api/document.xql: error found while loading module pages: Error while loading module ../pages.xql: error found while loading module pm-config: Error while loading module ../pm-config.xql: error found while loading module pm-docx-tei: Permission denied to read module source from location hint URI '../transform/docx-tei-module.xql.

We tried the slack forum and they told us:

"The permissions on modules/pm-config.xql in your generated app are wrong. Could you check what they are? The file should be owned by your app user and group "tei" and needs to be executable."

We checked and found that the file was indeed under a different group; however, we changed it, yet the error is still there. Would someone be able to help us identify if this is an issue with TEI Publisher or just something we are missing on our end.

Wrong password or invalid user (must be member of group tei).

Trying to annotate the word "Hotel" in Graves' letter as place first, then as a term results in an error:

The TEI is correctly changed though, so it's merely a client side issue:

There are applications of TEI-Publisher that use annotations. The service and client-parts have sucessfully been implemented with affordable effort.

However providing a feature-complete solution for annotations is not a trivial task and standards and interoperability come into play.

Hypothesis is a well-known and mature annotation system that shares the same Open Source mindset as TEI-Publisher - being Open Source, Open Standard and sustainable.

Now we got web components it should be possible to wrap the client-parts of Hypothesis thereby offering annotations to any application that might want it. Even an collaboration with Hypothesis might be interesting.

For the server-side part an image or Ansible installation would be needed. All in all it would take some effort but might be a nice extension. A poll could reveal the amount of interest within the community.

Passing a wrong root or id parameter to components.xql generates a cardinality error. Catch and report.

https://teipublisher.com/exist/apps/tei-publisher/index.html?tab=0&collection=playground

I've found these untranslated labels within Czech UI.

• Settings
• Regenerate All ODDs (Slow)
• Filter

They can be reached from index.html?tab=0 page.

I didn't found these strings in Crowdin.

Settings CZ

Settings EN

Regenrate CZ

Regenrate EN

Filter CZ

Filter EN

The generation of facets using data/taxonomy.xml is a great
feature. However, it would be nice, if the file name and path would be
more configurable.

Right now, it's a bit inconsistently configured. greping for the
file in an app that was generated with the app generator gives the
following result:

$ grep taxonomy\\.xml * -Rn
index.xql:64:    let $category := id(substring($target, 2), doc($idx:app-root || "/data/taxonomy.xml"))
modules/config.xqm:294:    doc($config:data-root || "/taxonomy.xml")/tei:TEI
modules/lib/api/generate.xql:435:        deploy:copy-resource($collection || "/data", $base || "/data", "taxonomy.xml", ($json?owner, "tei"), "rw-r--r--"),

Since the separation of app code and data is best practise and since
the taxonomy (at least IMO) should be part of the data, configuring
the file with it's own variable declaration in modules/config.xpm
would be cool. E.g. setting a path/uri with

declare variable $config:taxonomy := $config:data-root || "/taxonomy.xml";

or even a fragment with

declare variable $config:taxonomy := doc($config:data-root || "/taxonomy.xml")//classDecl;

I can't tell, which data type would be better.

Then, this variable could be used throughout the app for
$config:data-exclude, in the idx:get-genre function (and maybe
when copying files during app deployment).

When editing ODD files you often might wonder what a specific behavior is all about and which params it takes. It would be good if you could access those information (found in the docs) directly in context of the editing process.

When viewing a document that consists of both transcription and facsimile image (i.e. in the Dodis edition), annotations that are rendered as pop-ups in the transcription fail to load after toggling full page view on and off in the OpenSeadragon viewer.
Tested with Firefox and Chrome on Windows.
(EDIT: same goes for data that is displayed in a collapsible drawer (cf. Dantiscus Correspondence)

I use admin as the username without password to log in to the eXist-db app.
After launching the TEI-publisher page, I tried to log in with the same username-password pair and failed.

The error message is:Wrong password or invalid user (must be member of group tei).

Though it is said that default user: 'Login to upload files ######or see administrative functions (default user: 'tei-demo', password: 'demo'), I feel it is more convenient and reasonable to allow to use admin without password to log in.

Hi !
I'm using TEI Publisher to display egodocuments and documentation about these documents' encoding method. I found out XSLFO can't convert (and export) my documents if there is an element <list> or <item> in them. I tried to force the transformation by replacing <list> and <item> in my TEI documents by <fo:list-block>, <fo:list-item>, <fo:list-item-label>, <fo:block> and <fo:list-item-body> and adding xmlns:fo="http://www.w3.org/1999/XSL/Format" in TEI root element, and it worked, but it is not pratical nor ideal for the application.
An approaching issue concerns <table>, <row> and <cell>, which can be exported in FO source but can't be converted in PDF.
What can be done to fix this issue and ensure an adequate conversion of the file without having to cheat on the encoding ?
Best regards,
I.

Where: https://github.com/eeditiones/tei-publisher-app/blob/master/modules/lib/search.xql#L111-L144

The core module search.xql is returning a paper-card element, which implies a dependency to the branded Polymer "paper" library that is not customizable.
This should be absolutely avoided while being a core function. At best, the main search function should not return any markup at all and let users give the freedom to use the search function in any kind of markup.

Compare with pb-popover component where this does not seem to be an issue.

Hi,

Noticed the following while testing the filtering in the demo collection of TEI Publisher. There are three filtering options, title, author and file. Filtering by the default filter-by value, title, works as expected. E.g. filter by title, "boga*" (first title in the collection, Bogactwa mowy polskiej):

Parameters in url: .../tei-publisher/index.html?tab=0&collection=test&filter=Boga*&filterBy=title
Parameters array in console: {start: 1, sort: "title", filter: "Boga*", browse: "title"}

However, if one switches filter to author, it still filters by title and consequently finds nothing. E.g. filter by author, "Kant" (second title in the collection, Critik der reinen Vernunft, author Kant Immanuel):

Parameters in url are correct: .../tei-publisher/index.html?tab=0&collection=test&filter=Kant&filterBy=author
Parameters in the parameter array in console are not: {start: 1, sort: "title", filter: "Kant", browse: "title"}

This is further demonstrated by the fact that if one filters by author and a string found in a title, it returns results.

I uploaded a file "Otto Rank" and its name appears in the list, but it is not clickable and so I can't see it in TeiPublisher.

Feature request from the community https://e-editiones.slack.com/archives/C012YTJP5HB/p1625117516193300

to reproduce

• filter by Title Documentation in Demo collection

expected result is to find documentation.xml

modules/autocomplete.xql does not respect the field parameter passed

see https://teipublisher.com/exist/apps/tei-publisher/modules/autocomplete.xql?query=k&field=author

To be able to better understand you problem, please add as much information as possible to this ticket. Always test your bugs against the latest stable release of exist. We cannot provide support for older versions here on GitHub. If the version of eXist that is experiencing the issue is more than 1 major version behind the most recent release, please consider posting a question on our mailing list.

Describe the bug
I tried to migrate a TEI Publisher-App to eXist 5.3.0. This App does a certain amount of styling via ODD. When I try to recompile the ODD, I get an error that all files (*print, *epub, *latex, *web) couldn't be saved.
When opening e.g. *-web.invalid.xql, I see that one function was added twice. Since eXist 5.3.0, duplication of functions raises an error.

(: generated template function for element spec: item :)
declare %private function model:template-item($config as map(*), $node as node()*, $params as map(*)) {
    <t xmlns=""><li onclick="goTo('{$config?apply-children($config, $node, $params?uri)}')">{$config?apply-children($config, $node, $params?content)}
        				                
        				            </li></t>/*
};

(: generated template function for element spec: item :)
declare %private function model:template-item($config as map(*), $node as node()*, $params as map(*)) {
    <t xmlns=""><li onclick="goTo('{$config?apply-children($config, $node, $params?uri)}')">{$config?apply-children($config, $node, $params?content)}
        				                
        				            </li></t>/*
};

Expected behavior
I expect that recreating the functions from ODD Files works as it did on eXist 5.2.0.

To Reproduce

The best way is to provide an SSCCE (Short, Self Contained, Correct (Compilable), Example). One type of SSCCE could be a small test which reproduces the issue and can be run without dependencies. The XQSuite - Annotation-based Test Framework for XQuery makes it very easy for you to create tests. These tests can be executed from the eXide editor (XQuery - Run as Test)

<elementSpec ident="item" mode="change">
        				    <model predicate="ancestor::div[@type='SVPListe']" behaviour="inline">
        				        <param name="uri" value="substring(@corresp,2)"/>
        				        <param name="name" value="concat('id_', @xml:id)"/>
        				        <param name="content" value="."/>
        				        <pb:template xmlns="" xml:space="preserve">
        				            <li onclick="goTo('[[uri]]')">[[content]]
        				                
        				            </li>
                                </pb:template>
        				    </model>
        				</elementSpec>

If the above isn't working, please tell us the exact steps you took when you encountered the problem:

1. using attached ODD
2. regenerate files from ODD
   example.txt

Screenshots
If applicable, add screenshots to help explain your problem.

Context (please always complete the following information):
Mac M1
macOS Big Sur 11.4
JDK 15.0.2
eXist 5.3.0
TEI Publisher Lib 2.8.8
Open API Router 0.2.0

Additional context

• How is eXist-db installed? [e.g. JAR installer, DMG, … ]: builded via Maven and started via ./startup.sh
• Any custom changes in e.g. conf.xml? none

While headings are displayed, no text is shown (compare to a search in TEI documents).

Current UI does not support selecting multiple facet values for single dimension, while it is supported server-side, e.g. query for documents in test collection in English or German language collection=test&facet-language=en&facet-language=de

• some apps may need multiple ODDs, so it should be possible to select more than one when generating
• linked CSS files should also be copied

steps to reproduce

1. re-upload documentation.xml to Playground collection

Upload is successful, document can be accessed directly eg. via http://localhost:8080/exist/apps/tei-publisher/playground/documentation.xml and full text searches find matches in it but it is not visible in browsing nor filtering.

Assuming something is wrong with defining file field or metadata-query on docbook

Hi,

Building on the Van Gogh letter (TEI Pub 6), I noticed that when I switch to page view, no translation is displayed. This does not work even in the original example a in TEI Pub 7 it throws an error.
https://teipublisher.com/exist/apps/tei-publisher/test/let695.xml?id=pb-orig-1r-1&view=on

the server did not return any content
The request to the server failed.: exerr:ERROR XPTY0004: The actual cardinality for parameter 2 does not match the cardinality declared in the function's signature: pages:get-content($config as map(*), $div as element()) item()*. Expected cardinality: exactly one, got 0. [at line 358, column 53, source: /db/apps/tei-publisher/modules/lib/api/document.xql] In function: pages:get-content(map(*), element()) [357:44:/db/apps/tei-publisher/modules/lib/pages.xql] dapi:get-fragment(map(*)) [176:30:/db/apps/tei-publisher/modules/lib/api/document.xql]. XPTY0004: The actual cardinality for parameter 2 does not match the cardinality declared in the function's signature: pages:get-content($config as map(*), $div as element()) item()*. Expected cardinality: exactly one, got 0. [at line 358 of /db/apps/tei-publisher/modules/lib/api/document.xql]

Best

Ondrej

Hi there,

I am following your instructions here https://github.com/eeditiones/tei-publisher-app/blob/master/webtest/README.md to try and build and run the integration tests.

I am on macOS Catalina, and node 12.18.3.

When I reach the npm install step, the build fails with the error:

❯ cd webtest
❯ npm install

> [email protected] install /Users/aretter/tmp-code/tei-publisher-app/webtest/node_modules/fibers
> node build.js || nodejs build.js

  CXX(target) Release/obj.target/fibers/src/fibers.o
../src/fibers.cc:68:2: error: no template named 'Handle'
        Handle<String> NewLatin1String(Isolate* isolate, const char* string) {
        ^
../src/fibers.cc:69:10: error: no viable conversion from returned value of type 'Local<v8::String>' to function return type 'int'
                return String::NewFromOneByte(isolate, (const uint8_t*)string, NewStringType::kNormal).ToLocalChecked();
                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/fibers.cc:72:2: error: no template named 'Handle'
        Handle<String> NewLatin1Symbol(Isolate* isolate, const char* string) {
        ^
../src/fibers.cc:73:10: error: no viable conversion from returned value of type 'Local<v8::String>' to function return type 'int'
                return String::NewFromOneByte(isolate, (const uint8_t*)string, NewStringType::kNormal).ToLocalChecked();
                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/fibers.cc:94:2: error: no template named 'Handle'
        Handle<Object> NewInstance(Isolate* isolate, Local<Function> fn, int argc, Local<Value> argv[]) {
        ^
../src/fibers.cc:95:10: error: no viable conversion from returned value of type 'Local<v8::Object>' to function return type 'int'
                return fn->NewInstance(isolate->GetCurrentContext(), argc, argv).ToLocalChecked();
                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/fibers.cc:104:2: error: no template named 'Handle'
        Handle<Number> ToNumber(Local<Value> value) {
        ^
../src/fibers.cc:105:10: error: no viable conversion from returned value of type 'Local<v8::Number>' to function return type 'int'
                return value->ToNumber(Isolate::GetCurrent()->GetCurrentContext()).ToLocalChecked();
                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/fibers.cc:126:58: error: no template named 'Handle'
        void Reset(Isolate* isolate, Persistent<T>& persistent, Handle<T> handle) {
                                                                ^
../src/fibers.cc:139:26: error: no template named 'Handle'
        void SetInternalPointer(Handle<T> handle, int index, void* val) {
                                ^
../src/fibers.cc:143:27: error: no template named 'Handle'
        void* GetInternalPointer(Handle<T> handle, int index) {
                                 ^
../src/fibers.cc:148:2: error: no template named 'Handle'
        Handle<T> Deref(Isolate* isolate, Persistent<T>& handle) {
        ^
../src/fibers.cc:153:14: error: no template named 'Handle'
        void Return(Handle<T> handle, const Arguments& args) {
                    ^
../src/fibers.cc:157:14: error: no template named 'Handle'
        void Return(Handle<T> handle, GetterCallbackInfo info) {
                    ^
../src/fibers.cc:165:2: error: no template named 'Handle'
        Handle<Value> ThrowException(Isolate* isolate, Handle<Value> exception) {
        ^
../src/fibers.cc:165:49: error: no template named 'Handle'
        Handle<Value> ThrowException(Isolate* isolate, Handle<Value> exception) {
                                                       ^
../src/fibers.cc:169:2: error: no template named 'Handle'
        Handle<Context> GetCurrentContext(Isolate* isolate) {
        ^
../src/fibers.cc:170:10: error: no viable conversion from returned value of type 'Local<v8::Context>' to function return type 'int'
                return isolate->GetCurrentContext();
                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/fibers.cc:173:2: error: no template named 'Handle'
        Handle<Primitive> Undefined(Isolate* isolate) {
        ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
make: *** [Release/obj.target/fibers/src/fibers.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/aretter/.nvm/versions/node/v12.18.3/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
gyp ERR! System Darwin 19.6.0
gyp ERR! command "/Users/aretter/.nvm/versions/node/v12.18.3/bin/node" "/Users/aretter/.nvm/versions/node/v12.18.3/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--release"
gyp ERR! cwd /Users/aretter/tmp-code/tei-publisher-app/webtest/node_modules/fibers
gyp ERR! node -v v12.18.3
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
node-gyp exited with code: 1
Please make sure you are using a supported platform and node version. If you
would like to compile fibers on this machine please make sure you have setup your
build environment--
Windows + OS X instructions here: https://github.com/nodejs/node-gyp
Ubuntu users please run: `sudo apt-get install g++ build-essential`
Alpine users please run: `sudo apk add python make g++`
sh: nodejs: command not found
npm WARN [email protected] requires a peer of webpack@^2.0.0 || ^3.0.0 || ^4.0.0 but none is installed. You must install peer dependencies yourself.

npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! [email protected] install: `node build.js || nodejs build.js`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/aretter/.npm/_logs/2020-09-03T16_16_21_780Z-debug.log

We use node-gyp in several other projects, so I fairly sure my build environment is correct. Please advise...

Explain new parameters in config.xqm and how to regenerate scripts after changing them.

When I try to download the PDF document (Latex Version) in a tei-publisher application. Find the below-given error.

{ "details" : null, "description" : "Cannot run program "/usr/local/texlive/2020/bin/x86_64-darwin/pdflatex" (in directory "/tmp"): error=2, No such file or directory. An IO error occurred while executing the process /usr/local/texlive/2020/bin/x86_64-darwin/pdflatex: Cannot run program "/usr/local/texlive/2020/bin/x86_64-darwin/pdflatex" (in directory "/tmp"): error=2, No such file or directory [at line 179 of unknown]" }

Dear All,
I can not open the file which has used spaces in the file name and receive the below-given error.

This results in this error:
Failed to load document /db/apps/tei-publisher/data/playground/Aristoteles Seele (incomplete).xml: 400 Bad Request

These fails:
Critique of Judgment [CASSIRER 019].xml
God-s-New-Covenant_Full-edition w Matthew notes in situ.xml
HWC Categories [CASSIRER 004] (facs test).xml

It is an application limitation or we can remove this issue

Hi, teipublisher isn't working right now?

Hi!

I am using TEI Publisher 6 to display Old Czech texts in parallel with their translation, facsimile and notes.
The structure of the XML is roughly this:

<TEI>
    <teiHeader></teiHeader>
    <facsimile></facsimile>
    <text>
        <front></front>
        <body>
            <div type="original">text <anchor n="s.1"/></div>
            <div type="translation">text <anchor n="t.1"/></div>
            <div type="notes"><note n="s.1">text</note> <note n="t.1">text</note></div>
        </body>
    </text>
</TEI>

I display the original, translation, facsimile and notes in parallel (based on the simplified odd and template for van gogh).
The template displays the notes as:

<template title="Notes">
    <pb-view src="document1" xpath="//div[@type='original']"
        subscribe="transcription">
        <pb-param name="view" value="notes"/>
    </pb-view>
</template>

The odd uses a mode for div to list all notes for current page (in page view mode) like this:

<elementSpec ident="div" mode="change">
    <model predicate="$parameters?view='notes'" behaviour="inline">
        <param name="content" value="for $anchor in .//anchor/@n return  root($parameters?root)//div[@type='notes']//note[@n=$anchor]"/>
        <param name="type" value="'custom'"/>
    </model>
</elementSpec>

Unfortunately, this way I can only list notes based on the anchors either in the original text or in the translation (if I change the xpath in the template), but not of both together. I was able to display all notes together, but not per page changing the odd xpath from .//anchor/@n to root($parameters?root)//anchor/@n. I can also have two parallel divs in the template for two lists of notes.

However, what I want is one list of notes displaying notes from both the original and the translation per each page (in page view mode).

Is that feasible? Any hints would be greatly appreciated!

Best

Ondrej

Problem:
When clicking a link from a search result, the action parameter is persisting, so that you're unable to browse to the subchapter afterwards.

Must-have:
When clicking on a link, the action parameter should be deleted, as the actual search has been completed from a user's point of view..

Steps to reproduce:

1. Perform a search for keyword "behaviours"
2. Click on the first search result -> last link in the breadcrumb

Also, problem with browser navigation, see comment below: #29 (comment)

When searching for the correct authority entry in the popup, it would help if those entries, which have already been referenced in the same or other TEI files, would appear on top, maybe with a usage count next to them.

To implement this, we would need to do a database lookup after querying the authority and merge the information from both sources for display.

Since the documentation is growing along with the new great features the Publisher has to offer, it seems more and more necessary to directly search for a keyword within the documentation (documentation.xml).
At the moment, the search scope for keywords is containing every entry within all TEI-Publisher documents, so a filter option would be great, when users only want to look up a keyword within the documentation.

Alternative:
Integrate the documentation in the FAQ application (https://faq.teipublisher.com/), so all documentation-related topics are in one place.