Why does the English parallel translation show up for some Greek texts, while others don't?

Reply

Michel Pauw | Forum Activity | Posted: Sun, Apr 11 2021 4:40 AM

Ik heb twee collecties: 

• Greek: All Ancient Greek Literature (except Bibles) 
• Greek: All Ancient Greek Literature in Translation (except Bibles)

This allows me to search for words in Ancient Greek Literature, while Logos also displays the English Translation if I click 'Add Versions' and select the second collection.  

Fabulous feature, that works great with most resources (if you have both the Greek and the English of the same text). 

However, in the screenshot: 

• you see it works for Xenophon, Anabasis: both Greek and English is displayed
• but it doesn't work for Cassius Dio, Historiae Romanae: 

I can't find what goes wrong, here: 

• The Greek text displayed in the search window, is taken from resource 1 in the library (upper right) 
• I do have the English translation as you see, both in the library (upper right) and in the texts below

Nevertheless, the English translation of Cassius Dio, Hist. Rom. 44.33.3 doesn't show up in the search window. The only thing that might affect the issue at hand, is that the English translation doesn't have a milestone more specific than Hist. Rom. 44.33 (instead of 44.33.3). Would that be the reason? And if, so, is this something that can be solved? 

Any ideas how to resolve this?  

Reply

Michel Pauw | Forum Activity | Replied: Sun, Apr 11 2021 6:17 AM

Thanks, JT, for trying to understand the issue!

I am talking about the LOEB texts. These are ancient texts in both Greek and English. Some English texts do show up as English translation of the parallel Greek text, others don't. 

I think it's not the 'original language material' that need to be tied to each word, but the milestones of both resources need to be the same. 

Unfortunately the milestones in the Greek text go one level deeper than in the English translation. I'm afraid that might cause the issue. 

Reply

Andrew Batishko | Forum Activity | Replied: Tue, Dec 7 2021 7:25 AM

Andrew Batishko:

any resource of type Ancient Manuscript Translation is not considered a candidate to be shown in the list.

https://community.logos.com/forums/p/203251/1182140.aspx#1182140

Reply

Andrew Batishko | Forum Activity | Replied: Wed, Dec 8 2021 3:30 PM

Michel Pauw:

That would make sense.

However, why does one of the volumes show up and not the other, while both vols are of the type Ancient Manuscript Translation? 

In fact, Logos does pick up most of the vols of the type Ancient Manuscript Translation, but for some reason just a few of the vols are missing. 

Thanks for pointing this out. I believe the "Ancient Manuscript Translation" requirement only applies to what options show up in the suggestion box when selecting the additional resource(s) to use in the search results. You've worked around this problem by specifying a collection containing those resources.

I believe the reason why you don't see the additional resource in the one case is that the translation manuscript does not have a milestone that exactly matches the search result. From your screenshot, the Greek resource has Plut., Cat. Mi. 65.3, but the best matching option in the English resource is Plut., Cat. Mi. 65.3–5. This prevents it from being used. If you find a search result in a location where the English does have an exact milestone match (such as Plut., Cat. Mi. 61.4), then you will see the preview work as desired.

I'll pass along a request for more specific milestones in these resources.