NB. Undocumented config keys will now be flagged as exceptions by the latest
script that Dom uses to prepare submitted modules for release by CrossWire.
It’s vital that any new proposals are agreed if such modules are to be
distributed by CrossWire.
What I wrote earlier was relevant in the cont
Front-ends generally ignore config keys that are not documented in our wiki for
SWORD based front-ends.
So the fact that most of the modules in the IBT repository contain keys that
work primarily with xulsword doesn’t have any [negative] consequences when
these modules are installed to other fr
Does anything need to be added to our wiki page?
https://wiki.crosswire.org/DevTools:conf_Files#Elements_required_for_proper_rendering
It’s the last row in the table in this section.
Troy, How does Bishop handle CSS ?
Anyone, How do other JSword based front-ends handle CSS ?
eg. Does STEP Bible
On Thu, Mar 4, 2021 at 10:57 AM David Haslam wrote:
> NB. Undocumented config keys will now be flagged as exceptions by the
> latest script that Dom uses to prepare submitted modules for release by
> CrossWire.
>
> It’s vital that any new proposals are agreed if such modules are to be
> distribut
Thank you for prompt replies.
>
> 1) the conf file is a shared and joint space and we really do not want to
> introduce per-front-end special values there.
>
I would suggest having a namespace prefix with which module makers can add
also frontend specific options. For example, if there was
Fronten
Can you describe the specific lay out requirements and why they are as they are, aside from the namespace?Sent from my mobile. Please forgive shortness, typos and weird autocorrects. Original Message Subject: [sword-devel] About PreferredCSSXHTMLFrom: Tuomas Airaksinen To: SWORD Dev
From: David HaslamFront-ends generally ignore config keys that are not documented in our wiki That is not really relevant. It really is not. ___
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Inst
My main thoughts are, unsorted and without conclusion1) the conf file is a shared and joint space and we really do not want to introduce per-front-end special values there. 2) You have clearly thought deeper about the matter than so far anyone of us as far as I can tell from previous discussions on
