Has anyone ever used the -e switch of usfm2osis.pl to do character
encoding conversion on USFM docs as they're being converted to OSIS?
I'm doing the Python rewrite of usfm2osis and wondered whether I can
safely dump this functionality. It shouldn't be difficult to implement,
but it the usage
I do not think it Is necessary
Sent from my HTC
- Reply message -
From: "Chris Little"
To: "SWORD Developers' Collaboration Forum"
Subject: [sword-devel] USFM character encodings
Date: Thu, Jul 26, 2012 12:49 pm
Has anyone ever used the -e switch of usfm2osis.pl to do character encodi
Chris,
After doing a refresh, I still can't find a module called ChiUnL in the
av11n repo.
Please could you check that it's distinguishably accessible.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Classical-Chinese-Bible-tp4650616p4650624.html
Sent from the SW
Hi Chris,
I've never used the -e switch either.
All the Paratext/USFM files we've seen were already encoded UTF-8.
There are other software utilities that can perform the encoding conversions
for those rare instances where such might be needed.
David
--
View this message in context:
http:/
It's there. If your install manager sorts by language, note that it is
not the same as Chinese (zh). Xiphos, for example, does not recognize
the language code, and places the module in the Unknown language bucket.
--Chris
On 07/26/2012 05:36 AM, David Haslam wrote:
Chris,
After doing a refre
David, I suspected as much and don't deny the decision to support one
or more installation sites resides with the client developer. That
said, InstallMgr appears to be moving in that direction, which I think
is a wonderful feature. I suspect different client developers
influence each other featur
On Thu, Jul 26, 2012 at 6:49 AM, Chris Little wrote:
> Has anyone ever used the -e switch of usfm2osis.pl to do character encoding
> conversion on USFM docs as they're being converted to OSIS?
>
> I'm doing the Python rewrite of usfm2osis and wondered whether I can safely
> dump this functionality
Is there a way to create a link to a passage in swordweb and specify the
Bible module? I want it to go to the SBL GNT module.
Currently the link goes to:
http://www.crosswire.org/study/passagestudy.jsp?key=Luke.1.5. But that
goes to whatever default Bible (in my case, NASB appears, which is th
Thanks. Got that now!
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/Classical-Chinese-Bible-tp4650616p4650630.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
___
sword-devel mailing list: sword-devel@
It's worth knowing about this wiki page, even though there's no mention of
swordweb.
http://crosswire.org/wiki/Frontends:URI_Standard
It would be nice if this page were to be updated with the latest
information.
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/swo
Hi Daniel,
Yeah, swordweb takes a number of parameter from most any page:
mod is what you want, e.g.,
http://www.crosswire.org/study/passagestudy.jsp?key=Luke.1.5&mod=SBLGNT
A few other globals which might be interesting (with sample values:
setStyle=Parchment
lang=el
On 07/26/2012 06:43
Cool, thanks. That worked perfectly.
Daniel
On 07/26/2012 11:59 AM, Troy A. Griffitts wrote:
Hi Daniel,
Yeah, swordweb takes a number of parameter from most any page:
mod is what you want, e.g.,
http://www.crosswire.org/study/passagestudy.jsp?key=Luke.1.5&mod=SBLGNT
A few other globals whic
I am writing a stylesheet to display Abbott-Smith's Manual Greek Lexicon
of the New Testament from Github where I will post releases. I have no
idea how to get the namespace declaration right in the xsl file. I have
googled and tried several solutions, but so far nothing works.
The source docu
On Wed, Jul 25, 2012 at 8:24 PM, Andrew Thule wrote:
>>> On Wed, Jul 25, 2012 at 12:27 PM, Greg Hellings
>>> wrote:
>
>> It should. It does not. AFAIK it currently maintains no status
>> information on whether ABC came from site X, site Y, a local install
>> file, or was manually inserted into t
Oy, I've run into fun with namespaces before as well on XSL documents.
Going by the seat of my pants here, but I think my solution had to be
two step.
First, I would declare
xmlns:tei="http://www.crosswire.org/2008/TEIOSIS/namespace"; in the XSL
document.
Secondly, I would alter my matches statem
On 26/07/12 22:26, Daniel Owens wrote:
I am writing a stylesheet to display Abbott-Smith's Manual Greek Lexicon
of the New Testament from Github where I will post releases. I have no
idea how to get the namespace declaration right in the xsl file. I have
googled and tried several solutions, but s
Chris Little writes:
> Xiphos, for example, does not recognize the language code
Updated.
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at
Greg Hellings writes:
> there is a path underneath modules/ that corresponds with where kjv
> would have been downloaded to (modules/texts/ztext) but the kjv
> directory under that is gone.
...because it was mv'd to the normal location after retrieval.
> Thus, we just ensure that the module name
On Thu, Jul 26, 2012 at 5:53 PM, Karl Kleinpaste wrote:
> Greg Hellings writes:
>> there is a path underneath modules/ that corresponds with where kjv
>> would have been downloaded to (modules/texts/ztext) but the kjv
>> directory under that is gone.
>
> ...because it was mv'd to the normal locat
Greg Hellings writes:
> if I had electronic copies of the "Student's Bible" in KJV and my
> Defender's Study Bible also in KJV, both of them might want to just
> name their module the "KJV". The application should be able to discern
> between "Zondervan's KJV" and "ICR's KJV".
Even in such a case
Here's the root element of an OSIS document:
xsi:schemaLocation="http://www.bibletechnologies.net/2003/OSIS/namespace
http://www.bibletechnologies.net/osisCore.2.1.1.xsd";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns="http://www.bibletechnologies.net/2003/OSIS/namespace";>
And
On Thu, Jul 26, 2012 at 6:51 PM, Karl Kleinpaste wrote:
> Greg Hellings writes:
>> if I had electronic copies of the "Student's Bible" in KJV and my
>> Defender's Study Bible also in KJV, both of them might want to just
>> name their module the "KJV". The application should be able to discern
>>
Thank you all for your help. It came down to getting my xpath
expressions correctly prefixed, which took some digging. I will post the
results soon.
Daniel
On 07/26/2012 05:00 PM, David Troidl wrote:
Here's the root element of an OSIS document:
xsi:schemaLocation="http://www.bibletechnologies
Greg Hellings writes:
> Remember that module IDs, which are what I'm talking about, are
> extremely limited in which characters can be used. I believe A-Za-z0-9
> and maybe - and/or _. Regardless of the language, etc of the module.
> Theoretically that could easily lead to a collision between modu
24 matches
Mail list logo
