[sword-devel] module supplied v11n
kostyamaslyuk at gmail.com
Mon Jan 6 08:19:03 MST 2014
Another thing that was encountered with many concerns is ability to deploy
with module it's v11n system.
Technically this task is quite simple, but we have found that difficulty is
in the area of defining policies. Due to concerns that this feature will be
used as we not suppose it to be used it cant be "public" and even maybe
should not be documented.
I still see some points that this feature makes sense for:
1. It will help to test and fix bugs when we start to release sword with
av11n-mappings support. We would switch any particular module from sword
supplied v11n to module supplied and vice versa at any time and do not wait
next sword release.
2. if we define binary format for v11n it would give better sync with
jsword development. I think it would be useful if there will be ability to
export v11ns with mappings data from sword core into file and then supply
those files with jsword.
3. many v11ns would be supplied only with modules as not many people
actually use them. Regular Bible reader may need only one versification
4. it just add flexibility and freedom, important principles for free
module will have one additional file in its data folder, it store v11n data
in binary format. Mappings data is also included. When SWMgr loads module
it also register v11n from that file. To avoid collisions v11n name is
equal to loaded module name.
----------- ???????? ????? -----------
???????? ? ??????? HTML ???? ?????????…
More information about the sword-devel