• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Translation errors
#1
Hello Mike,


This is my first post on this forum and I would like to make my first contribution as a French speaker, pointing out some translation errors. The manual is very well done; I haven’t found anything objectionable so far. But in the windows of the software in French version, I have to point out two problems.

1) The phrase ‘Automatically crop pages’ has been translated to ‘Appliquer à automatiquement les pages’, which is incomprehensible. The correct translation is ‘Rognage automatique des pages’.


2) ‘Half-page’ has been translated to ‘Demie-page’ instead of ‘Demi-page’.

These errors appear in several places in the software.

Cordially,

Luc
Luc
Reply
#2
Thank you Luc. I will look into making those fixes. 

Mike
Reply
#3
Hereunder my contribution of today. For your information, the habit of capitalising each word in a title is unique to the English language. In French, only the first letter of the title is capitalised.

In the settings of the library, I also found:
Ouvrir Automatiquement la Morceau Suivante ---> Ouvrir automatiquement le morceau suivant
Ignorer la Vue des Groupes ne Contenant qu'une Morceau ---> Ignorer la vue des groupes ne contenant qu'un morceau

In the settings of ‘Morceaux’:
Afficher Morceau Suivante ---> Afficher le morceau suivant

Cordially,

Luc
Luc
Reply
#4
Thanks - I've updated the translation.

Mike
Reply
#5
Today I found two errors in the settings ‘Paramètres pédale et tactile’ / ‘Paramètres de la pédale d'actions’ / ‘Action’:
Revenir à la morceau précédente ----> Revenir au morceau précédent
Aller à la morceau suivante ----> Aller au morceau suivant

It seems that in several places we find the word ‘Morecau’ in the feminine, while this noun is masculine. I will probably find other occurrences in the course of my discoveries.
Luc
Reply
#6
Thank you for the updates - let me know if you see any more entries that need updating.

Mike
Reply
#7
OK Mike, I will do it step by step.

In the settings: ‘Morceaux’ – ‘Utiliser le Slider… ---->" Utiliser le curseur… »
« Change le comportement du slide… » ----> « Change le comportement du curseur… »

You will probably find other occurrences of ‘slider’ or ‘slide’ which should be replaced by ‘curseur’.
Luc
Reply
#8
If you would like a copy of the translation file that you can just update as you come across things and then you can send me back the translation file periodically, that is another option. Then you wouldn't have to report each change to me on the forum. Let me know what you prefer.

Mike
Reply
#9
It is an excellent idea! I am very enthusiastic about your software, and I would be happy to contribute my collaboration in a better organized way. You can send me this file, and I will gladly resent all the linguistic problems of the French version.

Luc
Luc
Reply
#10
As I wrote in another post :

"Nouveau collection" is wrong in French : "Nouvelle collection" because the word is "feminin"
Reply
#11
The same label is used for every type of group, as it's formatted like "New {0}" where the group name is inserted in place of the {0}, so "New Setlist", "New Collection", etc. Dealing with language specific genders for different group names is too much of a problem to deal with.

Mike
Reply
#12
Maybe an abbreviation "Nouv." would satisfy all?
Reply
#13
(03-23-2025, 03:33 AM)BRX Wrote: Maybe an abbreviation "Nouv." would satisfy all?

Why not Big Grin

Don't you use a framework ?
I used a translation file, more flexible for collocations and sentences.

New = Nouveau
New list = Nouvelle liste
New user = Nouvel utilisateur
Reply
#14
Sure, I use a framework that is different on every platform, but the idea is the same. In English, it's something like "New {0}" (this is the Windows format) and then in the code, it just replaces {0} with whatever "new" thing I'm inserting. This works perfectly fine in English, and in many other languages. I don't want to create a separate translation entry for every possible "new" thing I could be dealing with, and then having to take generic code and turn it into code specifically for each object, as it would then have to look up the translation specifically for that object (and get translations for all 18 languages to handle each of those new entries). That's why I said it's more trouble than it is worth in my opinion. If users complain about it in languages other than French, and it is bothersome in many places, then I can consider all of these changes, but I have limited bandwidth and would rather apply it to requests that provide functionality.

Mike
Reply




Users browsing this thread:
2 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2025 MyBB Group.