Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

<tag> for Strongs Numbers and or the newer Goodrick/Kohlenberger Numbers, morph etc. #49

Open
Berovowilare opened this issue Dec 30, 2020 · 1 comment

Comments

@Berovowilare
Copy link

Hello

I see in the USX 3.xx very good improvements for print Bibles. But I would suggest to give also more attention to electronic Bibles.

For example there are no tags for the Strong numbering system or the newer Goodrick/Kohlenbeger Enhanced system. For print Bibles you can then skip it, but for electronic Bibles this are very good informations. It would be good if this numbers can by creating a new Bible in Paratext or Bibledit or the one from the Wyclif add by direct by the translation. At the moment they can not link such numbers or morphology information.

In Paratext they have as translation help the ESV etc. with Strongs numbers that helps to translate. But they are not able to add the numbers in the new translation. Right in the time of translation. This would be the most easiest way. As they study over this words.

At the moment this information has later to add in another software. This makes for me no sense.

This image is from Paratext
Bildschirmfoto 2017-12-03 um 22 10 57

Here an image of an older transation tool. Not available anymore. Here are by the translaton the word direct linked to the Strong's numbers. As you export them they are included in the electronic texts.
Bildschirmfoto 2017-12-08 um 15 52 18

But for this the USFM USX or whatever need the tags.

Thanks for your attention.

@jonbitgood
Copy link
Contributor

Hey there are tags that handle this in usx3, check out the special features section under the char style type in the documentation. Are you asking about paratext support for strongs translation or about the schema itself?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants