> 5. I managed to use <milestone type="x-p" marker="¶"/> instead of ¶, but it
> seems that Xiphos does not render them (either for KJV) to indicate there is
> a new paragraph here. Or am I missing something, is this not for a new
> paragraph?
Xiphos displays these OK in the KJV module (& others) in my Windows PC. Always
has done.
It signifies a paragraph, but the printed KJV is a Verse Per Line work, so it's
best viewed in Xiphos with Verse Per Line selected.
It does'nt force a line break at all.
Best regards,
David
Sent with [Proton Mail](https://pr.tn/ref/SWXT9A5YZ67G) secure email.
On Sunday, March 23rd, 2025 at 8:22 PM, Kovács Zoltán <kov...@gmail.com> wrote:
> DM Smith <dmsm...@crosswire.org> ezt írta (időpont: 2025. márc. 21., P,
> 13:56):
>
>> Yes, StatResGNT is unique among our Koine Greek modules for having quotes.
>> Koine NT manuscripts do not have quotes.
>
>> But the module has the wrong quotes for Modern Greek. They should be «double
>> chevron» for level 1 and “Double quotes” level 2.
>
> Thanks for the hints, this can be fixed soon.
> Now I improved the text by following many hints given by you during the last
> few days.
> Also, I managed to compile the latest version of Xiphos on Ubuntu and it
> works nicely.
> Here are some questions I faced meanwhile:
> 1. Xiphos (and Bibletime) does not allow me to show the Greek text in a Koine
> Greek font. Is this planned as a feature in the future, or is this present in
> other Bible software?
> 2. Now I can handle <divineName> correctly and I get capitalized Greek
> letters accordingly, that's great.
> 3. Also, I managed to export the morph entries from Alan Bunning's .tsv file,
> but I do not have an idea which format it uses. For example, Matthew 1:1
> contains the morphs ....NFS, ....GFS, ....GMS and so on. Is this a well-known
> standard which is supported by SWORD, or should this be translated to
> Robinson, for example? (I did not find any docs about the Packard morphology
> standard.) In fact, the morph entries are preceded by a role entry, e.g. N,
> V, C or E, so I guess, lowercasing these codes and removing the dots, then
> connecting them with a dash may be a workaround, e.g. n-nfs, n-gfs, n-gms
> look very close to such entries from Byz (n-nsf, n-gsf, n-gsm), but the last
> two characters are swapped.
> 4. Alan's .tsv also contains a lemma for each word, and Koine Greek variant.
> Is there something similar to the Koine Greek variant in other Greek modules,
> or is there an automatic way to convert a modern Greek word into Koine Greek?
> (Sorry, I have no deeper background in this field.)
> 5. I managed to use <milestone type="x-p" marker="¶"/> instead of ¶, but it
> seems that Xiphos does not render them (either for KJV) to indicate there is
> a new paragraph here. Or am I missing something, is this not for a new
> paragraph?
> 6. The osis2mod always creates a 300 kB long file ot.bzv (and two zero-length
> files: ot.bzs and ot.bzz), which is unclear why it is there. It is empty (it
> contains only the 0x00 char in its entire content). The StatResGNT module has
> nothing to do with the Old Testament. If I omit this file from the
> .sword/modules/texts/ztext/statresgnt folder, everything works properly. But
> I would like to be sure that this file will not be created at all, if
> possible.
>
> Thank you for your further suggestions in advance.
> Kind regards, Zoltan
>
> DM Smith <dmsm...@crosswire.org> ezt írta (időpont: 2025. márc. 21., P,
> 13:56):
>
>> Yes, StatResGNT is unique among our Koine Greek modules for having quotes.
>> Koine NT manuscripts do not have quotes.
>>
>> But the module has the wrong quotes for Modern Greek. They should be «double
>> chevron» for level 1 and “Double quotes” level 2.
>>
>> That said, if the upstream had different quote marks for level 2, you’d have
>> never noticed visually when accents were stripped.
>>
>> In Him,
>> DM
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
