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: docs/general-development/machine-translation-services-in-sharepoint.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ Using the server object model, you can submit requests to the Machine Translatio
70
70
71
71
72
72
73
-
For sample code demonstrating how to use the server object model from a console application, see [SharePoint: Access Machine Translation Service using server object model](http://code.msdn.microsoft.com/SharePoint-Access-86639c3d).
73
+
For sample code demonstrating how to use the server object model from a console application, see [SharePoint: Access Machine Translation Service using server object model](http://code.msdn.microsoft.com/SharePoint-2013-Access-86639c3d).
74
74
75
75
76
76
@@ -274,7 +274,7 @@ For the .NET managed CSOM, get a **ClientContext** instance (located in the **Mi
274
274
275
275
276
276
277
-
For sample code demonstrating how to use the .NET Managed CSOM, see [SharePoint: Access Machine Translation Service using the client object model](http://code.msdn.microsoft.com/SharePoint-Perform-a-8e53b06a).
277
+
For sample code demonstrating how to use the .NET Managed CSOM, see [SharePoint: Access Machine Translation Service using the client object model](http://code.msdn.microsoft.com/SharePoint-2013-Perform-a-8e53b06a).
278
278
279
279
280
280
@@ -290,7 +290,7 @@ For the Silverlight CSOM, get a **ClientContext** instance (located in the **Mic
290
290
291
291
292
292
293
-
For sample code demonstrating how to use the Silverlight CSOM, see [SharePoint: Access Machine Translation Service from Silverlight application](http://code.msdn.microsoft.com/SharePoint-Access-cdaff6b2).
293
+
For sample code demonstrating how to use the Silverlight CSOM, see [SharePoint: Access Machine Translation Service from Silverlight application](http://code.msdn.microsoft.com/SharePoint-2013-Access-cdaff6b2).
294
294
295
295
296
296
@@ -492,7 +492,7 @@ For the JavaScript CSOM, get an **SP.ClientContext** instance, and then use the
492
492
493
493
494
494
495
-
For sample code demonstrating how to use the JavaScript CSOM, see [SharePoint: Accessing the Machine Translation Service with JavaScript](http://code.msdn.microsoft.com/SharePoint-Accessing-647f6dd9).
495
+
For sample code demonstrating how to use the JavaScript CSOM, see [SharePoint: Accessing the Machine Translation Service with JavaScript](http://code.msdn.microsoft.com/SharePoint-2013-Accessing-647f6dd9).
Copy file name to clipboardExpand all lines: docs/general-development/the-xliff-interchange-file-format-in-sharepoint.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -14,11 +14,11 @@ SharePoint provides XML Localization Interchange File Format (XLIFF) application
14
14
15
15
16
16
17
-
SharePoint adheres to the [XLIFF 1.2 representation guide for HTML](http://docs.oasis-open.org/xliff/v1.2/xliff-profile-html/xliff-profile-html-1.2-cd02l) published by OASIS when SharePoint Server HTML pages are extracted to XLIFF format. To eliminate the mix of translatable elements and code elements that would appear in XLIFF packages if unmodified SharePoint Server CDATA content were to be transported, SharePoint is delivered with the ability to produce fully XLIFF-compliant XLIFF documents that are also well-integrated with SharePoint. When exporting XML files in XLIFF format from `sharepointservernv`, the data that the human translator receives is clean and ready to translate.
17
+
SharePoint adheres to the [XLIFF 1.2 representation guide for HTML](http://docs.oasis-open.org/xliff/v1.2/xliff-profile-html/xliff-profile-html-1.2-cd02.html) published by OASIS when SharePoint Server HTML pages are extracted to XLIFF format. To eliminate the mix of translatable elements and code elements that would appear in XLIFF packages if unmodified SharePoint Server CDATA content were to be transported, SharePoint is delivered with the ability to produce fully XLIFF-compliant XLIFF documents that are also well-integrated with SharePoint. When exporting XML files in XLIFF format from `sharepointservernv`, the data that the human translator receives is clean and ready to translate.
18
18
19
19
20
20
21
-
This article documents specific SharePoint Server implementations of XLIFF elements and attributes that are defined more generally in version 1.2 of the XLIFF open standard document published by OASIS. For more information about specific XLIFF elements and attributes, see the [XLIFF 1.2 Specification](http://docs.oasis-open.org/xliff/xliff-core/xliff-corel).
21
+
This article documents specific SharePoint Server implementations of XLIFF elements and attributes that are defined more generally in version 1.2 of the XLIFF open standard document published by OASIS. For more information about specific XLIFF elements and attributes, see the [XLIFF 1.2 Specification](http://docs.oasis-open.org/xliff/xliff-core/xliff-core.html).
22
22
23
23
24
24
@@ -40,9 +40,9 @@ This article documents specific SharePoint Server implementations of XLIFF eleme
40
40
|Note <br/> ||Contains information that may be useful to the localizer, developer, or others who process the XLIFF file. <br/> `note` element values are generated by . `note` attributes contain GUIDs that identify ___location and types of content to provide context. <br/> |
41
41
|Body <br/> |||
42
42
|Trans-unit <br/> |`id` <br/> `datatype` <br/> |The `id` attribute contains a GUID that identifies the ___location of the import. <br/> The `datatype` attribute defines the type of data contained in the **trans-unit** element. For a list of available `datatype` attribute values, see the XLIFF open standard document. <br/> |
43
-
|Source <br/> ||HTML content often contains markup that has to be preserved. For this reason, SharePoint wraps markup in HTML content with tags that are defined in the [XLIFF 1.2 representation guide for HTML](http://docs.oasis-open.org/xliff/v1.2/xliff-profile-html/xliff-profile-html-1.2-cd02l). <br/> |
44
-
|Target <br/> |ph (optional) <br/> bpt (optional) <br/> ept (optional) <br/> sub (optional) <br/> |HTML content often contains markup that has to be preserved. For this reason, SharePoint wraps markup in HTML content with tags that are defined in the [XLIFF 1.2 representation guide for HTML](http://docs.oasis-open.org/xliff/v1.2/xliff-profile-html/xliff-profile-html-1.2-cd02l). <br/> |
45
-
|Bin-unit <br/> ||Files stored in SharePoint can be sent for localization via XLIFF through the **bin-unit** elements. The file can be extracted back into its original file format by using the [SharePoint: Extract and insert bin-unit elements in XLIFF files](http://code.msdn.microsoft.com/SharePoint-Extract-fe686878) code sample. <br/> |
43
+
|Source <br/> ||HTML content often contains markup that has to be preserved. For this reason, SharePoint wraps markup in HTML content with tags that are defined in the [XLIFF 1.2 representation guide for HTML](http://docs.oasis-open.org/xliff/v1.2/xliff-profile-html/xliff-profile-html-1.2-cd02.html). <br/> |
44
+
|Target <br/> |ph (optional) <br/> bpt (optional) <br/> ept (optional) <br/> sub (optional) <br/> |HTML content often contains markup that has to be preserved. For this reason, SharePoint wraps markup in HTML content with tags that are defined in the [XLIFF 1.2 representation guide for HTML](http://docs.oasis-open.org/xliff/v1.2/xliff-profile-html/xliff-profile-html-1.2-cd02.html). <br/> |
45
+
|Bin-unit <br/> ||Files stored in SharePoint can be sent for localization via XLIFF through the **bin-unit** elements. The file can be extracted back into its original file format by using the [SharePoint: Extract and insert bin-unit elements in XLIFF files](https://code.msdn.microsoft.com/sharepoint-2013-extract-fe686878) code sample. <br/> |
46
46
|Bin-source <br/> |||
47
47
|Bin-target <br/> |||
48
48
|Internalfile <br/> |form <br/> ||
@@ -98,7 +98,7 @@ The following example of an XML document in XLIFF interchange file format demons
0 commit comments