RobH123
commented
3 years ago Also, I've seen \m \v... in files (two spaces between them). If tC is outputting this, could the \m go onto the previous line.
Open birchamp opened 4 years ago
RobH123
commented
3 years ago Also, I've seen \m \v... in files (two spaces between them). If tC is outputting this, could the \m go onto the previous line.
Summary
The following is cut out of my translationCore folder in my Ubuntu home folder for a UST book that I'm aligning: \id ECC EN_UST en_English_ltr unfoldingWord® Simplified Text Mon May 18 2020 08:41:35 GMT+1200 (NZST) tc \usfm 3.0 \ide UTF-8 \h Ecclesiastes \toc1 The Book of Ecclesiastes \toc2 Ecclesiastes \toc3 Ecc \mt1 Ecclesiastes \s5 \c 1
\p \v 1 \zaln-s | x-strong="H1697" x-lemma="דָּבָר" x-morph="He,Ncmpc" x-occurrence="1" x-occurrences="1" x-content="דִּבְרֵי֙"*\w These|x-occurrence="1" x-occurrences="1"\w \w are|x-occurrence="1" x-occurrences="1"\w `
Is it possible for tC to upgrade \s5 fields (not valid USFM) to \ts*? (Would save a manual step.)
You can't see it above, but the \p has a trailing space (unlike the file exported without alignments). It's no big deal -- just unnecessary and untidy. Would it be easy to remove the trailing space?
The vertical bar | in the \w (last) line above has no space after it. This seems most like the examples in http://ubsicap.github.io/usfm/master/attributes/index.html. How easy would it be to remove the space after the vertical bar in the \zaln-s fields? (That would be tidier (i.e., closer to the spec) and would also reduce the ECC file size by 1.5K.)
Motivation
Why are we doing this? What use cases does it support? What is the expected outcome?
Specifications (If applicable)
A clear and concise description of the details about the feature that may or may not be obvious
Additional context
Add any other context or screenshots about the feature request here.