Skip to content

Commit 254117a

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into privatelink-cli
2 parents d1f344a + 684f0c3 commit 254117a

File tree

11 files changed

+204
-20
lines changed

11 files changed

+204
-20
lines changed
Lines changed: 176 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,176 @@
1+
The table below shows a mapping relationship between X-SAMPA (Extended Speech Assessment Methods Phonetic Alphabet) and IPA alphabets. The X-SAMPA symbols are shown at left, with the corresponding IPA symbols to the right.
2+
3+
```txt
4+
x-sampa (L) ipa (R)
5+
a a
6+
b b
7+
b_< ɓ
8+
c c
9+
d d
10+
d` ɖ
11+
d_< ɗ
12+
e e
13+
f f
14+
g ɡ
15+
g_< ɠ
16+
h h
17+
h\ ɦ
18+
i i
19+
j j
20+
j\ ʝ
21+
k k
22+
l l
23+
l` ɭ
24+
l\ ɺ
25+
m m
26+
n n
27+
n` ɳ
28+
o o
29+
p p
30+
p\ ɸ
31+
q q
32+
r r
33+
r` ɽ
34+
r\ ɹ
35+
r\` ɻ
36+
s s
37+
s` ʂ
38+
s\ ɕ
39+
t t
40+
t` ʈ
41+
u u
42+
v v
43+
P ʋ
44+
v\ ʋ
45+
w w
46+
x x
47+
x\ ɧ
48+
y y
49+
z z
50+
z` ʐ
51+
z\ ʑ
52+
A ɑ
53+
B β
54+
B\ ʙ
55+
C ç
56+
D ð
57+
E ɛ
58+
F ɱ
59+
G ɣ
60+
G\ ɢ
61+
G\_< ʛ
62+
H ɥ
63+
H\ ʜ
64+
I ɪ
65+
I\ ᵻ
66+
J ɲ
67+
J\ ɟ
68+
J\_< ʄ
69+
K ɬ
70+
K\ ɮ
71+
L ʎ
72+
L\ ʟ
73+
M ɯ
74+
M\ ɰ
75+
N ŋ
76+
N\ ɴ
77+
O ɔ
78+
O\ ʘ
79+
Q ɒ
80+
R ʁ
81+
R\ ʀ
82+
S ʃ
83+
T θ
84+
U ʊ
85+
U\ ᵿ
86+
V ʌ
87+
W ʍ
88+
X χ
89+
X\ ħ
90+
Y ʏ
91+
Z ʒ
92+
. .
93+
" ˈ
94+
% ˌ
95+
_j ʲ
96+
' ʲ
97+
: ː
98+
:\ ˑ
99+
@ ə
100+
@\ ɘ
101+
@` ˞ɚ
102+
{ æ
103+
} ʉ
104+
1 ɨ
105+
2 ø
106+
3 ɜ
107+
3\ ɞ
108+
4 ɾ
109+
5 ɫ
110+
6 ɐ
111+
7 ɤ
112+
8 ɵ
113+
9 œ
114+
& ɶ
115+
? ʔ
116+
?\ ʕ
117+
<\ ʢ
118+
>\ ʡ
119+
^ ꜛ
120+
! ꜜ
121+
!\ ǃ
122+
| |
123+
|\ ǀ
124+
‖ ‖
125+
|\|\ ǁ
126+
=\ ǂ
127+
-\ ‿
128+
_" ̈
129+
_+ ̟
130+
_- ̠
131+
_/ ̌
132+
_0 ̥
133+
= ̩
134+
_= ̩
135+
_> ʼ
136+
_?\ ˤ
137+
_\ ̂
138+
_^ ̯
139+
_} ̚
140+
` ˞
141+
~ ̃
142+
_~ ̃
143+
_A ̘
144+
_a ̺
145+
_B ̏
146+
_B_L ᷅
147+
_c ̜
148+
_d ̪
149+
_e ̴
150+
<F> ↘
151+
_F ̂
152+
_G ˠ
153+
_H ́
154+
_H_T ᷄
155+
_h ʰ
156+
_k ̰
157+
_L ̀`
158+
_l ˡ
159+
_M ̄
160+
_m ̻
161+
_N ̼
162+
_n ⁿ
163+
_O ̹
164+
_o ̞
165+
_q ̙
166+
<R> ↗
167+
_R ̌
168+
_R_F ᷈
169+
_r ̝
170+
_T ̋
171+
_t ̤
172+
_v ̬
173+
_w ʷ
174+
_X ̆
175+
_x ̽
176+
```

articles/cognitive-services/Speech-Service/speech-ssml-phonetic-sets.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -147,6 +147,7 @@ See the sections in this article for the phonemes that are specific to each loca
147147
## zh-TW
148148
[!INCLUDE [zh-TW](./includes/phonetic-sets/text-to-speech/zh-tw.md)]
149149

150+
## Map X-SAMPA to IPA
151+
[!INCLUDE [X-SAMPA](./includes/phonetic-sets/text-to-speech/x-sampa.md)]
150152

151-
***
152153

articles/cognitive-services/Speech-Service/speech-synthesis-markup-pronunciation.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Usage of the `phoneme` element's attributes are described in the following table
3131

3232
| Attribute | Description | Required or optional |
3333
| ---------- | ---------- | ---------- |
34-
| `alphabet` | The phonetic alphabet to use when you synthesize the pronunciation of the string in the `ph` attribute. The string that specifies the alphabet must be specified in lowercase letters. The following options are the possible alphabets that you can specify:<ul><li>`ipa` &ndash; See [SSML phonetic alphabets](speech-ssml-phonetic-sets.md)</li><li>`sapi` &ndash; See [SSML phonetic alphabets](speech-ssml-phonetic-sets.md)</li><li>`ups` &ndash; See [Universal Phone Set](https://documentation.help/Microsoft-Speech-Platform-SDK-11/17509a49-cae7-41f5-b61d-07beaae872ea.htm)</li></ul><br>The alphabet applies only to the `phoneme` in the element. | Optional |
34+
| `alphabet` | The phonetic alphabet to use when you synthesize the pronunciation of the string in the `ph` attribute. The string that specifies the alphabet must be specified in lowercase letters. The following options are the possible alphabets that you can specify:<ul><li>`ipa` &ndash; See [SSML phonetic alphabets](speech-ssml-phonetic-sets.md)</li><li>`sapi` &ndash; See [SSML phonetic alphabets](speech-ssml-phonetic-sets.md)</li><li>`ups` &ndash; See [Universal Phone Set](https://documentation.help/Microsoft-Speech-Platform-SDK-11/17509a49-cae7-41f5-b61d-07beaae872ea.htm)</li><li>`x-sampa` &ndash; See [SSML phonetic alphabets](speech-ssml-phonetic-sets.md#map-x-sampa-to-ipa)</li></ul><br>The alphabet applies only to the `phoneme` in the element. | Optional |
3535
| `ph` | A string containing phones that specify the pronunciation of the word in the `phoneme` element. If the specified string contains unrecognized phones, text-to-speech rejects the entire SSML document and produces none of the speech output specified in the document.<br/><br/>For `ipa`, to stress one syllable by placing stress symbol before this syllable, you need to mark all syllables for the word. Or else, the syllable before this stress symbol will be stressed. For `sapi`, if you want to stress one syllable, you need to place the stress symbol after this syllable, whether or not all syllables of the word are marked.| Required |
3636

3737
### phoneme examples
@@ -68,6 +68,14 @@ The supported values for attributes of the `phoneme` element were [described pre
6868
</speak>
6969
```
7070

71+
```xml
72+
<speak version="1.0" xmlns="http://www.w3.org/2001/10/synthesis" xml:lang="en-US">
73+
<voice name="en-US-JennyNeural">
74+
<phoneme alphabet='x-sampa' ph='he."lou'>hello</phoneme>
75+
</voice>
76+
</speak>
77+
```
78+
7179
## Custom lexicon
7280

7381
You can define how single entities (such as company, a medical term, or an emoji) are read in SSML by using the [phoneme](#phoneme-element) and [sub](#sub-element) elements. To define how multiple entities are read, create an XML structured custom lexicon file. Then you upload the custom lexicon XML file and reference it with the SSML `lexicon` element.

articles/communication-services/concepts/chat/concepts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.subservice: chat
1616

1717
Azure Communication Services Chat can help you add real-time text communication to your cross-platform applications. This page summarizes key Chat concepts and capabilities. See the [Communication Services Chat Software Development Kit (SDK) Overview](./sdk-features.md) for lists of SDKs, languages, platforms, and detailed feature support.
1818

19-
The Chat APIs provide an **auto-scaling** service for persistently storied text and data communication. Other key features include:
19+
The Chat APIs provide an **auto-scaling** service for persistently stored text and data communication. Other key features include:
2020

2121
- **Custom Identity and Addressing** - Azure Communication Services provides generic [identities](../identity-model.md) that are used to address communication endpoints. Clients use these identities to authenticate to the Azure service and communicate with each other in `chat threads` you control.
2222
- **Encryption** - Chat SDKs encrypt traffic and prevents tampering on the wire.

articles/iot-edge/how-to-update-iot-edge.md

Lines changed: 11 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ keywords:
55
author: PatAltimore
66

77
ms.author: patricka
8-
ms.date: 11/29/2022
8+
ms.date: 2/2/2023
99
ms.topic: conceptual
1010
ms.service: iot-edge
1111
services: iot-edge
@@ -106,7 +106,7 @@ The way that you update the IoT Edge agent and IoT Edge hub containers depends o
106106

107107
Check the version of the IoT Edge agent and IoT Edge hub modules currently on your device using the commands `iotedge logs edgeAgent` or `iotedge logs edgeHub`. If you're using IoT Edge for Linux on Windows, you need to SSH into the Linux virtual machine to check the runtime module versions.
108108

109-
![Find container version in logs](./media/how-to-update-iot-edge/container-version.png)
109+
:::image type="content" source="./media/how-to-update-iot-edge/container-version.png" alt-text="Screenshot of where to find the container version in console logs." lightbox="./media/how-to-update-iot-edge/container-version.png":::
110110

111111
### Understand IoT Edge tags
112112

@@ -137,21 +137,21 @@ If you use specific tags in your deployment (for example, mcr.microsoft.com/azur
137137

138138
1. In the IoT Hub in the Azure portal, select your IoT Edge device, and select **Set Modules**.
139139

140-
1. In the **IoT Edge Modules** section, select **Runtime Settings**.
140+
1. On the **Modules** tab, select **Runtime Settings**.
141141

142-
![Configure runtime settings](./media/how-to-update-iot-edge/configure-runtime.png)
142+
:::image type="content" source="./media/how-to-update-iot-edge/configure-runtime.png" alt-text="Screenshot that shows location of the Runtime Settings tab.":::
143143

144-
1. In **Runtime Settings**, update the **Image** value for **Edge Hub** with the desired version. Don't select **Save** yet.
144+
1. In **Runtime Settings**, update the **Image URI** value in the **Edge Agent** section with the desired version. Don't select **Apply** yet.
145145

146-
![Update Edge Hub Image version](./media/how-to-update-iot-edge/runtime-settings-edgehub.png)
146+
:::image type="content" source="./media/how-to-update-iot-edge/runtime-settings-edgeagent.png" alt-text="Screenshot that shows where to update the image U R I with your version in the Edge Agent.":::
147147

148-
1. Collapse the **Edge Hub** settings, or scroll down, and update the **Image** value for **Edge Agent** with the same desired version.
148+
1. Select the **Edge Hub** tab and update the **Image URI** value with the same desired version.
149149

150-
![Update Edge Hub Agent version](./media/how-to-update-iot-edge/runtime-settings-edgeagent.png)
150+
:::image type="content" source="./media/how-to-update-iot-edge/runtime-settings-edgehub.png" alt-text="Screenshot that shows where to update the image U R I with your version in the Edge Hub.":::
151151

152-
1. Select **Save**.
152+
1. Select **Apply** to save changes.
153153

154-
1. Select **Review + create**, review the deployment, and select **Create**.
154+
1. Select **Review + create**, review the deployment as seen in the JSON file, and select **Create**.
155155

156156
## Special case: Update from 1.0 or 1.1 to latest release
157157

@@ -214,8 +214,7 @@ Currently, there's no support for IoT Edge version 1.4 running on Windows device
214214

215215
---
216216

217-
Now that the IoT Edge service running on your devices has been updated, follow the steps in this article to also [Update the runtime containers](#update-the-runtime-containers).
218-
217+
Now that the latest IoT Edge service is running on your devices, you also need to [Update the runtime containers](#update-the-runtime-containers) to the latest version. The updating process for runtime containers is the same as the updating process the IoT Edge service.
219218

220219
## Next steps
221220

articles/iot-edge/iot-edge-as-gateway.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ Custom or third-party modules that are often specific to the downstream device's
105105

106106
There are two patterns for translation gateways: *protocol translation* and *identity translation*.
107107

108-
![Diagram - translation gateway patterns](./media/iot-edge-as-gateway/edge-as-gateway-translation.png)
108+
:::image type="content" source="./media/iot-edge-as-gateway/edge-as-gateway-translation.png" alt-text="Diagram showing translation gateway patterns." lightbox="./media/iot-edge-as-gateway/edge-as-gateway-translation.png":::
109109

110110
### Protocol translation
111111

articles/iot-edge/iot-edge-runtime.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ The IoT Edge runtime is responsible for the following functions on IoT Edge devi
3333
- An IoT Edge device and the cloud
3434
- IoT Edge devices
3535

36-
![Runtime communicates insights and module health to IoT Hub](./media/iot-edge-runtime/Pipeline.png)
36+
:::image type="content" source="./media/iot-edge-runtime/Pipeline.png" alt-text="Screenshot of how runtime communicates insights and module health to I o T Hub." lightbox="./media/iot-edge-runtime/Pipeline.png":::
3737

3838
The responsibilities of the IoT Edge runtime fall into two categories: communication and module management. These two roles are performed by two components that are part of the IoT Edge runtime. The *IoT Edge agent* deploys and monitors the modules, while the *IoT Edge hub* is responsible for communication.
3939

@@ -74,7 +74,7 @@ The IoT Edge hub isn't a full version of IoT Hub running locally. IoT Edge hub s
7474

7575
To reduce the bandwidth that your IoT Edge solution uses, the IoT Edge hub optimizes how many actual connections are made to the cloud. IoT Edge hub takes logical connections from modules or downstream devices and combines them for a single physical connection to the cloud. The details of this process are transparent to the rest of the solution. Clients think they have their own connection to the cloud even though they're all being sent over the same connection. The IoT Edge hub can either use the AMQP or the MQTT protocol to communicate upstream with the cloud, independently from protocols used by downstream devices. However, the IoT Edge hub currently only supports combining logical connections into a single physical connection by using AMQP as the upstream protocol and its multiplexing capabilities. AMQP is the default upstream protocol.
7676

77-
![IoT Edge hub is a gateway between physical devices and IoT Hub](./media/iot-edge-runtime/gateway-communication.png)
77+
:::image type="content" source="./media/iot-edge-runtime/gateway-communication.png" alt-text="Screenshot showing relationships to I o T Edge hub as a gateway between physical devices and I o T Hub." lightbox="./media/iot-edge-runtime/gateway-communication.png":::
7878

7979
IoT Edge hub can determine whether it's connected to IoT Hub. If the connection is lost, IoT Edge hub saves messages or twin updates locally. Once a connection is reestablished, it syncs all the data. The location used for this temporary cache is determined by a property of the IoT Edge hub's module twin. The size of the cache isn't capped and will grow as long as the device has storage capacity. For more information, see [Offline capabilities](offline-capabilities.md).
8080

@@ -86,7 +86,7 @@ IoT Edge hub facilitates local communication. It enables device-to-module and mo
8686

8787
The brokering mechanism uses the same routing features as IoT Hub to specify how messages are passed between devices or modules. First devices or modules specify the inputs on which they accept messages and the outputs to which they write messages. Then a solution developer can route messages between a source (for example, outputs), and a destination (for example, inputs), with potential filters.
8888

89-
![Routes between modules go through IoT Edge hub](./media/iot-edge-runtime/module-endpoints-routing.png)
89+
:::image type="content" source="./media/iot-edge-runtime/module-endpoints-routing.png" alt-text="Screenshot showing how routes between modules go through I o T Edge hub." lightbox="./media/iot-edge-runtime/module-endpoints-routing.png":::
9090

9191
Routing can be used by devices or modules built with the Azure IoT Device SDKs using the AMQP protocol. All messaging IoT Hub primitives (for example, telemetry), direct methods, C2D, twins, are supported but communication over user-defined topics isn't supported.
9292

-27 KB
Loading
-6.27 KB
Loading
-21.2 KB
Loading

0 commit comments

Comments
 (0)