[Turkish] l10n issues

[emir_sari]

Hello,

I thought I’d start a topic to document the l10n issues I’ve encountered in Fusion. These might apply to the other AutoDesk products as well.

1. Menu names

macOS standart menu names use “Düzen” and “Görüntü” for “Edit” and “View” menu names respectively. Below they are translated as “Düzenle” and “Görüntüle”, which is a common mistake when there is no context provided to the translators. Please refer to the standard macOS application translations to confirm this. Since the menus are visible all the time in macOS, it really gives an unprofessional vibe to the software.

2. Failure to properly capitalise Turkish İ

As you can see below, Animasyon is supposed to capitalise as ANİMASYON, since the capital form of i in Turkish is İ, not I. It looks like the locale-honouring `toUpperCase` needs to be used here, not the standard one. This is valid for all the other strings too, like DEĞİŞTİR, BİRLEŞTİR on the ribbon, they all miss the capital dotted İ.

3. Percent value is prepended in Turkish.

Here (and in all other possible places), the percent value needs to be prepended in Turkish. 100% is wrong, %100 is correct. There is an automatic percent formatter in ICU that can be used for this purpose, it will format according to all possible percent formats in other locales too.

4. “Unnamed” translation

This is a bit of a personal choice maybe but since the dawn of the Turkish locales in Classic Mac OS 7 and Windows 3.1, “Unnamed” was translated as “Adsız”. In Fusion, it is “İsimsiz”, which is not so much used in computer lingo, and it is a loan-word. It might sound more appropriate if “Adsız” to be used, more common for sure.

[lance.carocci]

Thanks for the detailed report, @emir_sari! I have notified our localization team. Please note that, due to our development cycle and string freeze, these changes will likely not be reflected in the app until late spring.

[emir_sari]

Thank you, appreciated!

[emir_sari]

Some more:

 MidPoint can be translated as “Orta Nokta”.

 This is more of a code-issue, but honouring language-specific decimal separators would be really nice. Many languages use comma as decimal separator.

 I’ve noticed buttons use “Title Case”, here there’s an exception.

 Labels use “Sentence case”, but here and in many preference panes, they use “Title Case” which look out of place, and not cohesive.

 

Mesh is not translated in many instances. There are places that it is translated, so looks inconsistent (“Örgü”?).

 “Loft” is not translated. “Yüzey Geçişi”?

 

Here “Sentence case” looks inconsistent.

 “Rip” is not translated. “Yırt”?

 Two issues here, first one is the also above mentioned Turkish İ capitalisation error (should be “ESKİZ PALETİ”), and second issue is, “Linetype” is not translated. “Çizgi Türü” should suffice I think.

 Here “Redo Equal” part has an issue in Turkish. Due to Turkish word order, verb comes last, so we generally use a form here like “Undo: Equal” or “Redo: Equal” with colon to indicate context. Therefore it looks like an error here. For undo/redo plus variable structure, a colon is needed for Turkish.

Also, Redo is generally translated as “Yinele” nearly in all Turkish l10n, “Tekrarla” works, but it’s a bit colloquial, and a loanword. But this is up to the translator’s discretion I guess.

[vladimir_michl]

I believe this is a useful feedback for the localization team. As for the decimal separators, there are deeper consequences and technical software apps usually keep the decimal separator at "." and list separator at "," even if local settings are different. Let's not show users decimal comma as it might raise false expectations how numbers and lists are expected in the application's input boxes.

Vladimir Michl, www.arkance.world  -  www.cadforum.cz
(authors of the Fusion CZ addon localization)

[emir_sari]

One more that I missed; in preferences the translations for “Animate view transitions” (I think, as per the tooltip) denotes a meaning like “Do not animate view transitions”. In Turkish, “Canlandırma” can mean both “Animation” and “Do not animate” depending on the stress of the word and the context. I think the translator tried to keep it neutral as “Animating view transitions”, but it ended up meaning “Do not animate view transitions”. 

The solution would be to just use imperative case, like, “Görünüm geçişlerini canlandır”.

 In the update notification, there is a stray (I believe) percent sign that is appended to the 3.

Also, as a general visual improvement, why not use typographical apostrophes (’) and “quotes” instead of plain ones. They make the text look very professional. This can be applied for other Unicode signs too, like using proper “minus sign” and en/em dashes where appropriate instead of plain -.

For instance,

on the title bar, em dash could be used, instead of plain -, since it is used to separate phrases and sections of the text.

 

 

[lance.carocci]

@vladimir_michl @emir_sari, the decimal notation can be configured in application preferences. If you find a command not respecting this preference, please let us know.

[vladimir_michl]

Oh, thanks! Never noticed that. I stand corrected.

Is it reliable across add-ons, exports/imports?

Vladimir Michl, www.arkance.world  -  www.cadforum.cz

[lance.carocci]

I don't believe so, but admittedly I am not very familiar with our API. I imagine addon devs would need to check the state of this preference and factor it into their functionality.

To be honest, I am not sure if the preference is purely cosmetic on the UI side, or if it extends to file export/import, too. I can give this a try at some point, but if you get to it first, please share your findings.

[lance.carocci]

---

Also, as a general visual improvement, why not use typographical apostrophes (’) and “quotes” instead of plain ones. They make the text look very professional. This can be applied for other Unicode signs too, like using proper “minus sign” and en/em dashes where appropriate instead of plain -.

---

The Autodesk style guidelines have us using sans-serif fonts in our applications, of which Fusion on Windows is a mix of Arial and our own Artifakt font, so those sorts of details are omitted by design. I get where you are coming from - users have requested the ability to swap fonts to improve legibility, but unfortunately it is not something supported at this time.

The use of the hyphen in the titlebar instead of en or em dash is a result of following established OS conventions, which generally use the hyphen to separate the current page/tab from the website/app name. At least on US keyboard layouts, we don't have quick access to en/em dashes, while the hyphen lives at shift+_, so I think it won out over the years due to convenience of not needing to open a character map or html encoding to utilize it.

[emir_sari]

Thanks for the explanation, appreciate it.

A couple of more errors I’ve found:

 

Here, “4 Kenarlar” means “4 Edges”, but we don’t actually say it like that. Unlike English, in Turkish plural forms associated to a value do not get plural suffix, therefore this one, and all the other similar examples should omit the “lar” plural suffix. “4 Kenar” is the correct version.

 

“Önbellek verilerini temizle” should use “Title Case”.

 

Default version explanation/description should be “Kullanıcı kaydetti”. The current one reads as “The user has been saved”.

[emir_sari]

 

The translation for “Delete” is missing (“Sil”).

 “Eskiz Kısayollar” is an ambiguity in Turkish. It ought to be “Eskiz Kısayolları” (Sketch Shortcuts).

 

macOS application menu does not use localised strings. This is likely an issue for all languages. Fusion might ought to use a more native application instance on macOS.

[emir_sari]

“Bulucuda Göster” (Show in Finder) is a bit of a funny mistake, because it tries to translate the application name, “Finder” of macOS, which is never ever translated. The correct phrase is “Finder’da Göster”. 

[emir_sari]

 In Quick Setup, “I am new in CAD” (or whatever was the English string) is translated as “It is a new thing in CAD”. Instead, it should be “CAD’de Yeniyim”.

[emir_sari]

“Offset Plane” (noun) is translated as “Düzlemi Dengele”, which indicates an action. Common when there is no context I guess. Instead it should be translated as a noun, like maybe “Ofset Düzlem” veya “Kaydırılmış Düzlem”? 

[emir_sari]

 All the commands here except “Sweep” and “Emboss” use the imperative addressing as it is common. However, these two commands use the verb form. Instead they should be “Süpür” and “Kabart” to be in line with the rest of the actions.

[emir_sari]

“Önizleme Sınırları” means something like “limits of the preview”, due to insufficient context I believe, “Preview” is used as a verb if I’m correct. The correct translation should be “Sınırları Önizle” which is “Preview (the) Limits”. 

 

[emir_sari]

@lance.carocci, just pinging to check if my later messages are being handled over to the localisation team. I’d like to continue reporting :).

[emir_sari]

“Fit Point Spline” is translated as “Nokta Eğrisini Sığdır”, again, translated as an action rather than a noun. “Uyum Noktası Eğrisi” maybe would be appropriate?

[emir_sari]

 

There are three different translations for “Pattern” here. Normally, in this context it would be ideal to translate is as “Örüntü” veya “Dizgi”, hence the action of “dizmek”. “Dizi” is acceptable, but in two instances “Desen” is used, which is mostly used in context for textures and other image-related stuff. It needs to be sorted out.