Hello,
As you see here some font is translated in rectangles...
It is probably a font issue. It is addressed in this thread.
Lexham Hebrew-English Interlinear Bible - Logos Bible Software Forums
Hi Douglas, what font do you have set as your Default Font in Program Settings?
Some fonts do not have all the characters that Logos needs to display transliterations. If they are not part of some European alphabet, they might be missing.
Unfortunately, there's nothing you can do about that other than choose a different font as your Default font.
Hi Rosie
Yep! It was the font I changed to
I wish all fonts could translate correctly...
Did I just come up with a suggestion?
Thanks!
I wish all fonts could translate correctly... Did I just come up with a suggestion?
It isn't something that Logos has any control over. The fonts on your system are made by various different font manufacturers. Font character sets are pretty much set in stone when the font is created. The makers of these fonts can't know in advance what uses you might want to make of them (e.g., displaying transliteration characters in a Bible software program). They choose the glyphs that are most likely to be useful the greatest number of people. The Unicode list of possible characters for fonts to include is enormous. Most fonts only contain a small subset of them. Even the so-called Unicode fonts (e.g., Arial Unicode) does not contain every possible Unicode character.
There's a free program for Windows called BabelMap that lets you explore the Unicode character map and see what fonts on your system support what glyphs.
There's a whole lot about fonts that I don't understand, so I might not have explained this very well. But essentially I don't think it's something that is going to change for that particular font that you like. You just need to find another font that is appealing to you and has the full complement of characters Logos needs.
Perhaps it would be helpful if Logos were to provide a list for us of all the characters that might be used by any of the resources they produce, and a suggested list of fonts that will display all Logos resources adequately. Of course such a list could never be exhaustive, because there are literally thousands and thousands of fonts out there available for purchase and download, and Logos can't be expected to examine all of them. But perhaps they could provide a list of the most common fonts that come with Windows and an indicator of whether that font is adequate for Logos use or not.
If Logos won't do it, maybe there's a user out there who would like to take this on as a project for posting on the wiki? But I think it would require some inside knowledge from Logos to come up with the full list of characters that they might ever use in a resource. EDIT: There are some funky ones, e.g., in the Lexham Discourse Greek New Testament. There's a special font called Libronix Symbols that contains some of these weird glyphs:
if Logos were to provide a list for us of all the characters that might be used by any of the resources they produce, and a suggested list of fonts that will display all Logos resources adequately
Logos has a responsibility in their selection of fonts to be sure that appropriate defaults are available. This is a problem that has well solved reasonably well on the web - I can go from Thai to Burmese to Hindi to Arabic to Russian to Polish with problems being rare. A hassle - yes, but a standard QA issue.
if Logos were to provide a list for us of all the characters that might be used by any of the resources they produce, and a suggested list of fonts that will display all Logos resources adequately Logos has a responsibility in their selection of fonts to be sure that appropriate defaults are available.
Logos has a responsibility in their selection of fonts to be sure that appropriate defaults are available.
Their Athelas font does show up all these characters appropriately. But they give us access to the entire set of fonts that are installed on our machine, so we can change the default resource font (which is also used for the transliterations in interlinears) to something that will not display correctly. Are you saying that they ought to limit the "Default Font" dropdown in Program Settings to only show fonts that will display everything correctly in all our resources? Or come up with a solution to display those special characters in a different font than the one the user has chosen if that font doesn't contain the glyph in question? Or something else?
Or something else?
There are a number of ways to solve the problem - I can think of 3 viable options. The issue is best described as an ordered list of font preferences matched to the fonts required for a specific resource. This requires some metadata regarding the fonts requirements of a document, consistency in the fonts used to create the documents and known default values for fonts that will show the character correctly.
My guess for the quickest implementation would be that a mouse over on character than cannot be rendered, display the character in a font that can display the entire resource. It would also allow one to switch to this font for this particular session for this particular resource. If the font does not exist on your machine, it provides the name of the default font it tried to use. Yes, this is a rough idea that needs polishing for usability - and needs to know what is required/available within Logos to determine minimum font requirements.
So I'm saying this is something Logos should handle rather than turning Logos users into font detectives.
Yes, I agree. [Y]
My guess for the quickest implementation would be that a mouse over on character than cannot be rendered, display the character in a font that can display the entire resource.
This effectively exists: if you right click on a word it is displayed in the menu in the system font. This is what I rely on for books that have the occasional transliteration that will not display in my preferred font.
The problem mainly occurs, as in the initial example in this thread, when using interlinears with transliterations. In that situation it should be pretty simple for Logos to specify that the transliteration line should be displayed in the default transliteration font—the user-selected font would be ignored in that case. This is, I think, what happens when you use the interlinear pane rather than the inline interlinear (although I have never figured out how to navigate in the interlinear pane so don't use it). In the inline interlinears, the greek/hebrew/aramaic lines seem to be displayed in the greek/hebrew/aramaic font rather than the user-selected font, so it is simple enough to specify that.
I seem to recall that in Logos 3 we had the opportunity to select a transliteration font; I don't have Logos 4 available at the moment to check whether that option is still in the settings.
For other books, I don't know if transliterations are tagged as transliterations. If so, again the program could use the default transliteration font for the tagged text and the user-selected font for the rest of the book. The user then just needs to choose any unicode font that contains basic greek and hebrew characters and accents.
In the inline interlinears, the greek/hebrew/aramaic lines seem to be displayed in the greek/hebrew/aramaic font rather than the user-selected font, so it is simple enough to specify that.
The user can select a default Greek, Hebrew, and Syriac font:
Not in Logos 4.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
