Add Place Detail for Better Translations
LegacyUser
✭✭✭✭
Jordi Kloosterboer said: I was thinking about how FamilySearch is adding support for many new languages and thinking about how place names are shown. Currently, displayed places and dates are not translating when the site is changed to a different language, even if the displayed place is exactly the same as the standardized place.
What the site does right now when a place and date has been typed in English shown on the English site and the German site:
With a place exactly the same as the standard place:
With a place not exactly the same as the standard place (in this case a place detail before the place):
Notice that the display name does not change, but the standardized name can change (if the standardized place is set up to support the other language).
To support other languages, they should see as much as possible of the place in their own language.
Dates that are inputted exactly the same as the standardized version should automatically translate to the other language version.
If the date does not look exactly the same as the standardized version, then it will do what the site currently does for that, and it won't be shown translated. (only the standardized date will show translated when editing the event (or wherever else the standardized date is shown instead of the display date)).
The same should happen with the place names.
What the site could look like in the future:
With a place detail and a place exactly the same as the standard place:
With a place detail and a place exactly the same as the standard place:
Obviously, to take full advantage of this, current places would have to be converted. For many already in the format of place detail, standard place, this is easy for a program to convert; others would have to manually converted when people see the record. And of course, it does not need to be converted, only for completeness.
What the site does right now when a place and date has been typed in English shown on the English site and the German site:
With a place exactly the same as the standard place:
With a place not exactly the same as the standard place (in this case a place detail before the place):
Notice that the display name does not change, but the standardized name can change (if the standardized place is set up to support the other language).
To support other languages, they should see as much as possible of the place in their own language.
Dates that are inputted exactly the same as the standardized version should automatically translate to the other language version.
If the date does not look exactly the same as the standardized version, then it will do what the site currently does for that, and it won't be shown translated. (only the standardized date will show translated when editing the event (or wherever else the standardized date is shown instead of the display date)).
The same should happen with the place names.
What the site could look like in the future:
With a place detail and a place exactly the same as the standard place:
With a place detail and a place exactly the same as the standard place:
Obviously, to take full advantage of this, current places would have to be converted. For many already in the format of place detail, standard place, this is easy for a program to convert; others would have to manually converted when people see the record. And of course, it does not need to be converted, only for completeness.
0
Comments
-
Bosch said: They should be shown not in the language of the program but in the language of the browser. That is the way it's working in memories, and I like that because FS in not in my language and I really appreciate to see the places names of my land in my language instead of foreign languages.0