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.
Jeremy Erickson <[EMAIL PROTECTED]> writes:
> I was running 2.2.3 on Kubuntu Gutsy (7.10), which is the latest in the
> package manager. It's probably something that was fixed in a later version.
Dom has put 2.3.1 for Ubuntu at http://dominique.corbex.net/gnomesword/
___
On Thursday 25 October 2007 11:27:48 pm Karl Kleinpaste wrote:
> I haven't any idea, of course, what version you're running, or under
> what environment, but GnomeSword 2.3.1 under both Fedora7 (in both
> gtkhtml3 and mozembed builds) and Cygwin do not crash on such errors.
>
> In a gtkhtml3 build,
Jeremy Erickson <[EMAIL PROTECTED]> writes:
> I noticed that some of the keys in the AmTract lexicon module (such
> as "Abraham's Bosom") have apostrophes that don't work properly in the
> frontends GnomeSword actually
> crashes when attempting to access those entries.
I haven't any idea,
On Oct 25, 2007, at 6:45 PM, Eeli Kaikkonen wrote:
> On Thu, 25 Oct 2007, DM Smith wrote:
>> But it is too late to change Sword now. It is an issue of backward
>> compatibility. There is no way to teach older apps to understand an
>> Encoding=cp1252. It would only be of value going forward (i.e.
Eeli Kaikkonen wrote:
> I still continue a bit on this issue.
>
>>From http://en.wikipedia.org/wiki/ISO_8859-1:
>
> ISO 8859-1 is not the same as ISO-8859-1. According to article Latin1 is
> the former, not the latter. Windows-1252 is not either. "In
> Windows-1252, codes between 0x80 and 0x9F
Eeli Kaikkonen wrote:
> I protest against this very strongly. All I get with Sword library
> encoding system is problems after problems.
That's rather an overstatement--or else simply unappreciative of the
work we've gone to to simplify encoding matters. We formerly supported
miscellaneous natio
On Fri, 26 Oct 2007, Eeli Kaikkonen wrote:
> Actually I didn't think about API but documentation. All documentation
> should speak explicitly about cp1252, never latin1. The wiki pages would
> be a good start - from there I got the impression that I could use
> QString::to/fromLatin1(). Now I see I
On Thu, 25 Oct 2007, DM Smith wrote:
> But it is too late to change Sword now. It is an issue of backward
> compatibility. There is no way to teach older apps to understand an
> Encoding=cp1252. It would only be of value going forward (i.e.
> MinimumVersion=1.5.11).
Actually I didn't think about A
On Thu, 25 Oct 2007, DM Smith wrote:
> But Chris gave the solution: On Linux, every module that is not UTF-8
> should use the Sword filter to convert it to UTF-8.
I think BibleTime uses it:
CSwordBackend::CSwordBackend()
: sword::SWMgr(0, 0, false, new sword::EncodingFilterMgr(
sword::ENC_UTF8 ),
On Oct 25, 2007, at 5:19 PM, Eeli Kaikkonen wrote:
> On Fri, 26 Oct 2007, Eeli Kaikkonen wrote:
>> I protest against this very strongly. All I get with Sword library
>> encoding system is problems after problems. Why use "latin1" which is
>> not latin1? Why not use real latin1? Why use latin1 at
On Fri, 26 Oct 2007, Eeli Kaikkonen wrote:
> I protest against this very strongly. All I get with Sword library
> encoding system is problems after problems. Why use "latin1" which is
> not latin1? Why not use real latin1? Why use latin1 at all? It is easy
At least all references to "latin1" shoul
On Thu, 25 Oct 2007, DM Smith wrote:
> Jeremy,
>
> We use cp1252 (Microsoft's extension of iso8859-1, aka Latin 1) or utf8
> as the encoding for the modules. The <92> indicates that it is cp1252.
> When the Encoding= is missing from the conf, then the file should be
> understood Encoding=Latin1.
>
Jeremy,
We use cp1252 (Microsoft's extension of iso8859-1, aka Latin 1) or utf8
as the encoding for the modules. The <92> indicates that it is cp1252.
When the Encoding= is missing from the conf, then the file should be
understood Encoding=Latin1.
Try changing to a font that includes Microsoft
No, this is not a bug. When we say Latin-1, we in fact mean Windows code
page 1252. There should be a function somewhere within sword to convert
this to UTF-8.
Not having a value set means use the default value, which for encoding
is "Latin-1".
--Chris
Jeremy Erickson wrote:
> Hi,
> I
Hi,
I noticed that some of the keys in the AmTract lexicon module (such
as "Abraham's Bosom") have apostrophes that don't work properly in the
frontends. In BibleTime (or at least the development code), the apostrophes
show up as boxes, and the contents are not fetched. GnomeSword actu
17 matches
Mail list logo
