David Haslam wrote:
Has anyone checked what the
http://en.wikipedia.org/wiki/Cambridge_Paragraph_Bible Cambridge Paragraph
Bible (2005) does?
There is now a paperback edition (2006) of this modern textual recension by
David Norton.
-- David
As the name would suggest (and I believe Ryan is
Ben Morgan wrote:
On 07/06/2009, *Chris Little* chris...@crosswire.org
mailto:chris...@crosswire.org wrote:
The *htmlhref filters are the GnomeSword filters. They may now be
used by other front ends, and the GnomeSword/Xiphos team may have
abandoned their maintenance
Dmitrijs Ledkovs wrote:
2009/6/10 Jonathan Marsden jmars...@fastmail.fm:
At the level of utilities that are used in scripts, and whose command
line parameters are therefore in some sense an API for those who write
scripts using them, the very recent (post 1.6.0) change to osis2mod that
adds
The *htmlhref filters are the GnomeSword filters. They may now be used
by other front ends, and the GnomeSword/Xiphos team may have abandoned
their maintenance, but they were originally written by Terry and do some
non-standard stuff (as opposed to the *html filters, which should just
output
Firstly, DM, let me express my appreciation for your taking on the task
of improving osis2mod further. It's a daunting task and I'm glad not to
be tackling it myself right now. :)
There are a couple of sections of your Wiki addition from today that
concern me. Hopefully they'll be easy to
Ted Janiszewski wrote:
Could someone well-versed in the OSIS spell out for me the difference
between head and the various types of title elements? It sort of
looks as though the community changed direction on the best practices
for titling books and chapters halfway through writing the
Latest SVN (r2420) of the utilities, compiled for Win32, is posted to
FTP:
http://crosswire.org/ftpmirror/pub/sword/utils/win32/sword-utilities-1.6.0-r2420.zip
This includes a few minor bits of cleanup since 1.6.0, some post-ICU 4.2
patches to ICU, and most notably all of DM's recent changes
Spaces are indeed gone from 1.5. I've got an updated version with this
and a couple of other corrections that I hope to upload tomorrow.
--Chris
Teus Benschop wrote:
I tried to install the new WLC module from the Beta repository. It was
installed in Xiphos. The 1.4 version has normal spaces
) Hebrew database
also included in the WLC module?
Teus.
On Mon, 2009-05-25 at 00:11 -0700, Chris Little wrote:
Spaces are indeed gone from 1.5. I've got an updated version with this
and a couple of other corrections that I hope to upload tomorrow.
--Chris
Teus Benschop wrote:
I tried to install
LXXM is an experimental module (hence its listing in the experimental
section of that wiki page). It employs features (notably VerseTreeKey)
not yet completely implemented in Sword, much less any front end.
There's no expectation that it should work under any front end, in its
posted state.
Mike Hart wrote:
ANY module in the production repository should work.
We're not talking about that.
The beta repository should be for things that are supposed to work. Issues
found with modules on the beta repository are supposed to be reported.
The beta repository is for stuff that is
The Win32 utilities bundle for 1.6.0 is posted at
http://crosswire.org/ftpmirror/pub/sword/utils/win32/sword-utilities-1.6.0.zip
Since we're now compiling utilities in MSVC, they are much smaller and
hopefully a bit faster. Due to their much reduced size, I've eliminated
the individual
Once you've got 1.6.0 in your hands and working, take a look at the new
WLC module, based on WLC 4.10.
The big new feature *should* be the use of native versification: Malachi
will have 3 chapters, Nehemiah is the last book of the Bible, the
Chronicles come between Malachi Psalms, and the NT
Troy A. Griffitts wrote:
I would like to add new officially supported methods, like adding:
o Installation of modules from another existing SWORD library
installation via HTTP ( e.g.,
http://crosswire.org/ftpmirror/pub/sword/raw )
A skeleton class for this method was already added in
And another thing...
This module is built with the most recent osis2mod (1.6.0), so look upon
it as a test of that as well.
--Chris
Chris Little wrote:
Once you've got 1.6.0 in your hands and working, take a look at the new
WLC module, based on WLC 4.10.
The big new feature *should
Karl Kleinpaste wrote:
Daniel Owens dhow...@pmbx.net writes:
I think MorphGNT is the module you're thinking of. Is there a reason
MorphGNT is still in beta?
MorphGNT is certainly not in beta. It was withdrawn due to copyright.
For further information, google openscriptures and morphgnt.
Martin Zibricky wrote:
Hi all,
I'm trying to convert Czech Bible 21 (B21) to sword format.
When using tool 'vpl2mod' (sword 1.5.11) I'm getting a lot of warnings
like:
Not a valid KJV ref: Genesis 32:33
appending to ref: Genesis 32:32
Warning, overwriting verse: Genesis 32:32
Not a
I've noticed a couple of locales now in SVN that have problems from the
perspective of Sword's verse parser. Sword's verse parser looks for the
first non-initial digit in a verse reference and interprets this as the
beginning of a chapter number. So 1Kings or 2Baruch are fine, since the
digits
Daniel,
It depends on the Bible. In the case of the NRSV, Psalm 151 is a
separate book within the intertestamental group of books. In other
traditions, it's simply the 151st chapter of Psalms. Traditions that
include Psalms 152-155 can likewise present 151-155 as a separate book
or
In general, I'm planning for the addition of versification systems to
progress slowly and conservatively. So I've recommended to Troy that we
release 1.6.0 with the current set (KJV(A), NRSV(A) supersets,
Leningrad, MT).
The main reason for this is that a v11n definition must remain stable
Peter von Kaehne wrote:
Chris Little wrote:
Does that all sound reasonable?
In principle, yes and particularly wrt the conservative approach you
suggest. It would be easy to go overboard with enthusiasm and then
create a mess which will be impossible to clear up.
But wrt the protestant
Jonathan Marsden wrote:
DM Smith wrote:
No it is not a translator's error. It is correct.
If not, what versification schemes do have that verse, but are
otherwise compatible with KJV versification?
NRSV
AFAICT, this differs from the KJV in having 3 John 1:15 and Revelation
12:18.
Did you rebuild your makefiles using automake (or autogen.sh)?
Barry Drake wrote:
Hi Troy .
Since your commit (New Revision: 2328) earlier today, my previously
successful mingw build now fails to link 'buildtest.exe' with the error:
undefined reference to
Though included in the OSIS spec, x-E- codes are no longer necessary and
therefore deprecated. With the introduction of ISO 639-3, all of the
Ethnologue codes should have an equivalent ISO code.
Current content has been transitioned to use ISO codes. Older versions
that people may still have
It's my understanding that, in order to sign apps for use on an
iPhone/iPod Touch, you have to enroll in the $99/yr iPhone SDK developer
program. (Not just ADC.)
IMO, it would be nice to have a jailbreak/Cydia version of the app.
These obviously reach a much smaller audience, but the whole
Jonathan Marsden wrote:
Matthew Talbert wrote:
I subscribe to sword-svn as an attempt to educate myself on the
library, and, of course, to keep track of current changes. It would be
a real help to me if the commit messages were longer and more
informative. As I am very new to a lot of the
FWIW, lookup (the cmdline example program called lookup) works fine on
LeningradV11N:
$ ./lookup.exe LeningradV11N Haggai 1:1
==Raw=Entry===
Haggai 1:1:
Hag 1.1
==Render=Entry
Hag 1.1
==
Entry Attributes:
I would be interested to hear whether
Matthew Talbert wrote:
The problem that I've had with that, is that it appears that the bug
tracker is not up-to-date and goes long periods with no activity. I
believe Peter mentioned this recently as well. A couple of examples:
I would say the tracker is fairly up to date (minus new bugs
Matthew Talbert wrote:
Xiphos missing strongs and morphology was my mistake. The rest still
are issues (except I see that the 1p issue is fixed, thanks Chris).
The mapping of 1P to 1 Chronicles rather than 1 Peter was a feature, not
a bug (although an undesired feature, obviously). It comes
Ted Janiszewski wrote:
I'm working on marking up the Ignatian Epistles in OSIS 2.1.1. If any
of you have a minute, could you glance through one of these documents
and let me know how they look? Especially the headers.
I'm sorry it took so long to get a reply. I would guess the message got
Manfred Bergmann wrote:
Am 07.04.2009 um 03:28 schrieb Chris Little:
they have trouble finding the Windows build of the binaries,
This sounds more like an advertising/publicity/documentation issue
than a technical one? Or it could be a packaging issue -- how are
such users getting
Let's ignore EULAs and DMCA violations for a moment (given that we're
discussing interoperability, and the DMCA specifically permits reverse
engineering in such circumstances). And let's just consider the quick
and simple method of reverse engineering e-Sword's format without ever
visiting
.
Is this intentional, and if so, what does it signify? Or am I just
doing something wrong in the download process?!
Thanks for pointing this out. Both were the result of errors (now fixed).
From memory (and Chris Little can probably confirm) this may be
because a user has tried to download this module
Jonathan Marsden wrote:
Greg Hellings wrote:
I was just chatting with Matthew Talbert about the process of making
module import a much easier task than it is now. ...
Interesting. To me (I am probably a very atypical module creator, but I
have played with the mod2* and *2mod tools as part
Jonathan Marsden wrote:
As to why the current documentation isn't better, or why there aren't
more modules in source format to look at, it's essentially CrossWire
policy to keep it so that average users can't create modules easily
In which case, any form of Making Import Easier, whether
DM Smith wrote:
WRT tei2mod, I wrote it. Chris enhanced it. It is a rather braindead
program, looking for start and end of entries. One thing that it does,
it recommends conf entries based on the module it creates. I plan to
change osis2mod to do this later.
Could I recommend we go one
Matthew Talbert wrote:
isa 1 goes to 1 Samuel
isaiah 1 goes to Rev 1:1
I don't know of any other parsing errors in particular, but these two
make me worried that perhaps there are.
I just committed a corrected builtin_abbrevs[]. The problem resulted
from an error on my part in the script
Jonathan Morgan wrote:
On Sat, Mar 28, 2009 at 3:34 PM, Jonathan Marsden jmars...@fastmail.fm wrote:
I think I've found an interesting bug... or maybe more than one?
This is a module problem, so I have CC'ed sword-devel.
There's no mention of which version of ISBE was tested here, but I'll
ISBE is now updated, BTW (in beta).
Jonathan Marsden wrote:
Chris Little wrote:
There's no mention of which version of ISBE was tested here, but I'll
address this as if it were the latest edition that is being discussed
since the problem does exist there. (But it's my suspicion
DM Smith wrote:
David (Mailing List Addy) wrote:
So now that we've had a discussion about how to indent poetry, is
there a reliable way to pragmatically detect poetry? In the ESV
instead of wrapping the lines in l/l tags it's in an l / tag. Is
this the standard way of encoding them?
David,
Is this in any way formally different from a pericope or section? I
would simply use div type=section. If you need to carry any
additional information (e.g. the pe and samekh marks) you have the
subtype and n attributes on div.
I don't believe we do anything special with pe samekh in our
Karl Kleinpaste wrote:
1. Interesting that it bypassed the beta repo entirely.
This module was done on Saturday. No one tests anything in the Beta
repo, so I tested it in a few frontends on Sunday until it appeared to
me that everything was satisfactory.
2. It is misnamed. I have been in
Karl Kleinpaste wrote:
4. It fails to use pre-verse headers properly (e.g. Psalms, Lamentations).
Thanks for catching this. I'd made an error in a script that failed to
place headings prior to the verse marker in cases other than basic
section headings.
5. It fails to respect poetry
Karl Kleinpaste wrote:
Chris Little chris...@crosswire.org writes:
Kinda ironic. What happened to release early, release often?
Kinda ironic. What happened to make our content as high quality as I
can and deserves better than a careless attitude in light of the fact
that your conversion has
DM Smith wrote:
The second example with only a single word after the br/ suggests that
they are an artifiact.
If not, and without looking at the source, I'd suggest that they be put
back in either as l n=2.../l (where n is one greater than the line
it breaks) or as lb/.
The full text of Ps
DM Smith wrote:
Manfred Bergmann wrote:
Am 18.03.2009 um 12:15 schrieb DM Smith:
When were were beta testing the German modules, many of them had the
same KJV versification problems. I'd like to see a versification for
that, if you don't already have one in the wings. If so, which is it?
DM Smith wrote:
Chris,
In the example, you are giving KJV as the work. Are we still of the
mindset that a reference without the work or with a work of Bible refers
to verse?
In a TEI document, an osisRef value will almost certainly be a Bible
reference--just because it's a non-standard
Daniel Owens wrote:
I think the engine should support multiple keys in a single dictionary
module so something like entryFree n=ἀγαπάω|agapaō|G25 would be a
feasible entry. A user could look up the same word in both the MorphGNT
and TR modules without having to switch dictionaries, and
Daniel Owens wrote:
I want to know how to encode a link to a Bible verse in a TEI
dictionary. The wiki isn't very specific about how to go about this.
External references are like so:
xr type=xrefref target=work:keykey text/ref/xr
But the wiki says to use osisRef. Should it be identical in
Jonathan Morgan wrote:
On Wed, Mar 18, 2009 at 1:49 PM, Chris Little chris...@crosswire.org wrote:
Jonathan Morgan wrote:
It is not backward, it is a pure statement of facts, which you can
find quite clearly in the GPL v2 FAQ
http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html
Matthew Talbert wrote:
That doesn't mean it is the sole property of CrossWire, but it does mean that
copyright is jointly held between CrossWire and the front end author(s).
Disagree? Ask licens...@fsf.org.
Did you really mean to say copyright here? It is my understanding,
reinforced by
I've committed the first non-KJV versification system to SVN HEAD, as
well as an expanded builtin_abbrevs[] array with all of the books we are
likely to support in 1.5.12 (or quite probably more books than that).
The v11n system I've committed is Leningrad--the v11n of the Leningrad
Codex.
Jonathan Morgan wrote:
It is not backward, it is a pure statement of facts, which you can
find quite clearly in the GPL v2 FAQ
http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#GPLModuleLicense.
You need to look at the question immediately following the one you link.
I'll quote:
Q: If
Greg Hellings wrote:
If not 1.6 or 2.0... then could you possibly explain to me the rhyme
or reason given to the versioning system?
The minor version indicates whether we're in a development (odd number)
or stable (even number) branch. Under that system, 1.6 and 2.0 wouldn't
be right for
DM Smith wrote:
mmital wrote:
Hi,
I have been using Alkitab bible study lately. Fantastic piece of
software, truly amazing.
I also noticed that it is in public domain, while using sword engine
that is in GPL v2, and other components that may have their own
license
David Haslam wrote:
Can someone please clarify whether deuterocanonical support in the pipeline
is just extending scope of the canonical support to the 75 books found in
many Catholic Bibles, or if it also will address the pseudo-epigraphical
books as found in the Ethiopian (Amharic script)
Ben Morgan wrote:
On Tue, Mar 17, 2009 at 10:04 AM, mmital mital.m...@gmail.com
mailto:mital.m...@gmail.com wrote:
Hi,
As Chris pointed out, all front-ends *have* to use GPL v2. So the
public domain door is closed for me.
The license for a front end has to be GPL v2 compatible.
Ben Morgan wrote:
I thought it was the whole glob of the application that had to be able
to be licensed under the GPL? An individual component of my application
can be released under another license.
Ok, I think I know what you're getting at. Assuming that you want to use
a GPL library (e.g.
Barry Drake wrote:
Hi Chris ...
Chris Little wrote:
We plan to have this ready for our next release
This is the most fantastic exciting news. I've been carefully following
all Troy's and your recent svn commits. Thanks for all the great work.
It's all coming along very nicely, and I
Ben Morgan wrote:
On Mon, Mar 16, 2009 at 10:41 AM, Chris Little wrote:
Barry Drake wrote:
Hi Chris ...
Chris Little wrote:
We plan to have this ready for our next release
This is the most fantastic exciting news. I've been carefully
DM Smith wrote:
With regard to OSIS, if there are short-comings, we should try to
influence the standard. This is a proper venue for how we at CrossWire
would like to work with OSIS.
Regarding the l element and indents here is what the manual has to say:
*l: The l element is used to mark
Daniel Owens wrote:
One more thing to consider is poetic elements that are right-justified.
One of the translations I have worked on preparing for SWORD had Selah
right justified (VietNVB, in case you're interested). I just encoded it
like so:
l level=4Sê-la./l
It isn't right-justified,
Peter von Kaehne wrote:
The OS support I would simply do as previous - one row only, but maybe
with icons to make faster to read. Win95+ or WinXP+ is adequate instead
of a whole list of variants (unless newer Wins do not work).
This may seem a minor matter, but I'm not sure whether the
Karl Kleinpaste wrote:
Manfred Bergmann bergman...@web.de writes:
What is meant by Ancillary texts and Verse Lists?
Many modules, both Bibles and commentaries, have additional introductory
material at the fictitious n:0 and 0:0 references. Some apps are able
to display this information;
David Haslam wrote:
Are any Frontend developers thinking about providing UI support for
http://www.code2000.net/numbersutf.htm non-Latin numerals for chapter and
verse references?
This should all be handled via your chosen l10n library. ICU should be
able to localize numbers, as appropriate
DM Smith wrote:
Peter von Kaehne wrote:
Am trying to clean up a new module but stumble over the Ps 119 acrostic
titles.
In USFM they are encoded \qa [Letter]
I tried lg type=acrostic [Letter] /lg but it appears that xmllint
does not like it. I get a message inside lg with attribute there may
Matthew Talbert wrote:
Thanks for the reply. It is much as I suspicioned. I do have Visual
Studio, and I was able to easily compile ICU with that, however it did
not give me an icudt that I could see. Perhaps I'd better look again.
Of considerable concern to me is whether I will be able to
Karl Kleinpaste wrote:
Peter von Kaehne ref...@gmx.net writes:
What exactly is it, why is it useful to have in a Bible study
programme? And yes, is it something done by the engine? To what extent
and which languages. Does it require specially marked up modules or is
it simply there? Do we
Just a heads up to anyone using the latest SVN, since I noticed there
was a little confusion on IRC today:
I removed SCSU support from Sword earlier today. If you run into
problems compiling, you probably need to re-run autogen.sh.
--Chris
___
SonWon wrote:
Please give David and I your opinion.
We are discussing the module installer for SwordReader.
Should it be windows based only?
Leaves the MAC and Linux users out in the cold.
Don't PocketPCs still require Windows for ActiveSync purposes? Are
there any precedents for content
Any versification that is fundamentally different from what I used to
produce the existing FreCrampon module is an incorrect versification.
That is not to discount the possibility of minor errors in versification
in my own edition, but my module's versification is fundamentally
correct and any
Minor things:
CrossWire (big C, big W)
The SWORD Project (big T, big SWORD, always with the The)
David Trotz wrote:
Thanks to help from David Overcash, I am happy to announce that the
SwordReader site is up and running with updated content reflecing the
new beta release.
Kahunapule Michael Johnson wrote:
Troy A. Griffitts wrote:
... I need a new laptop and considering buying a Mac! :)
Good choice. My MacBook is the best notebook computer I have ever used.
You should definitely seriously consider a new MacBook or MacBook Pro.
You can run Parallels on it and
Peter von Kaehne wrote:
As a side issue of the other debate - how can I achieve NFC for a text I
am working on via commandline utilities?
All I can find in ICU documentation is about programming methods
available, but I have seen no command line utilities.
DM's suggestion of using the Perl
Daniel Owens wrote:
The other MAJOR problem is that the dictionary keys are always
capitalized, which makes it really awkward to use for Greek. Can I lobby
again for a change in that? How many Greek students are used to looking
up words in capitals? I was taught using lower case letters, and
Daniel Owens wrote:
Chris Little wrote:
For TEI P5 documents, you can set any number of key values within the
n attribute, separated by |. For example n=a|aa|123 would put the
entry in a but link the keys aa and 123 to the main entry. This
is implemented in tei2mod, however I believe
Ben Morgan wrote:
On Wed, Jan 21, 2009 at 12:41 AM, DM Smith dmsmith...@yahoo.com
mailto:dmsmith...@yahoo.com wrote:
ICU has the notion of a collation key, which can be used for such a
purpose. (I think we've gotten to the point where ICU is a
requirement for UTF-8 modules.) In
Peter von Kaehne wrote:
My understanding of a discussion with Troy was that we are not supposed
to do beta testing on the Wycliffe modules as they are kind a separate
category - supplied and maintained by the organisation - and we only
host them
We need to test them to the extent that we need
Peter von Kaehne wrote:
I just guess it is time again to start testing and tried to parcel up
the job into what needs to be done, what should be done and what can wait.
You have updated a whole bunch of modules in November following various
updates to osis2mod.
The trouble is that there are
Peter von Kaehne wrote:
Looking finally on a long neglected pile of files for an Persian
commentary I stumbled over a few things which bug me dt lack of knowledge
1) If material is not meant to refer to any particular verse, but only
to the whole chapter - content summaries etc does it go
Jeremy Erickson wrote:
I have never really compiled anything on Windows not using Visual Studio,
unless I was using Cygwin and didn't care if it linked the DLL.
You always have the option of using VS itself. We have projects for the
last couple releases of VS in the source distribution.
I'm mostly happy with everything that's been implemented suggested.
There are only a couple of things I might do differently (probably based
on my own behavior on the wiki combined with our universal hatred of
actually facing captchas):
DM Smith wrote:
5) Adding an external URL to a page.
Mike Hart wrote:
I'm working on several bibles to get them into Sword Format (ultimately into
public domain, or as close to PD as possible), and I've got a few unresolved
issues.
Can someone point me to the how-to that covers these topics?
Issue number 1 - Versification standards
One
Basically, alternate versification support is phase 1. Mapping between
versifications is phase 2.
Jonathan Morgan wrote:
I am also concerned about the choice of using Genbooks to represent
books, just based (as far as I can tell) on the fact that we already
have Genbook support. Is there any
So write it and submit a patch.
[Some basic requirements: Don't add library dependencies to Sword
itself, make the validator toggleable at runtime, and ensure that the
validation library is in C/C++ and can compile under Win32 and with GCC.]
--Chris
Jonathan Morgan wrote:
I feel that,
Greg Hellings wrote:
So how do we label them? verse osisRef=Dan.3.77
canonical=not-considered-by-Protestants-as-such? Because the
reason that they're in that version is because they're probably
considered canonical by someone.
Just to qualify what I said previously about the purpose of the
Wolfgang Schultz wrote:
Hello,
if the utf-8 OSIS file has a BOM ( Byte Order Mark some editors
insert one) Osis2Mod will fail to make a sword-modul, it were nice if
this would be fixed, because it will cause lot of problems in further
steps :(
The BOM in UTF-8 is generally a Windows-ism.
Jonathan Morgan wrote:
On Tue, Jan 6, 2009 at 3:40 PM, Chris Little chris...@crosswire.org wrote:
So write it and submit a patch.
[Some basic requirements: Don't add library dependencies to Sword itself,
make the validator toggleable at runtime, and ensure that the validation
library is in C
Wolfgang Schultz wrote:
In my oppinion the Ne� is too long in the beta state,
crosswire should speed up their processes, but that is only my non
authoritative belief
The latest NeUE from Manfred has only been available for about a month,
during much of which various parts of the website
The categorization system is primarily concerned with presentation
within a frontend. E.g. a GenBook with category Bible would be
treated/displayed as a Bible (not that we've implemented this in .confs
yet), an LD module with type DailyDevotional would display mm.dd keys
using localized date
Peter von Kaehne wrote:
With regard to browser inconsistencies I am trying to keep the two
stylesheets in sync, but if I missed something, please tell me.
I also do think there should be ways of making it work with a single
sheet, making IE fail gracefully rather than badly. Any suggestions
Peter von Kaehne wrote:
Greg Hellings wrote:
I don't know where you the claim that The SWORD Project site is dead
from - I can tell you exactly one time when I looked at the wiki: when
someone else made a FAQ entry about an iPhone front-end and asked
anyone who might try to tackle it to edit
jhphx wrote:
Chris wrote:
I guess logic would dictate that the Wiki is dead and we should move
entirely to static pages.
Both forms of pages have their place for the purposes of displaying
these informative pages. There are those for whom Wikis are the web.
Others find Wikis
Peter von Kaehne wrote:
I put up yesterday a news item on a new release of a minor frontend ,
bringing it in line with current modules.
Within a short while the item had vanished without trace.
...
If this was a deletion by someone else who did not care to tell me that
s/he did not agree with
Peter von Kaehne wrote:
Sorry, Chris, this is not the correct stand of affairs. The news item
was new and fresh from the press. i.e. from yesterday.
LCDbible has been undeveloped until recently, but was recompiled
yesterday to work with 1.5.11.
Lynn also wrote to me that he plans to port the
Peter von Kaehne wrote:
re 1 line vs 2 line menu bar.
I have been given some grief regarding my choice of a single menu bar.
I think I have an acceptable solution - the real problem is to have
narrow screens and shallow screens (wide screens or even worse netbooks)
equally well accommodated.
Yes, the Wiki will be down until DM has an opportunity to restore it,
early next year.
--Chris
Ray Ellerd wrote:
Is the WIKI down?
Thanx,
Ray
___
sword-devel mailing
Peter von Kaehne wrote:
Chris Little wrote:
re styling and coloring.
This remains a contentious issue clearly. I do not expect anyone to like
my design choices - though some seem to do so.
The color scheme and overall design are another thing that were not
broken, but got fixed.
Actually
Wolfgang Schultz wrote:
BTW the step VolxbibelWiki Zefania XML is already finished
here you find the Volxbibel 3.0 with header and footnotes
http://downloads.sourceforge.net/zefania-sharp/volxbibel_v3_rev1.zip?use_mirror=heanet
This looks quite faithful, actually. I still wouldn't use an
Peter von Kaehne wrote:
Peter von Kaehne wrote:
As I said, I have found a solution with a a inline list which works
better on all kinds of screen designs.
This is now implemented on www.crosswire.org. The design is a inline
unordered list with nbsp in all spaces between words which should
501 - 600 of 1869 matches
Mail list logo
