-
After Joshy's merge #81 today, I did another pass on the USFM files using my various TextPipe filters.
Here are my analysis results.
**Character frequency** of concatenated USFM files: [merged.…
-
For the implementation and testing of
the python parser,
as well as the support for different USFM features by the underlying grammar,
we need to build a large test suite covering at least all t…
-
In today's meeting, we decided to close #47 as an editorial issue, saying that it describes the status quo. Currently, DBL uses USX, Paratext and most other editing tools use USFM.
There are some…
-
-
Instead of the USX, tS should be using the USFM source files from the catalog.
See https://github.com/unfoldingWord-dev/ts-requirements/issues/12 for more details
-
Instead of exporting in dokuwiki format, tS-android should be able to export in USFM format.
See https://github.com/unfoldingWord-dev/ts-requirements/issues/159 for more details
@klappy @neutrinog
-
Instead of the USX, tS should be using the USFM source files from the catalog.
See https://github.com/unfoldingWord-dev/ts-requirements/issues/12 for more details
-
For usfm:
```
\v 1 Au commencement Dieu\f + \fq Dieu\ft , hébr. \qt Elohim\ft . C’est le nom commun de la divinité, susceptible d’être employé à propos des faux dieux, comme à propos du vrai Dieu. C…
-
Especially for the 2.1 release coming up it would be good if we could attach downloadable assets for JSON and USFM representations of the OSIS files.
-
Those **Psalms** (e.g. Ps. 4) that have a **canonical description** should be supplied with these using tag **\d**
See https://en.wikipedia.org/wiki/Psalms#Superscriptions_and_attributions
Are t…