You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @djmitche, I noticed in #1974 that the timing information enters the translations. This is in some sense working as intended, but I fear that it creates extra work for the translators.
then the page titles would be extracted on their own — and they would match the title we already extract from each page. So it would reuse the translation for the page, which is kind of neat 🙂
I don't have a good idea for how to include the page link like in the current formatting. We include the link in the translatable message, so this would defeat the attempt at unifying the message here with the page title.
The text was updated successfully, but these errors were encountered:
The links probably aren't that useful -- they're available in the sidebar as well. We could just omit them.
Good point!
To be clear, then, the suggestion is to format the schedule as a table rather than a list?
Yeah, it was an idea for how to avoid generating extra translation work: tables are translated cell-by-cell, so if the content of a cell matches an existing heading, there is no extra work for our translators!
Hi @djmitche, I noticed in #1974 that the timing information enters the translations. This is in some sense working as intended, but I fear that it creates extra work for the translators.
On Welcome to Day 1, as an example, if we would format
as a table
then the page titles would be extracted on their own — and they would match the title we already extract from each page. So it would reuse the translation for the page, which is kind of neat 🙂
I don't have a good idea for how to include the page link like in the current formatting. We include the link in the translatable message, so this would defeat the attempt at unifying the message here with the page title.
The text was updated successfully, but these errors were encountered: