ONYX - Utilisation - PCL(UTF8) to XPS/en
Différence entre versions
De MappingDoc
(Page créée avec « ==Introduction== By default, MAPPING handles as input file, only PCL file encoded in ANSI. However, it is possible to take-in PCL files encoded in UTF8 in order to convert... ») |
(Mise à jour pour être en accord avec la nouvelle version de la source de la page) |
||
| (16 révisions intermédiaires par 2 utilisateurs non affichées) | |||
| Ligne 1 : | Ligne 1 : | ||
<languages/> | <languages/> | ||
| + | <div class="mw-translate-fuzzy"> | ||
==Introduction== | ==Introduction== | ||
By default, MAPPING handles as input file, only PCL file encoded in ANSI. | By default, MAPPING handles as input file, only PCL file encoded in ANSI. | ||
However, it is possible to take-in PCL files encoded in UTF8 in order to convert them into XPS, PDF or others. | However, it is possible to take-in PCL files encoded in UTF8 in order to convert them into XPS, PDF or others. | ||
| + | </div> | ||
| − | == | + | <div class="mw-translate-fuzzy"> |
| − | + | ==Settings== | |
| + | To force the input convertor to '''take-in a PCL encoded in UTF-8''', we must use the following tag in a -param parameter or in a conversion profile. | ||
| + | </div> | ||
<decodeutf8>ON</decodeutf8> | <decodeutf8>ON</decodeutf8> | ||
| − | + | This parameter is only used for the fromPCL convertion | |
| − | + | It is however possible to put it in a PDF convertion profile. | |
| − | == | + | <div class="mw-translate-fuzzy"> |
| − | === | + | ==Examples== |
| + | ===Convert a PCL(UTF8) into XPS via a convertion profile=== | ||
<xps> | <xps> | ||
<label>XPS</label> | <label>XPS</label> | ||
| Ligne 20 : | Ligne 25 : | ||
'''<decodeutf8>ON</decodeutf8>''' | '''<decodeutf8>ON</decodeutf8>''' | ||
</xps> | </xps> | ||
| + | </div> | ||
| − | <u> | + | <u>Example of the syntax of the commande to use</u> : |
/apps/mapping/bin/map_xps "-fromPCL" "-toXPS" "-infile:/apps/mapping/infile/infile.pcl" "-outfile:/apps/mapping/results/out/out.xps" "-profile:xps" | /apps/mapping/bin/map_xps "-fromPCL" "-toXPS" "-infile:/apps/mapping/infile/infile.pcl" "-outfile:/apps/mapping/results/out/out.xps" "-profile:xps" | ||
| − | === | + | <div class="mw-translate-fuzzy"> |
| + | ===Convert a PCL(UTF8) into XPS without a profile=== | ||
| + | </div> | ||
| − | <u> | + | <u>Example of the syntax of the commande to use</u> : |
/apps/mapping/bin/map_xps "-fromPCL" "-toXPS" "-infile:/apps/mapping/infile/infile.pcl" "-outfile:/apps/mapping/results/out/out.xps" "-param:decodeutf8=ON" | /apps/mapping/bin/map_xps "-fromPCL" "-toXPS" "-infile:/apps/mapping/infile/infile.pcl" "-outfile:/apps/mapping/results/out/out.xps" "-param:decodeutf8=ON" | ||
| − | === | + | <div class="mw-translate-fuzzy"> |
| − | + | ===Convert a PCL(UTF8) into PDFvia a convertion profile=== | |
| − | + | ||
| + | To avoid having to go through a XPS profile then to a PDF profile, it is possible to put the decodeutf8 to ON directly within the PDF convertion profile. | ||
| + | |||
<pdf> | <pdf> | ||
<label>PDF</label> | <label>PDF</label> | ||
| Ligne 38 : | Ligne 48 : | ||
'''<decodeutf8>ON</decodeutf8>''' | '''<decodeutf8>ON</decodeutf8>''' | ||
</pdf> | </pdf> | ||
| + | </div> | ||
| − | <u> | + | <u>Example of the syntax of the commande to use</u> : |
/apps/mapping/bin/map_xps "-fromPCL" "-toXPS" "-infile:/apps/mapping/infile/infile.pcl" "-outfile:/apps/mapping/results/out/out.xps" "-profile:pdf" | /apps/mapping/bin/map_xps "-fromPCL" "-toXPS" "-infile:/apps/mapping/infile/infile.pcl" "-outfile:/apps/mapping/results/out/out.xps" "-profile:pdf" | ||
| − | === | + | <div class="mw-translate-fuzzy"> |
| + | ===Convert a PCL(UTF8) into PDFwithout a profile=== | ||
| + | </div> | ||
| − | <u> | + | <u>Example of the syntax of the commande to use</u> : |
/apps/mapping/bin/map_xps "-fromPCL" "-toPDF" "-infile:/apps/mapping/infile/infile.pcl" "-outfile:/apps/mapping/results/out/out.xps" "-param:decodeutf8=ON" | /apps/mapping/bin/map_xps "-fromPCL" "-toPDF" "-infile:/apps/mapping/infile/infile.pcl" "-outfile:/apps/mapping/results/out/out.xps" "-param:decodeutf8=ON" | ||
Version actuelle datée du 26 mai 2020 à 10:38
Sommaire
Introduction
By default, MAPPING handles as input file, only PCL file encoded in ANSI. However, it is possible to take-in PCL files encoded in UTF8 in order to convert them into XPS, PDF or others.
Settings
To force the input convertor to take-in a PCL encoded in UTF-8, we must use the following tag in a -param parameter or in a conversion profile.
<decodeutf8>ON</decodeutf8>
This parameter is only used for the fromPCL convertion
It is however possible to put it in a PDF convertion profile.
Examples
Convert a PCL(UTF8) into XPS via a convertion profile
<xps> <label>XPS</label> <language>XPS</language> <decodeutf8>ON</decodeutf8> </xps>
Example of the syntax of the commande to use :
/apps/mapping/bin/map_xps "-fromPCL" "-toXPS" "-infile:/apps/mapping/infile/infile.pcl" "-outfile:/apps/mapping/results/out/out.xps" "-profile:xps"
Convert a PCL(UTF8) into XPS without a profile
Example of the syntax of the commande to use :
/apps/mapping/bin/map_xps "-fromPCL" "-toXPS" "-infile:/apps/mapping/infile/infile.pcl" "-outfile:/apps/mapping/results/out/out.xps" "-param:decodeutf8=ON"
Convert a PCL(UTF8) into PDFvia a convertion profile
To avoid having to go through a XPS profile then to a PDF profile, it is possible to put the decodeutf8 to ON directly within the PDF convertion profile.
<pdf> <label>PDF</label> <language>PDF</language> <decodeutf8>ON</decodeutf8> </pdf>
Example of the syntax of the commande to use :
/apps/mapping/bin/map_xps "-fromPCL" "-toXPS" "-infile:/apps/mapping/infile/infile.pcl" "-outfile:/apps/mapping/results/out/out.xps" "-profile:pdf"
Convert a PCL(UTF8) into PDFwithout a profile
Example of the syntax of the commande to use :
/apps/mapping/bin/map_xps "-fromPCL" "-toPDF" "-infile:/apps/mapping/infile/infile.pcl" "-outfile:/apps/mapping/results/out/out.xps" "-param:decodeutf8=ON"
