Something's changed in diatheke plain output format with regard to how it
renders text wrapped in the OSIS hi element.
Currently, it places an asterisk and space before and a space and asterisk
after the marked text.
From time immemorial, it simply placed an asterisk at both the start and end
The "strange reason" is a well understood design decision in the engine
that is, however, non obvious and leads frequently to this type of
behavior for client applications.
It is also patched in Subversion already.
--Greg
On Mon, Apr 9, 2018, 14:00 David Haslam wrote:
Apologies.
I seem to have forgotten what Greg pointed out only last week.
For some strange reason, the Psalm titles are currently output before verse 2
rather than before verse 1.
Best regards,
David
Sent with [ProtonMail](https://protonmail.com) Secure Email.
‐‐‐ Original Message
This used to be the syntax help for diatheke output format:
Valid output_format values are: GBF, ThML, RTF, HTML, HTMLHREF, XHTML, OSIS,
CGI, and plain (def)
This is the current syntax help:
Valid output_format values are: CGI, GBF, HTML, HTMLHREF, LaTeX, OSIS, RTF,
ThML, WEBIF, XHTML,
Developers seem to have neglected attending to version numbers for diatheke.
See https://wiki.crosswire.org/Frontends:Diatheke#Release_history
Release history
This section needs expanding.
- Version 4.6 was released during 2013.
- Version 4.7 was released on Aug 30 2015.
- Several updates to
Going on from the earlier thread.
It's evident that diatheke can output section headings, viz., try this:
>diatheke -b ESV2011 -o h -f plain -k Matt.1
The output includes:
The Genealogy of Jesus Christ
(before verse 2)
The Birth of Jesus Christ
(before verse 19)
both of which are titles supplied
Version number
Copyright date range?
Best regards, David
Sent from ProtonMail Mobile
On Tue, Mar 27, 2018 at 23:40, Troy A. Griffitts wrote:
> Nope, sorry Greg. I reviewed and approved of it :)
>
> Applied.
>
> On 03/27/2018 08:43 AM, Greg Hellings wrote:
>
>>
Nope, sorry Greg. I reviewed and approved of it :)
Applied.
On 03/27/2018 08:43 AM, Greg Hellings wrote:
> Troy,
>
> I know you were working on the repo quite a bit over the weekend. I
> didn't see this patch land. Did I miss it in the commit emails?
>
> --Greg
>
> On Wed, Mar 21, 2018 at
Troy,
I know you were working on the repo quite a bit over the weekend. I didn't
see this patch land. Did I miss it in the commit emails?
--Greg
On Wed, Mar 21, 2018 at 12:32 AM, Troy A. Griffitts
wrote:
> Thanks for the patch, Greg. Yes. Agreed it is not intuitive to
No - that makes no difference, neither did using osis2mod version $3431
Salmo de David, cuando huía de
delante de Absalom su hijo.
Jehová, ¡cuánto se han multiplicado
mis enemigos! muchos se levantan contra mí.
Muchos dicen de mi alma: No hay
para él salud en Dios. Selah.
However, examining
On Thu, Mar 22, 2018 at 8:51 AM, David Haslam wrote:
> Greg,
>
> Thanks for the comparison between *KJV* and *SpaRV1909*.
>
> It seems therefore that I assumed *incorrectly* that the "extra space"
> problem was more general, and that *any* module with Psalm titles could
>
Greg,
Thanks for the comparison between KJV and SpaRV1909.
It seems therefore that I assumed incorrectly that the "extra space" problem
was more general, and that any module with Psalm titles could be used
illustrate it.
FYI. Test module SpaRV1865 only exists so far in the text development
On Thu, Mar 22, 2018 at 4:01 AM, David Haslam wrote:
> Hi Greg,
>
> With *Plain* output format, there's a minor side effect in the way the
> Psalm title was output in the wrong place.
> Verse 2 of the same Psalm was output with a *leading space* before the
> Reference.
>
>
Hi Greg,
With Plain output format, there's a minor side effect in the way the Psalm
title was output in the wrong place.
Verse 2 of the same Psalm was output with a leading space before the Reference.
https://www.dropbox.com/s/uz1amnrp7ez0b4y/Screenshot%202018-03-22%2008.37.42.png?dl=0
This
A thread was begun in December 2015 with this topic. My reminder was sent on 21
November, last year.
See
http://sword-dev.350566.n4.nabble.com/Diatheke-and-MarkDown-format-tt4655468.html#a4657703
Is anyone willing to step forward to develop the code for this?
Best regards,
David
Sent with
Has the UI changed without me noticing?
This is what I got using version 4.7 of diatheke that comes with Xiphos 4.0.6a
for Windows.
S:\>xiphos\diatheke -b KJV -o h -k Ps 3
Psalms 3:1: LORD, how are they increased that trouble me! many are they that ris
e up against me.
Psalms 3:2: Many there be
Thanks Greg for the patch.
Thanks also to everyone who provided insightful input.
Best regards,
David
Sent from ProtonMail Mobile
On Wed, Mar 21, 2018 at 03:33, Greg Hellings wrote:
> On Tue, Mar 20, 2018 at 10:21 PM, Troy A. Griffitts
>
Thanks for the patch, Greg. Yes. Agreed it is not intuitive to the uninitiated.
The warring factions are that a module key can be changed with a reference
directly to its key, the module being oblivious to that fact that it changed.
Also, a module position might be incremented but never asked
On Tue, Mar 20, 2018 at 10:21 PM, Troy A. Griffitts
wrote:
> If I had to guess, I suspect diatheke is not calling renderText before
> asking for the header. The renderText method triggers all entryAttributes
> to be filled. The header is an entryAttribute.
>
Spot on. If I
If I had to guess, I suspect diatheke is not calling renderText before asking
for the header. The renderText method triggers all entryAttributes to be
filled. The header is an entryAttribute.
On March 20, 2018 8:13:41 PM MST, Greg Hellings wrote:
>To be quite specific:
To be quite specific: diatheke does not encounter that header in the
preverse content until it reaches Psalm 3:2 for some reason that is beyond
my ken. Therefore, it is properly rendering that content as preverse, but
it has attached it to the wrong verse. Output from my slightly modified
diatheke
It's easier to see the problem when using plain formatting:
$ diatheke -b KJV -o h -f Plain -k Ps 3
Psalms 3:1: LORD, how are they increased that trouble me! many are they
that rise up against me.
A Psalm of David, when he fled from Absalom his son.
Psalms 3:2: Many there be which say of my soul,
I'm not so sure your initial assertion is correct.
$ diatheke -b KJV -o h -k Ps 3
Psalms 3:1: Lord, how are they increased that trouble me!
many are they that rise up against me.
A Psalm
of David, when he
fled from Absalom his
son.Psalms 3:2: Many there be which say
of my soul, There
is no help
Maybe someone could patch diatheke to fix this?
Best regards, David
Sent from ProtonMail Mobile
On Wed, Mar 14, 2018 at 12:14, David Haslam wrote:
> Diatheke does not output the canonical Psalm titles when output option h is
> used.
>
> Try this and see what I mean.
>
Diatheke does not output the canonical Psalm titles when output option h is
used.
Try this and see what I mean.
diatheke -b KJV -o h -k Ps 3
This is a significant lack of feature.
Best regards,
David
Sent from ProtonMail Mobile___
sword-devel
> Von: "David Haslam"
> However, I've yet to see any set of Sword utilities for Windows that
> actually do that, as I observed back in October 2015.
You would not, because it had be kept out of releases. Only people building
against SVNhead would have access to it. It
Thanks Peter,
I'm sure you're the best candidate for the task, in view of the stirling
work you did by adding LaTeX format to its output capabilities.
However, I've yet to see any set of Sword utilities for Windows that
actually do that, as I observed back in October 2015.
> When will the
> Von: "David Haslam"
>
> A reminder for my suggestion made in December 2015 nearly two years ago:
> > It would be better to add a fully fledged output format for MarkDown,
> > and leave the default to just plain text with no frills.
I have done some work on this but
A reminder for my suggestion made in December 2015 nearly two years ago:
David Haslam wrote
> When outputting plain text, diatheke currently makes a half-hearted
> attempt to use a tiny bit of MarkDown format for anything that was wrapped
> in the OSIS hi element, whether italics or bold type
So, I did a little experimenting this weekend and found that the ICU
RegEx engine is actually really capable.
o It's fast.
o It supports {n,m} characters instead of bytes
o It even works (though a little slow) with lookaheads and lookbacks,
e.g., for words in any order:
Another possibility is to use Boost.Xpressive [1], which I think
supports the Perl regular expressions at runtime, and also static
regular expressions using C++ syntax:
using namespace boost::xpressive;
// sregex rex = sregex::compile( "(\\w+) (\\w+)!" );
sregex rex = (s1= +_w) >> ' '
OK, I've been tinkering more with *diatheke* and just found a bug in how
these two option filters act:
*-o e* should be Word *E*numerations
*-o n* should be Strongs *N*umbers
What actually happens with (say) output filter OSIS, is as follows:
*-o e* doesn't add anything
*-o n* adds Word
Thanks, Karl,
Xiphos 4.0.4 in Windows 7 x64 gave this:
S:\>xiphos\diatheke -b KJV -s regex -k Abed...nego
Verses containing "Abed...nego"-- Daniel 1:7 ; Daniel 2:49 ; Daniel 3:12 ;
Daniel 3:13 ; Daniel 3:14 ; Daniel 3:16 ; Daniel 3:19 ; Daniel 3:20 ; Daniel
3:22 ; Daniel 3:23 ; Daniel 3:26 ;
On 03/06/2017 09:06 PM, DM Smith wrote:
> Does setting CLANG (or whatever it is) in the env help? In unix you
> have to tell the program what charset you are using.
They already come along for the ride for free as a result of logging in,
per default specification when system was installed.
$
Does setting CLANG (or whatever it is) in the env help? In unix you have to
tell the program what charset you are using.
Cent from my fone so theer mite be tipos. ;)
> On Mar 6, 2017, at 7:52 PM, Karl Kleinpaste wrote:
>
>> On 03/06/2017 05:25 PM, Greg Hellings wrote:
>>
Yeah, so this page shows that c11x regex is still mostly unsupported in gcc:
http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.tr1
(see section 7)
And the old school gnu regex we use otherwise I don't think knows
anything about wide chars. It simply compares bytes and
On 03/06/2017 05:25 PM, Greg Hellings wrote:
> being off by 2 would seem strange to me
I don't understand this question at all.
0xE2 = 226 = 0342
0x80 = 128 = 0200
0x93 = 147 = 0223
There's no off-by error at all.
"od" is the "octal dump" tool; given -c, it tries to dump characters,
but outside
On Mon, Mar 6, 2017 at 4:15 PM, David Haslam wrote:
> Are we sure it's an "off by 2" error and not just an email typo?
>
I'm not sure of that at all. It was my first guess, but being off by 2
would seem strange to me, as I would expect a "fat finger" error to produce
an
Are we sure it's an "off by 2" error and not just an email typo?
I wasn't expecting decimal, I just didn't parse it as octal.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/diatheke-search-type-regex-and-the-dot-tp4656879p4656914.html
Sent from the SWORD Dev
147 = 0223 (octal)
128 = 0200 (octal)
226 = 0340 (octal)
So it's off by 2 in the top order byte. Not sure why, but it seems you're
expecting decimal but the tool is obviously giving out octal.
--Greg
On Mon, Mar 6, 2017 at 3:02 PM, David Haslam wrote:
> Thanks Karl,
>
>
Thanks Karl,
All the "hyphenated" names in the KJV OT use the *en dash* character U+2013
which has 3 UTF-8 bytes E2 80 93.
In decimal, these are 226 128 147 so we might well wonder how your tool gave
342 200 223 ?
Best regards,
David
--
View this message in context:
On 03/03/2017 09:16 PM, Troy A. Griffitts wrote:
> SWORD supports compiling with a variety of regex engines
I have an interesting result. My previous build of sword used
--with-cxx11regex, and that failed to find Abednego in any circumstance.
Reconfiguring without that option and rebuilding, I
Corrigendum: "everything outside ASCII"
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/diatheke-search-type-regex-and-the-dot-tp4656879p4656901.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
sword-devel
Thanks Troy,
The precise /flavour/ of *regex* supported by diatheke search really needs
to be properly documented.
Expecting the *dot* to be a byte when we're handling Unicode is just not on
at all.
I'm struggling more because I'm on Windows, where the UTF-16 verse UTF-8
disparity affects
SWORD supports compiling with a variety of regex engines-- typically GNU
regex on most linux system. We include 'internal regex' copy of this,
as well. We also will compile against the C++ standard regex engine
including the language spec. Each handles unicode characters different.
. is
Created http://tracker.crosswire.org/browse/MODTOOLS-101
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/diatheke-search-type-regex-and-the-dot-tp4656879p4656890.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
So what flavour of regex does diatheke actually use under Linux?
Why is it that the *dot metacharacter* is not recognized?
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/diatheke-search-type-regex-and-the-dot-tp4656879p4656889.html
Sent from the SWORD Dev
On 03/02/2017 02:14 PM, Greg Hellings wrote:
> I also get no results.
On the other hand...
$ mod2imp KJV | grep -B1 -i abed.nego | fgrep '$$'
$$$Daniel 1:7
$$$Daniel 2:49
$$$Daniel 3:12
$$$Daniel 3:13
$$$Daniel 3:14
$$$Daniel 3:16
$$$Daniel 3:19
$$$Daniel 3:20
$$$Daniel 3:22
$$$Daniel 3:23
Typo was only in the message, sorry!
The actual test in Windows shell with the -k there didn't give any matches.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/diatheke-search-type-regex-and-the-dot-tp4656879p4656884.html
Sent from the SWORD Dev mailing list
$ diatheke -b KJV -s regex -k Abed.nego
Verses containing "Abed.nego"-- none (KJV)
Once I correct the command to include the -k parameter, I also get no
results.
--Greg
On Thu, Mar 2, 2017 at 12:58 PM, David Haslam wrote:
> I was under the impression that the
I suspect this may be a further symptom of what Greg suggested as the
explanation in my other thread.
i.e. That SWORD expects to search in UTF-8 encoded text, whereas Windows
uses UTF-16 internally.
Still can't quite make out why the dot isn't treated how regular expressions
use it.
David
--
I was under the impression that the metacharacter *dot* in a regex means "any
single character".
It would seem that for diatheke with *-s regex* this is not the case at all.
Example:
diatheke -b KJV -s regex Abed.nego
In Windows command shell, that command line does not find the 15 instances
Thanks Peter.
If after it gets fixed, one of the programmers can recompile it for Win32,
that would enable me to test it.
Best regards,
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/diatheke-search-type-default-tp4656833p4656844.html
Sent from the SWORD Dev
There are two ways of looking at this - a programme bug or a documentation bug.
> Gesendet: Dienstag, 28. Februar 2017 um 07:17 Uhr
> Von: "David Haslam"
> So there's no sense in which "phrase" as a search type is (default), is
> there?
There is probably only in the
The command:
diatheke -b ESV -s -k Merodach
might be thought of as what to use were "phrase" truly a default that could
be omitted.
However, this produces the error message:
Unknown search_type: -k
Try diatheke --help
So there's no sense in which "phrase" as a search type is (default), is
In that case, the string "(default) " should be pruned from its syntax help,
n'est-ce pas?
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/diatheke-search-type-default-tp4656833p4656836.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
The omission of the "-s" attribute does not lead to search behavior but
instead to Diatheke trying to open the book/chapter/verse specified by the
-k argument. So, it seems safe to say, there is no real concept of a
"default" search type.
It would make sense to say there is a default if there was
"Something not quite right in the state of Denmark ..."
diatheke -b ESV -k Merodach
gives no matches!
diatheke -b ESV -s lucene Merodach
gives 5 matches.
The actual instances are as follows: (omitting the references)
2 matches to "Evil-merodach"
2 matches to "Merodach-baladan"
1 match to
As for Ubuntu, running the code from the subversion trunk, it was the usual
mixup between the system-installed 'diatheke' at /usr/bin, and the binary
installed from the trunk at /usr/local/bin. After cleaning it up, the
diatheke from trunk behaves fine on Ubuntu. Sorry for the false alarm. :)
Unfortunately Ubuntu is at least.2 iterations of releases behind the curve.
Always.
Sent from my phone. Apologies for brevity and typos.On 24 Oct 2016 1:02 pm,
Teus Benschop wrote:
>
> Something weird is happening to diatheke on Ubuntu 16.04 64 bits:
>
> $ diatheke -b
That leading colon suggests something is trying to parse a null and
reverting to the last text after a fail. Instead of looking for {John
3:16}, it appears to be searching for {John 3:16,} How the code detects
the end of the verse range (or whether the next range is null) is where I
would start.
Following up on the previous mail about diatheke, the SVN code, when
compiled on Ubuntu 16.04 64 bits, running diatheke still gives the double
output.
___
sword-devel mailing list: sword-devel@crosswire.org
Something weird is happening to diatheke on Ubuntu 16.04 64 bits:
$ diatheke -b NETfree -k Jn 3:16
John 3:16: For this is the way God loved the world: He gave his one and
only Son, so that everyone who believes in him will not perish but have
eternal life.
: For this is the way God loved the
On Sun, 2016-02-07 at 20:16 -0800, Brian Jolly wrote:
> Thank you Peter. I'll give it a shot with your .cls file.
Just delete the reference to sword.sty in diatheke's output.
Peter
>
> On Sat, Feb 6, 2016 at 12:59 AM, Peter von Kaehne
> wrote:
> > On Fri, 2016-02-05 at 17:14
Thank you Peter. I'll give it a shot with your .cls file.
On Sat, Feb 6, 2016 at 12:59 AM, Peter von Kaehne wrote:
> On Fri, 2016-02-05 at 17:14 -0800, Brian Jolly wrote:
> >
> > Peter, thanks for your work on the filters. Are any of the LaTeX
> > support files shareable even
On Fri, 2016-02-05 at 17:14 -0800, Brian Jolly wrote:
>
> Peter, thanks for your work on the filters. Are any of the LaTeX
> support files shareable even outside of SVN?
>
This is what i have started. My main aim so far was to make the
crossreferences work in a PDF. I have not put much effort
Latex is used to produce scholarly editions with heavy apparatus, so i would
dispute what you say re inability to achieve a good output
Sent from my phone. Apologies for brevity and typos.On 6 Feb 2016 5:39 am,
Michael H wrote:
>
> Brian,
>
> You'll run into issues trying to
$495 for a desktop licence
Sent from my phone. Apologies for brevity and typos.On 5 Feb 2016 8:17 am,
David Haslam wrote:
>
> If you have the OSIS XML source file, why not use Prince XML to create the
> PDF for printing a Bible?
>
> Or do you only have the module and
If you have the OSIS XML source file, why not use Prince XML to create the
PDF for printing a Bible?
Or do you only have the module and not the source text?
http://www.princexml.com/
Although the first page mentions HTML, the samples page gives an example for
OSIS.
Prince Whatnot is not open source. It is also a fairly rubbish output.
Sent from my phone. Apologies for brevity and typos.On 5 Feb 2016 8:17 am,
David Haslam wrote:
>
> If you have the OSIS XML source file, why not use Prince XML to create the
> PDF for printing a
Thanks Guys,
I am really trying to stick with the free and open set of tools
(sword/diatheke/LaTeX).
Peter, thanks for your work on the filters. Are any of the LaTeX support
files shareable even outside of SVN?
Feel free to contact me off list if that's more appropriate.
On Fri, Feb 5, 2016
Brian,
You'll run into issues trying to build a Bible in Latex. Simon Cozens did,
and decided to fix it. Resulting in Sile. (That's a stretch and mangled
history, but theres a bit of truth in there.)
Sile is free and open source and is designed to produce printed books, with
Bibles in mind.
Hi Everyone,
I am working on a personal project to print and bind my own bible. I'm
trying to use diatheke with LaTeX output to generate a set of pdf's to
print from.
I checked out what I believe to be the latest in SVN:
Repository Root: http://crosswire.org/svn/sword
Repository UUID:
Hi,
I am glad i am not the only potential user. The reason this is only in svn and
not in release is the absence of that aspect. I am slowly working in it and
have privately more, but it is not complete.
Peter
Sent from my phone. Apologies for brevity and typos.On 4 Feb 2016 11:10 pm,
Brian
When outputting plain text, diatheke currently makes a half-hearted attempt
to use a tiny bit of MarkDown format for anything that was wrapped in the
OSIS hi element, whether italics or bold type etc, which gets wrapped
between two asterisks.
See also https://en.wikipedia.org/wiki/Markdown
IMHO,
One of those rare occasions, eh, Peter ? :)
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Diatheke-and-MarkDown-format-tp4655468p4655474.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
sword-devel
I think you are right.
Sent from my phone. Apologies for brevity and typos.On 20 Dec 2015 11:20 am,
David Haslam wrote:
>
> When outputting plain text, diatheke currently makes a half-hearted attempt
> to use a tiny bit of MarkDown format for anything that was wrapped
When I updated to Mac OS 10.11.1, diatheke quit working for me. When I use
`cd $SWORD_PATH` it will still take me to the correct directory. While in
the correct directory, I can use diatheke but not any where else. My
SWORD_PATH is set to /Users/UserName/Library/Application Support/Sword.
I am
On 01/23/2014 05:11 AM, Peter von Kaehne wrote:
This a tentative question mostly re the doquery method of our diatheke.
I think it would be really useful if we could have this method somehow
be more part of our offerings, including e.g. in the bindings etc.
Reason: We are currently very much
I had been musing during an idle moment about designing a GUI for Diatheke
using the VBA that comes with MS Office.
A very low priority back-burner item in my tasks list.
David
--
View this message in context:
This a tentative question mostly re the doquery method of our diatheke.
I think it would be really useful if we could have this method somehow
be more part of our offerings, including e.g. in the bindings etc.
Reason: We are currently very much geared towards interactive continuous
Bible
Thank you for your help!
But I did some tests...
This is the Output for diatheke without arguments:
/C:\Users\Familie\Desktop\SWORD\TEST\installmgrdiatheke
Diatheke command-line SWORD frontend Version 4.5
Copyright 1999-2009 by the CrossWire Bible Society
http://www.crosswire.org/sword/diatheke/
There should be no mods.conf. you should see a modules/ data folder created by
installmgr in the same folder along side your mods.d/ configuration folder. Did
installmgr create this folder for the data files? Did installmgr place any
module configuration files inside your mods.d/ folder?
pHep
Okay it works
I've been misleaded by my bad english...
I thought I've to create the mods.conf - So the installmgr installed the
*.conf files in the mods.conf folder (but why?) and diatheke didn't find it!
I've deleted these folder and restarted the installmgr init and the other
stuff - and
Hi,
I've got a problem with diatheke!
I've successfully compiled installmgr, libsword, ... and diatheke! (I'm
working on Windows 8.1 And VS2012)
I've installed the KJV module with the installmgr. Now I'm trying to lookup
a verse with diatheke but it doesn't show anything...
That's my cmd
Paul,
The first thing to test is if diatheke is actually finding your install. To
do this, ask diatheke to give you a module list:
diatheke -b system -k modulelist
If that lists KJV, then the problem is with diatheke or its filter. If that
doesn't list any entries, then it's not finding your
I suspect Greg is correct that Diatheke isn't finding your Sword module
path. But you might also simply try running 'diatheke' (no arguments).
If it prints the help text, you've at least got a working binary. If it
fails to print anything at all, there's a problem with the binary, the
Sword
Hi,
Actually, I had another reason to suggest adding these to Diatheke.
Specifically, I'd like to have get to a full LaTeX exporter at some point,
i.e. supporting the options (Word of Christ in Red, etc.). I don't really
see how that could be done without using the API.
Any idea?
God bless
On Sun, Mar 31, 2013 at 3:35 AM, Chris Little chris...@crosswire.orgwrote:
On 3/30/2013 12:54 PM, Greg Hellings wrote:
There was a patch just the other day to add a few small command-line
options to diatheke.
I'd really prefer that this patch not be added, especially not without
On Sun, 2013-03-31 at 09:21 -0500, Greg Hellings wrote:
I don't know the limits of LaTeX and whether a custom exporter
program is feasible, but is there any particular reason to not want
changes to Diatheke?
Only starting now to get to grips with latex, but FWIW, Latex allows
embedding of
Hello,
For some time, I've been struggling with Diatheke's output, piping it
into sed and other string editors when I need to grab simple verses.
To make things easier, I'm attaching a patch to this email which adds
3 flags to Diatheke:
* --no-refs suppresses reference printing in output
Chris,
Re: http://www.crosswire.org/tracker/browse/MODTOOLS-29
If I (or anyone else) wished to use diatheke to export a substantial part or
all of a module (one with red-letters for Words of Jesus) to a standalone
RTF file, I don't see any valid reason to not include the single line to
define
On 09/15/2012 12:19 PM, David Haslam wrote:
Greg,
While you're into the code for Diatheke, please see if you can fix the RTF
font color table issue as well.
I would contend that we should move in the opposite direction and
eliminate all of the extra wrapper-type-stuff that diatheke generates
On Sun, Sep 16, 2012 at 7:27 PM, Chris Little chris...@crosswire.org wrote:
On 09/15/2012 12:19 PM, David Haslam wrote:
Greg,
While you're into the code for Diatheke, please see if you can fix the RTF
font color table issue as well.
I would contend that we should move in the opposite
The following patch adds XHTML output support to Diatheke and also
updates the help text to reflect the support for HTMLHREF and XHTML.
--Greg
diatheke-xhtml-support.patch
Description: Binary data
___
sword-devel mailing list:
Greg,
While you're into the code for Diatheke, please see if you can fix the RTF
font color table issue as well.
I can't access JIRA right now. See
http://www.crosswire.org/bugs/JiraLockedError
David
--
View this message in context:
The following command gives a valid RTF file that can be opened with Wordpad.
diatheke -b KJV -o x -f RTF -k Mt 1-28
Export\KJV\KJV.Mt.diatheke.rtfItalics are properly used for the words added
by the translators, as expected.
Yet the Words of Christ are not formatted as red text. Why not?
RTF
This thread should initially have been entitled Diatheke - output_format RTF
and Red Words of Christ?
Using output_format HTML does not produce Red Words of Christ either!
diatheke -b KJV -o x -f HTML -k Mt 1-28 Export\KJV\KJV.Mt.diatheke.html
btw. The help for diatheke is somewhat confusing in
Further light on the RTF issue...
I examined the RTF file with Notepad++, and observed that verses with Words
of Christ do contain a suitable markup.Matthew 5:3: {\f1 \cf6 {Blessed} {\i1
are} {the poor} {in spirit}: {for} {theirs} {is} {the kingdom} {of
heaven}.\cf0 {}}\par
The bug is that cf6
Moreover, there are no italics used for supplied words in the diatheke HTML
output_format.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Diatheke-output-encoding-RTF-and-Red-Words-of-Christ-tp3025205p3025885.html
Sent from the SWORD Dev mailing list archive at
1 - 100 of 185 matches
Mail list logo