[sword-devel] Locale differences
thulester at gmail.com
Sun Sep 16 17:19:54 MST 2012
And it makes sense ... why shouldn't the OSIS influence the modules
own configuration (its not like the .conf file is dealing with
something separate from what the OSIS markup is)? The less extraneous
configuration required outside of the module itself the cleaner the
Also, module creators look first to the OSIS to influence how the
module naturally. The creation of the .conf file is often an
after-thought required to make the module work because those details
in OSIS are ignored.
On Sun, Sep 16, 2012 at 8:11 PM, Chris Little <chrislit at crosswire.org> wrote:
> On 09/16/2012 12:40 PM, Andrew Thule wrote:
>> Needless osis filler ....?
>> I assume it's gone this way because modules needed conf-like influence
>> but the (osis) standard moves too slowly? (I think I read in this
>> list someone wondering if people were still working on it - with the
>> recommendation Sword developers should just adopt Sword specific
>> If so, I understand the practicality, but its too bad all of the .conf
>> stuff couldn't be contained in the module so we could do away with
>> having to generate .conf files apart from the modules' osis (or if its
>> a resource issue, make it so the .confs could be generated from the
>> module itself). The fact there are .conf suggests a defect in the
> From the OSIS header, <title>, <date>, <language>, <subject>, <identifier>,
> <rights>, and <description> are the elements that have close analogues in
> our .conf format.
> Of that set, exactly zero are guaranteed to be in the right format required
> by Sword's .conf files. The <date>, <language>, and <subject> elements,
> provided they have precisely the correct type, could be used directly in
> .confs. <description>, since it's a string value, could probably be used
> directly. The <title>, <rights>, and <identifier> elements are nearly
> guaranteed to be in the wrong format.
> They're different mechanisms for encoding data needed for different
> purposes. It's not as if we didn't have Sword's .conf format in
> approximately its current state at the time we helped create OSIS.
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel