Fields "Translation of the lettering" are show only in Numista in English

In this page in English N#12236 are show all filled fields, for example:

Obverse
Text around hole in center
Lettering: สยามรัฐ ๑/๒ สตางค์
Translation: Siam 1/2 Satang

Reverse
Date around top half of hole in center of a design - A Sudarshana Chakra of Lord Vishnu which is used as the symbol of Chakri Dynasty.
Lettering: พ.ศ.๒๔๘๐
Translation: BE 2480 (AD 1937)

In the Spanish version are show only:

Anverso
(en) Text around hole in center
Leyenda: สยามรัฐ ๑/๒ สตางค์

Reverso
(en) Date around top half of hole in center of a design - A Sudarshana Chakra of Lord Vishnu which is used as the symbol of Chakri Dynasty.
Leyenda: พ.ศ.๒๔๘๐

and similar in French:

Avers
(en) Text around hole in center
Inscription : สยามรัฐ ๑/๒ สตางค์

Revers
(en) Date around top half of hole in center of a design - A Sudarshana Chakra of Lord Vishnu which is used as the symbol of Chakri Dynasty.
Inscription : พ.ศ.๒๔๘๐

Because the fields Translation of the lettering are empty in Spanish and French versions.

Descriptions are copied from English version with "(en)" suffix. Can be do same with translation fields? For example, in Spanish page:

Anverso
(en) Text around hole in center
Leyenda: สยามรัฐ ๑/๒ สตางค์
Traducción: (en) Siam 1/2 Satang

Reverso
(en) Date around top half of hole in center of a design - A Sudarshana Chakra of Lord Vishnu which is used as the symbol of Chakri Dynasty.
Leyenda: พ.ศ.๒๔๘๐ 
Traducción: (en) BE 2480 (AD 1937) 

Would be smart indeed!

And the other way too (if english is empty, display french content)

Hello,
The reason this is not implemented is that it could be weird in some context.
For example, if the coin as lettering in Thai, it would be nice to show the translation into English from the English catalogue.
However, if the coin has lettering in Spanish, it would be weird to show the translation into English.

I'm not sure how to handle that.

Xavier

Hello,
The reason this is not implemented is that it could be weird in some context.
For example, if the coin as lettering in Thai, it would be nice to show the translation into English from the English catalogue.
However, if the coin has lettering in Spanish, it would be weird to show the translation into English.

I'm not sure how to handle that.

I dont think it would be that weird as we would have the (en) prefix. Not weirder than for other fields imo

davidhs

 

Descriptions are copied from English version with "(en)" suffix. 

This is commonly seen on the French version
(fr) on the English version does not stay long

It does look weird to me. See the mockup below. As a French user on a website in French, I would be surprised that the website is helping me to understand the lettering in French.

Or you could assume it's just a translation into English. French visitors would just not care and that would be acceptable…

I understand. I didnt have this usecase in mind: when the translation field is let empty simply because there is no need for translation as the text is fully legible already in the language of the website.

Pulling this thread, I'd say that “translation” field should be have an opted in display (to distinguish when it's empty by choice and empty by lack of info):

- either by selecting a language attached to the very coin (if french, then the field is hidden as the unabridged legend is sufficient)

- either by letting entries creator check a box ("is a translation needed")

My solution to this is to add translations manually to the text translation field.

In time, I will manually add French translations to some entries, so that they are all in English and in French. I tested this out a while back and posted a request for comments or criticism on the French forum. The lack of any replies would indicate that my French translation is sufficient.

CREPOSUC

davidhs

 

Descriptions are copied from English version with "(en)" suffix. 

This is commonly seen on the French version
(fr) on the English version does not stay long

This is always seen on the Spanish version😅 (Spanish version has not edition page for now).

Compendium

I understand. I didnt have this usecase in mind: when the translation field is let empty simply because there is no need for translation as the text is fully legible already in the language of the website.

Pulling this thread, I'd say that “translation” field should be have an opted in display (to distinguish when it's empty by choice and empty by lack of info):

- either by selecting a language attached to the very coin (if french, then the field is hidden as the unabridged legend is sufficient)

- either by letting entries creator check a box ("is a translation needed")

The first option can use the field Script (if is empty can be assume is the user language).

The second option (the check box) looks more easy but will be need a checkbox for each Numista language (en, fr, es,…): the translation can be need in Spanish and French and not in English.

Hibernia

My solution to this is to add translations manually to the text translation field.

 

In time, I will manually add French translations to some entries, so that they are all in English and in French. I tested this out a while back and posted a request for comments or criticism on the French forum. The lack of any replies would indicate that my French translation is sufficient.

As I write before, this is not possible to do in Spanish, and always is need display the English translation (or French if the English if empty). Except in objects in Spanish, of course (but is a minor problem see a translation “(en)” in objects in Spanish, that do not see any translation in objects in Thai and many other 😉).

Script is not language: latin alphabet dies not indicate which language is used

Compendium

Script is not language: latin alphabet dies not indicate which language is used

You are right! 😮

Can be your first option

Compendium

I understand. I didnt have this usecase in mind: when the translation field is let empty simply because there is no need for translation as the text is fully legible already in the language of the website.

Pulling this thread, I'd say that “translation” field should be have an opted in display (to distinguish when it's empty by choice and empty by lack of info):

- either by selecting a language attached to the very coin (if french, then the field is hidden as the unabridged legend is sufficient)

- either by letting entries creator check a box ("is a translation needed")

adding a new select box “Translation is not needed in” (with options: “None”, and the languages of Numista, English, French, Spanish…). Default value “None”.

At beginning all will be empty (“None”) and the (fr) will be displayed in English interface. Then, members can changed the option to “English”.

And the Numista Robot https://en.numista.com/forum/topic78271.html can set the option correct according the language of the country. For example, set  to “French” in all objects from France.

Language on coin is new proposed feature. I guess it could provide data for showing or not showing translation field in some website languages in theory.

Xavier

It does look weird to me. See the mockup below. As a French user on a website in French, I would be surprised that the website is helping me to understand the lettering in French.

 

Or you could assume it's just a translation into English. French visitors would just not care and that would be acceptable…

Put these entries in “Contribute” section… but only those that comply with users Settings/Public profile/Languages/Favourite language:

LP

What about coins with French and English language on it like we frequently have in Canada ?

The translation fields are left empty, but only for the spanish pages a translation will be needed… if I get you right ?

Exemple : 5 dollars 

There's no easy solution to please everyone !

Regards,