Content found in this wiki may not reflect official Church information. See Terms of Use for more information.
TechWiki talk:Translation
Level 1 headings
Using a level one heading for the translated title produces a nice look. However, it creates an oddity in the Table of Contents, since the translated title is the only Level-1 item, and all the Level-2 items are displayed as children of that item in the ToC. If it weren't for that extra Level-1 heading, all the Level-2 items would be at the top level of the ToC. A possible extension to fix this is described in Meta-Wiki (see the solution described at "UPDATE:"). With that extension, we could put the translated title in <xh1> tags and it would look like a regular Level-1 heading, but would not be included in the ToC. -- Aebrown 02:13, 21 July 2010 (UTC)
- We are now using the {{DISPLAYTITLE}} approach for titles instead of an extra Level-1 heading, which is a better solution anyway. -- Aebrown 16:11, 21 May 2012 (UTC)
Redirect
Why do we have a step telling us to create a redirect? It seems to me that once we use the {{Other languages}} and {{DISPLAYTITLE}} templates, we should not need a redirect at all. Am I missing something? - Ken 15:51, 18 November 2010 (UTC)
- The redirect exists to improve the search feature. Having a redirect from "Nombre de la página" to "Pagename/es" will allow a user to enter "Nombre de la página" in the search box and go to the page. Without the redirect that is not possible. You might well find the "Pagename/es" article in the search results, but it will be harder for a Spanish speaker to find that article among the search results, particularly since the article titles are all in English. -- Aebrown 16:11, 21 May 2012 (UTC)
Categories for translated pages
The new pages (articles and templates) that have been created for translating help for LDS.org apps use categories with subpages. In general, I think that's a good approach. It's much better than the approach taken by Meetinghouse Technology pages, where all the translations were lumped into the same category (for example, see Category:Meetinghouse Internet and see how ugly it is to have 10 versions of many of the pages). With this approach, the Spanish Newsletter calendar articles will be nicely grouped in the the Category:Newsletter/es category, with no clutter from pages in other languages.
But the approach of using subpages isn't perfect:
- Until LDSTECH-721 is deployed in production, categories with subpages won't work quite right, since subpages aren't enabled in the Category namespace at this point.
- We can use the {{DISPLAYTITLE}} technique to make the category pages (such as Category:Newsletter/es appear with a translated title. But that won't help the display of the categories in the actual pages; at the bottom of Newsletter/es the category will be shown as "Newsletter/es" (there is no facility for showing a translated category name there, at least not that I know of).
- We can (and probably should) create a set of {{Other languages}} templates for these categories. Then we can facilitate moving between the languages on Category pages, just like we do with templates and articles. (But that is also waiting on LDSTECH-721).
Thoughts? -- Aebrown 16:11, 21 May 2012 (UTC)