Help translate Logos 5 into another language!
Comments
-
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.
Hi Bohuslav,
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.
0 -
Hi is there a list of the relationship between each resource file and the section in Logos UI.
For example LDLS4.indexer\OurResources.resx is for section of the UI in Logos5 that will make translation much more easier and no need to ask for context for clarification.
0 -
Hey Stephen,Stephen Kao said:Hi is there a list of the relationship between each resource file and the section in Logos UI.
For example LDLS4.indexer\OurResources.resx is for section of the UI in Logos5 that will make translation much more easier and no need to ask for context for clarification.
First let me say thanks for all the help translating. I've seen you requests for context and I plan on addressing them soon.
Those sections for resource files, are from different projects we build when we build the application. So there is a relationship, but not necessarily a clear one. If the folder above is Guides, the string most likely will be found in the guides section, somewhere, or if documents then in some type of document. However, a majority of all the strings you see in the UI, are in the LDLS4 project and usually the keys will be prefixed with where in the app they might be. Like LayoutSaveDescription, is used in Layouts, and PrayerListAnsweredSectionLabel is used in PrayerLists. If there isn't information like that, usually it means it is used generically throughout the app, and most times context will probably need to be provided.As new features are developed and new UI strings are introduced, I will ask my fellow developers, to ensure to add context where it isn't clear.
Regards,
Seth Copeland
Logos SW Development
0 -
firstly I can't help in this area - just so no one gets the wrong idea,
second, I am unsure if this compensation / 'pseudo' job is clear enough. who are you paying?
the managers, (3rd last paragraph) and not the workers (last paragraph)? Not saying that you meant this, I am just saying: what are you saying? thats all
0 -
well, hi Kevin. its nice to be a Christian isn't it!Kevin said:Seriously? How is that a misconception. I can read both traditional and simplified Chinese fine. The burden of proof lies on you.
( well if not in this life, with certainty in the next)
I was thinking of the time I showed a Japanese exchange student the Japanese bible module in theword. He said something like: "ahh-mmm this is difficult."
if it is helpful...
0 -
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!
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 -
Mark Barnes said:
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!
[Y]
Mac Pro (late 2013) OS 12.6.2
0 -
Mark Barnes said:
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!
as some people who lives in the internet call it 'grammar nazi' .. [6][H]
lol
0 -
Mark Barnes said:
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
0 -
L.A. said:
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
0 -
Seth Copeland said:
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!! [Y] Thank you (and all the developer team) veeeeery much for this improvement!!!! (bow) I'm not a beta-tester/user (prefer patiently waiting instead [C]), but anyway, I'll post this Info on the faithlife German Logos User page. Be blessed!
0 -
Seth Copeland said:
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?
0 -
L.A. said:
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
0 -
Seth Copeland said:L.A. said:
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.
Have joy in the Lord!
0 -
-
NB.Mick said:
@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" [ap] 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á!
0 -
L.A. said:NB.Mick said:
@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"
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
Have joy in the Lord!
0 -
Bob Pritchett said:
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...
0 -
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
Director, New Languages & Business Line Management
0 -
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?
0
