Interface in other languages

I´ve searched the forum for posts about logos 4 becoming available with interfaces for other languages. Couldn't find anything. Last time I checked the "missing features"-page had nothing to say about this issue.

Does anyone know whether logos 4 will soon be available with intefaces in other languages but English?

Kindly,

Andreas Holmberg

Find more posts tagged with

Comments

toughski

I asked Logos about foreign interfaces and even offered my help with Russian, no response so far. They must me swamped.

Bob Pritchett

With Logos 3 we did whatever interface languages we could, even if only partially, and even if we didn't have a lot of books in the language.

With Logos 4 we're planning to do only complete, maintained translations. We'll have fewer -- primarily for languages in which we have many books -- but they're be well done and thorough.

Spanish will be first; I expect you'll see German, French, and Portuguese next.

-- Bob

toughski

https://community.logos.com/discussion/comment/48020#Comment_48020

thank you for working in this direction.

As far as Libronix (v3) is there opportunity to complete the "incomplete" interfaces, such as Russian? We have a Bible Institute here in Siberia and I am really promoting Logos Bible Software to our students and preachers. However, the only resource available in Russian is the Russian Bible. We are mitigating this by producing PBB resources, so possibly as the user base grows we may see publishers get on board as well.

Michael Cochran

https://community.logos.com/discussion/comment/48020#Comment_48020

I agree that if a user is mainly using resources in an international language then they should be able to handle a user interface in that language. In the past we were able to contribute to the localization of the Libronix software. If there will be resources that are added in many other languages then it would be great if we could continue to do so.

I would encourage you to allow partial interfaces. We have found in SIL that many times users who do not understand English well are still able to use a product that uses "standard" menus since they have used them in other products that only have an English user interface to do simple tasks (editing and using File open, Search, etc) while entering data in their mother tongue. When it comes to tasks that are unique to LOGOS 4 they need to interact with an interface in a language that they know. I believe this would allow you to do two things:

Incrementally introduce interfaces in other languages in a way that helped people.
Allow people to determine "how much" was enough in terms of user interface for the tasks that they do.

Bohuslav Wojnar

https://community.logos.com/discussion/comment/134490#Comment_134490

If I am correct, we have Spanish and Swedish already implemented. The local interface language IMHO is not only for people who do not speak English (they will use English books anyway), it is also a signal to them that Logos is also for them, for their language group. I would suggest to have an interface in all languages you have Bibles in Logos. I am willing to help with Czech of course [:)]

Rosie Perera

https://community.logos.com/discussion/comment/134495#Comment_134495

I would suggest to have an interface in all languages you have Bibles in Logos. I am willing to help with Czech of course

But there is no Czech Bible in Logos...yet. [:)]

Bohuslav Wojnar

https://community.logos.com/discussion/comment/134500#Comment_134500

I would suggest to have an interface in all languages you have Bibles in Logos. I am willing to help with Czech of course

But there is no Czech Bible in Logos...yet.

Well, you are mistaken Rosie [:)]. http://www.logos.com/ebooks/details/CS-KR1579

I know, it is an old translation, from 1579. We we are expecting new translation shortly.

Rosie Perera

https://community.logos.com/discussion/comment/134504#Comment_134504

But there is no Czech Bible in Logos...yet.

Well, you are mistaken Rosie . http://www.logos.com/ebooks/details/CS-KR1579

I know, it is an old translation, from 1579. We we are expecting new translation shortly.

Oh, my mistake (bad memory). I thought I'd remembered you asking and asking for a Czech Bible in Logos, but it was a newer translation you wanted.

Bohuslav Wojnar

https://community.logos.com/discussion/comment/134511#Comment_134511

I thought I'd remembered you asking and asking for a Czech Bible in Logos, but it was a newer translation you wanted.

Good, it means if you noticed I am asking and asking... Logos surely noticed also [:D] (That is my purpose in mentioning it from time to time - to keep it high on the list of the suggested new Bible translations in Logos [:)])

Matthew Carroll

https://community.logos.com/discussion/comment/137260#Comment_137260

Any update on a Portuguese language Interface?

I don't actually need the whole interface in Portuguese, but I'd like it to be able to handle Portuguese Scripture addresses and abbreviations.

For example, in Portuguese, "2 Timothy 2:2" is normally abbreviated, "2Tm 2.2", but Logos 4 doesn't recognize "Tm" as Timothy (Libronix 3 with Pt Interface did).

Ideally, I'd like to use the personal book builder to load a syllabus in Portuguese into Logos 4 so I can teach from it, but without the capability to recognize standard Portuguese Scripture abbreviations, it's not much use.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/309829#Comment_309829

For example, in Portuguese, "2 Timothy 2:2" is normally abbreviated, "2Tm 2.2", but Logos 4 doesn't recognize "Tm" as Timothy (Libronix 3 with Pt Interface did).

Looking at Logos 4 Bible Book abbreviations => http://www.logos.com/L4/support/biblebookabbrev noticed Timothy has many abbreviations, but not "Tm" (wonder if "tm" not included to avoid issues with "TM" abbreviation for Trade Mark).

Keep Smiling [:)]

George Somsel

https://community.logos.com/discussion/comment/48020#Comment_48020

Spanish will be first; I expect you'll see German, French, and Portuguese next.

I suggest the order: Spanish, German, Czech, Portuguese and French in order of importance.

DMB

https://community.logos.com/discussion/comment/309845#Comment_309845

Well, much of 'all the world' in early Christianity was what today we call 'Europe'. Seems only right.

toughski

https://community.logos.com/discussion/comment/309847#Comment_309847

I thought we were going by Domestic debt levels. I guess will never see Chinese then [;)]

George Somsel

https://community.logos.com/discussion/comment/309832#Comment_309832

Looking at Logos 4 Bible Book abbreviations => http://www.logos.com/L4/support/biblebookabbrev noticed Timothy has many abbreviations, but not "Tm" (wonder if "tm" not included to avoid issues with "TM" abbreviation for Trade Mark).

Note that the trade mark symbol (™) is superscripted.

NB.Mick

https://community.logos.com/discussion/comment/309829#Comment_309829

Any update on a Portuguese language Interface?

I don't actually need the whole interface in Portuguese, but I'd like it to be able to handle Portuguese Scripture addresses and abbreviations.

For example, in Portuguese, "2 Timothy 2:2" is normally abbreviated, "2Tm 2.2", but Logos 4 doesn't recognize "Tm" as Timothy (Libronix 3 with Pt Interface did).

Ideally, I'd like to use the personal book builder to load a syllabus in Portuguese into Logos 4 so I can teach from it, but without the capability to recognize standard Portuguese Scripture abbreviations, it's not much use.

As far as I recall previous discussions on localization, the handling of Scripture abbreviations is independent of the localized language user interface and some more countries are supported than the UIs (confirmed by Tonya, IIRC). I seem to remember that Bohuslav was happy with the Czech solution, whereas Russian and German turned out to be nonexisting back then. Maybe something has changed in the recent beta to this end.

You should check which books work (and if separating the verse by period instead of colon works) - if it's only a small number of abbreviations not working, maybe Logos will put these into their algorithm or you could replace them in Word prior to building the book.

Mick

Bohuslav Wojnar

https://community.logos.com/discussion/comment/309866#Comment_309866

I seem to remember that Bohuslav was happy with the Czech solution, whereas Russian and German turned out to be nonexisting back then.

Mick, it is true only for creating PBBs in the languages listed in the PBB Tool. When speaking about using Bible abbreviations in the UI of the program, I have to use English even in the Czech Bibles (including those PBB Bibles created with using the Czech abbreviations in the milestones). I think this is really connected to the UI language and it should be so IMHO.

NB.Mick

https://community.logos.com/discussion/comment/309872#Comment_309872

I seem to remember that Bohuslav was happy with the Czech solution, whereas Russian and German turned out to be nonexisting back then.

Mick, it is true only for creating PBBs in the languages listed in the PBB Tool. When speaking about using Bible abbreviations in the UI of the program, I have to use English even in the Czech Bibles (including those PBB Bibles created with using the Czech abbreviations in the milestones). I think this is really connected to the UI language and it should be so IMHO.

Yes, thanks for clarifying. I interpreted the question as referring to making a PB in Portuguese (wonder if the Compiler works better if one claims the text to be Spanish). The Bible abbreviations used in the UI are another piece of cake altogether.

George Somsel

https://community.logos.com/discussion/comment/309912#Comment_309912

Yes, thanks for clarifying. I interpreted the question as referring to making a PB in Portuguese (wonder if the Compiler works better if one claims the text to be Spanish). The Bible abbreviations used in the UI are another piece of cake altogether.

Why would you need to claim the text to be any particular language? If you enter your text in unicode, it shouldn't matter. I enter text in Greek and never tag it as Greek, but Greek is what I get.

toughski

https://community.logos.com/discussion/comment/309918#Comment_309918

Why would you need to claim the text to be any particular language? If you enter your text in unicode, it shouldn't matter. I enter text in Greek and never tag it as Greek, but Greek is what I get.

"claiming" the text in a particular language is done for the benefit of reference parser. The text itself will render just fine, but if you "claim" or tag English language source as being Russian for example, references will not be converted to links.

Bohuslav Wojnar

https://community.logos.com/discussion/comment/309918#Comment_309918

Yes, thanks for clarifying. I interpreted the question as referring to making a PB in Portuguese (wonder if the Compiler works better if one claims the text to be Spanish). The Bible abbreviations used in the UI are another piece of cake altogether.

Why would you need to claim the text to be any particular language? If you enter your text in unicode, it shouldn't matter. I enter text in Greek and never tag it as Greek, but Greek is what I get.

What I was speaking about George was the main language setting for the particular PB. It helps in 2 ways:

1... you can find it in the library under that language resources

2... your Bible references can be in that particular language and the PBB Tool recognizes them.

EDITED: Sorry Vladimir, I haven't noticed you answered already.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/309918#Comment_309918

Why would you need to claim the text to be any particular language? If you enter your text in unicode, it shouldn't matter. I enter text in Greek and never tag it as Greek, but Greek is what I get.

Technical Note: Unicode identifies the script of text, but not its language. Text in Greek script is basically always in the Greek language, so that's unambiguous. Text in the Hebrew script might be Hebrew or Aramaic. Text in the Latin script could be English, Latin, French, Spanish, Portuguese, German, Swedish, ….

It doesn't always matter, but if the application into which you're entering text needs to know whether "Die" is a verb or an article, identifying the language is important. Some Logos 4 features require a language to be specified in order to determine (for example) whether "John 3:16" or "Juan 3:16" is valid input. (And sometimes this is required for efficiency, to avoid having to try to detect Bible book names simultaneously in dozens of different languages, which (in the worst case) could introduce ambiguities.)

toughski

https://community.logos.com/discussion/comment/310127#Comment_310127

Some Logos 4 features require a language to be specified in order to determine (for example) whether "John 3:16" or "Juan 3:16" is valid input. (And sometimes this is required for efficiency, to avoid having to try to detect Bible book names simultaneously in dozens of different languages, which (in the worst case) could introduce ambiguities.)

So, Bradley, are L4 Personal Books capable of recognizing RUSSIAN scripture references and if not, when can we expect this working? (I am running Logos4 Windows SR-6 and my references are not recognized) In the mean time, can LOGOS developers provide a list of official reference abbreviations in languages other than English so users can prepare their source texts for compiling?