Re: [sword-devel] Method Name Normalization
Am 25.01.2013 20:47, schrieb Greg Hellings: On Sun, Jan 20, 2013 at 3:02 PM, Greg Hellings greg.helli...@gmail.comwrote: Additionally, BibleTime's sword-svn-compat branch has been updated to build cleanly against this, (excluding the unused variables message I mentioned in the other thread). --Greg On the heels of the second set of deprecations, Xiphos now works again and you can fetch r or beyond from the repository to solve compatibility with the new naming scheme. Updating Xiphos is more important than updating BibleTime as the changes caused Xiphos' build to fail compiling and later to produce blank module text, both of which r and the latest SWORD fix. BT's fixes only eliminate warnings. --Greg ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page Thanks, you can close bug #497 also. Best Regards ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
[sword-devel] Hello, I need help with the Sword Utilities
I have been trying to run the sword utilities for about a week now. i have tried to find information on the exact line to use in the command prompt i am running windows xp sp3, osis2mod wont run from the folder it is in, i have to run it from cmd. When i run it from the folder it appears breifly and dissappears, so i have to drag the exe to the command prompt, i dont know if this is normal. if someone could paste an example of what string to use to make a module that would be great. Here is some of what i have tried through the prompt C:\Documents and Settings\All Users\Application Data\Swordecho off -- addld: Lexicon and Dictionary creation tool diatheke: multi-purpose command-line frontend imp2gbs: General Book creation tool imp2ld: Lexicon and Dictionary creation tool imp2vs: VPL Bible/Commentary importer installmgr: command-line module installer mkfastmod: command-line module indexer mod2imp: export module to imp format mod2osis: export module to osis format mod2zmod: compress a sword module osis2mod: create Bible/Commentary/General Book from OSIS tei2mod: create Lexicon/Dictionary from TEI uconv: convert files from one character encoding to another vpl2mod: import from VPL file vs2osisreftxt: return an OSIS reference for any reference xml2gbs: import from OSIS/ThML to a General Book for more information, tutorials, and explanations of file formats, see http://cr osswire.org/wiki --- Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. You are running osis2mod: $Rev: 2571 $ OSIS Bible/commentary module creation tool for The SWORD Project usage: utils\osis2mod output/path osisDoc [OPTIONS] output/path an existing folder that the module will be written osisDoc path to the validated OSIS document, or '-' to read from standard input -a augment module if exists (default is to create new) -z use ZIP compression (default no compression) -Z use LZSS compression (default no compression) -b 2|3|4 compression block size (default 4): 2 - verse; 3 - chapter; 4 - book -c cipher_keyencipher module using supplied key (default no enciphering) -N do not convert UTF-8 or normalize UTF-8 to NFC (default is to convert to UTF-8, if needed, and then normalize to NFC) Note: UTF-8 texts should be normalized to NFC. -s 2|4 bytes used to store entry size (default is 2). Note: useful for commentaries with very large entries in uncompressed modules (2 bytes to store size equal 65535 characters) -v v11n specify a versification scheme to use (default is KJV) Note: The following are valid values for v11n: Catholic Catholic2 German KJV KJVA Leningrad Luther MT NRSV NRSVA Synodal SynodalP Vulg -d flags turn on debugging (default is 0) Note: This flag may change in the future. Flags: The following are valid values: 0 - no debugging 1 - writes to module, very verbose 2 - verse start and end 4 - quotes, esp. Words of Christ 8 - titles 16 - inter-verse material 32 - BSP to BCV transformations 64 - v11n exceptions 128 - parsing of osisID and osisRef 256 - internal stack 512 - miscellaneous This argument can be used more than once. (Or the flags may be added together.) See http://www.crosswire.org/wiki/osis2mod for more details. here is some of the errors i am getting C:\Documents and Settings\Christopher TwoC:\Documents and
[sword-devel] OSIS
Can anyone tell me whether I can post OSIS-related questions here - and if not, whether there is somewhere else which handles them? Thanks, Jamie Jamieson ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] OSIS
Hi Jamie, If after reading all the OSIS related pages http://crosswire.org/wiki/Category:OSIS in our developers' wiki, you still have OSIS related questions, then - yes - by all means ask them here. This list is very active (unlike some of our other lists). There'll be many messages that are probably over your head that relate to compiling SWORD etc. Yet the CrossWire community tries to be helpful ( patient) to respond to all questions posted here. Blessings! David -- View this message in context: http://sword-dev.350566.n4.nabble.com/OSIS-tp4651824p4651825.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
[sword-devel] OSIS questions
I'm trying to convert a number of USFM documents to OSIS using my own software, and then to Sword using osis2mod. However, I'm relatively new to OSIS, and am struggling somewhat. Don't know if anyone can comment on any of the following issues? * osisText osisIDWork={NAME} ...: Normalized name of the Bible version (Usually 3 letters for language, 3 for translation). Does this have any significance to anything (ie does it matter that I get it right)? If so, I assume the first three characters are the ISO language code? What should you do where you also have a variant code? Does the translation portion of the name need to follow any particular convention? * According to http://crosswire.org/wiki/OSIS_Bibles, the minimal document header consists of just work osisWork={Name}/. This does not seem at first sight to square with Appendix L of the OSIS user manual (dealing with conformance requirements), which appears to require a scope definition, to which the document must conform. Is the minimal header shown above in fact adequate? And what do you lose by not giving a fuller header (for example, by not giving scope)? * An example text I have picked up includes the refSystem tag in a number of places. I'd prefer to avoid using this if I can, since it is not always immediately apparent what versification schemes have been used in the texts I have available to me. Is it a problem if the tag is not supplied? (If it must be supplied, then I presume it has to come from some predefined list of valid schemes? Where do you get the details of these schemes?) * http://crosswire.org/wiki/OSIS_Bibles includes div type=bookGroup. I presume this enables you to group together, say OT or NT books? What are the implications of having it (or of not having it)? * OSIS appears to support a tableOfContents marker, which I believe corresponds to USFM toc/toc1/toc2/toc3. How is it used? Suppose I have the text for Matthew, and somewhere else I want a table of contents. Does the marker go at the start of Matthew itself, to mark the place to which the table of contents should point? Or does it go into the table of contents, to indicate that you want it to include a reference to Matthew? And either way what does the full tableOfContents tag look like? (I tried the former of the two options - putting div type='tableofContents'Matthew/div into Matthew itself, but the only effect seemed to be that the word Matthew was output as part of the text.) * In at least one of the vernaculars I'm dealing with, the translator has included in the USFM at the start of each book both a h and an mt tag (in that order, in case it's of any interest). According to the OSIS user manual, both of these should give rise to title tags (of type short and main respectively, although I gather Sword ignores this). Unsurprisingly, I end up with two titles appearing at the start of the book. Clearly with a certain amount of effort I can address this by filtering the data while I'm generating the OSIS, but does OSIS itself (or Sword) have any convention as to what to do in these circumstances? * Some USFM tags appear to need to be converted into right-justified paragraphs. Does OSIS support right justification? * Occasionally we work with right-to-left languages in which the verse number needs to come at the end of the verse rather than the start, and in some cases also the verse number needs to be decorated in some manner. Does OSIS cater for this at all? Thanks in advance, Jamie Jamieson attachment: winmail.dat___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Hello, I need help with the Sword Utilities
As a fellow Windows user (Win 7 x64) I found it useful to make (in my Sword directory) a symbolic link http://en.wikipedia.org/wiki/Symbolic_link to where the Sword utilities are stored. Symbolic links may be unfamiliar to many Windows users, but old-hat to Linux folk. They are created using the Windows command called *mklink* You can use Windows Help to find out more. Then for any of the individual tasks (especially those that need repeating), I create a custom Windows CMD file to launch the utility, such that I can just double-click it to start that from within Windows Explorer. You can use any decent text editor (even Notepad will do) to make a CMD file. btw, I'd recommend *Notepad++* as a replacement for Notepad. Here's an example: I've been working on the Norsk module yesterday, so my CMD file called *MakeNorsk.cmd* contains: ..\utils2\imp2vs ..\Import\Norsk.raw.imp.edited.txt -z -o ..\modules\texts\ztext\norsk 1..\log\imp2vs.log 2..\log\error.log You see that I also capture the stdout and stderr streams to a pair of log files in a separate subfolder. It's also useful to append a pause command within the CMD file, so that you can watch what happens before the CMD window closes, and then close it manually. Also, to avoid clutter, all my CMD files are in a sub-directory I created under Sword (called Make). Likewise, source text files being used to make a module, these are in a folder I created (called Import). Once you've mastered these techniques, you'll wonder why you ever thought it difficult. Finally, for all utility commands relating to modules, the module name is Case Sensitive. It must be exactly as in the first line of the conf file, less the square brackets. This requirement appertains to all commands that do something with an existing module. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Hello-I-need-help-with-the-Sword-Utilities-tp4651823p4651826.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Hello, I need help with the Sword Utilities
PS. I forgot to mention that I generally make use of relative paths http://en.wikipedia.org/wiki/Path_%28computing%29 in referring to input and output files. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Hello-I-need-help-with-the-Sword-Utilities-tp4651823p4651828.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Patches to fix compiler warnings
Jaak, Just getting to these sets of patches. sword-comparison-not-assignment-fix.diff.bz2 Applied. Thanks for finding this bug. On 12/21/2012 12:32 AM, Jaak Ristioja wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello! Please apply these patches (bzip2-ed to workaround sword-devel 90 KB message size limit and attached) to fix about 3000 compiler warnings with GCC and Clang. The patches should apply to https://crosswire.org/svn/sword/trunk@2751 Blessings, Jaak PS: Here are the sha1sums: 7ba3a0b954b8b545d407eb0f46821e4ebdb1c3bf sword-Wempty-body-fix.diff.bz2 e47776b086c1d8f686a09114bd162358db18a062 sword-Wmissing-field-initializers-fix.diff.bz2 fc68490a4aac0b8954fa02f0832fdccf95573fd7 sword-Wtype-limits-fix.diff.bz2 eb2749fe94fcb8018be61c8925a12b2503460ac0 sword-Wunused-parameter-fix.diff.bz2 004fbd6ac5bf6107cf37beb4b436f34400ec2774 sword-comparison-not-assignment-fix.diff.bz2 df8231f927ae1c34160b57d7b2a90e58a686448f sword-illegal-source-file-encoding.diff.bz2 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) iQgcBAEBAgAGBQJQ05/3AAoJEEqsYmEt1rCON2E//ArXCLZm2Mv0ERKpAoGTvDi+ JHOOaTf7JW42DkloDiPqMbOSYyLBAbuyJQUp0cFg9pQWTe2TpGu5Fr5n46hsKYSc FgFTM1fhVqimfeNt74425mxWKG9/DxuXskTI9MXLg6TwN/rVxr8kJpwqrYLnPy9C 118zyvKCO0YBGAhGx1lkQXmpZbDAvzFszWD9lTHdknDJ/OhMZ12kjmAcpkzraPJ0 H/KhWGxyGm2mlJ7HuBpKyhVz7oUO7kYBrj9CCBpQwnB17rOCglLqbRLodZIPnd30 ufL8YjAlwpDvhcIW7CiwaBq23xUjOefReKoAJ6TOw4CQ6AqWvTADj0T/509QoUKg ZfHBA0vQU0zxI4i67jmt86fI/2X3LuXNBdB9E+0wCLPxgVLuQImw3BufGdupkYe+ Y3WddcRhtkWh/1yNhxBcB6hZoDZWTWs2iz4pIJYeO40pN6UZKC1MXLoAWqbufMfS eN0sWDcC7cadq0hkgNLWkWe1fxPfdSwrWgOjICas44elCASBtnjOub9zWhh/HdOB 668wCQtgBUo0ICdpdNAnsvIQiOhf60sgd99zvwczPeGgJKjvURzK/W4nS9UbwpUE JESZfeQnLdOWJ2u+THozFLnjoOCw9c5NMZrFhGodVVb/u0bPQzyJ0Z1pT5/BZnOX 1WC5PuQvGTBx/zepoLAuDLmh+SDqAhVm96fNTvhefY6oq78oQb+aG3N/mq64scXS S+42S/BJWjDlz21AbfQJprkLOL3DbPBHOxG4/KdF8TFo73iNeTsPfLveumDbn6MS DUwZETBZdOiGCLuBgmj9GIp/lMmQktdPJHv1JkdoLj+kL23oKR0MdvX5i+4rWOk/ hs9D8JNCb+0bST71PUIW1HkF3elEYfZO/ciZ0U4mQVFFX/4VzXGJJqf5dh9HhCBZ 3N1srhXGw4GEEblUv0oT2q+czeSDCjs/zLFQ7ONzbT9qoLOhEbI3cJ89A8hRbSC7 3u9OXKjyvJPWQvALxCu90QeS0ygqJPK/JZcHyc7I5J7m61SwhuPU7axKsRTGpHuT X15w3SwaOz+P+r+WzRPj2OIcihBb4jnf+esk6ows7mNGa3jbm+UsGy/t2i5nb/p+ DDoSnbxfTTpg9S9KOOrp6mTIZ9voCLXQAkEnx0E/1wu5xTgWI7aSSrXf5eO2JawP riWTK9EaQ/yUf0SXhVsFKB948ATdoX45ag9OJfR1ShU27qaEE8BBgfGzXjYgcd/o YujHVNhHfUD1xS8BF4D3G3LoO+l9m4d/iNtnXpc4JPd6f6ZuRGhKiM8V3N7olYYC 3Xf4hX9V4S2txrPX0XXG5Zq4x90Jx8VxbjN1UKMjTKRgfhghh4c0EzVvpq47sF7z qtULiOLlbEPUlH78nTu8eZ4Vy1DFhG2BEOSzWZatvO4UxiioewnQtp987ZG7Cpzy I2RRqrL4vv4FQ2UvOCEqVwYuZTSckcG18Bfy9FjqzH6WW/idBBUzWDrOgcEnke34 0A+hQtNo8+WMKD9zBdGEGY8ymNk/lj7F2JAvEhvvdXYemsDBiVfrezCj7EA7ybZp c8Oisk+EZgo4FMV49ytnjWR1rlsS7wCtLJb1GLjWOggIesrNq8rg9P7j8/u3U/GZ HDj/UsxInZcZv91u60r8oEl90vdP3hXJxdowKXjRBODFBmfQkJTFYoPd1JIOqyvT 1eGoYZ/o6ClGbEwcg8XEMOo2MvoF889b/yOOjP6kPt/tQUviwug2McU/KmNThqvU Arw/+8c/XpW/69SOHIBzgSS1ipcjOafn4k5g8bgkRknx97FaBBQNG9AqYl0iHlMS LwT9n6gPPBp3lF9LSWlzPvh0+vMQKfH4cwuIQMGwzhd156OkfYmfskoBCDv3VDhh mhhH502LOleMfoHajzo2IXc2IFToVxZq8rwhWwipXmEoOIH9DpbaaRwgbSjXQr72 xerD7lzChmTqriH3TmhLXIe5IGpLhPJZOw4AMyuTC3IVvSvMyE4SX/9UHOvxHB3v sI9OfimIn2NCfsbxLI+0SI8cw7BlSHE63OJjp7yG7oVqbLL7T8VqK5uTgAHWuy16 HebEXEs5yJtiSh1s2BQX5qxIOs9IFORBtgVlaTFozaVDMk+HMhHSN+pxb49vel0P ME7AOf1zIxqs1zFeZuqCRRzT8z3UoWcbu5maluSDyyI08i+1nzKDvRMW+77UrAWD 6sQD+JrHDQoUK8fu3OtUbUaOSyLW5bJ5+MeHEnsPrgvxC+B2lZYw9Bz5QCUSs6xu FhC7N1OlfM8b+e0EE0IAD2nwTvl0IcJFgbFMEm6KIy2dA6ChoPkTSbi3l0Nm2y7r iX57mdzKrgcRfUXkFWTrfDx8951qQpw16HNjwCa0zgNbrvKbEFqPzvEPzkNlWw0S E992keRPJNzpEXe9ZWZUE+qr92CsyqwAvPZ1z1jUT7swIKqrl7/O33CxiK2Iifoc BRV15T5V8LzWiO0MgOb85UsXZjwSxHMw8theHRAKvqKF0ti8ospgCirEU9ZTv7VF pSqFVOUBCgWkCtcGE8GaLg7eEleTx5inliILgD6kC+80CV8j1f3L6P2+zLMDxQeo W/cqdkbk8oL6yoOdRGMXuozPu3g7MQZUDYQplLxGcxYk3fDb2DKgiJw57Rlo+5ji O7I7wqWI88nEuku0wUIe11ydDSGtYGoOvRC0C4T/Z6vsvd/oNcQAb4tjrjqtKIlY OdqdFXYt+xF3RepeinW5 =jSQt -END PGP SIGNATURE- ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] SWORD utilities for Windows
This reply is merely to alert new members to the location of Greg's most recent build of the Sword utilities. Christopher Brown may find this especially useful. After the current round of patches to SWORD ends up with a proper release of the engine, if the utils need to be recompiled, I trust Greg will again take the initiative. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/SWORD-utilities-for-Windows-tp4651209p4651830.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] SWORD utilities for Windows
Ooops! Just in case you don't have the past threads in your email client, this was Greg's message. If you want the latest build of the SWORD utilities for Windows - version 2741 - they're available from http://dl.thehellings.com/mingw32/r2741.zip These include the Xiphos patch to properly handle path names that contain non-ASCII characters. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/SWORD-utilities-for-Windows-tp4651209p4651831.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] OSIS questions
Others should chime in too. This just a partial answer. Basic overview: OSIS should be written to the OSIS specification. We recommend a document centric representation where Book, Chapter, Section, Paragraph, Line Group and Lines are dominant and verse elements are milestoned. This is transformed by osis2mod into Book, Chapter, Verse representation. Front-ends then use a SWORD renderer to transform module content into presentational output. This is driven by values in a module's conf. So questions regarding OSIS fall into: How should it be done in OSIS. How does osis2mod handle it. And how do SWORD renderers handle such and so content. On Jan 26, 2013, at 10:13 AM, a...@critos.co.uk wrote: I'm trying to convert a number of USFM documents to OSIS using my own software, and then to Sword using osis2mod. However, I'm relatively new to OSIS, and am struggling somewhat. Don't know if anyone can comment on any of the following issues? Peter and Chris maintain a converter for USFM to OSIS, written in Perl. You might find that helpful. Off hand I don't know where that is. You can get more information by searching this list or from them. Also, Kahunapule Michael Johnson on this list has converters that he uses. He has many, many texts in USFM. * osisText osisIDWork={NAME} ...: Normalized name of the Bible version (Usually 3 letters for language, 3 for translation). Does this have any significance to anything (ie does it matter that I get it right)? If so, I assume the first three characters are the ISO language code? What should you do where you also have a variant code? Does the translation portion of the name need to follow any particular convention? The documentation that we've provided relates to an OSIS document used as a source for a SWORD module. Most of our answers will also be SWORD centric. To SWORD, the value does not matter. Osis2mod strips out everything until the first meaningful div element. At some time in the future, osis2mod will examine the header info to provide a best guess for key conf elements. * According to http://crosswire.org/wiki/OSIS_Bibles, the minimal document header consists of just work osisWork={Name}/. This does not seem at first sight to square with Appendix L of the OSIS user manual (dealing with conformance requirements), which appears to require a scope definition, to which the document must conform. Is the minimal header shown above in fact adequate? And what do you lose by not giving a fuller header (for example, by not giving scope)? In a SWORD context, you lose nothing. At least until we improve osis2mod to suggest a conf. But it is a great place to document information that will be helpful to you or others later. * An example text I have picked up includes the refSystem tag in a number of places. I'd prefer to avoid using this if I can, since it is not always immediately apparent what versification schemes have been used in the texts I have available to me. Is it a problem if the tag is not supplied? (If it must be supplied, then I presume it has to come from some predefined list of valid schemes? Where do you get the details of these schemes?) Reference systems are rather bothersome. Your goal is to determine the best fit of those that SWORD provides. IIRC, Greg has put together a script that'll help figure out which reference system (which osis2mod refers to as a versification system) is most encompassing. Osis2mod is good in that it retains all verse material. But when you pick the wrong ref system, osis2mod will warn you that the verse is not in the versification and that it is being appended to the prior verse. The details are rather cryptic (held in arrays in SWORD header files.) Basically most of us just try each one to see which has the least warnings. And from there try to understand those warnings. Chris has defined these. So he might be able to clarify. * http://crosswire.org/wiki/OSIS_Bibles includes div type=bookGroup. I presume this enables you to group together, say OT or NT books? What are the implications of having it (or of not having it)? It is not needed for a SWORD module. All that osis2mod requires are the div type=book Having it has no impact. * OSIS appears to support a tableOfContents marker, which I believe corresponds to USFM toc/toc1/toc2/toc3. How is it used? Suppose I have the text for Matthew, and somewhere else I want a table of contents. Does the marker go at the start of Matthew itself, to mark the place to which the table of contents should point? Or does it go into the table of contents, to indicate that you want it to include a reference to Matthew? And either way what does the full tableOfContents tag look like? (I tried the former of the two options - putting div type='tableofContents'Matthew/div into Matthew itself, but the only effect seemed to be that the word Matthew was output as part of the text.) I
Re: [sword-devel] OSIS questions
DM wrote, Peter and Chris maintain a converter for USFM to OSIS, written in Perl. You might find that helpful. Off hand I don't know where that is. You can get more information by searching this list or from them. Also, Kahunapule Michael Johnson on this list has converters that he uses. He has many, many texts in USFM. - To which it may be useful to add that Chris has developed (but not yet released) a more comprehensive Python script to convert USFM to OSIS. Download from http://www.crosswire.org/svn/sword-tools/trunk/modules/python/ Any useful test results or issues with his new script should be reported via our tracker. http://www.crosswire.org/tracker/browse/MODTOOLS David PS. The developer of xulsword https://code.google.com/p/xulsword/ has also developed his own script to convert USFM to OSIS. -- View this message in context: http://sword-dev.350566.n4.nabble.com/OSIS-questions-tp4651827p4651833.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] OSIS questions
Yes, Kahunapule Michael Johnson has built Haiola. Recently he's made a big effort to get USFM/USFX texts into OSIS format. You can find Haiola here: http://haiola.org/ Chris On 26 January 2013 17:13, David Haslam dfh...@googlemail.com wrote: DM wrote, Peter and Chris maintain a converter for USFM to OSIS, written in Perl. You might find that helpful. Off hand I don't know where that is. You can get more information by searching this list or from them. Also, Kahunapule Michael Johnson on this list has converters that he uses. He has many, many texts in USFM. - To which it may be useful to add that Chris has developed (but not yet released) a more comprehensive Python script to convert USFM to OSIS. Download from http://www.crosswire.org/svn/sword-tools/trunk/modules/python/ Any useful test results or issues with his new script should be reported via our tracker. http://www.crosswire.org/tracker/browse/MODTOOLS David PS. The developer of xulsword https://code.google.com/p/xulsword/ has also developed his own script to convert USFM to OSIS. -- View this message in context: http://sword-dev.350566.n4.nabble.com/OSIS-questions-tp4651827p4651833.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
[sword-devel] Swahili localisation
Hi I'd like to find out if anybody has some Swahili Bible Names/abbreviations. I can't find these in either JSword or Sword libraries. Perhaps this has never been done. Chris ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Swahili localisation
I have the book names for the kiSwahili NT: Book: Matayo Book: Marko Book: Luka Book: Yohana Book: Matendo Ya Mitume Book: Warumi Book: 1 Wakorintho Book: 2 Wakorintho Book: Wagalatia Book: Waefeso Book: Wafilipi Book: Wakolosai Book: 1 Wathesalonike Book: 2 Wathesalonike Book: 1 Timotheo Book: 2 Timotheo Book: Tito Book: Filemoni Book: Waebrania Book: Yakobo Book: 1 Petro Book: 2 Petro Book: 1 Yohana Book: 2 Yohana Book: 3 Yohana Book: Yuda Book: Ufunua was Yohana Notes: Revelation (without the of John) is Ufunuo. Psalms is Zaburi If you require OT book names, I can put you in contact with someone in WBT who visits Tanzania. If you require the verbose book names for the NT, I could readily transcribe them from my printed edition of the 2001 Union Version. NB. Many online editions of the Swahili NT still omit Philippians. David Haslam -- View this message in context: http://sword-dev.350566.n4.nabble.com/Swahili-localisation-tp4651835p4651836.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Swahili localisation
The full 66 book names are displayed as hyperlinks here: http://www.biblica.com/bibles/swahili/ David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Swahili-localisation-tp4651835p4651837.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Swahili localisation
See also https://sw.wikipedia.org/wiki/Agano_Jipya https://sw.wikipedia.org/wiki/Agano_la_Kale David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Swahili-localisation-tp4651835p4651838.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Swahili localisation
Hi David Thanks for these. I'd done a few searches on Google and wikipedia myself. The issue is with finding the abbreviations. So thanks for the links above. It gives us the Swahili NT abbreviations. Chris On 26 January 2013 19:33, David Haslam dfh...@googlemail.com wrote: See also https://sw.wikipedia.org/wiki/Agano_Jipya https://sw.wikipedia.org/wiki/Agano_la_Kale David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Swahili-localisation-tp4651835p4651838.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] OSIS questions
Title: signature On 01/26/2013 06:05 AM, DM Smith wrote: On Jan 26, 2013, at 10:13 AM, a...@critos.co.uk wrote: I'm trying to convert a number of USFM documents to OSIS using my own software, and then to Sword using osis2mod. However, I'm relatively new to OSIS, and am struggling somewhat. Don't know if anyone can comment on any of the following issues? Peter and Chris maintain a converter for USFM to OSIS, written in Perl. You might find that helpful. Off hand I don't know where that is. You can get more information by searching this list or from them. Also, Kahunapule Michael Johnson on this list has converters that he uses. He has many, many texts in USFM. Please see http://haiola.org if you are interested in open source C# software that converts USFM to OSIS. It might give you a head start... -- Aloha, Michael Johnson mljohnson.org PO BOX 5278 KAILUA KONA HI 96745-5278 USA Phone: +1 808-333-6921 Skype: kahunapule ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Swahili localisation
The key to success was some lateral thinking, and remembering that Wikipedia has projects in 285 languages. With a bit of ingenuity, one can probably use the same method to find the book names and abbreviations for a high proportion of these languages. The point I made about the book of Philippians being missing also applies to our Swahili SWORD module! http://www.crosswire.org/tracker/browse/MOD-86 David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Swahili-localisation-tp4651835p4651841.html Sent from the SWORD Dev mailing list archive at Nabble.com. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page