But that said, I would expect that a module maker wishing to offer this facility to the users would take the text and mark it up appropriately by โwโ tagging each word.
Sent from Outlook for iOS
From: sword-devel <sword-devel-boun...@crosswire.org> on behalf of Peter von Kaehne <ref...@gmx.net>
Sent: Thursday, May 1, 2025 1:08 pm
To: SWORD Developers' Collaboration Forum <sword-devel@crosswire.org>
Cc: David Haslam <df.has...@btinternet.com>
Subject: Re: [sword-devel] Proposal for a new SWORD filter to display word dividers
Sent: Thursday, May 1, 2025 1:08 pm
To: SWORD Developers' Collaboration Forum <sword-devel@crosswire.org>
Cc: David Haslam <df.has...@btinternet.com>
Subject: Re: [sword-devel] Proposal for a new SWORD filter to display word dividers
I would not expect any Bible translator to do anything.
if they tell us they used whatever to mark up whatever then it is our job as module team tk take whatever and find the appropriate semantic mark up and apply it.
This is not different.
Peter
Sent from Outlook for iOS
From: sword-devel <sword-devel-boun...@crosswire.org> on behalf of David Haslam <dfh...@protonmail.com>
Sent: Thursday, May 1, 2025 12:59 pm
To: SWORD Developers' Collaboration Forum <sword-devel@crosswire.org>
Cc: David Haslam <df.has...@btinternet.com>
Subject: Re: [sword-devel] Proposal for a new SWORD filter to display word dividers
Sent: Thursday, May 1, 2025 12:59 pm
To: SWORD Developers' Collaboration Forum <sword-devel@crosswire.org>
Cc: David Haslam <df.has...@btinternet.com>
Subject: Re: [sword-devel] Proposal for a new SWORD filter to display word dividers
Hi Peter,
Undoubtedly, but we cannot demand or expect most Bible translators to be XML afficionados.
It's even difficult to teach some members of a translation team to use the ZWSP properly.
"If you cannot see it, key it again" can so easily become the modus operandi.
"If you cannot see it, key it again" can so easily become the modus operandi.
Witness the following in the same chapter prior to my involvement.
After I replaced all ZWSP by MIDDLE DOT, just look at the tangle!!!
See attached text file.
So we should do "belt and braces" to help the weak.
See attached text file.
So we should do "belt and braces" to help the weak.
Also called "going the extra mile". ๐
But worry not. My feedback is already helping the Khmer translation team.
Best regards,
David
David
Sent with Proton Mail secure email.
On Thursday, May 1st, 2025 at 12:47 PM, Peter von Kaehne <ref...@gmx.net> wrote:
I think this is not difficult per se, but it should be properly encoded.<w> seems correct, using zero with characters seems not correct.PeterSent from Outlook for iOSFrom: sword-devel <sword-devel-boun...@crosswire.org> on behalf of David Haslam <dfh...@protonmail.com>
Sent: Thursday, May 1, 2025 11:30 am
To: sword-devel mailing list <sword-devel@crosswire.org>
Cc: David Haslam <df.has...@btinternet.com>
Subject: [sword-devel] Proposal for a new SWORD filter to display word dividersI wish to propose that we design in a new SWORD filter.
The conf key would be:
- GlobalOptionFilter=ShowWordDividers
In the writing systems for the various languages of SE Asia (Thai, Khmer, Lao, Myanmar) there is [generally] no space between words.In this respect, they are like many European languages before the start of silent reading. The descriptive term is Scriptura Continua.
Some Bible translations for this region are already making use of one of the ZERO WIDTH characters to invisibly mark the divisions between lexical words.Options include:
- U+200B ZERO WIDTH SPACE
- U+200C ZERO WIDTH NON-JOINER
- U+FEFF ZERO WIDTH NO BREAK SPACE
They exclude:
- U+200D ZERO WIDTH JOINER
A further possibility, even without requiring a full study Bible with Strong's, etc, is to simply wrap each lexical word within the OSIS w element.One without any OSIS attributes would suffice for this purpose. Likewise, for the seg element.My proposal is that we design a feature to show/hide word dividers by displaying them using a suitable visible but non-intrusive character.My suggestion is to use this Unicode character by default:
- U+00B7 MIDDLE DOT
We could even allow the actual visible character to be specified in a second conf key, thus:
- VisibleWordDivider=U+00B7
Benefits would include:
- Helps with language learning to know where lexical words start and end
- Helps with front-end search for whole words, exact phrase or all words
- Helps with checking the accuracy of Bible translations by clearly displaying lexical word boundaries at the touch of a single key in the front-end
- Paves the way for Study Bible with the addition of Strong's mark-up, etc.
Here's a sample of Khmer verse text with the MIDDLE DOT as the visible word divider:Obad.1.1
DavidSent with Proton Mail secure email._______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
