Skip to content

Commit 129bf0c

Browse files
SeiyasuLinda Caputo
authored andcommitted
Update machine-translation-services-in-sharepoint.md (SharePoint#2592)
* Update the-xliff-interchange-file-format-in-sharepoint.md Fix invalid link. * Update machine-translation-services-in-sharepoint.md Fix code sample link: Access Machine Translation Service
1 parent 0a5ac38 commit 129bf0c

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

docs/general-development/machine-translation-services-in-sharepoint.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Using the server object model, you can submit requests to the Machine Translatio
7070

7171

7272

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 ).
7474

7575

7676

@@ -274,7 +274,7 @@ For the .NET managed CSOM, get a **ClientContext** instance (located in the **Mi
274274

275275

276276

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).
278278

279279

280280

@@ -290,7 +290,7 @@ For the Silverlight CSOM, get a **ClientContext** instance (located in the **Mic
290290

291291

292292

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).
294294

295295

296296

@@ -492,7 +492,7 @@ For the JavaScript CSOM, get an **SP.ClientContext** instance, and then use the
492492

493493

494494

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).
496496

497497

498498

docs/general-development/the-xliff-interchange-file-format-in-sharepoint.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,11 @@ SharePoint provides XML Localization Interchange File Format (XLIFF) application
1414

1515

1616

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.
1818

1919

2020

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).
2222

2323

2424

@@ -40,9 +40,9 @@ This article documents specific SharePoint Server implementations of XLIFF eleme
4040
|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/> |
4141
|Body <br/> |||
4242
|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/> |
4646
|Bin-source <br/> |||
4747
|Bin-target <br/> |||
4848
|Internalfile <br/> |form <br/> ||
@@ -98,7 +98,7 @@ The following example of an XML document in XLIFF interchange file format demons
9898
- [Add SharePoint capabilities](add-sharepoint-capabilities.md)
9999

100100

101-
- Code sample: [SharePoint: Extract and insert bin-unit elements in XLIFF files](http://code.msdn.microsoft.com/SharePoint-Extract-fe686878)
101+
- Code sample: [SharePoint: Extract and insert bin-unit elements in XLIFF files](https://code.msdn.microsoft.com/sharepoint-2013-extract-fe686878)
102102

103103

104104
- [Machine Translation Services in SharePoint](machine-translation-services-in-sharepoint.md)

0 commit comments

Comments
 (0)