Consult the tutorials after changes
When we change the API, we make sure that the tutorials show off all possibilities.
See the app-specific tutorials via
Nodes.walk() also accepts a parameter
so that you can not only walk through the total nodes set, but also
through arbitrary nodesets. Always in canonical order.
There is a new function
fix of a bug in the TF-browser caused by the previous change: the headings of section-3 levels came out wrong
the second parameter of
prettyTuple()is now optional. It passes the sequence number of the tuple to display. This is useful if the tuple is a member of a bigger list, but not if the tuple stands on its own.
Changes in the output of Text-Fabric to the console. It is detected whether it runs in interactive mode (e.g. Jupyter notebook) or not. If not, the display methods of the Jupyter notebook are suppressed, and many outputs are done in plain text instead of HTML.
Fixes in volume support.
Small fixes in version mappings.
Changes in the messages that TF emits.
Several functions have an optional
by which you could control the verbosity of TF.
That parameter now accepts different values, although the old values still work with nearly the same effect.
The default value for silent results in slightly terser behaviour than the previous default setting.
use() function has an extra optional parameter
by which you can prevent data loading.
That is useful if you want to inspect properties of a dataset without
the costly loading of much data.
There is a new function to get existing volumes in a dataset:
It is also available as methods on the
so you can also say
Improvements in the function
- its third argument (
volumes) is replaced from a positional argument into a keyword argument with default value
- Fixed a bug in reporting results
Improvement in the function
- Fixed a crash that occurred while executing this function under certain conditions
Addition of a module
tf.convert.variants that can be used in a
It can be used to process TEI app-lem-rdg elements (critical apparatus).
What it does for you is to create sentence-like nodes from sentence-boundary information.
It deals with the cases where variants have different sentence boundaries.
Some minor fixes in defaults and documentation.
Addition to the
cv.link() to manually link a node
to existing slots instead of relying on the automatic linking.
Bug fix in the Text-Fabric browser. Spotted by Jorik Groen.
The Text-Fabric browser was not able to download data correctly, because it communicated the name of the backend incorrectly to the TF-kernel.
It is now also possible to have datasets and modules of datasets coming from different backends.
- ditched the word
~/text-fabric-datacache dir now first has a layer of subdirectories according to the backend that the data comes from:
gitlaband whatever server is serving a GitLab instance.
- subfolder download for GitLab is supported if the gitlab backend supports it. If not, we fall back on downloading the whole repo and then discarding what we do not need. Gitlabs with versions at least 14.4.0 support downloading of subfolders.
Small fix. GitLab.com supports downloading of subfolders, and I am prepared to make use of that but the current python-gitlab module does not support that part of the API. So I work around it.
Backend support: see
A backend is an online repository where TF apps/data can be stored.
Up till now, Text-Fabric worked with a single backend: GitHub. It uses the API of GitHub to find releases and commits and to download required data on demand.
With this version, Text-Fabric can also talk to GitLab instances.
The most prominent calls on the backend are the
and the start of the Text-Fabric browser.
They will work with a GitLab backend if you pass the instance address
with the optional parameter
A = use("annotation/banks", backend="gitlab.huc.knaw.nl")
A = use("annotation/banks", backend="gitlab.com")
In the Text-Fabric browser that looks as follows:
text-fabric annotation/banks --backend=gitlab.huc.knaw.nl
text-fabric annotation/banks --backend=gitlab.com
backend is omitted or is
None, the backend defaults to
GitLab does not support Jupyter Notebooks. And even if you converted them to HTML, GitLab does not offer a rendered view on HTML pages, unless you use GitLab Pages.
But that is not always enabled.
Currently, Text-Fabric does not support publishing to GitLab pages, although everything up to building a Pages site is supported.
When on a closed on-premise installation of GitLab, there is no way to see rendered notebooks on NBViewer, simply because NBViewer has no access to the shielded notebooks.
Expand source code Browse git
""" .. include:: ../docs/about/releases.md """