convert pdf to png using c#: Copy from protected pdf application Library tool html asp.net azure online DITA12XLIFFArticle0-part566

DITA 1.2 Feature Article

Using XLIFF to Translate DITA Projects

An OASIS DITA Adoption

Technical Committee Publication

Copy from protected pdf - C# PDF Password Library: add, remove, edit PDF file password in C#.net, ASP.NET, MVC, WinForms, WPF

Help to Improve the Security of Your PDF Document by Setting Password

pdf user password; add password to pdf file

Copy from protected pdf - VB.NET PDF Password Library: add, remove, edit PDF file password in vb.net, ASP.NET, MVC, WinForms, WPF

Help to Improve the Security of Your PDF Document by Setting Password

convert password protected pdf to word; pdf password protect

2 | OpenTopic | Introduction

VB.NET PDF Convert to Jpeg SDK: Convert PDF to JPEG images in vb.

to text, C#.NET convert PDF to images, C#.NET PDF file & pages edit, C#.NET PDF pages extract, copy, paste, C# Able to convert password protected PDF document.

pdf password security; password protected pdf

C# PDF Convert to Jpeg SDK: Convert PDF to JPEG images in C#.net

Password protected PDF document can be converted and changed. using RasterEdge.XDoc. PDF; Copy demo code below to achieve fast conversion from PDF file to Jpeg

a pdf password online; copy text from protected pdf to word

Notice

OASIS (Organization for the Advancement of Structured Information

Standards) is a not-for-profit, international consortium that drives the

development, convergence, and adoption of e-business standards. Members

themselves set the OASIS technical agenda, using a lightweight, open process

expressly designed to promote industry consensus and unite disparate efforts.

The consortium produces open standards for Web services, security, e-

business, and standardization efforts in the public sector and for application-

specific markets. OASIS was founded in 1993. More information can be

found on the OASIS website at http://www.oasis-open.org.

The OASIS DITA Adoption Technical Committee members collaborate to

provide expertise and resources to educate the marketplace on the value of

the DITA OASIS standard. By raising awareness of the benefits offered by

DITA, the DITA Adoption Technical Committee expects the demand for, and

availability of, DITA conforming products and services to increase, resulting

in a greater choice of tools and platforms and an expanded DITA community

of users, suppliers, and consultants.

DISCLAIMER: All examples presented in this article were produced

using one or more tools chosen at the author's discretion and in no way

reflect endorsement of the tools by the OASIS DITA Adoption Technical

Committee.

This white paper was produced and approved by the OASIS DITA Adoption

Technical Committee as a Committee Draft. It has not been reviewed and/or

approved by the OASIS membership at-large.

All capitalized terms in the following text have the meanings assigned

to them in the OASIS Intellectual Property Rights Policy (the "OASIS

IPR Policy"). The full Policy may be found at the OASIS website. This

document and translations of it may be copied and furnished to others,

and derivative works that comment on or otherwise explain it or assist in

its implementation may be prepared, copied, published, and distributed,

in whole or in part, without restriction of any kind, provided that the

above copyright notice and this section are included on all such copies

and derivative works. However, this document itself may not be modified

in any way, including by removing the copyright notice or references to

OASIS, except as needed for the purpose of developing any document or

deliverable produced by an OASIS Technical Committee (in which case

the rules applicable to copyrights, as set forth in the OASIS IPR Policy,

must be followed) or as required to translate it into languages other than

English. The limited permissions granted above are perpetual and will not

be revoked by OASIS or its successors or assigns. This document and the

information contained herein is provided on an "AS IS" basis and OASIS

DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING

BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE

INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP

RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY

OR FITNESS FOR A PARTICULAR PURPOSE.

VB.NET PDF Convert to Word SDK: Convert PDF to Word library in vb.

Create editable Word file online without email. Supports transfer from password protected PDF. VB.NET class source code for .NET framework.

crystal report to pdf with password; convert pdf password protected to word online

C# PDF Convert to Word SDK: Convert PDF to Word library in C#.net

Password protected PDF file can be printed to Word for mail merge. C# source code is available for copying and using in .NET Class.

pdf print protection; copy protection pdf

4 | OpenTopic |

Document History

Revision

Date

Author

Summary

.NET PDF SDK - Description of All PDF Processing Control Feastures

Easy to copy, paste, and cut image from PDF. PDF Document Protect. PDF Password. Able to Open password protected PDF; Allow users to add password to PDF; Allow

adding password to pdf; add password to pdf online

C#: How to Add HTML5 Document Viewer Control to Your Web Page

Then, copy the following lines of RasterEdge_Demo_Docs/pdf/demo_1.pdf" })); _tabDemoFiles.addCommand AppSettings.Get("resourceFolder"); protected void Page_Load

copy protecting pdf files; password pdf files

OpenTopic | TOC | 5

Contents

Using XLIFF to Translate DITA Projects..........................................................................7

Initial workflow........................................................................................................................................7

Maintenance workflow.............................................................................................................................9

C# PDF: C# Code to Create Mobile PDF Viewer; C#.NET Mobile PDF

Copy package file "Web.config" content to public float DocWidth = 819; protected void Page_Load Demo_Docs/").Replace("\\" Sample.pdf"; this.SessionId

copy text from protected pdf; change password on pdf file

C# Image: How to Integrate Web Document and Image Viewer

RasterEdgeImagingDeveloperGuide8.0.pdf: from this user manual, you First, copy the following lines of C# code mode; public string fid; protected void Page_Load

add password to pdf document; convert protected pdf to word

6 | OpenTopic | TOC

Using XLIFF to Translate DITA Projects

DITA promises cost reductions in translation thanks to content reuse. Content reuse can lead to translation costs

reduction when proper planning is done. DITA topics are written once, updated once, and used in multiple

deliverables. With careful planning, costs can indeed be lowered. However, cost reduction depends on the nature of

the project; it is not possible to predict cost reductions percentages in advance.

Ideally, you should never pay twice for the translation of your content. The real world is not perfect, but with careful

selection of tools and strategies, you can get excellent results.

If you use DITA topics in the different DITA maps that make up your projects, you can also reuse the translations of

those topics.

XLIFF (XML Localization Interchange File Format) is an open standard published by OASIS (like DITA) that you

can use in your project workflow to manage the content that needs to be translated.

The XLIFF vocabulary has a rich set of elements and attributes that permit XLIFF-supporting applications to

• store source and translated text

• store alternative or suggested translations extracted from a Translation Memory (TM) system or generated by a

Machine Translation (MT) engine

• perform revision control

• keep track of the different stages of the translation process

• perform word-count calculations

The XLIFF standard was first published by OASIS in 2002. Most modern translation environments currently support

it. A Localization Service Provider (LSP) using up-to-date tools should be able to accept XLIFF files that you pre-

process in house.

You can translate DITA maps or individual topics using XLIFF as intermediate format. When translating DITA maps,

it is very important to use a tool that can handle the different content-linking mechanisms offered by DITA. It is not

necessary to resolve referenced content when translating individual topics, but you can still make good use of the

translation reuse strategies described in this article.

Note: It is usually very important to prepare glossary

terms and provide them to your LSP. Glossary definitions

of approved terminology helps in maintaining consistency

for special terms. Ask your LSP to provide translated

versions of your glossaries; you can use them with your

EMBT engine.

You can use the DITA Glossentry topic to prepare your

glossary terms, including definitions, part of speech, usage

rules, abbreviations and acronyms, and other detailed

information.

Resources

Download or view the latest approved DITA Specification.

Read the XLIFF 1.2 Specification, which defines the XML Localization Interchange File Format (XLIFF). The

purpose of this vocabulary is to store localizable data and carry it from one step of the localization process to the

other, while allowing interoperability between tools.

Initial workflow

As a technical author, you write your DITA topics, prepare your maps, and publish source-language drafts as you

would usually do. Refine your content as necessary, until you are satisfied with the published results. Once your

project is ready for translation, convert your maps to XLIFF format using a translation tool that supports DITA.

8 | OpenTopic | Using XLIFF to Translate DITA Projects

A translation tool that supports DITA will be able to

• resolve referenced content using @href, @conref, or other referencing attributes

• read the map(s) and generate matched-hierarchical XLIFF

• understand the standard “translate” attribute and the "xml-lang" attribute

• support your DITA specializations by using OASIS XML catalogs and allowing custom configuration of elements

and attributes that are translatable

The conversion to XLIFF will flatten the DITA map to a single file with all of the reference resolved. The XLIFF

file allows your Localization Service Provider (LSP) to work with one file rather than hundreds of files, simplifying

administrative activities and reducing administrative costs.

The initial workflow proceeds as follows:

1. Begin with your DITA map in the source language.

</map>

This map references three topics:

<title>Hummingbirds</title>

Smallest bird: Dwarf hummingbird (5.7 cm)

</conbody>

</concept>

<title>Ostrich</title>

Heaviest bird: Ostrich (150 kg)

</conbody>

</concept>

<title>Swift</title>

Fastest bird: flying: Common Swift (200 km/h)

</conbody>

</concept>

2. Prepare the XLIFF file.

Your tool should create a single XLIFF file for all strings in the map and topics. The source strings (in this case)

are English.

3. Once the XLIFF file is ready, send it and a PDF rendering to your LSP.

The PDF will help the LSP’s translators to understand the context for the translation. The following example

shows the XLIFF file with both English and German text.

<body>

<trans-unit id="map" resname="title">

<source>Birds</source>

<target>Vögel</target>

</trans-unit>

<trans-unit id="hummingbird" resname="title">

<source>Hummingbird</source>

<target>Kolibri</target>

</trans-unit>

<trans-unit id="hummingbird" resname="p">

<source>Smallest bird: Dwarf hummingbird (5.7 cm)</source>

<target>Kleinster Vogel: Zwergkolibri (5.7 cm)</target>

</trans-unit>

OpenTopic | Using XLIFF to Translate DITA Projects | 9

<trans-unit id="ostrich" resname="title">

<source>Ostrich</source>

<target>Strauß</target>

</trans-unit>

<trans-unit id="ostrich" resname="p">

<source>Heaviest bird: Ostrich (150 kg)</source>

<target>Schwerster Vogel: Strauß (150 kg)</target>

</trans-unit>

<trans-unit id="swift" resname="title">

<source>Swift</source>

<target>Mauersegler</target>

</trans-unit>

<trans-unit id="swift" resname="p">

<source>Fastest bird: flying: Common Swift (200 km/h)</source>

<target>Schnellster Vogel: fliegend: Mauersegler (200 km/h)</target>

</trans-unit>

</body>

</file>

</xliff>

4. After you receive the translated XLIFF file, convert it back to original DITA map and topics format.

After the XLIFF file is transformed back to DITA, the result is an identical German DITA map and topics:

</map>

The map references these three topics in German:

<title>Kolibri</title>

Kleinster Vogel: Zwergkolibri (5.7 cm)

</conbody>

</concept>

<title>Strauß</title>

Schwerster Vogel: Strauß (150 kg)

</conbody>

</concept>

<title>Mauersegler</title>

Schnellster Vogel: fliegend: Mauersegler (200 km/h)

</conbody>

</concept>

You should have a directory structure for the translated content that is identical to the original directory for the

source content.

5. If your images were not in SVG format, you will have to copy them to the new translation project structure before

you can render the translated project in PDF or other formats.

6. Export the translations in your XLIFF file to TMX (Translation Memory eXchange) format and update your

Translation Memory.

7. Store the translated XLIFF and the TMX file in your content repository. Both files will play a crucial role in the

maintenance workflow.

Maintenance workflow

As products and processes are updated, you will update some of your topics, write new ones, and need to update your

translations. At that point, you will see the benefits of translation reuse with these techniques:

10 | OpenTopic | Using XLIFF to Translate DITA Projects

• reuse In-Context Exact (ICE) matches

• recover translations of similar text from Translation Memory (TM)

• generate updated translations using EBMT (Example Based Machine Translation)

The maintenance workflow proceeds as follows:

1. Convert the updated DITA map to XLIFF.

2. Using your translation tool, compare the new XLIFF with the one you previously had translated and recover In-

Context Exact (ICE) matches.

This step recovers the translations of text that has not changed since last translation cycle.

3. After recovering all ICE matches, mark all translated segments as untranslatable ("do not translate").

Translations will remain visible in the XLIFF as context information for the translator but will not need to be

changed.

4. If you have not yet updated your Translation Memory with the translations from the previous cycle, import the

TMX into the Translation Memory of your translation environment.

5. Use your TM engine to retrieve matches for the segments that remain untranslated.

A TM engine can evaluate the similarities between current text requiring translation and entries that exist in

its database. Entries identical to the text being translated are considered 100% matches; entries that have some

differences with the searched text are called fuzzy matches.

6. If your translation memory only contains entries from a very similar project, you may want to accept all 100%

matches as final.

Because there is no guarantee that these matches are the right translations, you should let professional translators

approve them. Nevertheless, you may ask your LSP to set a special price for segments with good matches from

your own TM.

7. Use Example-Based Machine Translation (EBMT) and recover extra matches.

Sometimes the difference betweenthe old text and the new one is simply an updated number. Such a small

change is something a good CAT (Computer-Aided Translation) program can correct automatically using EBMT

techniques. An EBMT engine can also automatically correct the translation of known terms with the aid of a

terminology database.

You should now have an XLIFF file ready to send to an LSP for completing the translation cycle.

8. Send the XLIFF file with an updated PDF rendering.

9. Remember to update your TM engine when you receive the translated version back.

10.Finally, if your translation budget allows it, generate a PDF rendering of the translated project and send it with a

copy of the translated XLIFF to your LSP for proofreading.

If the reviewer finds an error, it can be corrected in the XLIFF file and sent back to you to update your topics.

Documents you may be interested

convert pdf to png using c# : Copy from protected pdf application Library tool html asp.net azure online DITA12XLIFFArticle0-part566