On Wed, Dec 2, 2009 at 10:27 PM, Nic Carter wrote:
> Firstly they rejected it cause they found a bug in the downloader. I think
> they assumed that was the normal behaviour, but it was something I've never
> encountered before. So I've asked for more information. :)
Good to know they actuall
Thanks for the emails :)
elaborating on my FYI, FYI #2:
Apple send you an email saying how/why it was rejected & I just triple checked
it for an NDA, but it doesn't seem to be under NDA, so . . .
Firstly they rejected it cause they found a bug in the downloader. I think
they assumed that wa
Bummer. Any reason given? Any direction for prayer?
In Him,
DM
On Dec 2, 2009, at 9:51 PM, Nic Carter wrote:
>
> Just an FYI...
>
> :(
>
> ___
> sword-devel mailing list: sword-devel@crosswire.org
> http://www.crosswire.org/mailman/listinfo/
David,
Notepad++ says that it is UTF-8 without BOM, just as it does for the
original Net Bible conf file that I have. Did you examine the attached
file? If so, can you recommend a text editor to use that can show me the
same results as what you have?
Thanks
John Duffy
> -Original Messa
> -Original Message-
> From: DM Smith [mailto:dmsm...@crosswire.org]
> Sent: 02 December 2009 13:13
> To: johndu...@cgcf.net; SWORD Developers' Collaboration Forum
> Subject: Re: [sword-devel] Font problem in conf file
>
>
>
> I don't know why it is not showing up. It should.
>
>
Hi everyone,
Just a brief note to report that we have received permission from IBEC to go
ahead with a SWORD module and Go Bible for the BEC 2000 translation.
Details have been sent to Troy.
The http://www.crosswire.org/wiki/Module_Requests#Latin_script_languages
wiki page has been updated.
Hi John,
UTF-8 encoding with or without BOM ?
Some programs fall over just because they expect UTF-8 without BOM, yet the
file contains a BOM.
David Haslam
johnduffy-2 wrote:
>
>
> So it appears that while my previous UTF-8 files were just that, and some
> converted using tools, there is no
On Dec 2, 2009, at 5:24 AM, wrote:
>
> I've played around with this for a fair while, and it seems to me that it is
> an encoding problem. I see that the NetBible has the same issue also in the
> About text in BibleCS but not in Xiphos.
>
> I've used some conversion programs to UTF-8, in cas
Thanks Eeli,
I've since opened the Net Bible UTF-8 conf file in Notepad++ and saved it as
a different filename for the Bible in Irish. Then, erased the text, and
wrote it all in from the keyboard as I did for an ANSI version similarly
beforehand. Now, this file works in Xiphos, is visible in Bi
We do have an agreement which would allow all frontend developers to run their
own show as described by DM Smith
We have not done much about it in tersm of updating old module configuration
pages.
Peter
Original-Nachricht
> Datum: Wed, 02 Dec 2009 23:11:39 +1100
> Von: Nic Ca
I agree with what Mark said.
I think that the end user should come first, and that us as developers should
come second. Sure, it makes it harder for us to keep an eye on all the
modules, but we also have very easy access to the mods.d folder (in svn or our
own install of SWORD). Or, as devel
On Wed, 2 Dec 2009 johndu...@cgcf.net wrote:
> It seems that the conf file text must be limited to the basic ASCII
> character set, and saved in ANSI format. Is this correct? Or, I could be
> making a silly mistake on the encoding (files attached for comparison).
>
> Help much appreciated.
I thi
On Wed, Dec 2, 2009 at 10:38 PM, Mark Trompell wrote:
> I wonder if it wouldn't make sense to always display the name of the
> bible/book in the language it is written in.
> You wouldn't read a chinese bible if you can't read it anyway.
>
We've been over this before both for module names and the
On Wed, Dec 2, 2009 at 3:23 AM, Nic Carter wrote:
>
> Hi all. :)
>
> Given I'm an English speaker & I can only speak and read English, this may
> seem like a strange proposition, but . . . :)
>
> As I'm going through the i18n process for PocketSword I'm eliminating
> everything that is in Engl
> Von: Chris Little
> Now that you've got it working, how did the Synodal versification work
> for your Bible?
There are four verses which are not contained. I am at work right now, but will
forward you later the list.
There are also a bunch of chapters where the Synodal is meant to have a v
15 matches
Mail list logo
