-
USFM denotes **Unified Standard Format Markers**.
This markup format is simpler than XML to write.
For details see http://paratext.org/usfm
There are existing scripts available to convert USF…
-
I want the chance to create a custom transaction.
For example:
sendTokens( from, to, network, token, amount);
Is it possible to include that in the library?
@osis
-
The file 'STVA.xml' is only a portion of an OSIS XML file.
It cannot be validated as such against the OSIS schema unless it is suitably enhanced to become a standalone source.
Were this to be im…
-
```
A general book or devotional module with an ("Not "scriptref") internal link
using the OSIS markup as described on the Crosswire wiki OSIS page.
markup pattern: module:div1.div2.div3 or the mo…
-
When a Table of Contents line in the source USFM file includes character markup (e.g., italics), the resulting XML in the OSIS output file is not well formed and results in a parsing error.
- **Sou…
-
@ThomHehl
- The top level file `moffatt.xml` fails to validate to the OSIS 2.1.1 schema!
- This seems to be a template rather than a complete file. There's no usable content.
- The individual fi…
-
@osis , do we have a way to show the Metamask notification popup by code?
I'm having issues with wallet.confirmTransaction() because sometimes is not shown or remains hidden under extension icon. If …
-
figure out where those sample pipelines come from, or invent/choose a place for them to live and tell osis. put their existence in code (like the reconfigure pipeline)
-
Empowering through arguments.
I wan't to add some features:
1) prop: "chromium" // chrome with extra features
2) prop: chromiumContext // for extra chromium settings from 'launchPersistentContext…
-
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.