Closed jonathanrobie closed 3 years ago
This is for Scripture textTranslations.
@jonathanrobie can you describe the use case behind this so we can better determine if the spec supports this already or should support it?
I have two use cases in mind.
I think a source variant should be able to contain USX without USFM to support these cases.
On Thu, Nov 5, 2020 at 12:07 PM Jesse Griffin notifications@github.com wrote:
@jonathanrobie https://github.com/jonathanrobie can you describe the use case behind this so we can better determine if the spec supports this already or should support it?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bible-technology/scripture-burrito/issues/167#issuecomment-722510461, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANPTPM5BKGFJONCNFQAGV3SOLLU3ANCNFSM4LPH3WHA .
Long term this might be a good addition, but for now it doesn't help with interoperability as many tools can only import USFM. e.g. Autographa, translationCore, etc.
This is not part of the Minimum Required to Declare Victory, and interop is our main goal, so I suggest we close this for this version, and revisit in the future.
@mvahowe wrote:
Or at least allow USX in default variants. In many applications, it would be easier for me to generate XML than to generate USFM and the data is not created using the editing window in a scripture editing application.