You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: powerapps-docs/maker/canvas-apps/global-apps.md
+27-25Lines changed: 27 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,12 +17,12 @@ search.app:
17
17
# Build global support into canvas apps
18
18
Power Apps is a global product. You can build and use canvas apps in many different languages and regions.
19
19
20
-
Both while building and running apps, the text displayed by Power Apps has been translated into a variety of languages. You will see menu items, dialog boxes, ribbon tabs, and other text in your native language. Typing in and displaying dates and numbers is also adapted for your particular language and region. For example, some regions of the world use a **.** (dot or period) as the decimal separator while others use a **,** (comma).
20
+
Both while building and running apps, the text displayed by Power Apps has been translated into different kinds of languages. You'll see menu items, dialog boxes, ribbon tabs, and other text in your native language. Typing in and displaying dates and numbers is also adapted for your particular language and region. For example, some regions of the world use a **.** (dot or period) as the decimal separator while others use a **,** (comma).
21
21
22
-
The apps you create can be globally aware as well. Use the **[Language](functions/function-language.md)**, **[Text](functions/function-text.md)**, **[Value](functions/function-value.md)**, **[DateValue](functions/function-datevalue-timevalue.md)** and other functions to adapt what is displayed and used as input in different languages.
22
+
The apps you create can be globally aware as well. Use the **[Language](functions/function-language.md)**, **[Text](functions/function-text.md)**, **[Value](functions/function-value.md)**, **[DateValue](functions/function-datevalue-timevalue.md)**, and other functions to adapt what is displayed and used as input in different languages.
23
23
24
24
## Language settings
25
-
When using the native studio or a native player, the language used is provided by the host operating system. For Windows, this can be controlled under "All Settings" and then "Time & language" settings. Windows also allows you to specify the characters to use for the decimal separator, overriding the language setting.
25
+
When using the native studio or a native player, the language used is provided by the host operating system. For Windows, this setting can be controlled under "All Settings" and then "Time & language" settings. Windows also allows you to specify the characters to use for the decimal separator, overriding the language setting.
26
26
27
27
When using the web experiences, the language used is provided by the browser. Most browser default to the host operating system's setting with some also providing a way to set the language manually.
28
28
@@ -32,23 +32,23 @@ The authoring environment adapts to the language setting of the author. The app
32
32
### Names in formulas
33
33
Most elements in formula are always in English:
34
34
35
-
* Function names: **If**, **Navigate**, **Collect**, ...
36
-
* Control property names: **Screen.Fill**, **Button.OnSelect**, **Textbox.Font**, ...
* Signal records: **Compass.Heading**, **Location. Latitude**, **App.ActiveScreen**, ...
39
-
* Operators: **Parent**, **in**, **exactIn**, ...
35
+
* Function names: **If**, **Navigate**, **Collect**, and so on.
36
+
* Control property names: **Screen.Fill**, **Button.OnSelect**, **Textbox.Font**, and so on.
37
+
* Enumeration names: **Color.Aqua**, **DataSourceInfo.MaxValue**, **FontWeight.Bold**, and so on.
38
+
* Signal records: **Compass.Heading**, **Location. Latitude**, **App.ActiveScreen**, and so on.
39
+
* Operators: **Parent**, **in**, **exactIn**, and so on.
40
40
41
41
As the authoring experience is localized, control and other object names will appear in the native language of the author. In Spanish, some of the control names appear as:
42
42
43
-
43
+
![Control names in Spanish](media/global-apps/insert-controls-es.png"Control names in Spanish")
44
44
45
-
When you insert one of these into your app, their name will default to English. This is done for consistency with the control property names and the rest of the formula. For example, **Casilla** listed above is inserted as **Checkbox1**.
45
+
When you insert one of these controls into your app, their name will default to English. This change is done for consistency with the control property names and the rest of the formula. For example, **Casilla** listed above is inserted as **Checkbox1**.
46
46
47
-
After a control is inserted, you can change the name to whatever you like. While selected, the far lefthand side of the "Content" ribbon displays the name of the control. Selecting this name drops down a text box where you can edit the name:
47
+
After a control is inserted, you can change the name to whatever you like. While selected, the far left-hand side of the "Content" ribbon displays the name of the control. Selecting this name drops down a text box where you can edit the name:
48
48
49
-
49
+
![Experience in Spanish](media/global-apps/control-rename.png"Experience in Spanish")
50
50
51
-
If you like, here you can rename the control to **Casilla1**. The red squiggly, in this case displayed by a browser, is because the name is not a Spanish word and is of no concern.
51
+
If you like, here you can rename the control to **Casilla1**. The red squiggly, in this case displayed by a browser, is because the name isn't a Spanish word and is of no concern.
52
52
53
53
You can use whatever names you like for:
54
54
@@ -72,15 +72,15 @@ The change in the Power Apps list separator is consistent with what happens to t
72
72
73
73
For example, consider the following formula expressed in a language and region that uses dot or period as the decimal separator, such as Japan or the United Kingdom:
74
74
75
-
75
+
76
76
77
77
Now view this same formula in a language and region where a comma is used for the decimal separator, such as France or Spain:
78
78
79
-
79
+
80
80
81
-
The highlight shows the operators that change between the two versions. Note that the property selection operator **.** (dot or period) in **Slider1.Value** is always the same, no matter what the decimal separator is.
81
+
The highlight shows the operators that change between the two versions. The property selection operator **.** (dot or period) in **Slider1.Value** is always the same, no matter what the decimal separator is.
82
82
83
-
Internally the formula does not change, all that changes is how it is displayed and edited by the author. Two different authors using two different languages can view and edit the same formula, with each seeing the appropriate separators and operators for their language.
83
+
Internally the formula doesn't change, all that changes is how it's displayed and edited by the author. Two different authors using two different languages can view and edit the same formula, with each seeing the appropriate separators and operators for their language.
84
84
85
85
## Creating a global app
86
86
The app you create can adapt to different languages, providing a great user experience for your users around the world.
@@ -90,13 +90,15 @@ The **[Language](functions/function-language.md)** function returns the language
90
90
91
91
Among other things, you can use **Language** to display translated text for your users. Your app can include a table of translated values in your app:
92
92
93
-
93
+
![Table with localized text](media/global-apps/loc-table.png"Table with localized text")
94
94
95
95
And then use a formula such as the following to pull translated strings from the table:
Be aware that translated strings in other languages could be significantly longer than they are in your language. In many cases, the labels and other elements that display the strings in your user interface will need to be wider to accommodate.
101
+
Translated strings in other languages could be longer than they are in your language. In many cases, the labels and other elements that display the strings in your user interface will need to be wider to accommodate.
100
102
101
103
For more information, see the documentation for the **[Language](functions/function-language.md)** function.
102
104
@@ -107,10 +109,10 @@ The **[Text](functions/function-text.md)** function formats numbers and dates us
107
109
108
110
**Text** requires a format string to know how you want to format the number or date. This format string can take one of two forms:
109
111
110
-
***A global aware enumeration.** For example, **Text( Now(), DateTimeFormat.LongDate )**. This formula will format the current date in a language appropriate format. This is the preferred way to specify the format string.
112
+
***A global aware enumeration.** For example, **Text( Now(), DateTimeFormat.LongDate )**. This formula will format the current date in a language appropriate format. This method is the preferred way to specify the format string.
111
113
***A custom format string.** For example, **Text( Now(), "[$-en-US]dddd, mmmm dd, yyyy" )** displays the same text as the enumeration when used in the language "en-US". The advantage of the custom format string is that you can specify exactly what you want.
112
114
113
-
The "[$-en-US]" on the front of the custom format string tells **Text** in which language to interpret the custom format string. This is inserted for you and defaults to your authoring language. Normally you will not need to change this. It is useful when authors from different languages are editing the same app.
115
+
The "[$-en-US]" on the front of the custom format string tells **Text** in which language to interpret the custom format string. This string is inserted for you and defaults to your authoring language. Normally you won't need to change this string. It's useful when authors from different languages are editing the same app.
114
116
115
117
The third argument to **Text** specifies which language to use for the result of the function. The default is the language setting of the current user.
116
118
@@ -120,15 +122,15 @@ For more information, see the documentation for the **[Text](functions/function-
120
122
There are four functions for reading numbers, dates, and times provided by the user:
121
123
122
124
***[Value](functions/function-value.md)**: Converts a number in a text string to a number value.
123
-
***[DateValue](functions/function-datevalue-timevalue.md)**: Converts a date value in a text string to a date/time value. Any time specified in the text string is ignored.
125
+
***[DateValue](functions/function-datevalue-timevalue.md)**: Converts a date value in a text string to a date/time value. Anytime specified in the text string is ignored.
124
126
***[TimeValue](functions/function-datevalue-timevalue.md)**: Converts a time value in a text string to a date/time value. Any date specified in the text string is ignored.
125
127
***[DateTimeValue](functions/function-datevalue-timevalue.md)**: Converts a date and time value in a text string to a date/time value.
126
128
127
-
If you have used Excel, all of these functions are combined in the single **Value** function. They are broken out here since Power Apps has separate types for date/time values and numbers.
129
+
If you have used Excel, all of these functions are combined in the single **Value** function. They're broken out here since Power Apps has separate types for date/time values and numbers.
128
130
129
131
All of these functions have the same arguments:
130
132
131
-
**String, required*: A string from the user. For example a string types into a **Text input** control and read from the control with the **Text** property.
133
+
**String, required*: A string from the user. For example, a string types into a **Text input** control and read from the control with the **Text** property.
132
134
**Language, optional*: The language in which to interpret the *String*. By default, the language setting of the user.
0 commit comments