-
```
What steps will reproduce the problem?
JSON.decode(the blow string) will produce the error:
JSONParseError: Unexpected s encountered
at
com.adobe.serialization.json::JSONTokenizer/parseError()…
-
```
Andreas:
Wherever there exists a Strong's number only this is displayed and the
Morphology tags only for those words where there is no Strong's number.
Observed for both KJV and LXX modules.
Da…
-
```
I have compared out with BibleTime (Linux platform) and there are some issues
in rendering when using translations created from IMP files using GBF notation.
Some of issues can be tested using …
-
```
I have compared out with BibleTime (Linux platform) and there are some issues
in rendering when using translations created from IMP files using GBF notation.
Some of issues can be tested using …
-
```
Andreas:
Wherever there exists a Strong's number only this is displayed and the
Morphology tags only for those words where there is no Strong's number.
Observed for both KJV and LXX modules.
Da…
-
```
Andreas:
Wherever there exists a Strong's number only this is displayed and the
Morphology tags only for those words where there is no Strong's number.
Observed for both KJV and LXX modules.
Da…
-
```
Andreas:
Wherever there exists a Strong's number only this is displayed and the
Morphology tags only for those words where there is no Strong's number.
Observed for both KJV and LXX modules.
Da…
-
```
I have compared out with BibleTime (Linux platform) and there are some issues
in rendering when using translations created from IMP files using GBF notation.
Some of issues can be tested using …
-
```
What steps will reproduce the problem?
1. Download the KJV with Strong's and Morphology codes
2. Open the KJV bible
3. View the text
What is the expected output? What do you see instead?
I expect…
-
```
What steps will reproduce the problem?
1. Download the KJV with Strong's and Morphology codes
2. Open the KJV bible
3. View the text
What is the expected output? What do you see instead?
I expect…