Help translate Logos 5 into another language!

Page 4 of 4 (72 items) < Previous 1 2 3 4
This post has 71 Replies | 10 Followers

Posts 762
Patrick S. | Forum Activity | Replied: Sat, Oct 19 2013 7:03 AM

Mark Barnes:

Could you add British English to your list? I'm a pedant, and every time I see a spelling 'mistake', I have an urge to correct it!

And not forgetting the one-and-only Australian English!

"I want to know all God's thoughts; the rest are just details." - Albert Einstein

Posts 195
LogosEmployee
Seth Copeland | Forum Activity | Replied: Tue, Oct 22 2013 9:56 PM

L.A.:

compiling german books is fine, but german bible references like Offbg = Rev (Offenbarung = Revelation) doesn't work. The "," as a chapter,verse separator does not work either. However I'm fine with my PBB. ... and the new (sometimes funny) German UI ... step by step Logos goes international again, as Libronx was some years ago. 

5.2 beta 2 which shipped today, should now parse German bible references and render them appropriately when in the German UI, and also should parse them for PBBs with the German language. The "," character will function as a chapter verse separator, instead of a multiple reference separator. The "." character can be used as a multiple verse separator.

Ephesians, chapter 2, verse 8 should be rendered as "Epheser 2,8" in German. Ephesians, chapter 2, verses 8 and 10, would be rendered as "Epheser 2,8.10". Ephesians, chapter 2 verses 6 through 10 would be rendered as "Epheser 2,6-10".

Feel free to post a new thread with any problems that might arise when compiling PBBs in German.

Regards,

Seth Copeland

Logos SW Development

Posts 536
L.A. | Forum Activity | Replied: Sun, Oct 27 2013 7:50 AM

Seth Copeland:

5.2 beta 2 which shipped today, should now parse German bible references and render them appropriately when in the German UI, and also should parse them for PBBs with the German language. The "," character will function as a chapter verse separator, instead of a multiple reference separator. The "." character can be used as a multiple verse separator.

Ephesians, chapter 2, verse 8 should be rendered as "Epheser 2,8" in German. Ephesians, chapter 2, verses 8 and 10, would be rendered as "Epheser 2,8.10". Ephesians, chapter 2 verses 6 through 10 would be rendered as "Epheser 2,6-10".

Feel free to post a new thread with any problems that might arise when compiling PBBs in German.

Seth, that's really great!! Yes Thank you (and all the developer team) veeeeery much for this improvement!!!! (bow) I'm not a beta-tester/user (prefer patiently waiting instead Coffee), but anyway, I'll post this Info on the faithlife German Logos User page. Be blessed!

Posts 536
L.A. | Forum Activity | Replied: Wed, Feb 12 2014 8:28 AM

Seth Copeland:
Ephesians, chapter 2, verse 8 should be rendered as "Epheser 2,8" in German. Ephesians, chapter 2, verses 8 and 10, would be rendered as "Epheser 2,8.10". Ephesians, chapter 2 verses 6 through 10 would be rendered as "Epheser 2,6-10".

YES! it really works... GREAT!! ...until compiling books with references to the Psalms... for example: the reference "Psalm 36,10" (in German Bibles) shows verse 11 in the compiled PB (with German localization). 

...is this due to the different bible-verse-maps? (maybe the bible verse map Logos generally refers to?) 

...could this problem be solved for the German localization? 

Posts 195
LogosEmployee
Seth Copeland | Forum Activity | Replied: Wed, Feb 12 2014 8:40 AM

L.A.:

YES! it really works... GREAT!! ...until compiling books with references to the Psalms... for example: the reference "Psalm 36,10" (in German Bibles) shows verse 11 in the compiled PB (with German localization). 

...is this due to the different bible-verse-maps? (maybe the bible verse map Logos generally refers to?) 

...could this problem be solved for the German localization? 

I'm unsure. I'll look into it and see what I can find.

-Seth

Posts 9967
Forum MVP
NB.Mick | Forum Activity | Replied: Wed, Feb 12 2014 10:16 AM

Seth Copeland:

L.A.:

YES! it really works... GREAT!! ...until compiling books with references to the Psalms... for example: the reference "Psalm 36,10" (in German Bibles) shows verse 11 in the compiled PB (with German localization). 

...is this due to the different bible-verse-maps? (maybe the bible verse map Logos generally refers to?) 

...could this problem be solved for the German localization? 

I'm unsure. I'll look into it and see what I can find.

-Seth

Not to preclude any findings from your side, but it is probably due to bible verse mapping in the Psalms. German bibles typically are one or two verses off.

@LA: have you tried giving the verse map (e.g. to Luther84) in the reference? This should work. 

 

Running Logos 8 latest beta version on Win 10

Posts 195
LogosEmployee
Seth Copeland | Forum Activity | Replied: Wed, Feb 12 2014 11:04 AM

NB.Mick:
@LA: have you tried giving the verse map (e.g. to Luther84) in the reference? This should work. 

You're right. It looks like we are defaulting to using an English verse map. It is a bug. I'll make a case for it.

Posts 536
L.A. | Forum Activity | Replied: Wed, Feb 12 2014 12:20 PM

NB.Mick:
@LA: have you tried giving the verse map (e.g. to Luther84) in the reference? This should work.

I did it with the BHS (res=LLS:1.0.200). 

Tried to "overtake" Travel your efforts with the German Herrnhut Watchwords (Losungen), incl. hebrew and greek texts (finished on last monday). On tuesday I realized the differences... (see the watchword for February 11, 2014 / 14. Februar 14). There are some 23 other errors relating the interpretation of Lukas 2,36.38 etc. (on February 20, 2014). If you have time, please revise the docx.

I attach the MSWord docx... It might be a help for Seth too. 5001.Logos PB BHS_NA27 Losungen Free 2014.docx

Source of the docx is an Excel file, provided on the www.losungen.de  download-site. I simply opened new rows and filled the cells with the tagging-info, before copying the data into a Word-docx and converting the table into text. Voilá! 

Posts 9967
Forum MVP
NB.Mick | Forum Activity | Replied: Sun, Aug 3 2014 4:41 PM

L.A.:

NB.Mick:
@LA: have you tried giving the verse map (e.g. to Luther84) in the reference? This should work.

I did it with the BHS (res=LLS:1.0.200). 

Tried to "overtake" Travel your efforts with the German Herrnhut Watchwords (Losungen), incl. hebrew and greek texts (finished on last monday). On tuesday I realized the differences... (see the watchword for February 11, 2014 / 14. Februar 14). There are some 23 other errors relating the interpretation of Lukas 2,36.38 etc. (on February 20, 2014). If you have time, please revise the docx.

It took a bit longer... but see my post in the German language subforum: http://community.logos.com/forums/t/87488.aspx 

Running Logos 8 latest beta version on Win 10

Posts 2
Wheeler Feng | Forum Activity | Replied: Sun, Nov 26 2017 8:33 PM

Bob Pritchett:

I regularly get email from people who love Logos Bible Software and would like to help translate it into another language, so that it can be useful to more Bible students.

We have set up a web-based project using the Crowdin translation tool, so anyone who would like to contribute to a translation project can. Right now the Logos 5 desktop UI has been uploaded for translation; help files and other content will follow in the coming weeks.

http://crowdin.net/project/logos-desktop-ui

We have set up projects for around 20 languages of interest to existing/potential users (based on the language their web browser is set to when people visit Logos.com).

Most Logos users read English, by necessity -- most of our the content is in English! (Except for our Spanish product line.) But having the UI in your native-tongue can be more comfortable even when you're using English resources, and this will enable users to contribute to that effort if they wish.

We will build Logos in any of these languages that get 90% or more of the UI translated, and enable switching to that language through the Program Settings. (Though you may have to wait for a beta or SR for updated language resources, until we're able to automate the update process more.)

We do not have in-house skills in all these languages, and will need to rely on user contributions, and on users with strong language skills volunteering to be proof readers who approve submitted translations. (An easy function once you're authorized for that role in Crowdin.)

For a small number of languages we intend to do a full-scale localization effort. This involves translating the software UI, the help files, our unique biblical data sets, creating reverse interlinears for Bibles in that language, translating a significant portion of our web site and automated transaction and service emails, hiring bi-lingual customer service agents, and licensing books in that language.

For these languages we will need translation managers who are willing to commit to the project, and we expect to compensate these individuals in exchange for their commitment to 'treat it like a job' -- making sure the translation is done 100% before a release, reviewing/standardizing vocabulary, etc. It's possible we'll contract this out to professional firms, but we're also open to working with users who would like to work remotely, part-time, in exchange for software credit.

I anticipate (in no particular order, and with no schedule, and we're not quite ready yet) that the first 'done thoroughly' languages will be German, Dutch, Portuguese, Chinese (Simplified and Traditional), Korean, and French, in addition to Spanish, which we manage in-house.

(We are not ready to go full-throttle on all this yet, and won't be for some time, but if you want to help in a bigger way, email me -- bob@logos.com -- and I'll add your email to my file for that language, even if I don't respond immediately.)

Again, if you volunteer to contribute to the translation project online at Crowdin, please know that we can't commit to payment or any compensation right now. So we have no expectations, but if you want to do it, you're welcome to and we'll build the localized UI if we get enough coverage in your language. And if you choose to contribute, please use the same email or name at Crowdin as you use on your Logos account, so we can see who contributes and thank you appropriately.

-- Bob

How did the project go now? Is it still open for translation. As a mandarin translator I could put some contribution to it. Will check it out...

Posts 652
LogosEmployee
Thomas Reiter (Faithlife) | Forum Activity | Replied: Mon, Nov 27 2017 9:14 AM

Hi Wheeler,

Since this project was created, we have actually substantially expanded our approach to languages and now have dedicated staff for a number of languages, Chinese being one of them. We have already completed the interface and much more, but still have plenty left to localize, so I have forwarded your info to our Chinese product manager who will reach out to you.

Thomas

Posts 2
Wheeler Feng | Forum Activity | Replied: Tue, Nov 28 2017 1:55 AM

OH thank you, I've received an email from Philip Peng and I am going to write back to him. 

BTW I am running a professional Chinese translation team here. Will you consider engaging professional service providers like us, or you are only in need of language volunteers?

Page 4 of 4 (72 items) < Previous 1 2 3 4 | RSS