microsoft / advanced-formula-environment

Create, edit, and reuse formulas in Excel
https://aka.ms/get-afe
MIT License
113 stars 11 forks source link

Support multiple locales #3

Open jack-williams opened 2 years ago

jack-williams commented 2 years ago

This issue is used to track the popularity of adding multiple locale support. Feel free to provide relevant feedback, or indicate support with a 👍. We can make no guarantees about supporting such a feature, but your feedback is greatly appreciated, and will help prioritize any work we undertake.

4tti commented 2 years ago

Absolutely required feature for multi-regional companies!

Pasark commented 2 years ago

Would be nice to have support for locales that use semi-colon(;).

petepan commented 2 years ago

I dont know if me adding a comment will do much difference, but i say, hear hear!

maninweb commented 2 years ago

My first suggestion is to support ; as list separator and/or add a setting so that a user can define/select that character by him/herself, if e.g. the list separator can not be retrieved from the windows settings.

My second suggestion is to add the localization of the Excel functions, as many people out there use Excel in their language and AFE currently only knows the english Excel functions.

My third suggestion is to localize AFE itself to different languages.

FrankFromGermany commented 2 years ago

English is now spoken by less than 400 million people as a mother tongue. If the second language speakers are added (a good 600 million), the number is 1 billion plus speakers. World population is about 8 billion. Do you really want to discriminate nearly 7 billion people? ☹

ovdlende commented 2 years ago

Localization ( ; instead of ,) is an must. Unusable otherwise.

noschinl commented 2 years ago

Since unfortunately Excel does not allow changing the formula language by its own, I believe supporting the different formula languages is criticial - otherwise I am unable to use it. Localized UI would be nice, but not critical for me.

patrikvk commented 2 years ago

For me, English only is quite OK as language support.

But locale support is really required for it to be usable at all - in the form of correct separator (system separator) and preferably also auto-translation / recognition of the function library similar to FormulaLocal in VBA.

Until other locales are supported I recommend a line in the description stating that English system settings are required for functionality.

Thanks for your efforts!

KyeRamos commented 2 years ago

It really needs to have support for locales that use semi-colon(;).

phobo3s commented 2 years ago

Must have feature for many compaines around the World. The seperator "," to ";" support is urgently needed at least.

jotapece commented 2 years ago

Please, hurry up!

TNielsen86 commented 2 years ago

Would be nice to have support for locales that use semi-colon(;).

I have exactly the same Issue, im using a Scandinavian version of O365 and when i try to use AFE i can import Functions from text and URL's but AFE will not sync to Name manager because of my language settings, If i then do replace all Commas"," to Semicolons ";" and then save it again. then everything after the first Semicolon disappears without warning. so for us not using American language Setting the Name manager is still a better option.

This issue should be prioritized and it would be nice if AFE when Importing from Github Gist automatically would identify Origin language setting and convert to the users language setting Automatically

Please solve this fast.

JackDMF commented 2 years ago

If locale support is not easily achieved, maybe it is a solution to convert from formula using e.g. ";" to AFE using ",". That way you would not need to find an alternate solution for the formula delimiting ";" in AFE.

jack-williams commented 2 years ago

I am working on an update to AFE that will support loading and saving with workbooks in locales using ";" as an argument separator. Within AFE, you will still be required to write formulas using ",", however with the update we will do the translation on read and write to the workbook.

The update may include support for function name localisation for some locales. No confirmation yet. In the case that we do not provide function name localisation, we will disable English autocomplete, as well as errors for unrecognised English names.

I appreciate that this is not a complete solution, but it will enable the use of AFE for workbooks using ";". Today, AFE is completely broken if you try to interact with workbooks using ";".

Further stages of localisation, such as writing within AFE using ";" require significantly more work, which is why this is not included in the proposed work.

ergru commented 2 years ago

I say hear hear, it it very useful to have localisation and make it work with " ; " as argument separator. Otherwise its to much of a pain to change every instance in formulas in order to use this tool and hence not useful. Otherwise it is a great add-on in excel.

jack-williams commented 2 years ago

We have just updated AFE to support some localization, in particular:

We'll be adding support for authoring in AFE using ; in an upcoming release.

jack-williams commented 1 year ago

We have just released an update than now allows you to author formulas using the locale's separators.

image

In the modules tab, use ;; to separate definitions when ; is the argument separator:

IFOMITTED = LAMBDA(value; value_is_blank; IF(ISOMITTED(value); value_is_blank; value));;

example = IFOMITTED("hello"; "world");;
vsoler commented 1 year ago

Thank you indeed !!!

KDean-Dolphin commented 1 year ago

Is the localization API publicly available? I'm considering developing an add-in for a multinational client that would install and automatically update a LAMBDA functions library and localization is a critical requirement.

jack-williams commented 1 year ago

The localization we use is not available as an API. If it fits within your constraints, one workaround might be to use the range API to translate:

(I've not checked if this works).

KDean-Dolphin commented 1 year ago

I'll look into that, thanks.

phish108 commented 7 months ago

see also #78