It seems that the copyright of the new testament part of Japanese sinkaiyaku
(新改訳) translation ( first edition published in 1965) is expired.
Note that the Old testament part published in 1970, or the revised edition
(1978) of sinkaiyaku are still under the copyright.
--
ad...@bible.salterrae.
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 la
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, they
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
fou
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 found
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 w
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
rea
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 ha
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 August.
>
> Given enough sam
Not here
Sent from my phone. Apologies for brevity and typos.On 3 Jan 2016 9:12 am,
Martin Denham wrote:
>
> It looks like the main web site, repo, etc are down.
>
> Martin
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.or
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.
http://en.bab.la/dictionary/turkish-english/a%C
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 characte
Sorry for top-posting, but this is FIO.
More about PEG here
http://en.wikipedia.org/wiki/Parsing_expression_grammar
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/PEG-parser-for-USFM-tp4655560p4655586.html
Sent from the SWORD Dev mailing list archive at Nabb
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 entry
> On Jan 2, 2016, at 7:21 PM, Kahunapule Michael Johnson
> wrote:
>
> Also, one word of caution: There is no proper way to do a one-to-one,
> lossless, round tripable correspondence between USFM to OSIS.
Thank you for your help, I'm finding your emails most helpful.
Because I'm doing this wi
15 matches
Mail list logo
