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.
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 -- email@example.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.
Peace, Bob! *smile* Again I must say, "Well-Done!" You and your compatriots do a wonderful Work that benefits so many peoples (sic!) as you diligently strive "to get the Word out"!
I thank you and I thank our Gracious God and Father for you! Indeed! My mind is often "blown" by your wisdom and daring and enthusiasm. God Bless you in this latest endeavour! *smile* You -- and your colleagues at Logos Bible Software -- will continue in my personal prayers!
Philippians 4: 4 Rejoice in the Lord always; again I will say, Rejoice. 5 Let your reasonableness be known to everyone. The Lord is at hand..........
This is great news!
How to Ask for Help | Logos Wiki | My Machine Specs | My Blog
It is exciting to see the influence of Logos expand to other languages.
Using adventure and community to challenge young people to continually say "yes" to God
This is great to see. All we need now is a Welsh Bible - electronic files are available from the American Bible Society.
If anyone is concerned about the current security error when logging into the crowdin website, it's due to a server configuration error at their end. I reported it to their support, and got the following reply: "We are sorry for this temporary inconvenience. We assure you that you can trust the connection, there is nothing to worry about."
How to ask for help ● Logos Tutorial Videos ● Search Help
Rosie is right (as usual): this is GREAT news! Just imagine, that "little" startup Bible software outfit way up there (from a US perspective) in "tiny" Bellingham, WA, is moving from the shallow end to the deep end of the linguistic pool of our Lord's Church that includes disciples "from every nation and tongue! Gott sei Dank!
Peace, Steve! *smile* Great post! My personal life theme for now and the foreseeable future = Gott sei Dank!
Wish I could help with this awesome new project, but I don't see any options for 1337 or Ubbi Dubbi.
It is exciting to see Logos being translated and also exciting to see an open project where users and fans can directly contribute something back and help move it forward.
My Base Packages
Dell XPS 8300: Core i7; 12GB RAM; GeForce GTX 970; Win 10 ProSamsung ATIV Smart PC Pro 700T: Core i5; 4GB RAM; Win 10 ProASUS Nexus 7 | Samsung GALAXY S5
Randy W. Sims (Shayne):Wish I could help with this awesome new project, but I don't see any options for 1337 or Ubbi Dubbi.
. Both of those "languages" are machine translatable with near 100% accuracy, so crowd sourcing probably isn't needed---unless 1337 slang is required (see the Leet Speak language setting in Facebook). For novelty languages, I would prefer to see Logos available in Pirate English.
Bob Pritchett: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.
This is exciting, especially if it means Logos will be licensing more Bibles in those languages.
Wiki Links: Enabling Logging / Moving Logos between systems / Detailed Search Help - ThinkPad T520: 2.4GHz i5-2430M, 8GB, 7200RPM HD, integrated video
The project would probably benefit from each 'done thoroughly' language including a dictionary for the user to translate some of the more difficult English words (in the resources) into the interface language.
(That way the rest of us will benefit from the availability of the German-English dictionary to help us with German language resources u.s.w.!!)
Hey collaborators!There are two ways you can get more information from Logos about the context of a particular string. There is the "Suggest context" link, and the Comments section on the right hand side. Some of you have been asking questions using the "Suggest context" link, and that's great! The only problem is it sends a private message to all the managers, so when we reply to you, no one else can see the answer but you. So, we encourage you to ask questions via the Comments pane on the right side. This way everyone can see the question and answer and benefit. Thanks!
You do realise that Simplified and Traditional Chinese are exactly the same except for the appearance of the characters...? I see that you have both languages listed. Once the translation is done in Traditional characters it can be automatically converted into simplified (but not as easily the other way).
That's not really accurate. Traditional Chinese is used in Taiwan and Hongkong, so there will be appreciable differences in translation compared to Simplified Chinese.
Hi Lee,Could you please elaborate or give some examples? I don't see how their could be appreciable differences in translation in a software GUI. Many (most?) Christian books are translated from English by Traditional users and then converted to simplified so I would think that would be a lot easier than translating the entire program twice into Chinese.
No need to elaborate. The perception that you are operating under is a common misconception.
Christian books are translated from English by Traditional users and then converted to simplified
Christian books are translated from English by Traditional users and then converted to simplified
That's why some books are readable, while a surprising number of books are so unreadable that in reality, few people read them. Suffice it to say that in secular industry practice, e.g. Hollywood, Microsoft, there are different translation teams in Mainland China, Taiwan, Hongkong for localization projects.
Seriously? How is that a misconception. I can read both traditional and simplified Chinese fine. The burden of proof lies on you.
You read Chinese? Both Simp Chin and Trad Chin? Great. If you want proof, go google it.
This is going off-topic as it is. I was just merely trying to correct someone's well-intentioned but inaccurate suggestion that Simp Chin and Trad Chin localization would be freely inter-convertible.
I was unawares that the Oriental/Asian Languages were categorized as 'simple' and traditional'. It was my understanding that the dialect was based on locale......that the phonology of one area could be a close similarity of another, but not grammatically the same.
The things you learn on the internet.................
How could I miss your post Bob for so long! It is great. I have been waiting for that since Logos 4 launch. Thank you for that decision. Now I have to find somebody who will have more time than me to work on that . Excellent move.
I read the blog post last night at 1am when I came home from my work trip and in the morning I was wondering if this was a dream or true. And it's true! Thank you very much for this new project! I'm in the project!
This makes Logos much more globally oriented program! Some new key resources for those new languages and Logos will be soon top 1 Bible software also for lay people in many non-English languages.
Lutheran Gold, Standard Gold, Nelson Bible Reference Bundle, Luther's Works, etc.Laptop: Win 8.1 Pro, Intel Core2Duo T8100 2.1GHz, 4GB RAM, 128GB SSD, ATI HD3470 256MB.Tablet: iPad Mini 2. Phone: Nokia Lumia 820.