Re: [sword-devel] ppc64le build error

[Greg Hellings]

That is a rather sizeable patch. I don't want to just apply it wholesale to
the Sword engine without some input from people who know more about the
code than I do. It should, however, be workable if Troy doesn't have a more
permanent fix in mind.

--Greg

On Wed, Jul 17, 2019 at 4:52 PM Jaak Ristioja  wrote:

> In Sword++ we fixed [1] this by using the fixed-width integer types
> provided by . Note also that some certain names containing
> underscores are reserved to the C++ implementation [2], e.g. names
> beginning with underscores and names containing adjacent underscores.
>
>
> Best regards,
> Jaak
>
>
> [1]: Feel free to integrate
>
> https://github.com/swordxx/swordxx/commit/3934674fd8db1302cc323c0a56235292d6d7
> back to Sword. In Sword++ most of these type names were later prefixed
> with std::, e.g. std::uint64_t instead of plain uint64_t.
>
> [2]: See https://stackoverflow.com/a/228797 for a good summary on this.
>
>
> On 17.07.19 17:52, Greg Hellings wrote:
> > I got an automated report this week that Sword 1.8.1 has begun failing to
> > build on ppc64le architecture with type redefinition errors. The errors
> are
> > reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1730318
> >
> > To copy from that link, the relevant error is:
> >
> >  /usr/include/asm-generic/int-l64.h:29:25: error: conflicting
> > declaration 'typedef long int __s64'
> > 29 | typedef __signed__ long __s64;
> >| ^
> >
> >  /usr/include/asm-generic/int-l64.h:30:23: error: conflicting
> > declaration 'typedef long unsigned int __u64'
> > 30 | typedef unsigned long __u64;
> >|   ^
> >
> > I try to shy away from knowing too much about C's typing system. I can
> > easily locate the places in our code where we are defining those types
> > ourself. However, I don't want to mess up proper detection and
> > definition of them in a patch if I can help it.
> >
> > --Greg
> >
> >
> > ___
> > sword-devel mailing list: sword-devel@crosswire.org
> > http://www.crosswire.org/mailman/listinfo/sword-devel
> > Instructions to unsubscribe/change your settings at above page
> >
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How to deal with invalid markup?

[Michael Johnson]

Mea culpa. Sorry about that. The engNET2016eb module has been updated to get 
rid of some residual XHTML notes at ends of chapters that were missed in the 
first filtering process. Oddly enough, the result was actually valid XML 
syntax, but its semantics were wrong.

On 7/16/19 9:36 PM, David Haslam wrote:
> Hi Tobias,
>
>
> OSIS Modules submitted for release by CrossWire should always be validated 
> prior to submission. They would be rejected if the XML cannot be validated to 
> one of the OSIS schemas that SWORD supports. All the more so if the input 
> file fails to pass an XML syntax check. 
>
> CrossWire has no control over the preparation of modules for the associated 
> repositories such as eBible.org
>
> Such errors should be reported to the repository owner, in this case 
> Kahunapule Michael Paul Johnson. 
> He is a member of this mailing list. 
>
> Best regards,
>
> David
>
> Sent from ProtonMail Mobile
>
>
> On Wed, Jul 17, 2019 at 07:13, Tobias Klein  > wrote:
>>
>> Hi everyone,
>>
>> Is there a recommended way on how to deal with invalid markup (in a 
>> frontend) when using the text from a Sword module?
>>
>> To me invalid markup is basically invalid XML.
>> You find an example below (Exodus 3:22 / engNET2016eb).
>>
>> Are Sword modules validated with standard XML validation tools before being 
>> published?
>>
>> Best regards,
>> Tobias
>>
>> Module: engNET2016eb
>>
>> Mark-up text of Exodus 3:22 (module->getRawEntry()):
>>
>> Every woman > lemma="strong:H7592">will ask her neighbor 
>> and the one who happens to be  staying > lemma="strong:H1004">in her house for items 
>> of silver and gold 
>> and for clothing. You 
>> will put these articles > lemma="strong:H5921">on your sons > lemma="strong:H1323">and daughters – thus you
>>
>> INVALID section starts here:
>>
>> will plunder Egypt*!” ‘*span class=”footnote” 
>> id=”footnote-65”*’‘*span class=”key”’65‘
>> a**href=”#note-65” 
>> class=”backref”’*3:19‘/a’‘*span class=”text”’ tn: > type="italic">Heb “
>>
>> and not > lemma="strong:H1004">with a mighty hand.”
>> ...
>>
>
>
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page


-- 
signature

Aloha,
*/Michael Johnson/**
PO BOX 881143 • PUKALANI HI 96788-1143*• USA
mljohnson.org  • Phone: +1 808-333-6921 • Skype: 
kahunapule



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] ppc64le build error

[Jaak Ristioja]

In Sword++ we fixed [1] this by using the fixed-width integer types
provided by . Note also that some certain names containing
underscores are reserved to the C++ implementation [2], e.g. names
beginning with underscores and names containing adjacent underscores.


Best regards,
Jaak


[1]: Feel free to integrate
https://github.com/swordxx/swordxx/commit/3934674fd8db1302cc323c0a56235292d6d7
back to Sword. In Sword++ most of these type names were later prefixed
with std::, e.g. std::uint64_t instead of plain uint64_t.

[2]: See https://stackoverflow.com/a/228797 for a good summary on this.


On 17.07.19 17:52, Greg Hellings wrote:
> I got an automated report this week that Sword 1.8.1 has begun failing to
> build on ppc64le architecture with type redefinition errors. The errors are
> reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1730318
> 
> To copy from that link, the relevant error is:
> 
>  /usr/include/asm-generic/int-l64.h:29:25: error: conflicting
> declaration 'typedef long int __s64'
> 29 | typedef __signed__ long __s64;
>| ^
> 
>  /usr/include/asm-generic/int-l64.h:30:23: error: conflicting
> declaration 'typedef long unsigned int __u64'
> 30 | typedef unsigned long __u64;
>|   ^
> 
> I try to shy away from knowing too much about C's typing system. I can
> easily locate the places in our code where we are defining those types
> ourself. However, I don't want to mess up proper detection and
> definition of them in a patch if I can help it.
> 
> --Greg
> 
> 
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
> 


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How to deal with invalid markup?

[Tobias Klein]

Thanks, David! To have this broken note shown in the middle of the Bible text 
without being asked for is rather distracting in my opinion. I'd rather choose 
the "validate and fall back to plain text" option recommended by Peter.

Best regards,
Tobias

Am 17. Juli 2019 22:19:13 MESZ schrieb David Haslam :
>I installed the aforementioned module in PocketSword and sent a
>screenshot of the invalid XML verse to Tobias via Facebook Messenger.
>
>It does seem to display the errant markup text as best it can, with
>footnote references shown as links, etc.
>
>David
>
>Sent from ProtonMail Mobile
>
>On Wed, Jul 17, 2019 at 21:12, Tobias Klein 
>wrote:
>
>> Thanks, good advice! Especially the idea about dynamically validating
>markup text and then going for the plain text version as a fallback.
>I'll think about using that option in node-sword-interface (Ezra
>Project's SWORD integration library).
>>
>> Best regards,
>> Tobias
>>
>> On 17.07.19 13:59, Peter Von Kaehne wrote:
>>
>>> 1) The best way is to recognise it and either fall back to something
>sane or refuse to deal with the module without crashing. You could
>presumably if an xml chunk is delivered by the engine to you and is not
>internally valid ask the engine to re-render it plainly and spit out
>some message to that effect on the terminal. Then a use may be in the
>position to see this and send a bug report to whoever is responsible
>for the dodgy module.
>>>
>>> 2) CrossWire modules are for teh last 10 years or so always tested
>and validated before they are published but other repositories are
>subject to their own rules. The module you reference is from eBible and
>not CrossWire. But - admittedly - we have in CrossWire still a lot of
>old modules which may well have bugs which only show up slowly.
>>>
>>> Peter
>>>
>>> Gesendet: Mittwoch, 17. Juli 2019 um 07:13 Uhr
>>> Von: "Tobias Klein"
>[](mailto:cont...@tklein.info)
>>> An: "SWORD Developers' Collaboration Forum"
>[](mailto:sword-devel@crosswire.org)
>>> Betreff: [sword-devel] How to deal with invalid markup?
>>>
>>> Hi everyone,
>>>
>>> Is there a recommended way on how to deal with invalid markup (in a
>frontend) when using the text from a Sword module?
>>>
>>> To me invalid markup is basically invalid XML.
>>> You find an example below (Exodus 3:22 / engNET2016eb).
>>>
>>> Are Sword modules validated with standard XML validation tools
>before being published?
>>>
>>> Best regards,
>>> Tobias
>>>
>>> Module: engNET2016eb
>>>
>>> Mark-up text of Exodus 3:22 (module->getRawEntry()):
>>>
>>> Every woman lemma="strong:H7592">will ask her
>neighbor and the one who happens to be 
>staying in her house lemma="strong:H3627">for items of
>silver and gold lemma="strong:H8071">and for clothing. You
>will put these articles lemma="strong:H5921">on your sons lemma="strong:H1323">and daughters – thus
>you
>>>
>>> INVALID section starts here:
>>>
>>> will plunder Egypt!” ‘span
>class=”footnote” id=”footnote-65”’‘span class=”key”’65‘
>>> ahref=”#note-65”
>class=”backref”’3:19‘/a’‘span class=”text”’ tn:
>Heb “
>>>
>>> and not lemma="strong:H1004">with a mighty
>hand.”
>>> ...
>>>
>>> ___ sword-devel mailing
>list: sword-devel@crosswire.org
>http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to
>unsubscribe/change your settings at above page
>>>
>>> ___
>>> sword-devel mailing list:
>>> sword-devel@crosswire.org
>>>
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page

-- 
Message sent from my phone. Please excuse brevity.___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] Displaying the chapter and verse in other numbers

[David Haslam]

Several other non-Roman scripts have their own digit characters corresponding 
to our 0-9.

IMHO the possibilities for using non-Roman digits ought to be facilitated in 
the back-end.

Even so, each front-end would then require a new UI control to select which 
script should be used to display the chapter and verse numbers.

An alternate idea would be to specify the non-Roman digits as a ten character 
UTF-8 string in a module .conf file.

Adapting the back-end to use this module specific configuration key might be 
much simpler.

Front-ends would still require adapting for the UI features that require 
chapter and verse numbers to be input or displayed or adjusted by controls.

Best regards,

David

Sent from ProtonMail Mobile

On Wed, Jul 17, 2019 at 22:00, Cyrille  wrote:

> Hello,
> I'm still working on a modern NT-Ps-Pr translation in Burmese. My friends 
> from Myanmar send me the text. But they don't use the arab numbers, they hava 
> their own numbers.
> It could be very important for them to write in they own numbers (If I had tu 
> use their I will be lost ;) ).
> Is it possible to add this possibility to the frontend, or this should be in 
> sword directly?
> Need I to open a new issue on the bug tracker?
>
> Example of text, in bold the chapter and verses:
>
> ၃ ၁။ ထိုနေ့ရက်တို့၌ ယောဟန်ဘတ္တိဇံသည် ရောက်လာ၍ ဂျူဒေးယပြည်၊ တောကန္တာရတွင် ဟော
>
> ၂။ ပြောသည်မှာ၊- နောင်တရကြလော့၊ အကြောင်းမူကား ကောင်းကင်နိုင်ငံတော်သည် 
> ရောက်လုနီးပြီဟူ၍တည်း။-
>
> ၃။ ပရောဖက်အီဇာယဟောထားခဲ့သည့်အတိုင်း၊ ထာ၀ရ 
> ဘုရားသခင်ကြွလာတော်မူမည့်လမ်းကိုပြင်ဆင်ကြ လော့၊ ကိုယ်တော်၏ လမ်းများကို 
> ဖြောင့်တန်းစေကြ လော့ဟူ၍ တောကန္တာရ၌ ကြွေးကြော်သောသူ၏အသံသည်ကား ဤသူပင်ဖြစ်သတည်း။-
>
> ၄။ ယောဟန်သည် ကုလားအုတ်မွေးဖြင့် ရက်လုပ်သောအဝတ်ကိုဝတ်ဆင်ကာ ခါး၌ 
> သားရေခါးစည်းကြိုးကိုစည်းထား၏။ သူ၏အစာသည်ကား ကျိုင်းကောင်နှင့် 
> တောပျားရည်တို့သာဖြစ်၏။-
>
> ၅။ ထိုအခါ ဂျေရုဆလင်မြို့မှစ၍ ဂျူဒေးယနယ်တစ်နယ် လုံးနှင့် 
> ဂျော်ဒန်မြစ်တစ်လျှောက်ရှိဒေသမှ လူအပေါင်း တို့သည် သူ့ထံသို့ လာကြ၏။-
>
> ၆။ ထိုသူတို့သည် မိမိတို့၏ အပြစ်များကို ထုတ်ဖော်ဝန်ခံကြလျက် ဂျော်ဒန်မြစ်တွင် 
> သူ့အားဖြင့် ဆေးကြောခြင်းကို ခံယူကြ၏။___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] Displaying the chapter and verse in other numbers

[Cyrille]

Hello,
I'm still working on a modern NT-Ps-Pr translation in Burmese. My
friends from Myanmar send me the text. But they don't use the arab
numbers, they hava their own numbers.
It could be very important for them to write in they own numbers (If I
had tu use their I will be lost ;) ).
Is it possible to add this possibility to the frontend, or this should
be in sword directly?
Need I to open a new issue on the bug tracker?

Example of text, in bold the chapter and verses:

၃ ၁။ ထိုနေ့ရက်တို့၌ ယောဟန်ဘတ္တိဇံသည် ရောက်လာ၍ ဂျူဒေးယပြည်၊ တောကန္တာရတွင် ဟော

*၂။* ပြောသည်မှာ၊- နောင်တရကြလော့၊ အကြောင်းမူကား ကောင်းကင်နိုင်ငံတော်သည်
ရောက်လုနီးပြီဟူ၍တည်း။-

*၃။* ပရောဖက်အီဇာယဟောထားခဲ့သည့်အတိုင်း၊ ထာ၀ရ
ဘုရားသခင်ကြွလာတော်မူမည့်လမ်းကိုပြင်ဆင်ကြ လော့၊ ကိုယ်တော်၏ လမ်းများကို
ဖြောင့်တန်းစေကြ လော့ဟူ၍ တောကန္တာရ၌ ကြွေးကြော်သောသူ၏အသံသည်ကား ဤသူပင်ဖြစ်သတည်း။-

*၄။* ယောဟန်သည် ကုလားအုတ်မွေးဖြင့် ရက်လုပ်သောအဝတ်ကိုဝတ်ဆင်ကာ ခါး၌
သားရေခါးစည်းကြိုးကိုစည်းထား၏။ သူ၏အစာသည်ကား ကျိုင်းကောင်နှင့် 
တောပျားရည်တို့သာဖြစ်၏။-

*၅။* ထိုအခါ ဂျေရုဆလင်မြို့မှစ၍ ဂျူဒေးယနယ်တစ်နယ် လုံးနှင့်
ဂျော်ဒန်မြစ်တစ်လျှောက်ရှိဒေသမှ လူအပေါင်း တို့သည် သူ့ထံသို့ လာကြ၏။-

၆။ ထိုသူတို့သည် မိမိတို့၏ အပြစ်များကို ထုတ်ဖော်ဝန်ခံကြလျက်
ဂျော်ဒန်မြစ်တွင် သူ့အားဖြင့် ဆေးကြောခြင်းကို ခံယူကြ၏။



___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How to deal with invalid markup?

[David Haslam]

I installed the aforementioned module in PocketSword and sent a screenshot of 
the invalid XML verse to Tobias via Facebook Messenger.

It does seem to display the errant markup text as best it can, with footnote 
references shown as links, etc.

David

Sent from ProtonMail Mobile

On Wed, Jul 17, 2019 at 21:12, Tobias Klein  wrote:

> Thanks, good advice! Especially the idea about dynamically validating markup 
> text and then going for the plain text version as a fallback. I'll think 
> about using that option in node-sword-interface (Ezra Project's SWORD 
> integration library).
>
> Best regards,
> Tobias
>
> On 17.07.19 13:59, Peter Von Kaehne wrote:
>
>> 1) The best way is to recognise it and either fall back to something sane or 
>> refuse to deal with the module without crashing. You could presumably if an 
>> xml chunk is delivered by the engine to you and is not internally valid ask 
>> the engine to re-render it plainly and spit out some message to that effect 
>> on the terminal. Then a use may be in the position to see this and send a 
>> bug report to whoever is responsible for the dodgy module.
>>
>> 2) CrossWire modules are for teh last 10 years or so always tested and 
>> validated before they are published but other repositories are subject to 
>> their own rules. The module you reference is from eBible and not CrossWire. 
>> But - admittedly - we have in CrossWire still a lot of old modules which may 
>> well have bugs which only show up slowly.
>>
>> Peter
>>
>> Gesendet: Mittwoch, 17. Juli 2019 um 07:13 Uhr
>> Von: "Tobias Klein" [](mailto:cont...@tklein.info)
>> An: "SWORD Developers' Collaboration Forum" 
>> [](mailto:sword-devel@crosswire.org)
>> Betreff: [sword-devel] How to deal with invalid markup?
>>
>> Hi everyone,
>>
>> Is there a recommended way on how to deal with invalid markup (in a 
>> frontend) when using the text from a Sword module?
>>
>> To me invalid markup is basically invalid XML.
>> You find an example below (Exodus 3:22 / engNET2016eb).
>>
>> Are Sword modules validated with standard XML validation tools before being 
>> published?
>>
>> Best regards,
>> Tobias
>>
>> Module: engNET2016eb
>>
>> Mark-up text of Exodus 3:22 (module->getRawEntry()):
>>
>> Every woman > lemma="strong:H7592">will ask her neighbor 
>> and the one who happens to be  staying > lemma="strong:H1004">in her house for items 
>> of silver and gold 
>> and for clothing. You 
>> will put these articles > lemma="strong:H5921">on your sons > lemma="strong:H1323">and daughters – thus you
>>
>> INVALID section starts here:
>>
>> will plunder Egypt!” ‘span class=”footnote” 
>> id=”footnote-65”’‘span class=”key”’65‘
>> ahref=”#note-65” class=”backref”’3:19‘/a’‘span 
>> class=”text”’ tn: Heb “
>>
>> and not > lemma="strong:H1004">with a mighty hand.”
>> ...
>>
>> ___ sword-devel mailing list: 
>> sword-devel@crosswire.org 
>> http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to 
>> unsubscribe/change your settings at above page
>>
>> ___
>> sword-devel mailing list:
>> sword-devel@crosswire.org
>>
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How to deal with invalid markup?

[Tobias Klein]

Thanks David!

On 17.07.19 09:36, David Haslam wrote:

Hi Tobias,


OSIS Modules submitted for release by CrossWire should always be 
validated prior to submission. They would be rejected if the XML 
cannot be validated to one of the OSIS schemas that SWORD supports. 
All the more so if the input file fails to pass an XML syntax check.


CrossWire has no control over the preparation of modules for the 
associated repositories such as eBible.org


Such errors should be reported to the repository owner, in this case 
Kahunapule Michael Paul Johnson.

He is a member of this mailing list.

Best regards,

David

Sent from ProtonMail Mobile


On Wed, Jul 17, 2019 at 07:13, Tobias Klein > wrote:


Hi everyone,

Is there a recommended way on how to deal with invalid markup (in a 
frontend) when using the text from a Sword module?


To me invalid markup is basically invalid XML.
You find an example below (Exodus 3:22 / engNET2016eb).

Are Sword modules validated with standard XML validation tools before 
being published?


Best regards,
Tobias

Module: engNET2016eb

Mark-up text of Exodus 3:22 (module->getRawEntry()):

Every woman lemma="strong:H7592">will ask her 
neighbor and the one who happens to be 
staying in her house lemma="strong:H3627">for items of 
silver and gold lemma="strong:H8071">and for clothing. lemma="strong:H7760">You will put these 
articles on lemma="strong:H1121">your sons and 
daughters – thus you


INVALID section starts here:

will plunder Egypt*!” ‘*span 
class=”footnote” id=”footnote-65”*’‘*span class=”key”’65‘
a**href=”#note-65” 
class=”backref”’*3:19‘/a’‘*span class=”text”’ type="italic">tn: Heb “


and not lemma="strong:H1004">with a mighty hand.”

...





___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How to deal with invalid markup?

[Tobias Klein]

Thanks, good advice! Especially the idea about dynamically validating 
markup text and then going for the plain text version as a fallback. 
I'll think about using that option in node-sword-interface (Ezra 
Project's SWORD integration library).


Best regards,
Tobias

On 17.07.19 13:59, Peter Von Kaehne wrote:
1) The best way is to recognise it and either fall back to something 
sane or refuse to deal with the module without crashing. You could 
presumably if an xml chunk is delivered by the engine to you and is 
not internally valid ask the engine to re-render it plainly and spit 
out some message to that effect on the terminal. Then a use may be in 
the position to see this and send a bug report to whoever is 
responsible for the dodgy module.
2) CrossWire modules are for teh last 10 years or so always tested and 
validated before they are published but other repositories are subject 
to their own rules. The module you reference is from eBible and not 
CrossWire. But - admittedly - we have in CrossWire still a lot of old 
modules which may well have bugs which only show up slowly.

Peter
*Gesendet:* Mittwoch, 17. Juli 2019 um 07:13 Uhr
*Von:* "Tobias Klein" 
*An:* "SWORD Developers' Collaboration Forum" 
*Betreff:* [sword-devel] How to deal with invalid markup?

Hi everyone,

Is there a recommended way on how to deal with invalid markup (in a 
frontend) when using the text from a Sword module?


To me invalid markup is basically invalid XML.
You find an example below (Exodus 3:22 / engNET2016eb).

Are Sword modules validated with standard XML validation tools before 
being published?


Best regards,
Tobias

Module: engNET2016eb

Mark-up text of Exodus 3:22 (module->getRawEntry()):

Every woman lemma="strong:H7592">will ask her 
neighbor and the one who happens to be  
staying in her house lemma="strong:H3627">for items of 
silver and gold lemma="strong:H8071">and for clothing. You 
will put these articles lemma="strong:H5921">on your sons lemma="strong:H1323">and daughters – thus 
you


INVALID section starts here:

will plunder Egypt*!” ‘*span 
class=”footnote” id=”footnote-65”*’‘*span class=”key”’65‘
a**href=”#note-65” 
class=”backref”’*3:19‘/a’‘*span class=”text”’ type="italic">tn: Heb “


and not lemma="strong:H1004">with a mighty hand.”

...

___ sword-devel mailing 
list: sword-devel@crosswire.org 
http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to 
unsubscribe/change your settings at above page


___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] ppc64le build error

[Greg Hellings]

I got an automated report this week that Sword 1.8.1 has begun failing to
build on ppc64le architecture with type redefinition errors. The errors are
reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1730318

To copy from that link, the relevant error is:

 /usr/include/asm-generic/int-l64.h:29:25: error: conflicting
declaration 'typedef long int __s64'
29 | typedef __signed__ long __s64;
   | ^

 /usr/include/asm-generic/int-l64.h:30:23: error: conflicting
declaration 'typedef long unsigned int __u64'
30 | typedef unsigned long __u64;
   |   ^

I try to shy away from knowing too much about C's typing system. I can
easily locate the places in our code where we are defining those types
ourself. However, I don't want to mess up proper detection and
definition of them in a patch if I can help it.

--Greg
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How to deal with invalid markup?

[Peter Von Kaehne]

1) The best way is to recognise it and either fall back to something sane or refuse to deal with the module without crashing. You could presumably if an xml chunk is delivered by the engine to you and is not internally valid ask the engine to re-render it plainly and spit out some message to that effect on the terminal. Then a use may be in the position to see this and send a bug report to whoever is responsible for the dodgy module.
 

2) CrossWire modules are for teh last 10 years or so always tested and validated before they are published but other repositories are subject to their own rules. The module you reference is from eBible and not CrossWire. But - admittedly - we have in CrossWire still a lot of old modules which may well have bugs which only show up slowly.

 

Peter

 

 

 

Gesendet: Mittwoch, 17. Juli 2019 um 07:13 Uhr
Von: "Tobias Klein" 
An: "SWORD Developers' Collaboration Forum" 
Betreff: [sword-devel] How to deal with invalid markup?



Hi everyone,

Is there a recommended way on how to deal with invalid markup (in a frontend) when using the text from a Sword module?

To me invalid markup is basically invalid XML.
You find an example below (Exodus 3:22 / engNET2016eb).

Are Sword modules validated with standard XML validation tools before being published?

Best regards,
Tobias
 

Module: engNET2016eb

Mark-up text of Exodus 3:22 (module->getRawEntry()):

Every woman will ask her neighbor and the one who happens to be  staying in her house for items of silver and gold and for clothing. You will put these articles on your sons and daughters – thus you

INVALID section starts here:

will plunder Egypt!” ‘span class=”footnote” id=”footnote-65”’‘span class=”key”’65‘
a href="" class=”backref”’3:19‘/a’‘span class=”text”’ tn: Heb “

and not with a mighty hand.”
...
___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page





___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Re: [sword-devel] How to deal with invalid markup?

[David Haslam]

Hi Tobias,

OSIS Modules submitted for release by CrossWire should always be validated 
prior to submission. They would be rejected if the XML cannot be validated to 
one of the OSIS schemas that SWORD supports. All the more so if the input file 
fails to pass an XML syntax check.

CrossWire has no control over the preparation of modules for the associated 
repositories such as eBible.org

Such errors should be reported to the repository owner, in this case Kahunapule 
Michael Paul Johnson.
He is a member of this mailing list.

Best regards,

David

Sent from ProtonMail Mobile

On Wed, Jul 17, 2019 at 07:13, Tobias Klein  wrote:

> Hi everyone,
>
> Is there a recommended way on how to deal with invalid markup (in a frontend) 
> when using the text from a Sword module?
>
> To me invalid markup is basically invalid XML.
> You find an example below (Exodus 3:22 / engNET2016eb).
>
> Are Sword modules validated with standard XML validation tools before being 
> published?
>
> Best regards,
> Tobias
>
> Module: engNET2016eb
>
> Mark-up text of Exodus 3:22 (module->getRawEntry()):
>
> Every woman  lemma="strong:H7592">will ask her neighbor  lemma="strong:H1481">and the one who happens to be  staying  lemma="strong:H1004">in her house for items 
> of silver and gold  lemma="strong:H8071">and for clothing. You will 
> put these articles  lemma="strong:H5921">on your sons  lemma="strong:H1323">and daughters – thus you
>
> INVALID section starts here:
>
> will plunder Egypt!” ‘span class=”footnote” 
> id=”footnote-65”’‘span class=”key”’65‘
> ahref=”#note-65” class=”backref”’3:19‘/a’‘span 
> class=”text”’ tn: Heb “
>
> and not  lemma="strong:H1004">with a mighty hand.”
> ...___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

[sword-devel] How to deal with invalid markup?

[Tobias Klein]

Hi everyone,

Is there a recommended way on how to deal with invalid markup (in a 
frontend) when using the text from a Sword module?


To me invalid markup is basically invalid XML.
You find an example below (Exodus 3:22 / engNET2016eb).

Are Sword modules validated with standard XML validation tools before 
being published?


Best regards,
Tobias

Module: engNET2016eb

Mark-up text of Exodus 3:22 (module->getRawEntry()):

Every woman lemma="strong:H7592">will ask her 
neighbor and the one who happens to be 
staying in her house lemma="strong:H3627">for items of silver 
and gold and for 
clothing. You will put lemma="strong:H3627">these articles on 
your sons and 
daughters – thus you


INVALID section starts here:

will plunder Egypt*!” ‘*span 
class=”footnote” id=”footnote-65”*’‘*span class=”key”’65‘
a**href=”#note-65” 
class=”backref”’*3:19‘/a’‘*span class=”text”’ tn: 
Heb “


and not lemma="strong:H1004">with a mighty hand.”

...

___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page