I have a specific request regarding localization that I will describe below. Before that, however, I would like to point out that there have been many requests for small improvements in localization. Some of these requests have been answered (thanks!) but many remain unaddressed. I think that AppSheet may tend to look at the number of votes for localization requests and get the impression that because the number for individual types of localization are small, not many creators need these changes. That, of course, is a problematic assumption because we only have a limited number of votes. Also, as the AppSheet platform because increasingly international, I think it should be clear that the need for improved, more comprehensive localization will continue to grow.
My proposal to colleagues such as @Fabian , @Steve_Fuller , @tsuji_koichi and others who have expressed an interest in improved localization is to unite and form a “localization” union! I’m half kidding but half serious. I think that if we make separate, individual requests for incremental improvements in localization, it’s going to take a very long time to get major improvements. If, however, everyone who is interested in making multilingual apps or apps that adjust easily to the location of linguistic choice of the user can come together behind one request (this one?) we have a better chance of getting AppSheet’s attention. If you agree and you think this request that I’m making is OK for that purpose, please vote for this and ask your multilingual friends to vote too.
Now, here are some examples of other related requests that have been made:
Localize for "Local changes have not been synced. Proceed anyway?" Questions
[image]
This message will Pop Up for example when you leave your actual App via LINKTOAPP() and still have changes to be synced.
Localize for "Accept" Feature Requests
Please enable Localization for “No” and “Accept” in the app use consent page.
[image]
Localize for "App Gallery" Questions
I would like to translate the term “App Gallery” via Localize.
[image]
Localize for "App Gallery" and "Add Shortcut" Feature Requests
In Menu we have “App Gallery” and “Add Shortcut”.
I would like to translate them in my Language.
[image]
Localise Confirmation Messages Feature Requests
In the Copy Action we can set the Display name dynamically to adjust for a User Setting for Language
[Screenshot 2019-12-18 at 14.31.29]
However, the confirmation text is not dynamic.
[Screenshot 2019-12-18 at 14.31.41]
Any chance this can be changed?
Address type fields to localize the address value displayed as option Feature Requests
Address type is useful and give the list of options for address value as we keep typing in the value into the field. (Assuming Google Map API coud be running in the backend…)
It is clever enough, but it is also troublesome as it is always converted the address to English all the time. For instance, I type address in Japanese, then tooptips with address value pops up below the fields, it is picking up the right address value, but it is in English terms all the time. User should expect the opt…
And here’s the specific issue I noticed today:
We are able to localize (choose the language for) “About” in the side menu. However, we are not able to use expressions to make adjustments to Info → Properties → Information for App Users, which controls what will be shown when the user taps on “About.”
UX → Localize, however, does allow such expressions. Please make it possible for us to use expessions in Information fo App Users in the same way. I have two reasons for requesting this. One is that my app is bilingual and I would like to choose the language according to the setting. The other is that I want the “About” menu to direct the user to another part of that app, but the location can be changed using settings I have made for the user so I want to be able to make the message adjust automatically using and expression.
Thanks!
... View more