Re: [sword-devel] Turkish to English glossary problem

Hi DM, You mentioned MDB - that's certainly the MS Access file extension. For those who don't have Access installed, and if you only want to read/view/export data, this is a useful tool. http://www.alexnolan.net/software/mdb_viewer_plus.htm I've used it successfully many times. David --

Re: [sword-devel] Turkish to English glossary problem

On 01/06/2016 09:26 AM, David Haslam wrote: > You mentioned MDB - that's certainly the MS Access file extension. On Linux systems, "mdbtools" packages (main plus -devel, -lib, and -gui) are available. The viewer tool is gmdb2 in mdbtools-gui. Also, https://sourceforge.net/projects/mdbtools/.

Re: [sword-devel] Turkish to English glossary problem

I do speak minimal Turkish. David is right. Sent from my phone. Apologies for brevity and typos.On 5 Jan 2016 15:33, David Haslam wrote: > > For the word you cited as an example, the missing letter would be Ğ. > > The word is AĞUSTOS = Ağustos = the name of the month

Re: [sword-devel] Turkish to English glossary problem

Thanks David and Peter. This module ERtr_en has been around since 2002. No one has complained. Every one of the first 26 examples are wrong. (according to Google translate) Even the one for Christ! I’m of the opinion that the module should be taken down as being bad and not of value. I don’t

Re: [sword-devel] Turkish to English glossary problem

Hey DM, I am fluent in Turkish and can help out here. That being said I'm a little confused what you're into here. Can you point me at where to see the source files for this in context and where it comes out in an app? It looks from the bits you pasted like a file somewhere along the line got

Re: [sword-devel] Turkish to English glossary problem

Hi DM, On of my friends is the Secretary of the Translation Trust, the charity behind the modern Turkish Bible. Either PM me for contact details, or visit http://www.translation-trust.org/ My guess is that the module was badly formed from a non-Unicode text. Turkish has several accented

Re: [sword-devel] Turkish to English glossary problem

For the word you cited as an example, the missing letter would be Ğ. The word is AĞUSTOS = Ağustos = the name of the month August. Given enough samples, it may be feasible to reconstruct the mapping table without external help. This site may help.

[sword-devel] Turkish to English glossary problem

Does anyone know Turkish that can help figure out a problem I am having? Background: In ASCII the first 32 characters (00 to 1F) are control characters and most are not valid for XML, but are valid for UTF-8. In one of our modules, ERtr_en, I am seeing data such as: For the 26th entry, the

Re: [sword-devel] Turkish to English glossary problem

DM, Honestly I'm willing to put some effort into this if it will be beneficial to anybody using Turkish scriptures, but the Wayback Machine link you provided is not encouraging. Not only is the encoding garbage, but the data itself is rife with mistakes.Not a full minute of skimming it and I

Re: [sword-devel] Turkish to English glossary problem

Thanks Caleb, I’m working on JSword which is the Java version of the SWORD engine. As such I run all the modules I can get my hands on through a process that reads all of each module reporting what it cannot handle. It was that effort that made me look closer at the module. Either the problem

Re: [sword-devel] Turkish to English glossary problem

Disregard about the module, I found it in a different section of the module manager. So I have the ERtr_en module now, but as far as I can figure in Xephos it's useless. Turkish is an agglutinated language and almost no words in an actual text like the Bible appear in their root or stem form as

Re: [sword-devel] Turkish to English glossary problem

Caleb, I was just typing up instructions on how to get it via the Module Manager. I agree that the module is bad. I’ll take your word that it’s really bad, less than useless. I’m not sure how useful glossaries and dictionaries are in general to our users. Looking at the download statistics,

Re: [sword-devel] Turkish to English glossary problem

Meant to reply also on the rabbit hole question. The description of the Ergane software is that it somehow combines the Esperanto language data with the other language data to produce the result. I’m dubious as to whether that is useful in any language other than Esperanto, which is a made up

Re: [sword-devel] Turkish

Hi Caleb, It's still with Chris for checking before uploading. I guess he's somewhat busy, but I fully expect it will be available soon. David PS. Excellent news about And-Bible localization for Turkish. :) -- View this message in context:

Re: [sword-devel] Turkish

Hey David, Thanks for your efforts on this. Can I ask what the status is on the new module getting into the sword repo? I don't mean to be impatient I was just wondering since it was announced as a couple of days but I haven't seen it yet. Another guy and I have already finished the Turkish

Re: [sword-devel] Turkish

That makes good sense, even though there is [at least] one exception to the observation that no one tests them anyway. I wonder who that might be? David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Turkish-tp4113535p4127641.html Sent from the SWORD Dev mailing list

Re: [sword-devel] Turkish

Okay, sorry, you're right, but only you test modules. :) There are actually a few people who have made notes, depending on their personal interest in particular modules, and obviously I do some testing of everything before posting. But to encourage more widespread testing, it will be better to

Re: [sword-devel] Turkish

I fully agree - better visibility = more testing = better feedback. The wider community is really looking forward to the new Turkish Bible module which Peter submitted, after I was sent the source text by the publishers. btw. The Go Bible edition is already available for download. See

Re: [sword-devel] Turkish

By way of clarification of our policy regarding the beta repository: Nothing new will ever go into the beta repo because no one tests them anyway. New versions of texts currently in beta will be released to other repositories, as they become available. So we've essentially changed from a

Re: [sword-devel] Turkish

Is there a strong enough reason for still using CrossWire Beta for TurNTB? Why can't this replacement module go straight into CrossWire Main? Especially as it was made with established tools that we have high confidence in. The old module in Beta did have serious issues, which is why we are

[sword-devel] Turkish

Hi guys, We have now finally obtained a quality text for the Turkish Bible, Kutsal Kitap The publisher has kindly offered us their source text, which I made a module off. Chris has it right now for his last checks. It should then replace the the existing TurNTB module which is riddled with

Re: [sword-devel] Turkish module

I'd always thought that OK - yes - that is what it does. I suppose it might be a slight improvement if it put out a verse range - but it's never been an issue ass far as I am concerned. I disagree. The BibleCS and Bibletime version of presenting things could create serious problems when

Re: [sword-devel] Turkish module

This might be a bit naive on my part, but is there a mechanism in the Sword library that will tell the front-end that the presented text covers multiple verses? If I set a VerseKey to Genesis 1:2 is there a way to retrieve where that entry begins and ends? For example, if the OSIS entry spans from

Re: [sword-devel] Turkish module

Hi there . Greg Hellings wrote: This might be a bit naive on my part, but is there a mechanism in the Sword library that will tell the front-end that the presented text covers multiple verses? I'm fairly sure there isn't. I handled it by doing a strcmp() between the previous verse and

Re: [sword-devel] Turkish module

Hi there . [EMAIL PROTECTED] wrote: Or rather gnomesword will make verses appear twic, while Bibletime will not show that there are two verses linked... Not sure what the Windows programme does here. BibleCS does handle linked verses in the correct way. God bless, Barry -- From

Re: [sword-devel] Turkish module

Hi there .. Chris Little wrote: I think (based on a copy of the TEV that I encoded and imported from OSIS) that BibleCS functions like BibleTime. It doesn't print multiple instances of a verse, but it fails to make any note of the verse range covered. It just prints the verse number

Re: Re: [sword-devel] Turkish module

I'd always thought that OK - yes - that is what it does. I suppose it might be a slight improvement if it put out a verse range - but it's never been an issue ass far as I am concerned. I disagree. The BibleCS and Bibletime version of presenting things could create serious problems when

Re: [sword-devel] Turkish module

I have entered an issue into Jira against BibleCS. Here is the text I entered: When two or more verses are marked in OSIS with a single verse tag, such as verse osisID=gen.1.1 gen.1.2 n=1,2.../verse the rendering of the text by any client should indicate both 1 and 2. Of course part of the

Re: [sword-devel] Turkish module

According to ccim (http://www.ccim.org/bible/dcb.html) the module belongs to The Translation Trust 107 Stanstead Road London SE23 1HH United Kingdom. Tel: 44 181 699 0967 Fax: 44 181 291 6764 [EMAIL PROTECTED] http://www.translation-trust.org/html/home.html These contact details appear to be

Re: [sword-devel] Turkish module

These contact details are accurate: The Translation Trust PO Box 1017 Lessingham NORWICH NR12 0WA UNITED KINGDOM Tel. +44 (0)1692 584900 Email [EMAIL PROTECTED] National Patient Safety Agency - supporting

Re: [sword-devel] Turkish module

The verses are actually combined, so you'd need something like: verse osisID=Matt.1.1 Matt.1.2Ýbrahim oðlu, Davut oðlu Ýsa Mesih'in soyuyla ilgili kayýt þöyledir: Ýbrahim, Ýshak'ýn babasýydý. Ýshak, Yakub'un babasý; Yakup da Yahuda ve onun kardeþlerinin babasýydý./verse I

Re: [sword-devel] Turkish module

Or rather gnomesword will make verses appear twic, while Bibletime will not show that there are two verses linked... Not sure what the Windows programme does here. I suppose this is then something which needs to be dealt with at the application level. I have done this now for all missing

Re: [sword-devel] Turkish module

Yes, like I said, I have contacted them. The fact that other parties have permission to distribute the text, while showing good promise that they may extend the same permission to us, does not mean that we may distribute the text ourselves. --Chris [EMAIL PROTECTED] wrote: These contact

Re: [sword-devel] Turkish module

[EMAIL PROTECTED] wrote: Or rather gnomesword will make verses appear twic, while Bibletime will not show that there are two verses linked... Not sure what the Windows programme does here. I suppose this is then something which needs to be dealt with at the application level. This is

[sword-devel] Turkish module

The Turkish NT currently on crosswire has two significant problems 1) three characters are wrongly encoded - the capital I with dot appears as a capital Y with dot, the small I without dot appears as a small y with dot and the yumusak g a g with a circumflex appears as some runic kind of sign.

Re: [sword-devel] Turkish module

Addendum: The following link should give access to both files - the OSIS file and the new conf file http://www.doctors.net.uk/DocStore/DSView/Album.aspx?folderid=36645 Thanks National Patient Safety Agency - supporting

Re: [sword-devel] Turkish module

OK, so I don't know Turkish. I don't pretend to know Turkish. I hope someday to know it, but I do know a little about OSIS. The problem just seems to be that the text for the misplaced verses is placed within the following reference. As for correcting those mistakes, if you happen to know

Re: Re: [sword-devel] Turkish module

OK, so I don't know Turkish. I don't pretend to know Turkish. I hope someday to know it, but I do know a little about OSIS. The problem just seems to be that the text for the misplaced verses is placed within the following reference. As for correcting those mistakes, if you happen to know

Re: [sword-devel] Turkish module

The Turkish NT actually had some more significant problems than that, so I have removed it from the site. The primary problem was that it was copyrighted, so I have emailed the copyright holders to get permission for us to distribute it. The second problem was that it had the OLB as its