-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default to display field when first setting labels enabled on a layer #30245
Conversation
Good one! |
Would it be overthinking it to add a few translated strings in there? French, German, etc.? |
Why not using a tag list like in processing algorithms? So the list is translated and it's easy to add more in transifex. |
OK, translated list it is! (although I wonder how a translator would ever interpret the string "name,desc,street,road,id" correctly, without any additional context...) |
-1 as it currently is.
I'm not sure how to deal with the last one (configurable list?) but I would hate to let the English list go in favour of only a translated one. |
To translate tag list, I personally keep original words in English then complete with translated. That way, knowing an alg reference in English or French, I'm sure it'll be found in the toolbox. |
Yes, I was going to add what @DelazJ said. It's what we do for French in Transifex. It's not done by all translators unfortunately I think. Something to add the translation guidelines? It would be nice to get the untranslated string automatically and to merge translated and untranslated in the application but it seems not possible: https://stackoverflow.com/questions/31613339/qt-convert-translated-text-to-english @m-kuhn I agree with your points except:
Because you are from Switzerland and you are internationals and multi-linguist there ;-) I worked one year in one small French administration, 99% of fields names and data schemas were in French ;-) |
Sorry, what I meant to imply is adding translated names, not translatable strings :) Ie, name,nom,heibt, etc. :) |
How do you decide the languages to use? |
I'd be arbitrary, take say the top 5 languages across the globe, derived from latin (the latter being an historical restriction pre unicode). That or the top 5 language derived from our user base. |
Let's not go the Excel way where data is interpreted based on the locale |
wouldn't it make sense to actually use the user's language? |
That could make sense. QStringLiteral( "name" ) << tr( "name" ) << ... |
That said, I'd still go for a few hardcoded translations. QStringLiteral( "name" ) << QStringLiteral( "nom" ) << ... << tr( "name" ) ... That'd be the most flexible way forward. |
enabled on a layer Helps with new users -- they see an immediate effect after setting labels enabled on a layer
…ndidates" This reverts commit bb6993f.
(harcoded) localized versions See discussion at qgis#30245
83e90aa
to
2ad2514
Compare
Ok, going for a hardcoded list of strings, including localized ones. Let's see if this works in practice and revisit if needed. |
Helps with new users -- they see an immediate effect after setting labels enabled on a layer