Help translate Logos 5 into another language!
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
Comments
-
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..........
0 -
This is great news!
0 -
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
0 -
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."
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
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!
0 -
Peace, Steve! *smile* Great post! My personal life theme for now and the foreseeable future = Gott sei Dank!
*smile*
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..........
0 -
Wish I could help with this awesome new project, but I don't see any options for 1337 or Ubbi Dubbi. [:P]
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.
0 -
Randy W. Sims (Shayne) said:
Wish I could help with this awesome new project, but I don't see any options for 1337 or Ubbi Dubbi.
[Y]. 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 said: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.
MacBook Pro (2019), ThinkPad E540
0 -
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.!!)
0 -
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!0 -
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).
0 -
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.
0 -
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.
0 -
No need to elaborate. The perception that you are operating under is a common misconception.
Tom Reynolds said: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.
0 -
Seriously? How is that a misconception. I can read both traditional and simplified Chinese fine. The burden of proof lies on you.
PCA Church
L4 Platinum, L5 Reformed Platinum, L6 Reformed Diamond, Reformed Studies XL, Platinum, Logos Now0 -
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.
0 -
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.................
DISCLAIMER: What you do on YOUR computer is your doing.
0 -
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. [Y]
Bohuslav
0 -
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.
Faithlife Connect + several Base Packages + Luther's Works, etc.
Lenovo ThinkPad Yoga 260, Win 10 Pro, Intel Core i7-6500U, 16GB RAM, 256GB SSD, Intel HD Graphics 520.
iPhone 11.0 -
Do TitleCases really have to be Title Cases? I mean it's not proper Finnish. I guess there's some kind of technical reason for this and they really have to be Title Cases?
0 -
I just want to say a big THANK YOU to God and for this initiative!!
0 -
Elias Okkonen said:
Do TitleCases really have to be Title Cases? I mean it's not proper Finnish. I guess there's some kind of technical reason for this and they really have to be Title Cases?
They often do not. Use whatever would be most appropriate for the language.
0 -
Indonesian, Tagalog, and Vietnamese have been added. Keep those translations coming, and a big thanks to those who have already contributed.
0 -
I hope to see one day,Amharic and Tigrinya Bibles fully integrated in Logos format.
Blessings in Christ.
0 -
Another two cents on Chinese translations - (sorry) - yes the characters may be freely interconverted back and forth between simplified and traditional script freely, but there are terms that will be viewed as between odd to just plain wrong by various groups of people, ie mainlanders vs Taiwanese, Cantonese, or Hong Kong residents (Western influenced region with lots of pop culture and rapidly changing expressions). Keep in mind that the Chinese region comprises lots of people who, though they have a common written script (with a recent modification), have had centuries of lo tech living to develop different ways of speaking... A common thing that I see with children's books in Chinese is that they will apparently be written by a non mainlander and will then generate lots of fairly harsh criticism from Chinese teachers on the mainland (some cultural norms come into effect here). So it's important to know where your translator is coming from if you allow them to lead a project... They may be native speaking, but a slightly different native, with varying levels of sensitivity to speakers from other areas, and a varying sensitivity to vocabulary changes over time, though this is less critical for a UI than for literature, of course.
0 -
Wow big difference between Traditional and Simplified Chinese! Do we want Logos to be translated into British English, Scottish English and Australian English as well? If you want proof for these differences? Go google it.
Surely there are differences between Traditional and Simplified Chinese (just like any local dialect), but it is not astronomical.
PCA Church
L4 Platinum, L5 Reformed Platinum, L6 Reformed Diamond, Reformed Studies XL, Platinum, Logos Now0 -
KevinC said:
Wow big difference between Traditional and Simplified Chinese! Do we want Logos to be translated into British English, Scottish English and Australian English as well? If you want proof for these differences? Go google it.
Surely there are differences between Traditional and Simplified Chinese (just like any local dialect), but it is not astronomical.
Since you have such a low post count, supposed ability to read in Simplified and Traditional (as if that were some indication of expertise), and you obviously like "proof", I would urge you to support your conclusions and limit your observations to Chinese, and keep in topic.
0 -
Tes said:
I hope to see one day,Amharic and Tigrinya Bibles fully integrated in Logos format.
Tes, this thread has to do with translating the User Interface of Logos.
0 -
Today I have translated Simplified Chinese to 8%. haha[:D]
2 Peter 3:18 But grow in the grace and knowledge of our Lord and Savior Jesus Christ. To him be the glory both now and to the day of eternity. Amen.
0 -
Rosie Perera said:Tes said:
I hope to see one day,Amharic and Tigrinya Bibles fully integrated in Logos format.
Tes, this thread has to do with translating the User Interface of Logos.
OK.thank you Rosie.
Blessings in Christ.
0 -
If what I said is false, there is no need for argumentum ad hominem.
人身攻擊？ 还是。。。人身攻击？
And, keep in topic.
PCA Church
L4 Platinum, L5 Reformed Platinum, L6 Reformed Diamond, Reformed Studies XL, Platinum, Logos Now0 -
Not ad hominem. You're talking about Scottish English, Australian English, etc.
这也扯得太远了吧。别一上這裡耍大牌，要人家證明什麽……你提Scottish English能證明什麽？天下有多少軟件有Scottish English，又有多少軟件有繁簡之分，甚至有中港台之分?
销往全世界的电脑产品的标签，你读过吗?
所谓人身攻击只存在你的幻想里。I would urge you to support your conclusions and limit your observations to Chinese, and keep in topic. 这句客气的英语够清楚了。
This is an English forum. Here is it, translated:
You're really stretching it. Don't come up here and pretend to be someone big, to want somebody to prove something to you. And what do you hope to prove by bringing up Scottish English? How many software programs have Scottish English? And how many programs are differentiated into Simplified and Traditional Chinese, even localized into Mainland Chinese, Hongkong Chinese, and Taiwan Chinese?
Have you ever read the label of a computer product meant for worldwide sale?
The so-called personal attacks only exist in your imagination. "I would urge you to support your conclusions and limit your observations to Chinese, and keep in topic." That English was polite and clear enough.
I hate to see a perfectly good thread by the CEO of Logos, hijacked by some gadfly. If you want to say something about the original post suggesting that one translation be made into Chinese and split into two sets of characters, go ahead and argue it. I just wanted to correct that, and did not want to go off-topic. Someone called Matt Kim decided to add his perspective.
Now you, KevinC, want a rejoinder. Go ahead, if it matters that much to you, but please don't shoot all over the place. If proof is so important to you, bring it on. If you have some major point to pick, start a new thread.
0 -
I like the idea Bob. If the UI are in different languages, they are more likely to request that works in their languages be published also.
Mission: To serve God as He desires.
0 -
Lynden Williams said:
I like the idea Bob. If the UI are in different languages, they are more likely to request that works in their languages be published also.
True. [Y]
0 -
That's really great news!! Logos is going international - step by step - ... (ap)
I've been really missing it after using libronix-sesb2/3 etc.
Thanks a lot!!!!!!! [Y] I appreciate also the growing resources in spanish, portuguese... ...?and german?... (OK - this isn't the resource forum - however :-)
0 -
As a former user of German SESB (Libronix) who recently changed to Logos 5 with Windows 8 it would be VERY useful to have a German user interface of Logos 5, especially the chance to use bible book references in the form of "Joh 1,1" instead of "Jhn 1:1" or "Offb 12,4" instead of "Rev 12:4".
I'm looking forward to this! Thanks for your efforts.
Friedhelm
0 -
arjeh said:
As a former user of German SESB (Libronix) who recently changed to Logos 5 with Windows 8 it would be VERY useful to have a German user interface of Logos 5, especially the chance to use bible book references in the form of "Joh 1,1" instead of "Jhn 1:1" or "Offb 12,4" instead of "Rev 12:4".
I'm looking forward to this! Thanks for your efforts.
Friedhelm
Blessings in Christ.
0 -
We've uploaded the help files for Logos 5!
If you would like to help out translating click on the following link.
http://crowdin.net/project/logoshelpfiles
Thanks!
Seth
0 -
YES! YES! YES! :-) PLEASE!arjeh said:As a former user of German SESB (Libronix) who recently changed to Logos 5 with Windows 8 it would be VERY useful to have a German user interface of Logos 5, especially the chance to use bible book references in the form of "Joh 1,1" instead of "Jhn 1:1" or "Offb 12,4" instead of "Rev 12:4".
I'm looking forward to this! Thanks for your efforts.
Friedhelm
0 -
L.A. said:
YES! YES! YES! :-) PLEASE!arjeh said:As a former user of German SESB (Libronix) who recently changed to Logos 5 with Windows 8 it would be VERY useful to have a German user interface of Logos 5, especially the chance to use bible book references in the form of "Joh 1,1" instead of "Jhn 1:1" or "Offb 12,4" instead of "Rev 12:4".
I'm looking forward to this! Thanks for your efforts.
Friedhelm
A German user interface has been added to Logos 5.1a which is currently being beta-tested. However, Bible book names are all still in English. This post explains why, and offers some hope: http://community.logos.com/forums/t/72954.aspx
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Would be nice for the PBB Tool compiling German books. Prefer to be patient awaiting the 5.1a :-) However... ;-)
Thanks for the Info, Mark!
0 -
L.A. said:
Would be nice for the PBB Tool compiling German books. Prefer to be patient awaiting the 5.1a :-) However... ;-)
Thanks for the Info, Mark!
It shouldn't be a problem to compile German books in PBB. I do a lot of Czech books and it works fine.
Bohuslav
0 -
Mark Barnes said:
A German user interface has been added to Logos 5.1a which is currently being beta-tested.
The localization in current RC 3 is actually quite good.
One thing I stumbled upon when I tried to correct this typo in Crowdin
(actually it's a double mistake: "durhführen" is misspelled, it needs to read "durchführen" with a ch, but then "durchführen" only might be an acceptable translation of "to make" in the sense of performing an action, whereas here it has the sense of "to create", which would be "erzeugen" in German - anyway), when I tried to correct this error in Crowdin, I found that this platform has a major weakness: each UI string is treated on its own.
@Logos: This is bad, since you need to have a canonical list of Logos vocabulary that appears over and over in the application. These need to be translated consistently everywhere.
Take a look:
Basically, I'm totally indifferent if "visual filters" become "optische Filter" or "visuelle Filter" in German - both would be acceptable translations in my mind - but you definitely need to translate it consistently throughout the application.
OT: it's Verknüpfung, not Verknüpung for link(s)
Mick
Have joy in the Lord!
0 -
Bohuslav Wojnar said:
It shouldn't be a problem to compile German books in PBB. I do a lot of Czech books and it works fine.
But Logos hasn't implemented German bible book names - and it doesn't apply continental reference style to German text. Thus the PB compiler detects books that happen to have the same name or abbreviation in English and in German and - if so - detects the chapter reference, but not the verse.
1 Thess 1, 8 will be the first chapter of First Thessalonians, but will not resolve verse 8.
Have joy in the Lord!
0 -
NB.Mick said:
when I tried to correct this error in Crowdin, I found that this platform has a major weakness: each UI string is treated on its own.
@Logos: This is bad, since you need to have a canonical list of Logos vocabulary that appears over and over in the application. These need to be translated consistently everywhere.
replying to myself here: it seems that this is less an issue with Crowdin but with the usage. The "Terms" database (a bit hidden to the right of the screen, tab alternates with Comments) seems to be the feature intended to hold the canonical vocabulary - but it needs to be used consistently by translators and Logos.
Have joy in the Lord!
0 -
NB.Mick said:NB.Mick said:
when I tried to correct this error in Crowdin, I found that this platform has a major weakness: each UI string is treated on its own.
@Logos: This is bad, since you need to have a canonical list of Logos vocabulary that appears over and over in the application. These need to be translated consistently everywhere.
replying to myself here: it seems that this is less an issue with Crowdin but with the usage. The "Terms" database (a bit hidden to the right of the screen, tab alternates with Comments) seems to be the feature intended to hold the canonical vocabulary - but it needs to be used consistently by translators and Logos.
I am not sure with Crowdin, but in PB compiler I can use Czech Bible references (Mt 5, 1-10) but it accepts also a combination of Czech - English ref. (Matouš 5:1-10)
Bohuslav
0 -
Shouldn't new threads be started for details like these?
0 -
I'd like to expect about new language traslate ~
is it possible copy korean version to logos bible resources ?
many korean websites provids standard korean bible translate version ~
0 -
May I suggest that we start new threads titled "Localization: ___________________" in the General forum.
This can help everybody get to the specific issues.
0
