scription2dlx 0.12.3

scription2dlx

A JavaScript library that converts linguistic texts in scription format to the Data Format for Digital Linguistics (DaFoDiL). This library is useful for language researchers who want to work with their data in text formats that are simple to type and read (scription), but want to convert their data for use in other Digital Linguistics tools.

npm i @digitallinguistics/scription2dlx
yarn add @digitallinguistics/scription2dlx

Or download the latest release from the releases page.

Node:

import convert from '@digitallinguistics/scription2dlx';

HTML:

<script src=scription2dlx.js type=module></script>

The library exports a single function which accepts a string and returns a DaFoDiL Text Object.

data.txt

---
title: How the world began
---
waxdungu qasi
one day a man

script.js

const data = await fetch(`data.txt`);
const text = scription2dlx(data);

console.log(text.utterances.transcription); // "waxdungu qasi"

You may also pass an options hash as the second option. See the Options section below.

const text = scription2dlx(data, { /* options */ });

If your project does not support ES modules and/or the latest JavaScript syntax, you may need to transpile this library using tools like Babel, and possibly bundle the library using a JavaScript bundler.
The scription2dlx library does not perform validation on the text data. You should use another validator like AJV to validate your data against the DLx DaFoDiL format.
In order to keep this library small and dependency-free, scription2dlx does not automatically parse the YAML header of a scription document. Instead, the header string is returned as a header property on the text object. If you would like scription2dlx to parse the header, pass a YAML parser to the parser option when calling the scription2dlx function:
```
import yaml from 'yaml'; // use your preferred YAML parsing library

const text = scription2dlx(data, { parser: yaml.parse });
```

Option	Default	Description
`alignmentError`	`"warn"`	This option specifies whether the library should throw an error when it encounters an utterance which has a different number of words on each line, or a different number of morphemes in each word. The Leipzig glossing rules state that each line in an interlinear example must have the same number of words and morphemes on each line. By default, this option is set to `"warn"`, which displays a warning if an alignment problem is encountered. To turn off warnings entirely, set this option to `false`; to throw an error, set this option to `true`.
`codes`	`{}`	This option allows you to use custom backslash codes in your interlinear glosses. It should be a hash containing the scription code as a key (without a leading backslash), and the custom code as the value; ex: `"txn": "t"` will allow you to write `\t` instead of `\txn` for transcription lines.
`orthography`	`"default"`	An abbreviation for the default orthography to use for transcriptions when one is not specified.
`parser`	`undefined`	A YAML parser to use in parsing the header of a scription document. If none is present, the header will be provided as a string in the `header` property of the returned object.
`utteranceMetadata`	`true`	Whether to parse the utterance metadata line (the first line when it begins with `#`). If set to `true`, a `metadata` property will be added to each utterance that has it.