On 29/12/11 09:05, David Haslam wrote:
Thanks for the detailed explanations.
I guess this was a comment to Matej's last email rather than a facetious
one to my one-liner?
:-)
But FWIW - I would suggest that cs-utf8.conf is looked through regarding
any missed out abbreviations or abbreviations
Yes - threaded views in email clients (or Nabble) help to contextualize such
one liners!
It would be helpful to module developers to know where to obtain the conf
files necessary for localization of book names, etc.
The fledgeling wiki page does not yet cover this topic.
Matěj Cepl wrote,
⌈ and ⌉ are more complicated. They are originally bkzavorka/ and
ekzavorka/ and they limit the text for which the appropriate translator
note is used.
-
I think ⌜top corners⌝ are visually less obtrusive for this purpose than
⌈ceilings⌉, so I have included such a
You could easily test if this is the case by finding a phrase that
wraps around a note in one of our heavily annotated modules like the
KJV or ESV.
Remember, if you test it, that BibleTime has its own implementation of
a search engine that is separate from what SWORD provides for the rest
of the
Matěj Cepl wrote, pomlcka/ stands for em-dash;
and the original code snippet he cited from Mark.1.1 includes,
61,1pomlcka/3;
yet upon examining Matěj's OSIS file, this snippet appears as 61,13;
rather than 61,1—3;
It would seem that his XSLT script has not converted any of the pomlcka/
to an
Thanks Greg,
Xiphos certainly supports it, so this means SWORD does.
As I'm working towards improving the OSIS for the CzeCSP module, that's what
I just tested.
A search for the exact phrase, posla před found just one hit in Mark.1.2
even though the word posla is followed by a note.
I also
I managed to find the ISV 2.0 Word docs - docm, docx, and doc - on an
archived version of isv.org. If anybody would like them I can send a link.
The docs are about a year old, include the OT, NT, footnotes, introductory
text, and appendixes.
Best regards
Martin
On 17 September 2011 13:38,