tei-publisher-app issueshttps://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues2020-03-13T11:45:56Zhttps://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/213[i18n] mechanism to overwrite TEI Publisher common labels2020-03-13T11:45:56ZMagdalena Turska[i18n] mechanism to overwrite TEI Publisher common labelsFor custom TEI Publisher-based apps ideal i18n customization and fallback scenario would involve TEI Publisher backend and local project backend:
* [x] TEI Publisher backend (all tei-publisher labels and their community-maintained trans...For custom TEI Publisher-based apps ideal i18n customization and fallback scenario would involve TEI Publisher backend and local project backend:
* [x] TEI Publisher backend (all tei-publisher labels and their community-maintained translations)
* [x] Local project backend (for customized labels)
* [x] `app` custom app namespace for project-specific labels
* [ ] `common` for overwriting tei-publisher labels
NB TEI Publisher v6.0.0 already implements double-backend scenario and custom project labels. Only overwriting tei-publisher labels is missing7.0.0https://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/212Bad request error when creating ODD from examples2020-03-09T07:46:55ZMaria NikuBad request error when creating ODD from examplesLatest version of eXist-db and TEI Publisher. Trying to create ODD from examples gives a bad request error (400), see message below. This occurs both with the examples that come with TEI Publisher and with TEI 5-files I have added myself...Latest version of eXist-db and TEI Publisher. Trying to create ODD from examples gives a bad request error (400), see message below. This occurs both with the examples that come with TEI Publisher and with TEI 5-files I have added myself. Number of examples selected has no effect.
`<?xml version="1.0" ?><exception><path>/db/apps/tei-publisher/modules/lib/components-odd.xql</path><message>exerr:ERROR Exception while transforming node: java.lang.IllegalArgumentException: URI is not absolute [at line 139, column 31]
In function:
obe:merge(node()*, xs:string, xs:string?, node()) [139:21:/db/apps/tei-publisher/modules/odd-by-example.xql]
obe:process-example(xs:string, xs:string, xs:string?, xs:string*, xs:string?) [76:6:/db/apps/tei-publisher/modules/odd-by-example.xql]
local:create-by-example(item()*, item()*, item()*) [116:34:/db/apps/tei-publisher/modules/lib/components-odd.xql]</message></exception>`https://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/92following with a positional predicate was: Processing model for notes2019-09-12T16:54:45ZMartin Muellerfollowing with a positional predicate was: Processing model for notesWe've run into a problem with the placement of notes. In the EEBO TCP texts note elements are recorded inline. They nearly always carry a `@place= "margin"` attribute. For a variety of reasons I moved the notes to a separate back element...We've run into a problem with the placement of notes. In the EEBO TCP texts note elements are recorded inline. They nearly always carry a `@place= "margin"` attribute. For a variety of reasons I moved the notes to a separate back element, leaving a ref element as a placeholder with a @target attribute that points the note.
Thus in the following toy example
```xml
<note xml:id="A20069-e123" place ="margin"><w>this</w>...</note>
```
we end up with
```xml
<ref xml:id="A20069-e123-a" corresp="A20069-e123-b"target = "#A20069-e123-b">
```
in the original location of the note, while the note appears somewhere in
```xml
<back>
<div type="notes">
<note xml:id="A20069-e123-b" corresp="A20069-e123-a" place="margin"><w>this</w>...</note>
</div>
```
When I did this I assumed that it would be a trivial matter to adjust the Processing Model. Am I right in this or is it harder ( as one of my colleagues argues)? In the inline notation, `<note place="margin">` triggers a processing instruction to do something with the `<note>` , i.e. display it in the margin.
If the note is at the end, one needs a processing instruction for `<ref>`, which would say "go to the place marked by the `@target` attribute, pick up the note and then process it, display it in the margin in the location of the `ref` attribute." So there is just one additional step.
Am I right on this, or is this not as straightforward as I think?https://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/161PDF output of Serafin letter broken2019-09-12T10:32:25ZWolfgangPDF output of Serafin letter brokenNeed to choose a better font for the PDFNeed to choose a better font for the PDFVersion 4.0https://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/159publisher should be a single-page app2019-03-19T15:42:34ZJoern Turnerpublisher should be a single-page appcurrently we have several pages sharing at least the same header so we have duplicated markup.
Furthermore to have a global configuration for the UI we would need to duplicate that also with the danger of things going out-of-sync.
Furt...currently we have several pages sharing at least the same header so we have duplicated markup.
Furthermore to have a global configuration for the UI we would need to duplicate that also with the danger of things going out-of-sync.
Further advantages of single-page app would be better control of lazy loading as well as a smoother experience with page transitions.https://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/137Cannot execute Webtest on a Mac2018-10-04T11:05:52ZGhost UserCannot execute Webtest on a MacI followed the instructions in `webtest/README.md`, but when I execute `./node_modules/.bin/wdio wdio.conf.js`, I get the following error repeated many times:
```
ERROR: unknown error: no chrome binary at /usr/bin/google-chrome
(Drive...I followed the instructions in `webtest/README.md`, but when I execute `./node_modules/.bin/wdio wdio.conf.js`, I get the following error repeated many times:
```
ERROR: unknown error: no chrome binary at /usr/bin/google-chrome
(Driver info: chromedriver=2.40.565386 (45a059dc425e08165f9a10324bd1380cc13ca363),platform=Mac OS X 10.13.3 x86_64)
chrome
at new RuntimeError (/Users/aretter/code/tei-publisher-app/webtest/node_modules/webdriverio/build/lib/utils/ErrorHandler.js:143:12)
at Request._callback (/Users/aretter/code/tei-publisher-app/webtest/node_modules/webdriverio/build/lib/utils/RequestHandler.js:316:39)
at Request.self.callback (/Users/aretter/code/tei-publisher-app/webtest/node_modules/request/request.js:185:22)
at Request.emit (events.js:127:13)
at Request.emit (domain.js:421:20)
at Request.<anonymous> (/Users/aretter/code/tei-publisher-app/webtest/node_modules/request/request.js:1157:10)
at Request.emit (events.js:127:13)
at Request.emit (domain.js:421:20)
at IncomingMessage.<anonymous> (/Users/aretter/code/tei-publisher-app/webtest/node_modules/request/request.js:1079:12)
at Object.onceWrapper (events.js:219:13)
```
As I am on Mac OS, I would not expect there to be a `/usr/bin/google-chrome`.
What am I doing wrong?https://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/140options to evolve app generation2018-09-21T09:04:03ZJoern Turneroptions to evolve app generation# App generation in Web Components age
## what is 'App generation'
'App generation' (AG) is available as 'App Generator' from the admin menu of TEI-Publisher.
## what is discussed in this paper?
This discussion is about how to evolve...# App generation in Web Components age
## what is 'App generation'
'App generation' (AG) is available as 'App Generator' from the admin menu of TEI-Publisher.
## what is discussed in this paper?
This discussion is about how to evolve the AG. There are certainly different aspects mixing up in the current layout that need further work.
## what is the purpose of the AG?
Seems to be an obvious question but also raises some questions in the way it currently exists.
Naively the purpose is to create a website for publishing text in some form or another. It can be seen as a website generator.
But when you generate a site you actually get more than the website. For logged-in users there is the possibility to edit and manage odd-files that are the basis for the various text representations the site uses (Html, PDF, ePub). It can be argued that this is actually a separate app (the one that initially creates a site plus the odd editing (in a broad sense).
## what needs improvement?
The abovementioned two-fold nature of an generated app also has implications on the layout. A website does not follow the same principles as an app regarding layout or structuring of the navigation.
I the Material Design world e.g. there no top-navigation as found in websites (and generated by AG currently). Of course the app can integrate into some website view (as is the case now) but this creates issues with responsiveness and the menu might break if there are more links. In contrast a standalone app in Material Design uses usually a left drawer navigation to switch between views.
So, here a little mismatch exists that should be resolved.
## separate generated site from publisher app?
I consiously used a question mark here. Given the above points it might make sense to completely separate out the functionality of the publisher app.
Everything that deals with:
* creating an odd
* editing an odd
* switching the odd for a document
* uploading an odd
* regenerting an odd
* update index
* recompile odd
* generate application
would go into a standalone app that uses a Material Design (Polymer app-layout) layout and give us a working frame for a responsive and even mobile-ready application.
Furthermore i can imagine that the separation into a *generating* and *generated* part is easier to understand when using the publisher. A person with access to the Publisher App would deal with the app in one window (tab) and (re)generate the publication at will. If a user publishes more than one publication with Publisher there would still be just one copy of the app needed. Some further workflow support might be easier to integrate 'when looking at an publication from the outside'.
The separation of concerns would lead to smaller apps and should also be easier to maintain.
For me currently it's not totally obvious which technical implications this creates. So this is certainly an aspect to be considered when making such a change.
## conclusion
First of all we should clarify if the above is valid and a separation makes sense. I'd suggest to vote up or do an '+1' comment to signal your view of things.
I brought this to the table as this has been discussed before several times here in Berlin in some personal talks and it at least seemed to be a valid topic which we should handle now as we're in the process of introducting web components into publisher.https://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/167Add label next to document title showing the XML schema used2018-09-17T12:39:28ZWolfgangAdd label next to document title showing the XML schema usede.g. TEI, docbook, jatse.g. TEI, docbook, jatshttps://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/105[question] how to define and update vendor scripts2017-12-28T10:10:03ZDuncan Paterson[question] how to define and update vendor scriptsNot all vendor scripts are defined in the package.json. Where do they come from? I was just trying to update Jquery to 1.12 to avoid a console error with highligh,js:
![Screenshot_2017-12-21_11.18.27](/uploads/5cc4df2fb31dd79af6ddf273a32...Not all vendor scripts are defined in the package.json. Where do they come from? I was just trying to update Jquery to 1.12 to avoid a console error with highligh,js:
![Screenshot_2017-12-21_11.18.27](/uploads/5cc4df2fb31dd79af6ddf273a32cb57b/Screenshot_2017-12-21_11.18.27.png)
but gulp keeps building with 1.11 :( Shouldn't all js vendor scripts be part of package.json, so that gulp can use it when building the app?
P.S.: the error is more annoying then breaking functionality as far as i can tellhttps://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/90search results: error after click on kwic search term if variable $config:sea...2017-12-22T18:37:39ZEmmanuellesearch results: error after click on kwic search term if variable $config:search-default is set to "tei:body"- a click on the search term in the kwic view of the search results works fine when $config:search-default is set to "tei:div"
- when $config:search-default is set to "tei:body", something is going wrong:
exerr:ERROR XPTY0004: The actua...- a click on the search term in the kwic view of the search results works fine when $config:search-default is set to "tei:div"
- when $config:search-default is set to "tei:body", something is going wrong:
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 231, column 46, source: /db/apps/test1/modules/lib/pages.xql]
In function:
pages:get-content(map, element()) [231:46:/db/apps/test1/modules/lib/pages.xql]
(...)https://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/101Error with view "plain" when creating an app without tei_simplePrint.odd2017-10-10T12:47:27ZEmmanuelleError with view "plain" when creating an app without tei_simplePrint.oddI tested creating an app that uses other ODDs than the default ones (teipublisher.odd and tei_simplePrint.odd). It works fine unless for the "plain" view (via click on "single Page" in the tools menu).
This situation produces an error ...I tested creating an app that uses other ODDs than the default ones (teipublisher.odd and tei_simplePrint.odd). It works fine unless for the "plain" view (via click on "single Page" in the tools menu).
This situation produces an error message:
```
err:XPTY0004 text()(
) is not a sub-type of element() [at line 52, column 55, source: /db/apps/matrix2/modules/lib/transform.xql]
In function:
local:postprocess(node()*, element()?, xs:string) [52:13:/db/apps/matrix2/modules/lib/transform.xql]
```
The fix is to have an elementSpec for the TEI element in one of the app's ODDs:
```
<elementSpec ident="TEI" mode="change">
<model behaviour="document"/>
</elementSpec>
```https://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/99console error because of missing css.map files (main app)2017-09-12T14:31:13ZDuncan Patersonconsole error because of missing css.map files (main app)![Screenshot_2017-09-12_16.25.28](/uploads/0e43165f58c44bb458af93f49806cc8f/Screenshot_2017-09-12_16.25.28.png)
While these errors are easy to fix, I m not sure if we are using gulp to its full potential here. AFAIK exist-db has no less...![Screenshot_2017-09-12_16.25.28](/uploads/0e43165f58c44bb458af93f49806cc8f/Screenshot_2017-09-12_16.25.28.png)
While these errors are easy to fix, I m not sure if we are using gulp to its full potential here. AFAIK exist-db has no less processor, so why does the deployed app include these files? Where do we expect users to modify css, and what about the assortment of css that comes from other resources, either straight from odd, or from ``/transform``?
See #48https://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/84Create deep links2017-09-07T09:08:25ZGhost UserCreate deep linksTo be ported from HSG-Guides:
* https://gitlab.com/HistoryAtState/guides/merge_requests/20/commits
* https://gitlab.com/HistoryAtState/guides/merge_requests/22/commits
* Related issue https://gitlab.com/HistoryAtState/guides/issues/50 ...To be ported from HSG-Guides:
* https://gitlab.com/HistoryAtState/guides/merge_requests/20/commits
* https://gitlab.com/HistoryAtState/guides/merge_requests/22/commits
* Related issue https://gitlab.com/HistoryAtState/guides/issues/50 including mentioned commitshttps://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/46Provide easy LTR / RTL switch for user2017-09-06T15:43:58ZGhost UserProvide easy LTR / RTL switch for userWhile refactoring the css for the inner content (#35), I noticed the entanglement of the current language direction with the indentation plus some side-boxes (notes).
With my fixes for #35, the user is already to easily customize the te...While refactoring the css for the inner content (#35), I noticed the entanglement of the current language direction with the indentation plus some side-boxes (notes).
With my fixes for #35, the user is already to easily customize the text direction and the margin. But it's not possible to easily customize notes in the sidebar.
In order to provide the requested feature "User can switch text direction for the inner content in one central file/interface", a mixin has to be added, so margins will adapt automatically according to the direction.https://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/49Create bigger favicon2017-09-06T15:43:58ZGhost UserCreate bigger faviconThe Publisher favicon is too small. I would like to remove the whitespace around the icon and render it again.The Publisher favicon is too small. I would like to remove the whitespace around the icon and render it again.https://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/56Create script for updating an existing app2017-09-06T15:43:47ZWolfgangCreate script for updating an existing appWhen you generated an app via tei-publisher, you may want to update its general code libraries and styles whenever tei-publisher has a new release. Suggested approach:
1. Create an update page which lists all apps available in the eXi...When you generated an app via tei-publisher, you may want to update its general code libraries and styles whenever tei-publisher has a new release. Suggested approach:
1. Create an update page which lists all apps available in the eXistdb instance, e.g. in a select. To get all installed apps, call repo:list(), then find out where they are installed in the db and check if they were created from tei-publisher.
2. When the user requests an update, copy everything in
* templates/basic/modules/lib
* templates/basic/resources/css, except _content.less
To make clear which files a user can change, we should maybe set them to read-only in the post-install.xql of the generated app.
Related #66, #62https://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/89Strategy for merging adjacent TEI elements (eg supplied)2017-06-21T16:47:28ZEmmanuelleStrategy for merging adjacent TEI elements (eg supplied)How to deal with adjacent <supplied> tags or <unclear> so that the before and after typographic convention is merge ?
for example, if <supplied> is defined in a <model> to be surrounded by ‘{‘ and ‘}’, two adjacent supplied:
<supplied ...How to deal with adjacent <supplied> tags or <unclear> so that the before and after typographic convention is merge ?
for example, if <supplied> is defined in a <model> to be surrounded by ‘{‘ and ‘}’, two adjacent supplied:
<supplied reason="lost">suppliedText1</supplied><supplied reason="lost">suppliedText2</supplied>
would produce:
{suppliedText1}{suppliedText2}
what to do to have them merge:
{suppliedText1suppliedText2} or {suppliedText1 suppliedText2}
testing for a preceding and/or following supplied seems cumbersome and sometimes there would be <lb/> or other milestones element that shouldn’t stop the merge…
Is it then possible to pass a transformation in a second step, once all the tags have been transformed ?
thanks for your advicehttps://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/76search box support2017-05-16T13:07:54ZEduard Drenthsearch box supportPerhaps a title for the searchbox giving basic query support and/or a link to a referencePerhaps a title for the searchbox giving basic query support and/or a link to a referencehttps://gitlab.existsolutions.com/tei-publisher/tei-publisher-app/-/issues/82Fix missing offset when opening in-page links2017-05-16T12:39:12ZGhost UserFix missing offset when opening in-page linksTo be ported from HSG Guides:
* All commits in https://gitlab.com/HistoryAtState/guides/merge_requests/17/commits
Resulted from related issue in Guides:
"Content is covered up by menu bar"
https://gitlab.com/HistoryAtState/guides/...To be ported from HSG Guides:
* All commits in https://gitlab.com/HistoryAtState/guides/merge_requests/17/commits
Resulted from related issue in Guides:
"Content is covered up by menu bar"
https://gitlab.com/HistoryAtState/guides/issues/46