1knerd.knitter
We have converted the Translate page to LT2. I know this isn't a page that everyone knows about, so if you don't know what it is, disregard!
We've updated the layout to be more modern and responsive, and we've also paginated it. You can still choose to show all the items on a single page, if you want to. We've also added a filter so you can choose to see only the ones that have no translations. This is the default when you access the page.
Please let us know if you have any issues as I know this is a major screen for people who use it.
We've updated the layout to be more modern and responsive, and we've also paginated it. You can still choose to show all the items on a single page, if you want to. We've also added a filter so you can choose to see only the ones that have no translations. This is the default when you access the page.
Please let us know if you have any issues as I know this is a major screen for people who use it.
2birder4106
On the new page there are some expressions that cannot be translated. E.g.:
-
-
3birder4106
>2 birder4106:
Not the entire text of the above message (>2 birder4106:) is being displayed.
However, I can see the full text by selecting the "Edit" button.
This may be an error on this page.
Not the entire text of the above message (>2 birder4106:) is being displayed.
However, I can see the full text by selecting the "Edit" button.
This may be an error on this page.
4birder4106
If the translation page is revised, I have a few more suggestions:
- I would like the option on the translation page to show only the expressions still to be translated from the current page, as well as their submenus and their associated buttons, options, etc.
Or all untranslated expressions of the respective language in all of LT.
- The possibility of sorting. Both the original expressions and the translated ones.
- Some of the translators in LT will not only be bilingual but trilingual and multilingual.
Especially when introducing new and larger topics, it might be desirable if not only one target language was displayed. In this way, several languages can be processed in one step.
- Many expressions that appear in multiple LT pages are the same. However, they must be recompiled for each occurrence. Wouldn't it be possible for programmers to use just one translation for the same expressions?
I am aware that when translating from English, depending on the context, it has to be translated differently into other languages. Then the translators should be able to enter such an entry. Also for this reason I suggested above also the desire for a sorting of the expressions.
Some translations have to be done over and over again. Partly monthly, e.g. SOTT or Early Reviewers, or annually, such as Christmas, Easter, or treasure hunt campaigns. In my opinion, it should not be necessary to translate these entries again and again.
I guess some of these suggestions/requests have been suggested before.
I think the revision of their translation page would be a good moment for some general and additional thoughts.
- I would like the option on the translation page to show only the expressions still to be translated from the current page, as well as their submenus and their associated buttons, options, etc.
Or all untranslated expressions of the respective language in all of LT.
- The possibility of sorting. Both the original expressions and the translated ones.
- Some of the translators in LT will not only be bilingual but trilingual and multilingual.
Especially when introducing new and larger topics, it might be desirable if not only one target language was displayed. In this way, several languages can be processed in one step.
- Many expressions that appear in multiple LT pages are the same. However, they must be recompiled for each occurrence. Wouldn't it be possible for programmers to use just one translation for the same expressions?
I am aware that when translating from English, depending on the context, it has to be translated differently into other languages. Then the translators should be able to enter such an entry. Also for this reason I suggested above also the desire for a sorting of the expressions.
Some translations have to be done over and over again. Partly monthly, e.g. SOTT or Early Reviewers, or annually, such as Christmas, Easter, or treasure hunt campaigns. In my opinion, it should not be necessary to translate these entries again and again.
I guess some of these suggestions/requests have been suggested before.
I think the revision of their translation page would be a good moment for some general and additional thoughts.
5knerd.knitter
>3 birder4106: we cannot edit your post to see the full text.
6knerd.knitter
- I would like the option on the translation page to show only the expressions still to be translated from the current page, as well as their submenus and their associated buttons, options, etc.
Or all untranslated expressions of the respective language in all of LT.
I am pretty sure this is available; when you click translate from a page, it should be just those associated with that page, but if you use ?remaining=1 I believe it shows you everything left for the language
- Many expressions that appear in multiple LT pages are the same. However, they must be recompiled for each occurrence. Wouldn't it be possible for programmers to use just one translation for the same expressions?
I do not think that the same string should appear multiple times; differences in capitalization or tags would make them appear as separate items to translate, but if they are exactly the same, they should not appear more than once.
Or all untranslated expressions of the respective language in all of LT.
I am pretty sure this is available; when you click translate from a page, it should be just those associated with that page, but if you use ?remaining=1 I believe it shows you everything left for the language
- Many expressions that appear in multiple LT pages are the same. However, they must be recompiled for each occurrence. Wouldn't it be possible for programmers to use just one translation for the same expressions?
I do not think that the same string should appear multiple times; differences in capitalization or tags would make them appear as separate items to translate, but if they are exactly the same, they should not appear more than once.
7anglemark
>4 birder4106: Some translations have to be done over and over again. Partly monthly, e.g. SOTT or Early Reviewers, or annually, such as Christmas, Easter, or treasure hunt campaigns. In my opinion, it should not be necessary to translate these entries again and again.
On the other hand, many words like "edit", "history", "event", etc mean different things in different contexts, so reusing the same string everywhere makes many things impossible to translate.
On the other hand, many words like "edit", "history", "event", etc mean different things in different contexts, so reusing the same string everywhere makes many things impossible to translate.
8AnnieMod
>7 anglemark: Not to mention that in highly inflected languages that may mean the same but may require different ending depending on where it is on the page and what it will be inserted into - I would rather have it stay in English than use a translation in the wrong gender/case... The untranslated looks like unfinished job (and someone may decide to assist), the latter looks like machine translation that is not checked by a human (so people may not realize they can help).
Just saying :)
Just saying :)
9timspalding
>7 anglemark: On the other hand, many words like "edit", "history", "event", etc mean different things in different contexts, so reusing the same string everywhere makes many things impossible to translate.
If you give us examples, we can change "Edit" to "Edit \note: imperative verb\", etc.
If you give us examples, we can change "Edit" to "Edit \note: imperative verb\", etc.
10birder4106
>2 birder4106:, >3 birder4106:, >5 knerd.knitter:
I was able to identify the problem with the text not being displayed. The problem was the inserted characters "open angle bracket" and "close angle bracket" as in >2 birder4106:.
Hence the text again as it should have appeared in >2 birder4106:
On the new page there are some expressions that cannot be translated. E.g.:
- Go back (ger. "Zurück")
- Translate This Page (Diese Seite übersetzen)
- items per page (Ausdrücke pro Seite)
- OK as is (Kann so bleiben)
- revert to this (Übersetzung zurücksetzen)
- 1 cheer for this edit. (1 Beifall für diese Bearbeitung.)
- No translations found. (Keine Übersetzungen gefunden.)
I was able to identify the problem with the text not being displayed. The problem was the inserted characters "open angle bracket" and "close angle bracket" as in >2 birder4106:.
Hence the text again as it should have appeared in >2 birder4106:
On the new page there are some expressions that cannot be translated. E.g.:
- Go back (ger. "Zurück")
- Translate This Page (Diese Seite übersetzen)
- items per page (Ausdrücke pro Seite)
- OK as is (Kann so bleiben)
- revert to this (Übersetzung zurücksetzen)
- 1 cheer for this edit. (1 Beifall für diese Bearbeitung.)
- No translations found. (Keine Übersetzungen gefunden.)
11anglemark
>9 timspalding: Those were mostly off the top of my head, I'm not sure that "edit" really has caused any actual problem, but one that is really causing problems is "event", because "historical event" and "literary event" do not use the same word in Swedish. In the future I can point such out when I encounter them.
12knerd.knitter
>10 birder4106: You would have to click the Translate link in the top right when you're on that page to get to the page with only that page's translations, if that makes sense. So go to any page, click Translate in the top right, then click Translate in the top right again.
