Troy A. Griffitts wrote:
Also, it's polytonic Greek, so you'll need to use a polytonic keyboard.
If you paste "βα�λλω", you should get the work you're looking for (it's
there).
can you show lemmas in one of the new greek modules, right click on one
and then choose dictionary lookup?
I
Eeli Kaikkonen wrote:
On Sat, 27 Oct 2007, Eeli Kaikkonen wrote:
Searching in LiddellScott does not work. The index can be created but
the results are completely broken. It may be an encoding problem (well,
now it bites you too...)
Another encoding issue: after opening some lexicon entries the
> Also, it's polytonic Greek, so you'll need to use a polytonic keyboard.
> If you paste "βάλλω", you should get the work you're looking for (it's
> there).
can you show lemmas in one of the new greek modules, right click on one
and then choose dictionary lookup?
>
> BibleCS's LD pane doesn'
Eeli Kaikkonen wrote:
> First, it's almost impossible to find a word entry. Try to find for
> example such basic word as "ballw". You cannot write it because it's
> greek. You cannot navigate inside the work, only scroll down one by one.
> And when you scroll to the place where ballw should be, i
On Sat, 27 Oct 2007, Eeli Kaikkonen wrote:
> Searching in LiddellScott does not work. The index can be created but
> the results are completely broken. It may be an encoding problem (well,
> now it bites you too...)
Another encoding issue: after opening some lexicon entries the Back
button breaks
On Tue, 23 Oct 2007, Chris Little wrote:
> The latest build of BibleCS is on the alpha site
> (BibleCS-1.5.10pre4.zip). The changes to BibleCS are cosmetic, but this
> also contains a new build of Install Manager. Install Manager includes a
> minor change to permit installing unsupported modules (
peter wrote:
> On a practical note, would it be useful to convert the remaining non
> UTF-8 modules into UTF-8? If so, I am happy to do the actual work over
> the next few weeks. I would probably need some advise, but could do the
> actual foot work. I am not at all suggesting this should be done,
On Fri, 26 Oct 2007, Eeli Kaikkonen wrote:
> If there are no objections I will eliminate the "Latin1" from there so
> that future readers will not be mislead. Latin1 is not the same as
> cp1252 or iso-8859-1 after all as Chris pointed out and as already had
> read in wikipedia, so it is not right t
On Thu, 25 Oct 2007, DM Smith wrote:
> > Actually I didn't think about API but documentation. All documentation
> > should speak explicitly about cp1252, never latin1.
>
> It is documented at http://www.crosswire.org/wiki/index.php/
> DevTools:Modules
>
> Take a look at the conf entry for Encoding.
Dear all,
I am not part of the core developer team and probably have little right
to speak up here, but could I ask you to consider that the anger
displayed by several in the debate above is probably quite misplaced?
Encoding is a technical subject, but it appears to me that several
contributors
10 matches
Mail list logo
