search

unfoldingWord-dev / d43-catalog

Lambda functions for the Door43 Catalog.
https://api.door43.org/v3/catalog
MIT License
1 stars 8 forks source link

tN Link Expansion Issue #41

Closed jag3773 closed 6 years ago

jag3773 commented 6 years ago

For some reason there are some links in tN that are getting a link name injected in the tS API conversion process. For example, there is a tN for Acts 17:1 that links to [[rc://en/ta/man/translate/translate-names]]. However, in the tS API endpoint (item 255.tn.4) it shows up as [[:en:ta:vol1:translate:translate_names|How to Translate Names]].

There are other seemingly random occurrences of this phenomena as well.

In contrast, Acts 1:1 also has a link to translate_names but it does not get the link name injected.

tS Desktop 11.1 is not able to handle the links that have the link names injected, so it is preferable to not inject any link names into the tS v2 API endpoint.

da1nerd commented 6 years ago

@jag3773 actually [[:en:ta:vol1:translate:translate_names|How to Translate Names]] is the proper form. That has been the preferred for since before tS desktop.

da1nerd commented 6 years ago

I am however investigating how the links are generated and am having trouble figuring out how the titles are getting there in the first place! Who wrote this thing? :P

da1nerd commented 6 years ago

@jag3773 tS Desktop does not show the title in Acts 1:1 because the indexed data is a bit outdated and is missing the title in the link.

da1nerd commented 6 years ago

It was determined there was no inconsistency. The tS api is displaying all the links without titles. tS android is automatically displaying titles by reading the cached data. tS desktop is simply displaying the slug.