diff --git a/OmegaT/.classpath b/OmegaT/.classpath
new file mode 100644
index 0000000..735127a
--- /dev/null
+++ b/OmegaT/.classpath
@@ -0,0 +1,24 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/OmegaT/.project b/OmegaT/.project
new file mode 100644
index 0000000..cfb0b03
--- /dev/null
+++ b/OmegaT/.project
@@ -0,0 +1,17 @@
+
+
+ OmegaT
+
+
+
+
+
+ org.eclipse.jdt.core.javabuilder
+
+
+
+
+
+ org.eclipse.jdt.core.javanature
+
+
diff --git a/OmegaT/.settings/org.eclipse.jdt.core.prefs b/OmegaT/.settings/org.eclipse.jdt.core.prefs
new file mode 100644
index 0000000..838bd9d
--- /dev/null
+++ b/OmegaT/.settings/org.eclipse.jdt.core.prefs
@@ -0,0 +1,11 @@
+eclipse.preferences.version=1
+org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled
+org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.7
+org.eclipse.jdt.core.compiler.codegen.unusedLocal=preserve
+org.eclipse.jdt.core.compiler.compliance=1.7
+org.eclipse.jdt.core.compiler.debug.lineNumber=generate
+org.eclipse.jdt.core.compiler.debug.localVariable=generate
+org.eclipse.jdt.core.compiler.debug.sourceFile=generate
+org.eclipse.jdt.core.compiler.problem.assertIdentifier=error
+org.eclipse.jdt.core.compiler.problem.enumIdentifier=error
+org.eclipse.jdt.core.compiler.source=1.7
diff --git a/OmegaT/addons/javahelp-filters/build.xml b/OmegaT/addons/javahelp-filters/build.xml
new file mode 100644
index 0000000..89955a5
--- /dev/null
+++ b/OmegaT/addons/javahelp-filters/build.xml
@@ -0,0 +1,69 @@
+
+
+
+
+
+ Builds, tests, and runs the project javahelp-filters.
+
+
+
diff --git a/OmegaT/addons/javahelp-filters/manifest.mf b/OmegaT/addons/javahelp-filters/manifest.mf
new file mode 100644
index 0000000..5f4fa5d
--- /dev/null
+++ b/OmegaT/addons/javahelp-filters/manifest.mf
@@ -0,0 +1,8 @@
+Manifest-Version: 1.0
+OmegaT-Plugin: true
+
+Name: org.omegat.filters2.javahelp.helpset.HelpSetFilter
+OmegaT-Filter: true
+
+Name: org.omegat.filters2.javahelp.toc.TOCFilter
+OmegaT-Filter: true
diff --git a/OmegaT/addons/javahelp-filters/nbproject/build-impl.xml b/OmegaT/addons/javahelp-filters/nbproject/build-impl.xml
new file mode 100644
index 0000000..1a17422
--- /dev/null
+++ b/OmegaT/addons/javahelp-filters/nbproject/build-impl.xml
@@ -0,0 +1,486 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must set src.dir
+ Must set build.dir
+ Must set dist.dir
+ Must set build.classes.dir
+ Must set dist.javadoc.dir
+ Must set build.test.classes.dir
+ Must set build.test.results.dir
+ Must set build.classes.excludes
+ Must set dist.jar
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select some files in the IDE or set javac.includes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set run.class
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set debug.class
+
+
+
+
+ Must set fix.includes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select some files in the IDE or set javac.includes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Some tests failed; see details above.
+
+
+
+
+
+
+
+
+ Must select some files in the IDE or set test.includes
+
+
+
+ Some tests failed; see details above.
+
+
+
+
+ Must select one file in the IDE or set test.class
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set applet.url
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set applet.url
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/OmegaT/addons/javahelp-filters/nbproject/genfiles.properties b/OmegaT/addons/javahelp-filters/nbproject/genfiles.properties
new file mode 100644
index 0000000..e57400a
--- /dev/null
+++ b/OmegaT/addons/javahelp-filters/nbproject/genfiles.properties
@@ -0,0 +1,8 @@
+build.xml.data.CRC32=9eab5f91
+build.xml.script.CRC32=0147d762
+build.xml.stylesheet.CRC32=e2435cb5
+# This file is used by a NetBeans-based IDE to track changes in generated files such as build-impl.xml.
+# Do not edit this file. You may delete it but then the IDE will never regenerate such files for you.
+nbproject/build-impl.xml.data.CRC32=9eab5f91
+nbproject/build-impl.xml.script.CRC32=6f286c58
+nbproject/build-impl.xml.stylesheet.CRC32=3b89b5a6
diff --git a/OmegaT/addons/javahelp-filters/nbproject/project.properties b/OmegaT/addons/javahelp-filters/nbproject/project.properties
new file mode 100644
index 0000000..3273a20
--- /dev/null
+++ b/OmegaT/addons/javahelp-filters/nbproject/project.properties
@@ -0,0 +1,57 @@
+file.reference.xerces-2.6.2.jar=lib/xerces-2.6.2.jar
+manifest.file=manifest.mf
+
+application.args=
+build.classes.dir=${build.dir}/classes
+build.classes.excludes=**/*.java,**/*.form
+# This directory is removed when the project is cleaned:
+build.dir=build
+# Only compile against the classpath explicitly listed here:
+build.sysclasspath=ignore
+build.test.classes.dir=${build.dir}/test/classes
+build.test.results.dir=${build.dir}/test/results
+debug.classpath=\
+ ${run.classpath}
+debug.test.classpath=\
+ ${run.test.classpath}
+# This directory is removed when the project is cleaned:
+dist.dir=dist
+dist.jar=${dist.dir}/javahelp-filters.jar
+dist.javadoc.dir=${dist.dir}/javadoc
+jar.compress=false
+javac.classpath=\
+ ${reference.OmegaT.jar}
+# Space-separated list of extra javac options
+javac.compilerargs=
+javac.deprecation=false
+javac.source=${default.javac.source}
+javac.target=${default.javac.target}
+javac.test.classpath=\
+ ${javac.classpath}:\
+ ${build.classes.dir}:\
+ ${libs.junit.classpath}
+javadoc.additionalparam=
+javadoc.author=false
+javadoc.encoding=
+javadoc.noindex=false
+javadoc.nonavbar=false
+javadoc.notree=false
+javadoc.private=false
+javadoc.splitindex=true
+javadoc.use=true
+javadoc.version=false
+javadoc.windowtitle=
+platform.active=default_platform
+project.OmegaT=../../../omegat
+reference.OmegaT.jar=${project.OmegaT}/dist/OmegaT.jar
+run.classpath=\
+ ${javac.classpath}:\
+ ${build.classes.dir}
+# Space-separated list of JVM arguments used when running the project
+# (you may also define separate properties like run-sys-prop.name=value instead of -Dname=value
+# or test-sys-prop.name=value to set system properties for unit tests):
+run.jvmargs=
+run.test.classpath=\
+ ${javac.test.classpath}:\
+ ${build.test.classes.dir}
+src.dir=src
diff --git a/OmegaT/addons/javahelp-filters/nbproject/project.xml b/OmegaT/addons/javahelp-filters/nbproject/project.xml
new file mode 100644
index 0000000..ab6c8f3
--- /dev/null
+++ b/OmegaT/addons/javahelp-filters/nbproject/project.xml
@@ -0,0 +1,24 @@
+
+
+ org.netbeans.modules.java.j2seproject
+
+
+ javahelp-filters
+ 1.6
+
+
+
+
+
+
+
+ OmegaT
+ jar
+
+ jar
+ clean
+ jar
+
+
+
+
diff --git a/OmegaT/addons/nbedge-filter/build.xml b/OmegaT/addons/nbedge-filter/build.xml
new file mode 100644
index 0000000..80e6686
--- /dev/null
+++ b/OmegaT/addons/nbedge-filter/build.xml
@@ -0,0 +1,17 @@
+
+
+ Builds, tests, and runs the project nbedge-filter.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/OmegaT/addons/nbedge-filter/manifest.mf b/OmegaT/addons/nbedge-filter/manifest.mf
new file mode 100644
index 0000000..b525043
--- /dev/null
+++ b/OmegaT/addons/nbedge-filter/manifest.mf
@@ -0,0 +1,5 @@
+Manifest-Version: 1.0
+OmegaT-Plugin: true
+
+Name: org.omegat.filters2.xml.edge.NBEdgeFilter
+OmegaT-Filter: true
\ No newline at end of file
diff --git a/OmegaT/addons/nbedge-filter/nbproject/build-impl.xml b/OmegaT/addons/nbedge-filter/nbproject/build-impl.xml
new file mode 100644
index 0000000..fa8693c
--- /dev/null
+++ b/OmegaT/addons/nbedge-filter/nbproject/build-impl.xml
@@ -0,0 +1,486 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must set src.dir
+ Must set build.dir
+ Must set dist.dir
+ Must set build.classes.dir
+ Must set dist.javadoc.dir
+ Must set build.test.classes.dir
+ Must set build.test.results.dir
+ Must set build.classes.excludes
+ Must set dist.jar
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select some files in the IDE or set javac.includes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set run.class
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set debug.class
+
+
+
+
+ Must set fix.includes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select some files in the IDE or set javac.includes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Some tests failed; see details above.
+
+
+
+
+
+
+
+
+ Must select some files in the IDE or set test.includes
+
+
+
+ Some tests failed; see details above.
+
+
+
+
+ Must select one file in the IDE or set test.class
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set applet.url
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set applet.url
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/OmegaT/addons/nbedge-filter/nbproject/genfiles.properties b/OmegaT/addons/nbedge-filter/nbproject/genfiles.properties
new file mode 100644
index 0000000..b88a68e
--- /dev/null
+++ b/OmegaT/addons/nbedge-filter/nbproject/genfiles.properties
@@ -0,0 +1,8 @@
+build.xml.data.CRC32=d67b6303
+build.xml.script.CRC32=3daf673e
+build.xml.stylesheet.CRC32=e2435cb5
+# This file is used by a NetBeans-based IDE to track changes in generated files such as build-impl.xml.
+# Do not edit this file. You may delete it but then the IDE will never regenerate such files for you.
+nbproject/build-impl.xml.data.CRC32=1520cbf5
+nbproject/build-impl.xml.script.CRC32=b0d9e943
+nbproject/build-impl.xml.stylesheet.CRC32=3b89b5a6
diff --git a/OmegaT/addons/nbedge-filter/nbproject/project.properties b/OmegaT/addons/nbedge-filter/nbproject/project.properties
new file mode 100644
index 0000000..727d950
--- /dev/null
+++ b/OmegaT/addons/nbedge-filter/nbproject/project.properties
@@ -0,0 +1,58 @@
+application.args=
+build.classes.dir=${build.dir}/classes
+build.classes.excludes=**/*.java,**/*.form
+# This directory is removed when the project is cleaned:
+build.dir=build
+# Only compile against the classpath explicitly listed here:
+build.sysclasspath=ignore
+build.test.classes.dir=${build.dir}/test/classes
+build.test.results.dir=${build.dir}/test/results
+debug.classpath=\
+ ${run.classpath}
+debug.test.classpath=\
+ ${run.test.classpath}
+# This directory is removed when the project is cleaned:
+dist.dir=dist
+dist.jar=${dist.dir}/nbedge-filter.jar
+dist.javadoc.dir=${dist.dir}/javadoc
+file.reference.nbedge-filter-src=src
+jar.compress=false
+javac.classpath=\
+ ${reference.OmegaT.jar}
+# Space-separated list of extra javac options
+javac.compilerargs=
+javac.deprecation=false
+javac.source=${default.javac.source}
+javac.target=${default.javac.target}
+javac.test.classpath=\
+ ${javac.classpath}:\
+ ${build.classes.dir}:\
+ ${libs.junit.classpath}
+javadoc.additionalparam=
+javadoc.author=false
+javadoc.encoding=
+javadoc.noindex=false
+javadoc.nonavbar=false
+javadoc.notree=false
+javadoc.private=false
+javadoc.splitindex=true
+javadoc.use=true
+javadoc.version=false
+javadoc.windowtitle=
+main.class=
+manifest.file=manifest.mf
+no.dependencies=true
+platform.active=default_platform
+project.OmegaT=../../../omegat
+reference.OmegaT.jar=${project.OmegaT}/dist/OmegaT.jar
+run.classpath=\
+ ${javac.classpath}:\
+ ${build.classes.dir}
+# Space-separated list of JVM arguments used when running the project
+# (you may also define separate properties like run-sys-prop.name=value instead of -Dname=value
+# or test-sys-prop.name=value to set system properties for unit tests):
+run.jvmargs=
+run.test.classpath=\
+ ${javac.test.classpath}:\
+ ${build.test.classes.dir}
+src.dir=${file.reference.nbedge-filter-src}
diff --git a/OmegaT/addons/nbedge-filter/nbproject/project.xml b/OmegaT/addons/nbedge-filter/nbproject/project.xml
new file mode 100644
index 0000000..6513637
--- /dev/null
+++ b/OmegaT/addons/nbedge-filter/nbproject/project.xml
@@ -0,0 +1,24 @@
+
+
+ org.netbeans.modules.java.j2seproject
+
+
+ nbedge-filter
+ 1.6
+
+
+
+
+
+
+
+ OmegaT
+ jar
+
+ jar
+ clean
+ jar
+
+
+
+
diff --git a/OmegaT/addons/properties-import/build.xml b/OmegaT/addons/properties-import/build.xml
new file mode 100644
index 0000000..c227378
--- /dev/null
+++ b/OmegaT/addons/properties-import/build.xml
@@ -0,0 +1,19 @@
+
+
+ Builds, tests, and runs the project properties-import.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/OmegaT/addons/properties-import/gpl-2.0.txt b/OmegaT/addons/properties-import/gpl-2.0.txt
new file mode 100644
index 0000000..82fa1da
--- /dev/null
+++ b/OmegaT/addons/properties-import/gpl-2.0.txt
@@ -0,0 +1,339 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License along
+ with this program; if not, write to the Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) year name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ , 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.
diff --git a/OmegaT/addons/properties-import/manifest.mf b/OmegaT/addons/properties-import/manifest.mf
new file mode 100644
index 0000000..83abe09
--- /dev/null
+++ b/OmegaT/addons/properties-import/manifest.mf
@@ -0,0 +1,3 @@
+Manifest-Version: 1.0
+Class-Path: lib/lib-mnemonics.jar
+Main-Class: org.omegat.tools.align.bundles.ImportBundles
diff --git a/OmegaT/addons/properties-import/nbproject/build-impl.xml b/OmegaT/addons/properties-import/nbproject/build-impl.xml
new file mode 100644
index 0000000..13a0b05
--- /dev/null
+++ b/OmegaT/addons/properties-import/nbproject/build-impl.xml
@@ -0,0 +1,486 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must set src.dir
+ Must set build.dir
+ Must set dist.dir
+ Must set build.classes.dir
+ Must set dist.javadoc.dir
+ Must set build.test.classes.dir
+ Must set build.test.results.dir
+ Must set build.classes.excludes
+ Must set dist.jar
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select some files in the IDE or set javac.includes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set run.class
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set debug.class
+
+
+
+
+ Must set fix.includes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select some files in the IDE or set javac.includes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Some tests failed; see details above.
+
+
+
+
+
+
+
+
+ Must select some files in the IDE or set test.includes
+
+
+
+ Some tests failed; see details above.
+
+
+
+
+ Must select one file in the IDE or set test.class
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set applet.url
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set applet.url
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/OmegaT/addons/properties-import/nbproject/genfiles.properties b/OmegaT/addons/properties-import/nbproject/genfiles.properties
new file mode 100644
index 0000000..d0a40ad
--- /dev/null
+++ b/OmegaT/addons/properties-import/nbproject/genfiles.properties
@@ -0,0 +1,8 @@
+build.xml.data.CRC32=a78e934c
+build.xml.script.CRC32=7acbf7b6
+build.xml.stylesheet.CRC32=e2435cb5
+# This file is used by a NetBeans-based IDE to track changes in generated files such as build-impl.xml.
+# Do not edit this file. You may delete it but then the IDE will never regenerate such files for you.
+nbproject/build-impl.xml.data.CRC32=c748df97
+nbproject/build-impl.xml.script.CRC32=8069193c
+nbproject/build-impl.xml.stylesheet.CRC32=3b89b5a6
diff --git a/OmegaT/addons/properties-import/nbproject/project.properties b/OmegaT/addons/properties-import/nbproject/project.properties
new file mode 100644
index 0000000..5c7c55e
--- /dev/null
+++ b/OmegaT/addons/properties-import/nbproject/project.properties
@@ -0,0 +1,60 @@
+javac.debug=true
+
+
+application.args=
+build.classes.dir=${build.dir}/classes
+build.classes.excludes=**/*.java,**/*.form
+# This directory is removed when the project is cleaned:
+build.dir=build
+# Only compile against the classpath explicitly listed here:
+build.sysclasspath=ignore
+build.test.classes.dir=${build.dir}/test/classes
+build.test.results.dir=${build.dir}/test/results
+debug.classpath=\
+ ${run.classpath}
+debug.test.classpath=\
+ ${run.test.classpath}
+# This directory is removed when the project is cleaned:
+dist.dir=dist
+dist.jar=properties-import.jar
+dist.javadoc.dir=${dist.dir}/javadoc
+file.reference.properties-import-src=src
+jar.compress=false
+javac.classpath=\
+ ${reference.lib-mnemonics.jar}
+# Space-separated list of extra javac options
+javac.compilerargs=
+javac.deprecation=false
+javac.source=${default.javac.source}
+javac.target=${default.javac.target}
+javac.test.classpath=\
+ ${javac.classpath}:\
+ ${build.classes.dir}:\
+ ${libs.junit.classpath}
+javadoc.additionalparam=
+javadoc.author=false
+javadoc.encoding=
+javadoc.noindex=false
+javadoc.nonavbar=false
+javadoc.notree=false
+javadoc.private=false
+javadoc.splitindex=true
+javadoc.use=true
+javadoc.version=false
+javadoc.windowtitle=
+main.class=org.omegat.tools.align.bundles.ImportBundles
+manifest.file=manifest.mf
+platform.active=default_platform
+project.lib-mnemonics=../../lib-mnemonics
+reference.lib-mnemonics.jar=${project.lib-mnemonics}/dist/lib-mnemonics.jar
+run.classpath=\
+ ${javac.classpath}:\
+ ${build.classes.dir}
+# Space-separated list of JVM arguments used when running the project
+# (you may also define separate properties like run-sys-prop.name=value instead of -Dname=value
+# or test-sys-prop.name=value to set system properties for unit tests):
+run.jvmargs=
+run.test.classpath=\
+ ${javac.test.classpath}:\
+ ${build.test.classes.dir}
+src.dir=${file.reference.properties-import-src}
diff --git a/OmegaT/addons/properties-import/nbproject/project.xml b/OmegaT/addons/properties-import/nbproject/project.xml
new file mode 100644
index 0000000..ca192f3
--- /dev/null
+++ b/OmegaT/addons/properties-import/nbproject/project.xml
@@ -0,0 +1,24 @@
+
+
+ org.netbeans.modules.java.j2seproject
+
+
+ properties-import
+ 1.6
+
+
+
+
+
+
+
+ lib-mnemonics
+ jar
+
+ jar
+ clean
+ jar
+
+
+
+
diff --git a/OmegaT/addons/properties-import/readme.txt b/OmegaT/addons/properties-import/readme.txt
new file mode 100644
index 0000000..79f83fa
--- /dev/null
+++ b/OmegaT/addons/properties-import/readme.txt
@@ -0,0 +1,23 @@
+.properties Import 1.4 ReadMe file
+
+This import tool supplements OmegaT in the following way:
+
+If there's an existing translation of Java application, usually done using
+Java(TM) Resource Bundles (.properties files), then in order not to loose the
+existing work, while migrating to OmegaT, translator is given an opportunity
+to import his work into OmegaT-compatible TMX file.
+
+To run from a terminal or DOS window, change to this directory
+and type
+ java -jar properties_import.jar
+
+The sources are supplied inside the OmegaT sources distribution.
+
+----------------------------------------------------------------------
+
+version 1.4_1: Corrected the Japanese localization
+version 1.4: Added the Japanese localization
+Version 1.3: Fixed a filecase bug (occuring only on Unixes)
+Version 1.2: Make it look nicer
+Version 1.1: Some bugs fixed
+Verison 1.0: Initial release
diff --git a/OmegaT/addons/sentseg-tmx/build.xml b/OmegaT/addons/sentseg-tmx/build.xml
new file mode 100644
index 0000000..56c04c3
--- /dev/null
+++ b/OmegaT/addons/sentseg-tmx/build.xml
@@ -0,0 +1,26 @@
+
+
+ Builds, tests, and runs the project sentseg-tmx.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/OmegaT/addons/sentseg-tmx/manifest.mf b/OmegaT/addons/sentseg-tmx/manifest.mf
new file mode 100644
index 0000000..8749977
--- /dev/null
+++ b/OmegaT/addons/sentseg-tmx/manifest.mf
@@ -0,0 +1,3 @@
+Manifest-Version: 1.0
+Main-Class: org.omegat.tools.tmx.sentseg.SentSeg
+Class-Path: lib/OmegaT.jar lib/lib-mnemonics.jar
diff --git a/OmegaT/addons/sentseg-tmx/nbproject/build-impl.xml b/OmegaT/addons/sentseg-tmx/nbproject/build-impl.xml
new file mode 100644
index 0000000..8d9a718
--- /dev/null
+++ b/OmegaT/addons/sentseg-tmx/nbproject/build-impl.xml
@@ -0,0 +1,488 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must set src.dir
+ Must set build.dir
+ Must set dist.dir
+ Must set build.classes.dir
+ Must set dist.javadoc.dir
+ Must set build.test.classes.dir
+ Must set build.test.results.dir
+ Must set build.classes.excludes
+ Must set dist.jar
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select some files in the IDE or set javac.includes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set run.class
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set debug.class
+
+
+
+
+ Must set fix.includes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select some files in the IDE or set javac.includes
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Some tests failed; see details above.
+
+
+
+
+
+
+
+
+ Must select some files in the IDE or set test.includes
+
+
+
+ Some tests failed; see details above.
+
+
+
+
+ Must select one file in the IDE or set test.class
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set applet.url
+
+
+
+
+
+
+
+
+ Must select one file in the IDE or set applet.url
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/OmegaT/addons/sentseg-tmx/nbproject/genfiles.properties b/OmegaT/addons/sentseg-tmx/nbproject/genfiles.properties
new file mode 100644
index 0000000..49a9683
--- /dev/null
+++ b/OmegaT/addons/sentseg-tmx/nbproject/genfiles.properties
@@ -0,0 +1,8 @@
+build.xml.data.CRC32=feb37075
+build.xml.script.CRC32=e2eb66a2
+build.xml.stylesheet.CRC32=e2435cb5
+# This file is used by a NetBeans-based IDE to track changes in generated files such as build-impl.xml.
+# Do not edit this file. You may delete it but then the IDE will never regenerate such files for you.
+nbproject/build-impl.xml.data.CRC32=642a391c
+nbproject/build-impl.xml.script.CRC32=d17f31bf
+nbproject/build-impl.xml.stylesheet.CRC32=3b89b5a6
diff --git a/OmegaT/addons/sentseg-tmx/nbproject/project.properties b/OmegaT/addons/sentseg-tmx/nbproject/project.properties
new file mode 100644
index 0000000..d9da3c4
--- /dev/null
+++ b/OmegaT/addons/sentseg-tmx/nbproject/project.properties
@@ -0,0 +1,63 @@
+application.args=
+build.classes.dir=${build.dir}/classes
+build.classes.excludes=**/*.java,**/*.form
+# This directory is removed when the project is cleaned:
+build.dir=build
+# Only compile against the classpath explicitly listed here:
+build.sysclasspath=ignore
+build.test.classes.dir=${build.dir}/test/classes
+build.test.results.dir=${build.dir}/test/results
+debug.classpath=\
+ ${run.classpath}
+debug.test.classpath=\
+ ${run.test.classpath}
+# This directory is removed when the project is cleaned:
+dist.dir=dist
+dist.jar=sentseg-tmx.jar
+dist.javadoc.dir=${dist.dir}/javadoc
+file.reference.lib-mnemonics.jar=lib/lib-mnemonics.jar
+file.reference.OmegaT.jar=lib/OmegaT.jar
+file.reference.sentseg-tmx-src=src
+jar.compress=false
+javac.classpath=\
+ ${reference.OmegaT.jar}:\
+ ${reference.lib-mnemonics.jar}
+# Space-separated list of extra javac options
+javac.compilerargs=
+javac.deprecation=false
+javac.source=${default.javac.source}
+javac.target=${default.javac.target}
+javac.test.classpath=\
+ ${javac.classpath}:\
+ ${build.classes.dir}:\
+ ${libs.junit.classpath}
+javadoc.additionalparam=
+javadoc.author=false
+javadoc.encoding=
+javadoc.noindex=false
+javadoc.nonavbar=false
+javadoc.notree=false
+javadoc.private=false
+javadoc.splitindex=true
+javadoc.use=true
+javadoc.version=false
+javadoc.windowtitle=
+main.class=org.omegat.tools.tmx.sentseg.SentSeg
+manifest.file=manifest.mf
+no.dependencies=true
+platform.active=default_platform
+project.lib-mnemonics=../../lib-mnemonics
+project.OmegaT=../../../omegat
+reference.lib-mnemonics.jar=${project.lib-mnemonics}/dist/lib-mnemonics.jar
+reference.OmegaT.jar=${project.OmegaT}/dist/OmegaT.jar
+run.classpath=\
+ ${javac.classpath}:\
+ ${build.classes.dir}
+# Space-separated list of JVM arguments used when running the project
+# (you may also define separate properties like run-sys-prop.name=value instead of -Dname=value
+# or test-sys-prop.name=value to set system properties for unit tests):
+run.jvmargs=
+run.test.classpath=\
+ ${javac.test.classpath}:\
+ ${build.test.classes.dir}
+src.dir=${file.reference.sentseg-tmx-src}
diff --git a/OmegaT/addons/sentseg-tmx/nbproject/project.xml b/OmegaT/addons/sentseg-tmx/nbproject/project.xml
new file mode 100644
index 0000000..5c5801b
--- /dev/null
+++ b/OmegaT/addons/sentseg-tmx/nbproject/project.xml
@@ -0,0 +1,32 @@
+
+
+ org.netbeans.modules.java.j2seproject
+
+
+ sentseg-tmx
+ 1.6
+
+
+
+
+
+
+
+ OmegaT
+ jar
+
+ jar
+ clean
+ jar
+
+
+ lib-mnemonics
+ jar
+
+ jar
+ clean
+ jar
+
+
+
+
diff --git a/OmegaT/addons/sentseg-tmx/readme.txt b/OmegaT/addons/sentseg-tmx/readme.txt
new file mode 100644
index 0000000..55e588b
--- /dev/null
+++ b/OmegaT/addons/sentseg-tmx/readme.txt
@@ -0,0 +1,14 @@
+TMX Sentence Segmenter 1.0 ReadMe file
+
+This tool allows to re-segment old TMX files (created by OmegaT)
+in a sentence-segmentation mode.
+
+To run from a terminal or DOS window, change to this directory
+and type
+ java -jar sentseg-tmx.jar
+
+----------------------------------------------------------------------
+
+Verison 1.0: Initial release
+
+Verison 1.1: Updated to work using OmegaT 1.6.0 RC7+ core classes
diff --git a/OmegaT/build.xml b/OmegaT/build.xml
new file mode 100644
index 0000000..96025ce
--- /dev/null
+++ b/OmegaT/build.xml
@@ -0,0 +1,379 @@
+
+
+
+
+
+ Builds, tests, and runs the project OmegaT.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/OmegaT/build/built-jar.properties b/OmegaT/build/built-jar.properties
new file mode 100644
index 0000000..4fa530d
--- /dev/null
+++ b/OmegaT/build/built-jar.properties
@@ -0,0 +1,4 @@
+#Sun, 17 Jun 2012 15:41:35 -0400
+
+
+E\:\\2012Fall\\Prjs\\OmegaT\\OmegaT=
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/glossary/.ignoreme b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/glossary/.ignoreme
new file mode 100644
index 0000000..e69de29
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/omegat.project b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/omegat.project
new file mode 100644
index 0000000..c9d1ee9
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/omegat.project
@@ -0,0 +1,12 @@
+
+
+
+ __DEFAULT__
+ __DEFAULT__
+ __DEFAULT__
+ __DEFAULT__
+ EN
+ EN
+ true
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/omegat/.ignoreme b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/omegat/.ignoreme
new file mode 100644
index 0000000..e69de29
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/.ignoreme b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/.ignoreme
new file mode 100644
index 0000000..e69de29
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/AboutOmegaT.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/AboutOmegaT.xml
new file mode 100644
index 0000000..705d57c
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/AboutOmegaT.xml
@@ -0,0 +1,229 @@
+
+
+
+ About <application>OmegaT</application> - introduction
+
+
+ OmegaT highlights
+
+ OmegaT is a free multi platform Computer
+ Aided Translation tool, with the following highlights:
+
+
+
+ Translation
+ memory:OmegaT stores your
+ translations in a translation memory file. At the same time, it can
+ use memories files from previous translations for reference.
+ Translation memories can be very useful in a translation where there
+ are numerous repetitions or reasonably similar segments of text.
+ OmegaT uses translation memories to store your previous translations
+ and then suggest likely translations for the text you are currently
+ working on.
+
+ These translation memories can be very useful when a document
+ that has already been translated needs to be updated. Unchanged
+ sentences are automatically translated, while updated sentences are
+ shown with the translation of the most similar, older sentence.
+ Modifications to the original document are thus handled with greater
+ ease. If you are supplied with previously created translation memories
+ , for example by your translation agency or your client, OmegaT is
+ able to use these as reference memories.
+
+ OmegaT uses the standard tmx file format to store and access
+ translation memories, which guarantees that you can exchange your
+ translation material with other CAT applications supporting this file
+ format.
+
+
+
+
+
+ Terminology management:
+ Terminology management is important for translation consistency.
+ OmegaT uses glossaries containing translations of single words or
+ small phrases: a simplified bilingual dictionary for a specific
+ domain. For your reference, OmegaT displays the translation of any
+ words that happen to be present in the segment that currently has
+ focus.
+
+
+
+
+
+ Translation process: Imagine
+ having to translate something; from a single file to a folder
+ containing subfolders each with a number of files in a variety of
+ formats. When you let OmegaT know the files that you need to
+ translate, it looks for the files it understands based on file
+ filtering rules, recognizes the textual parts within them, splits up
+ the text groups according to the segmentation rules, and displays the
+ segments one by one so that you can proceed with the translation.
+ OmegaT stores your translations and proposes possible translations
+ from similar segments in previous memory files. When you are ready to
+ view the final product, you can export the translated files, open them
+ in the appropriate application and view the translation in the final
+ format...
+
+
+
+
+
+ Summary of chapters
+
+ This documentation is intended both as a tutorial and as a reference
+ guide. Here is a short summary of the chapters and their contents.
+
+
+
+ Instant start guide: this
+ chapter is intended as an Instant Start Guide for beginners and “tyre
+ kickers”, showing the complete procedure from opening a new
+ translation project through to completing the translation.
+
+
+
+
+
+ Installing and running OmegaT:
+ this chapter is useful when you first begin using OmegaT.
+ It contains the specific instructions on how to install OmegaT and run
+ it on Windows, Mac OS X and Linux. For advanced users, the chapter
+ describes the command line mode and its possibilities.
+
+
+
+
+
+ The user interface,Main Menu and Keyboard Shortcuts: these two
+ chapters are likely to be heavily consulted, since they explain the
+ user interface of OmegaT and the functions available via the main menu
+ and the keyboard shortcuts.
+
+
+
+
+
+ Project properties, OmegaT Files and
+ Directories: a project in the context of OmegaT is the
+ piece of work that OmegaT as a CAT tool is able to handle. This
+ chapter describes the project properties, such as the source and
+ target languages. The second of these chapters describes the various
+ subfolders and files in a translation project and their role as well
+ as other user and application files associated with OmegaT.
+
+
+
+
+
+ Editing field behavior: a short
+ chapter describing how to set up the editing behavior of the segment
+ being translated.
+
+
+
+
+
+ Working with plain text and
+ Working with formatted text: these
+ two chapters explain certain important points concerning texts to be
+ translated, such as the encoding set (in the case of plain text files)
+ and tag handling (in the case of formatted text).
+
+
+
+
+
+ Translation memories: explains
+ the role of the various subdirectories containing translation
+ memories, and provides information on other important aspects relating
+ to translation memories.
+
+
+
+ Segmentation:translation memory
+ tools work with textual units called segments. In OmegaT, segments can
+ be based on paragraphs or on segmentation rules. Paragraph
+ segmentation is less frequently used, but can be useful in cases of
+ so-called "creative" texts, The rule-based segmentation is usually
+ synonymous with sentence-based segmentation. A number of rule sets are
+ provided while additional rules can be defined by the user, as
+ described in this chapter.
+
+
+
+ Searches andRegular
+ expressions: Searches in OmegaT can be as simple as
+ "list segments with the word 'kangaroo'
+ ". They can also be complex, allowing for instance to
+ search for segments with two or more consecutive spaces. In this case
+ the regular expression ^s^s+ would be used to find and list the
+ offending segments. Regular expressions are also used extensively in
+ the segmentation rules.
+
+
+
+ Dictionaries, Glossaries,
+ Machine translation and Spellchecker: OmegaT enables the extensive of
+ dictionaries and glossaries. If an Internet connection is available,
+ various MT services such as Google Translate can be utilized from
+ within OmegaT. If spell checking is activated, spelling mistakes and
+ typos are recognized and can be corrected during translation.
+
+
+
+ Miscellanea: deals with other
+ issues of interest, such as how to avoid losing data.
+
+
+
+ Appendices contain the
+ following information
+
+
+
+ OmegaT on the web:
+ information regarding on-line OmegaT resources
+
+
+
+
+
+ Languages: contains the ISO
+ list of languages and language codes
+
+
+
+
+
+ Keyboard shortcuts in the
+ editor: the list of shortcuts used in the editor
+
+
+
+ Shortcuts
+ customization:shortcuts can be customized to suit your
+ personal preferences
+
+
+
+
+
+ Legal notices
+
+
+
+
+
+ Keyword index: an extensive
+ keyword index is provided to help the reader find the relevant
+ information.
+
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/App_Aknowledgements.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/App_Aknowledgements.xml
new file mode 100644
index 0000000..50b72f2
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/App_Aknowledgements.xml
@@ -0,0 +1,60 @@
+
+
+
+ Acknowledgements
+
+
+ Thank you all!
+
+ Whatever the inconsistencies, omissions and straightforward errors
+ you may find in the present version, I declare them all my own. This
+ manual, however, would not be possible without the help and support from a
+ number of people. Explicit thanks to:
+
+
+
+ Mark Prior: correcting my first draft was an act of love for
+ OmegaT and the English language.
+
+
+
+
+
+ Didier Briel: I could not do without Didier's patient and
+ persistent help with DocBook intricacies. Not to mention his care and
+ diligence, keeping repositories intact and in good order.
+
+
+
+ Samuel Murray: for the introductory chapter "Learn to use OmegaT
+ in 5 minutes" .
+
+
+
+
+
+ Will Helton: his final reading of the draft has spared me a lot
+ of embarrassment. One could only wonder, how many the and a
+ prepositions would still be missing without his invaluable
+ help.
+
+
+
+
+
+ Jean-Christophe Helary: special thanks to JC for his concise
+ description of OmegaT run, command line parameters and all other
+ details, I have yet to notice.
+
+
+
+ Last but not least: my thanks to all the contributors to
+ OmegaT documentation tracker for all the inconsistencies found
+ in the previous versions of the documentation. Keep up your good
+ work!
+
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/App_Keyboard.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/App_Keyboard.xml
new file mode 100644
index 0000000..7512fef
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/App_Keyboard.xml
@@ -0,0 +1,196 @@
+
+
+
+ Keyboard shortcuts in the editor
+
+ This short text describes key behavior in the editor pane. The term
+ "Move to inside segment" means, that the cursor moves to the beginning of
+ the segment if it was previously before the segment, and to the end of the
+ segment if it was previously after it.
+
+
+ Key behavior in the editor
+
+
+
+
+
+
+
+
+ Key combination
+
+ Action
+
+
+
+
+
+ Left:
+
+ one char left, but not further than the beginning of
+ segment
+
+
+
+ Right:
+
+ one char right, but not further than the end of
+ segment
+
+
+
+ Ctrl+Left:
+
+ one word left, but not further than the beginning of
+ segment
+
+
+
+ Ctrl+Right:
+
+ one word right, but not further than the end of
+ segment
+
+
+
+ PgUp:
+
+ page up through the document
+
+
+
+ PgDn:
+
+ page down through the document
+
+
+
+ Home*
+
+ move to the beginning of the line in the segment
+
+
+
+ End*
+
+ move to the end of the line in the segment
+
+
+
+ Ctrl+Home
+
+ move to the start of the segment
+
+
+
+ Ctrl+End
+
+ move to the end of the segment
+
+
+
+ Ctrl+PgUp
+
+ move to the start of the document (Mac: Cmd+PgUp)
+
+
+
+ Ctrl+PgDn
+
+ move to the end of the document (Mac: Cmd+PgDn)
+
+
+
+ Backspace*
+
+ remove char before cursor
+
+
+
+ Delete*
+
+ remove char after cursor
+
+
+
+ Ctrl+Backspace
+
+ remove chars up to the start of the current word (Mac:
+ Alt+Backspace)
+
+
+
+ Ctrl+Delete
+
+ remove chars up to the start of next word (Mac: Alt+Delete)
+
+
+
+ Ctrl+Enter
+
+ open previous segment (Mac: Cmd+Enter)
+
+
+
+ Ctrl+A
+
+ select complete segment (Mac: Cmd+A)
+
+
+
+ Ctrl+Shift+O
+
+ RTL-LTR switch
+
+
+
+
+
+ * These keys behave differently when the cursor is outside the
+ editable segment:
+
+
+
+ Home: cursor to the beginning of
+ the active segment
+
+
+
+ End: cursor to the end of the
+ active segment
+
+
+
+ Backspace: nothing
+
+
+
+ Delete: nothing
+
+
+
+ Any char key, if clicked outside
+ editable segment, will be ignored.
+
+
+
+ The "Shift" key doesn't exhibit any special behavior per se: when the
+ "Shift" key is pressed, all keys move the cursor in their usual
+ manner.
+
+ System-wide commands: Paste (Ctrl+V
+ or Ctrl+Insert), Cut (Ctrl+X or Ctrl+C),
+ Insert match (Ctrl+I) and Insert source
+ (Ctrl+Shift+I) act in principle on any
+ selection, including those that extend beyond the current segment. In such a
+ case the selection will of course be pared down to segment
+ boundaries.
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/App_Languages.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/App_Languages.xml
new file mode 100644
index 0000000..2d1365e
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/App_Languages.xml
@@ -0,0 +1,961 @@
+
+
+
+ Languages - ISO 639 code list
+ <indexterm class="singular">
+ <primary>Languages</primary>
+ </indexterm>
+ <indexterm class="singular">
+ <primary>ISO language codes</primary>
+ </indexterm>
+ <indexterm class="singular">
+ <primary>Project</primary>
+ <secondary>Properties</secondary>
+ <seealso>Languages</seealso>
+ </indexterm>
+
+
+ Please check the
+ ISO 639 Code Tables for further and up-to-date information about
+ language codes.
+
+
+ ISO 639-1/639-2 Language code list
+
+
+
+
+
+
+ Language name
+ ISO 639-1
+ ISO 639-2
+
+
+
+
+ Abkhaz
+ ab
+ abk
+
+
+ Afar
+ aa
+ aar
+
+
+ Afrikaans
+ af
+ afr
+
+
+ Akan
+ ak
+ aka
+
+
+ Albanian
+ sq
+ sqi
+
+
+ Amharic
+ am
+ amh
+
+
+ Arabic
+ ar
+ ara
+
+
+ Aragonese
+ an
+ arg
+
+
+ Armenian
+ hy
+ hye
+
+
+ Assamese
+ as
+ asm
+
+
+ Avaric
+ av
+ ava
+
+
+ Avestan
+ ae
+ ave
+
+
+ Aymara
+ ay
+ aym
+
+
+ Azerbaijani
+ az
+ aze
+
+
+ Bambara
+ bm
+ bam
+
+
+ Bashkir
+ ba
+ bak
+
+
+ Basque
+ eu
+ eus
+
+
+ Belarusian
+ be
+ bel
+
+
+ Bengali
+ bn
+ ben
+
+
+ Bihari
+ bh
+ bih
+
+
+ Bislama
+ bi
+ bis
+
+
+ Bosnian
+ bs
+ bos
+
+
+ Breton
+ br
+ bre
+
+
+ Bulgarian
+ bg
+ bul
+
+
+ Burmese
+ my
+ mya
+
+
+ Catalan
+ ca
+ cat
+
+
+ Chamorro
+ ch
+ cha
+
+
+ Chechen
+ ce
+ che
+
+
+ Chichewa, Chewa, Nyanja
+ ny
+ nya
+
+
+ Chinese
+ zh
+ zho
+
+
+ Chuvash
+ cv
+ chv
+
+
+ Cornish
+ kw
+ cor
+
+
+ Corsican
+ co
+ cos
+
+
+ Cree
+ cr
+ cre
+
+
+ Croatian
+ hr
+ hrv
+
+
+ Czech
+ cs
+ ces
+
+
+ Danish
+ da
+ dan
+
+
+ Divehi, Dhivehi, Maldivian
+ dv
+ div
+
+
+ Dutch
+ nl
+ nld
+
+
+ Dzongkha
+ dz
+ dzo
+
+
+ English
+ en
+ eng
+
+
+ Esperanto
+ eo
+ epo
+
+
+ Estonian
+ et
+ est
+
+
+ Ewe
+ ee
+ ewe
+
+
+ Faroese
+ fo
+ fao
+
+
+ Fijian
+ fj
+ fij
+
+
+ Finnish
+ fi
+ fin
+
+
+ French
+ fr
+ fra
+
+
+ Fula, Fulah, Pulaar, Pular
+ ff
+ ful
+
+
+ Galician
+ gl
+ glg
+
+
+ Georgian
+ ka
+ kat
+
+
+ German
+ de
+ deu
+
+
+ Greek, Modern
+ el
+ ell
+
+
+ Guaraní
+ gn
+ grn
+
+
+ Gujarati
+ gu
+ guj
+
+
+ Haitian, Haitian Creole
+ ht
+ hat
+
+
+ Hausa
+ ha
+ hau
+
+
+ Hebrew (modern)
+ he
+ heb
+
+
+ Herero
+ hz
+ her
+
+
+ Hindi
+ hi
+ hin
+
+
+ Hiri Motu
+ ho
+ hmo
+
+
+ Hungarian
+ hu
+ hun
+
+
+ Interlingua
+ ia
+ ina
+
+
+ Indonesian
+ id
+ ind
+
+
+ Interlingue
+ ie
+ ile
+
+
+ Irish
+ ga
+ gle
+
+
+ Igbo
+ ig
+ ibo
+
+
+ Inupiaq
+ ik
+ ipk
+
+
+ Ido
+ io
+ ido
+
+
+ Icelandic
+ is
+ isl
+
+
+ Italian
+ it
+ ita
+
+
+ Inuktitut
+ iu
+ iku
+
+
+ Japanese
+ ja
+ jpn
+
+
+ Javanese
+ jv
+ jav
+
+
+ Kalaallisut, Greenlandic
+ kl
+ kal
+
+
+ Kannada
+ kn
+ kan
+
+
+ Kanuri
+ kr
+ kau
+
+
+ Kashmiri
+ ks
+ kas
+
+
+ Kazakh
+ kk
+ kaz
+
+
+ Khmer
+ km
+ khm
+
+
+ Kikuyu, Gikuyu
+ ki
+ kik
+
+
+ Kinyarwanda
+ rw
+ kin
+
+
+ Kirghiz, Kyrgyz
+ ky
+ kir
+
+
+ Komi
+ kv
+ kom
+
+
+ Kongo
+ kg
+ kon
+
+
+ Korean
+ ko
+ kor
+
+
+ Kurdish
+ ku
+ kur
+
+
+ Kwanyama, Kuanyama
+ kj
+ kua
+
+
+ Latin
+ la
+ lat
+
+
+ Luxembourgish, Letzeburgesch
+ lb
+ ltz
+
+
+ Luganda
+ lg
+ lug
+
+
+ Limburgish, Limburgan, Limburger
+ li
+ lim
+
+
+ Lingala
+ ln
+ lin
+
+
+ Lao
+ lo
+ lao
+
+
+ Lithuanian
+ lt
+ lit
+
+
+ Luba-Katanga
+ lu
+ lub
+
+
+ Latvian
+ lv
+ lav
+
+
+ Manx
+ gv
+ glv
+
+
+ Macedonian
+ mk
+ mkd
+
+
+ Malagasy
+ mg
+ mlg
+
+
+ Malay
+ ms
+ msa
+
+
+ Malayalam
+ ml
+ mal
+
+
+ Maltese
+ mt
+ mlt
+
+
+ Māori
+ mi
+ mri
+
+
+ Marathi (Marāṭhī)
+ mr
+ mar
+
+
+ Marshallese
+ mh
+ mah
+
+
+ Mongolian
+ mn
+ mon
+
+
+ Nauru
+ na
+ nau
+
+
+ Navajo, Navaho
+ nv
+ nav
+
+
+ Norwegian Bokmål
+ nb
+ nob
+
+
+ North Ndebele
+ nd
+ nde
+
+
+ Nepali
+ ne
+ nep
+
+
+ Ndonga
+ ng
+ ndo
+
+
+ Norwegian Nynorsk
+ nn
+ nno
+
+
+ Norwegian
+ no
+ nor
+
+
+ Nuosu
+ ii
+ iii
+
+
+ South Ndebele
+ nr
+ nbl
+
+
+ Occitan
+ oc
+ oci
+
+
+ Ojibwe, Ojibwa
+ oj
+ oji
+
+
+ Old Church Slavonic, Church Slavic, Church Slavonic, Old
+ Bulgarian, Old Slavonic
+ cu
+ chu
+
+
+ Oromo
+ om
+ orm
+
+
+ Oriya
+ or
+ ori
+
+
+ Ossetian, Ossetic
+ os
+ oss
+
+
+ Panjabi, Punjabi
+ pa
+ pan
+
+
+ Pāli
+ pi
+ pli
+
+
+ Persian
+ fa
+ fas
+
+
+ Polish
+ pl
+ pol
+
+
+ Pashto, Pushto
+ ps
+ pus
+
+
+ Portuguese
+ pt
+ por
+
+
+ Quechua
+ qu
+ que
+
+
+ Romansh
+ rm
+ roh
+
+
+ Kirundi
+ rn
+ run
+
+
+ Romanian, Moldavian, Moldovan
+ ro
+ ron
+
+
+ Russian
+ ru
+ rus
+
+
+ Sanskrit (Saṁskṛta)
+ sa
+ san
+
+
+ Sardinian
+ sc
+ srd
+
+
+ Sindhi
+ sd
+ snd
+
+
+ Northern Sami
+ se
+ sme
+
+
+ Samoan
+ sm
+ smo
+
+
+ Sango
+ sg
+ sag
+
+
+ Serbian
+ sr
+ srp
+
+
+ Scottish Gaelic, Gaelic
+ gd
+ gla
+
+
+ Shona
+ sn
+ sna
+
+
+ Sinhala, Sinhalese
+ si
+ sin
+
+
+ Slovak
+ sk
+ slk
+
+
+ Slovene
+ sl
+ slv
+
+
+ Somali
+ so
+ som
+
+
+ Southern Sotho
+ st
+ sot
+
+
+ Spanish, Castilian
+ es
+ spa
+
+
+ Sundanese
+ su
+ sun
+
+
+ Swahili
+ sw
+ swa
+
+
+ Swati
+ ss
+ ssw
+
+
+ Swedish
+ sv
+ swe
+
+
+ Tamil
+ ta
+ tam
+
+
+ Telugu
+ te
+ tel
+
+
+ Tajik
+ tg
+ tgk
+
+
+ Thai
+ th
+ tha
+
+
+ Tigrinya
+ ti
+ tir
+
+
+ Tibetan Standard, Tibetan, Central
+ bo
+ bod
+
+
+ Turkmen
+ tk
+ tuk
+
+
+ Tagalog
+ tl
+ tgl
+
+
+ Tswana
+ tn
+ tsn
+
+
+ Tonga (Tonga Islands)
+ to
+ ton
+
+
+ Turkish
+ tr
+ tur
+
+
+ Tsonga
+ ts
+ tso
+
+
+ Tatar
+ tt
+ tat
+
+
+ Twi
+ tw
+ twi
+
+
+ Tahitian
+ ty
+ tah
+
+
+ Uighur, Uyghur
+ ug
+ uig
+
+
+ Ukrainian
+ uk
+ ukr
+
+
+ Urdu
+ ur
+ urd
+
+
+ Uzbek
+ uz
+ uzb
+
+
+ Venda
+ ve
+ ven
+
+
+ Vietnamese
+ vi
+ vie
+
+
+ Volapük
+ vo
+ vol
+
+
+ Walloon
+ wa
+ wln
+
+
+ Welsh
+ cy
+ cym
+
+
+ Wolof
+ wo
+ wol
+
+
+ Western Frisian
+ fy
+ fry
+
+
+ Xhosa
+ xh
+ xho
+
+
+ Yiddish
+ yi
+ yid
+
+
+ Yoruba
+ yo
+ yor
+
+
+ Zhuang, Chuang
+ za
+ zha
+
+
+ Zulu
+ zu
+ zul
+
+
+
+
+ Help Menu
+
+
+ Shortcuts Customization
+
+ Help Menu
+
+
+
+
+
+
+
+
+
+
+
+ Menu Item
+
+ Default shortcut
+
+ Menu Item Code
+
+
+
+
+
+ User Manual...
+
+ F1
+
+ helpContentsMenuItem
+
+
+
+ About...
+
+
+
+ helpAboutMenuItem
+
+
+
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/App_Using_tokenizers_in_OmegaT.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/App_Using_tokenizers_in_OmegaT.xml
new file mode 100644
index 0000000..d8dd66a
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/App_Using_tokenizers_in_OmegaT.xml
@@ -0,0 +1,122 @@
+
+
+
+ Using tokenizers in OmegaT
+
+
+ Introduction
+
+ Tokenizers (or stemmers) improve the quality of matches by
+ recognizing inflected words in source and translation memory data. They
+ also improve glossary matching.
+
+ A stemmer for English, for example, should identify the string
+ "cats" (and possibly "catlike", "catty" etc.) as based on the root "cat",
+ and "stemmer", "stemming", "stemmed" as based on "stem". A stemming
+ algorithm reduces the words "fishing", "fished", "fish", and "fisher" to
+ the root word, "fish". This especially useful in case of languages that
+ use pre- and postfix forms for the stem words. Borrowing an example from
+ Slovenian, here "good" in all possible grammatically correct forms:
+
+
+
+ lep, lepa, lepo - singular, masculine, feminine, neutral
+
+
+
+
+
+ lepši, lepša, lepše . - comparative, nominative, masculine,
+ feminine, neutral, resp. Plural form of the adjective
+
+
+
+
+
+ najlepših - superlative, plural, genitive for M,F,N
+
+
+
+
+
+ Installation and command line use
+
+ A tokenizer package adapted from the Lucene project is distributed
+ as an OmegaT plug-in at
+ http://sourceforge.net/projects/omegat-plugins/files/. Download the most
+ recent files (OmegaT-tokenizers_0.4_2-2.1.zip at the time of this
+ writing).
+
+ To install the tokenizer, create a folder with the name "plugins" in
+ the folder where OmegaT.jar is found and unpack the above files within
+ that folder.
+
+ To run OmegaT with the tokenizer you need to specify which tokenizer
+ you'll use for the source language and which tokenizer you'll use for the
+ target language. The syntax is as follows:
+
+ java -jar OmegaT.jar --ITokenizer=[source language
+ tokenizer name] --ITokenizerTarget=[target language tokenizer
+ name]
+
+ The tokenizer names are given in the Readme.txt file distributed
+ with the tokenizer files. For example, if you wish to use the Lucene CJK
+ tokenizer in source and the Lucene French tokenizer in target, your
+ command will look like this:
+
+ java -jar OmegaT.jar
+ --ITokenizer=org.omegat.plugins.tokenizer.LuceneCJKTokenizer
+ --ITokenizerTarget=org.omegat.plugins.tokenizer.LuceneFrenchTokenizer
+
+
+
+ Mac OSX specifics
+
+ If you wish to use the tokenizers with the Mac OSX OmegaT.app
+ package, the tokenizer installation described above applies (right-click
+ on OmegaT.app to find the location of OmegaT.jar), but you'll need to
+ specify the tokenizer names in the info.plist that
+ contains the Java launch options. Follow the instructions above to access
+ the info.plist file and edit it so that it looks as
+ follows for the example we just gave:
+
+
+<key>VMOptions</key>
+<string>-Xmx1024M</string>
+
+<key>Arguments</key>
+<array>
+ <string>--ITokenizer=org.omegat.plugins.tokenizer.LuceneCJKTokenizer</string>
+ <string>--ITokenizerTarget=org.omegat.plugins.tokenizer.LuceneFrenchTokenizer</string>
+</array>
+
+
+
+ Troubleshooting
+
+ To make sure that the tokenizers are being used, open a project and
+ check the log information from the console. With the example above it
+ should look like that:
+
+
+84528: Info: Source tokenizer: org.omegat.plugins.tokenizer.LuceneCJKTokenizer
+84528: Info: Target tokenizer: org.omegat.plugins.tokenizer.LuceneFrenchTokenizer
+
+
+ The numbers on the left are likely to be different on your system so
+ make sure that the source and target tokenizer names,specified in the
+ start-up options, correspond to what the log is showing. If the tokenizers
+ are not properly launched, the log will look like this:
+
+
+12719: Info: Source tokenizer: org.omegat.core.matching.Tokenizer
+12719: Info: Target tokenizer: org.omegat.core.matching.Tokenizer
+
+
+ With the Mac OSX OmegaT.app package, you'll need to double-click on
+ the JavaApplicationStub located in
+ /OmegaT.app/Contents/MacOS/ (see above to access it) to launch OmegaT from
+ the console and have immediate access to the log.
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/App_Website.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/App_Website.xml
new file mode 100644
index 0000000..765003b
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/App_Website.xml
@@ -0,0 +1,127 @@
+
+
+
+ <application><indexterm class="singular">
+ <primary>OmegaT on the web</primary>
+ </indexterm>OmegaT</application> on the web
+
+
+ <application>OmegaT</application> sites and
+ <application>OmegaT</application> SourceForge project<indexterm
+ class="singular">
+ <primary>OmegaT on the web</primary>
+
+ <secondary>SourceForge Project</secondary>
+ </indexterm>
+
+ The
+ OmegaT web site contains links to
+ numerous OmegaT resources. User support is
+ provided on a volunteer basis at the OmegaT
+ Yahoo User Group. The FAQ
+ is a good starting point for finding answers to questions you may
+ have. For the latest version of OmegaT, refer to the downloads page at
+ www.omegat.org. You can also file bug
+ reports and requests
+ for enhancements.
+
+
+
+ Bug reports<indexterm class="singular">
+ <primary>OmegaT on the web</primary>
+
+ <secondary>Reporting bugs</secondary>
+ </indexterm>
+
+ Remember that every good bug report needs just three things:
+
+
+
+ Steps to reproduce
+
+
+
+ What you expected to see
+
+
+
+ What you saw instead
+
+
+
+ More can be found in the Painless
+ Bug Tracking article by Joel Spolsky.
+
+ You should add copies of files, portions of the log, screenshots, and
+ anything else that you think will help the developers to find and fix your
+ bug. Note that bug reports and requests for enhancements are publicly
+ visible, so you should not add any sensitive files. If you wish to keep
+ track of what is happening to the report, register as a SourceForge user,
+ login and file a bug report or simply click Monitor at the top of the
+ report.
+
+
+
+ Contributing to <application>OmegaT</application> project<indexterm
+ class="singular">
+ <primary>OmegaT on the web</primary>
+
+ <secondary>Contributing to OmegaT</secondary>
+ </indexterm>
+
+ To contribute to
+ OmegaT:
+
+ first join the user group (via web or
+ by sending an email to OmegaT-subscribe@yahoogroups.com).
+ To get involved in the OmegaT development
+ effort you can join the developer group, via the web or by sending an
+ email to omegat-development-request@lists.sourceforge.net
+ with "subscribe" as the subject line.
+
+ To translate
+ OmegaT's user interface, user manual or other
+ related documents:
+
+ first read the Localizing
+ and Customizing OmegaT guide, and join
+ the OmegaT translators' group via web or by
+ sending an email to omegat-l10n-request@lists.sourceforge.net
+ with subject "subscribe".
+
+
+ OmegaT on the web
+
+ Development, Localizing
+
+
+ To support the OmegaT project financially
+ OmegaT on the web
+
+ Financial support
+
+
+ If you would like to help support the continued development of
+ OmegaT, it would be very much appreciated - click on this link to go to
+ the
+ OmegaT PayPal account.
+
+
+ OmegaT on the web
+
+ Donating to OmegaT
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Dictionaries.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Dictionaries.xml
new file mode 100644
index 0000000..91365bf
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Dictionaries.xml
@@ -0,0 +1,161 @@
+
+
+
+ <indexterm class="singular">
+ <primary>Dictionaries</primary>
+ </indexterm>Dictionaries
+
+
+
+
+ How to download and install dictionaries<indexterm class="singular">
+ <primary>Dictionaries</primary>
+
+ <secondary>Downloading and installing</secondary>
+ </indexterm>
+
+ Dictionaries in OmegaT are based on the
+ StartDict Platform. To install the necessary files, proceed as
+ follows:
+
+
+
+ Search for the required language combination - for instance on
+ the
+ FreeDict
+
+ Dictionaries
+ StartDict Platform above or on FreeDict
+ Stardict
+
+ Dictionaries
+
+
+
+
+
+
+ Download the file - it should be a tarball
+ archive (extension tar.bz or
+ tar.bz2).
+
+
+
+
+
+ Use untar utility (or its equivalent, for instance
+ winrar in Windows) to extract its contents into the project
+ folder "Dictionary". There should be three files, with extensions
+ dz, idx and ifo.
+
+
+
+ Note that in addition to "source-target" dictionaries you can, using
+ the Dictionary feature, obtain access to information such as:
+
+
+
+
+ Webster
+
+ Dictionaries
+ Webster's Revised Unabridged Dictionary (1913)
+
+
+
+
+
+
+ Longman
+
+ Dictionaries
+ Longman Dictionary of Contemporary English
+
+
+
+
+
+
+ Britannica
+
+ Dictionaries
+ The Britannica Concise Encyclopedia
+
+
+
+
+
+ etc...
+
+
+
+ Some of the dictionaries have no strings attached - i.e. are "Free
+ to use", and others, like the selection above, are under the GPL license.
+ The following example shows Merriam Webster 10th dictionary "in
+ action":
+
+
+ <indexterm class="singular">
+ <primary>Dictionary</primary>
+
+ <secondary>Merriam Webster - figure</secondary>
+
+ <seealso>Dictionaries</seealso>
+ </indexterm>Merriam Webster dictionary - use
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ <indexterm class="singular">
+ <primary>Dictionaries</primary>
+
+ <secondary>Problems with</secondary>
+ </indexterm>Problems with dictionaries
+
+
+
+ Check that your dict files are in the correct folder (or in a subfolder
+ below it). Check in
+
+
+
+ Shortcuts
+
+ Ctrl+E - Project properties
+ Ctrl
+
+ E
+
+
+
+ Project
+
+ Properties
+ .
+
+
+
+
+
+ Does the folder contain three files of the same name, with
+ extensions ? If only one file is present, check its extension. If it
+ is tar.bz, you have forgotten to unpack (untar)
+ it.
+
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/EditingBehavior.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/EditingBehavior.xml
new file mode 100644
index 0000000..be5531b
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/EditingBehavior.xml
@@ -0,0 +1,160 @@
+
+
+
+ Editing behavior<indexterm class="singular">
+ <primary>Menu options</primary>
+
+ <secondary>Editing behavior...</secondary>
+ </indexterm>
+
+ The dialog in
+ Options
+
+ Editing Behavior...
+ enables the user to select, how the current segment in the
+ editing field is to be initialized and handled:
+
+
+ Editing behavior options
+
+
+
+
+
+
+
+
+
+ Editing behaviour - options<indexterm class="singular">
+ <primary>Editing behaviour</primary>
+
+ <secondary>Options</secondary>
+ </indexterm>
+
+ You translate your files by moving from segment to segment, editing
+ each current segment in turn. When moving between segments, you may wish
+ to populate the editing field with an existing translation in the fuzzy
+ match pane or with the source text. In
+ Options
+
+ Editing Behavior...
+ OmegaT offers you the following
+ alternatives:
+
+
+
+ The source text
+
+
+ You can have the source text inserted automatically into the
+ editing field. This is useful for texts containing many trade marks
+ or other proper nouns you which must be left unchanged.
+
+
+
+
+ Leave the segment empty
+ Editing behaviour
+
+ Empty translation
+
+
+
+ OmegaT leaves the editing field blank. This option allows you
+ to enter the translation without the need to remove the source text,
+ thus saving you two keystrokes (Ctrl+A
+ and Del). Empty
+ translations are now allowed. They are displayed as <EMPTY> in
+ the Editor. To create one, right-click in a segment, and select
+ "Set empty translation". The entry
+ Remove translation in the same
+ popup menu also allows to delete the existing translation of the
+ current segment. You achieve the same by clearing the target segment
+ and pressing Enter.
+
+
+
+
+ Insert the best fuzzy match
+ Editing behaviour
+
+ Inserting fuzzy matches
+
+
+
+ OmegaT inserts the translation of the string most similar to
+ the current source, if it is above the similarity threshold that you
+ have selected in this dialog. The prefix (per default empty) can be
+ used to tag translations, done via fuzzy matches. If you add a
+ prefix (for instance [fuzzy]), you can trace those translations
+ later to see they are correct.
+
+
+
+
+
+
+ Allow the translation to be equal to source<indexterm
+ class="singular">
+ <primary>Editing behaviour</primary>
+
+ <secondary>Translation equal to source</secondary>
+ </indexterm>
+
+ Documents for translation may contain trade marks, names or other
+ proper nouns that will be the same in translated documents. There are two
+ strategies for segments that contain only such invariable text.
+
+ You can decide not to translate such segments at all. OmegaT will
+ then report these segments as not translated. This is the default. The
+ alternative is to enter a translation that is identical to the source
+ text. OmegaT is able to recognize that you have done this. To make this
+ possible, go to
+ Options
+
+ Editing Behavior...
+ and check the box Allow translation
+ to be equal to source.
+
+
+
+ Export the segment to text files<indexterm class="singular">
+ <primary>Editing behaviour</primary>
+
+ <secondary>Exporting the current segment</secondary>
+ </indexterm>
+
+ The text export function exports data from within the current
+ OmegaT project to plain text files. The data
+ are exported when the segment is opened. The files appear in the /script
+ subfolder in the OmegaT user files folder, and include:
+
+
+
+ The content of the segment source text
+ (source.txt).
+
+
+
+ The content of the segment target text
+ (target.txt).
+
+
+
+ The text highlighted by the user, when
+ Ctrl-Shift-C is pressed or Edit >
+ Export Selection is selected
+ (selection.txt).
+
+
+
+ The content of the files is overwritten either when a new segment is
+ opened (source.txt and target.txt) or when a new selection is exported
+ (selection.txt). The files are unformatted plain text files. The whole
+ process can be steered and controlled via Tck/Tcl-based scripting. See
+ Using the
+ OmegaT text export function for specifics, examples and
+ suggestions.
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/FileFilters.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/FileFilters.xml
new file mode 100644
index 0000000..2644eb8
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/FileFilters.xml
@@ -0,0 +1,518 @@
+
+
+
+ File Filters
+
+ OmegaT features highly customizable filters, enabling you to configure
+ numerous aspects. File filters are pieces of code capable of:
+
+
+
+ Reading the document in some specific file format. For instance,
+ plain text files.
+
+
+
+
+
+ Extracting the translatable content out of the file.
+
+
+
+
+
+ Automating modifications of the translated document file names by
+ replacing translatable contents with its translation.
+
+
+
+ To see which file formats can be handled by OmegaT, see the menu
+ Options > File Filters ...
+
+ Most users will find the default file filter options sufficient. If
+ this is not the case, open the main dialog by selecting Options → File Filters... from the main menu. You
+ can also enable project-specific file filters, which will only be used on
+ the current project, by selecting the File
+ Filters... option in Project Properties.
+
+ You can enable project specific filters via the Options → Properties... . Klick on File
+ Filters button and activate the check box Enable
+ project specific filters
+ File filters
+
+ project specific file filters
+ . A copy of the filters configuration will be stored with the
+ project in this case. If you later change filters, only the project filters
+ will be updated, while the user filters stay unchanged.
+
+ Warning! Should you change filter
+ options whilst a project is open, you must reload the project in order for
+ the changes to take effect.
+
+
+ File filters dialog<indexterm class="singular">
+ <primary>File filters</primary>
+
+ <secondary>Dialog</secondary>
+ </indexterm>
+
+ This dialog lists available file filters. Should you wish not to use
+ OmegaT to translate files of a certain type, you can turn off the
+ corresponding filter by deactivating the check box beside its name. OmegaT
+ will then omit the appropriate files while loading projects, and will copy
+ them unmodified when creating target documents. When you wish to use the
+ filter again, just tick the check box. Click Defaults to reset the file filters to the default
+ settings. To edit which files in which encodings the filter is to process,
+ select the filter from the list and click Edit.
+
+
+
+ Filter options<indexterm class="singular">
+ <primary>File filters</primary>
+
+ <secondary>Options</secondary>
+ </indexterm>
+
+ Five filters (Text files, XHTML files, HTML and XHTML files,
+ OpenDocument/OpenOffice.org files and Microsoft Open XML files) have one
+ or more specific options. To modify the options select the filter from the
+ list and click on Options. The available
+ options are:
+
+ Text files
+
+
+
+ Paragraph segmentation on line breaks, empty lines or
+ never:
+
+ if sentence segmentation rules are active, the text will further
+ be segmented according to the option selected here.
+
+
+
+ PO files
+
+
+
+ Allow blank translations in the target
+ file:
+
+ If on, when a PO segment (which may be a whole paragraph) is not
+ translated, the translation will be empty in the target file.
+ Technically speaking, the msgstr segment in the PO target
+ file, if created, will be left empty. As this is the standard behavior
+ for PO files, it is on by default. If the option is off, the source
+ text will be copied to the target segment.
+
+
+
+ XHTML Files
+
+
+
+ Translate the following attributes - the
+ selected attributes will appear as segments in the Editor
+ window.
+
+
+
+
+
+ Start a new paragraph on: the <br>
+ HTML tag will constitute a paragraph for segmentation purposes.
+
+
+
+
+
+ Skip text matching regular expression: the
+ text matching the regular expression gets skipped. It is shown
+ rendered red in the tag validator. Text in source segment that matches
+ is shown in italic.
+
+
+
+
+
+ Do not translate the content attribute of meta-tags
+ ... :
+
+ It is sometimes useful to be able make some tags untranslatable
+ based on the value of attributes. E.g., <div
+ class="hide"> <span translate="no"> You can define
+ key-value pairs for tags to be left untranslated. For the example
+ above, the field would contain: class=hide, translate=no
+
+
+
+
+ Microsoft Office Open XML
+ files
+
+ You can select which elements are to be translated. They will appear
+ as separate segments in the translation.
+
+
+
+ Word: non-visible instruction
+ text, comments, footnotes, endnotes, footers
+
+
+
+
+
+ Excel: comments, sheet
+ names
+
+
+
+
+
+ Power Point: slide comments,
+ slide masters, slide layouts
+
+
+
+
+
+ Global: charts, diagrams,
+ drawings, WordArt
+
+
+
+
+
+ Other Options:
+
+
+
+ Aggregate tags: if checked, tags
+ without translatable text between them will be aggregated into
+ single tags.
+
+
+
+ Preserve spaces for all tags: if
+ checked, "white space" (i.e., spaces and newlines) will be
+ preserved, even if not set technically in the document
+
+
+
+
+
+ HTML and XHTML files
+
+
+
+ Add or rewrite encoding declaration in HTML and XHTML
+ files: Always (default), Only if (X)HTML file has a header,
+ Only if (X)HTML file has an encoding declaration, Never
+
+
+
+
+
+ Translate the following attributes: the
+ selected attributes will appear as segments in the Editor
+ window.
+
+
+
+
+
+ Start a new paragraph on: the <br>
+ HTML tag will constitute a paragraph for segmentation purposes.
+
+
+
+
+
+ Skip text matching regular expression: The
+ text, matching the regular expression, will be skipped.
+
+
+
+
+
+ Do not translate the content attribute of
+ meta-tags ... : the attribute key-value pairs, separated by
+ commas, will be left untranslated
+
+
+
+ Text files
+
+
+
+ Paragraph segmentation on line breaks, empty lines or
+ never:
+
+ if sentence segmentation rules are active, the text will further
+ be segmented according to the option selected here.
+
+
+
+ OpenDocument/OpenOffice.org
+ files
+
+
+
+ You can select which of the following items are to be
+ translated:
+
+ index entries, bookmarks, bookmark references, notes, comments,
+ presentation notes, links (URL), sheet names
+
+
+
+
+
+ Edit filter dialog<indexterm class="singular">
+ <primary>File filters</primary>
+
+ <secondary>Editing</secondary>
+ </indexterm>
+
+ This dialog enables you to set up the source filename patterns of
+ files to be processed by the filter, customize the filenames of translated
+ files, and select which encodings should be used for loading the file and
+ saving its translated counterpart. To modify a file filter pattern, either
+ modify the fields directly or click Edit.
+ To add a new file filter pattern, click Add. The same dialog is used to add a pattern or to
+ edit a particular pattern. The dialog is useful because it includes a
+ special target filename pattern editor with which you can customize the
+ names of output files.
+
+
+ <indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>File type, filename pattern</secondary>
+ </indexterm>Source file type, filename pattern<indexterm
+ class="singular">
+ <primary>File filters</primary>
+
+ <secondary>Source file type, filename</secondary>
+ </indexterm>
+
+ When OmegaT encounters a file in its source folder, it attempts to
+ select the filter based upon the file's extension. More precisely,
+ OmegaT attempts to match each filter's source filename patterns against
+ the filename. For example, the pattern *.xhtml
+ matches any file with the .xhtml extension.
+ If the appropriate filter is found, the file is assigned to it for
+ processing. For example, by default, XHTML filters are used for
+ processing files with the .xhtml extension. You can change or add
+ filename patterns for files to be handled by each file. Source filename
+ patterns use wild card characters similar to those used in Searches. The '*' character matches zero or more
+ characters. The '?' character matches exactly one character. All other
+ characters represent themselves. For example, if you wish the text
+ filter to handle readme files (readme, read.me, and
+ readme.txt) you should use the pattern
+ read*.
+
+
+
+ Source and Target file encoding
+
+
+ Source files
+
+ Encoding
+
+
+
+ Target files
+
+ Encoding
+
+
+
+ File filters
+
+ Source, target encoding
+
+
+ Only a limited number of file formats specify a mandatory
+ encoding. File formats that do not specify their encoding will use the
+ encoding you set up for the extension that matches their name. For
+ example, by default .txt files will be loaded using
+ the default encoding of your operating system. You may change the source
+ encoding for each different source filename pattern. Such files may also
+ be written out in any encoding. By default, the translated file encoding
+ is the same as the source file encoding. Source and target encoding
+ fields use combo boxes with all supported encodings included.
+ <auto> leaves the encoding choice to
+ OmegaT. This is how it works:
+
+
+
+ OmegaT identifies the source file encoding by using its
+ encoding declaration, if present (HTML files, XML based
+ files)
+
+
+
+
+
+ OmegaT is instructed to use a mandatory encoding for certain
+ file formats (Java properties etc)
+
+
+
+
+
+ OmegaT uses the default encoding of
+ the operating system for text files.
+
+
+
+
+
+ Target filename<indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Filenames</secondary>
+ </indexterm>
+
+ Sometimes you may wish to rename the files you translate
+ automatically, for example adding a language code after the file name.
+ The target filename pattern uses a special syntax, so if you wish to
+ edit this field, you must click Edit...and use the
+ File filters
+
+ Dialog
+ Edit Pattern Dialog. If you wish to revert to default
+ configuration of the filter, click Defaults. You may also modify the name directly
+ in the target filename pattern field of the file filters dialog. The
+ Edit Pattern Dialog offers among others the following options:
+
+
+
+ Default is ${filename}– full filename of
+ the source file with extension: in this case the name of the
+ translated file is the same as that of the source file.
+
+
+
+
+
+ ${nameOnly}– allows you to insert only the
+ name of the source file without the extension.
+
+
+
+ ${extension} - the original file
+ extension
+
+
+
+
+
+ ${targetLocale}– target locale code (of a
+ form "xx_YY").
+
+
+
+
+
+ ${targetLanguage}– the target language and
+ country code together (of a form "XX-YY").
+
+
+
+
+
+ ${targetLanguageCode} – the target language
+ - only "XX"
+
+
+
+
+
+ ${targetCountryCode}– the target country -
+ only "YY"
+
+
+
+ $(timestamp-????) - system date time at
+ generation time in various patterns
+
+ See Oracle
+ documentation for examples of the "SimpleDateFormat"
+ patterns
+
+
+
+ ${system-os-name} - operating system of the computer
+ used
+
+
+
+ ${system-user-name) - system user name
+
+
+
+ ${system-host-name} - system host name
+
+
+
+ ${file-source-encoding} - source file encoding
+
+
+
+ ${file-target-encoding} - target file encoding
+
+
+
+ ${targetLocaleLCID) - Microsoft target locale
+
+
+
+ Additional variants are available for variables ${nameOnly} and
+ ${Extension}. In case the file name has ambivalent name, one can apply
+ variables of the form $(name only-number of
+ extensions) and
+ ${extension-number of extensions}
+ . If for example the original file is named Document.xx.docx,
+ the following variables will give the following results:
+
+
+
+ ${nameOnly-0} Document
+
+
+
+ ${nameOnly-1} Document.xx
+
+
+
+ ${nameOnly-2} Document.xx.docx
+
+
+
+ ${extension-0} docx
+
+
+
+ ${extension-1} xx.docx
+
+
+
+ ${extension-2} Document.xx.docx
+
+
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/FilesAndDirectories.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/FilesAndDirectories.xml
new file mode 100644
index 0000000..a200b63
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/FilesAndDirectories.xml
@@ -0,0 +1,527 @@
+
+
+
+ <application>OmegaT</application> Files and Directories
+
+ OmegaT works with three types of
+ files.
+
+
+
+ Translation project files: These constitute a translation project.
+ Losing them may affect the project's integrity and your ability to
+ complete a job. Project files are the most important files in
+ OmegaT. They are the files you deal with on a
+ daily basis while translating.
+
+
+
+
+
+ User settings files: These are created when OmegaT's behavior is
+ modified by user preference settings. Losing them usually results in
+ OmegaT reverting to its "factory settings". This can sometimes cause a
+ little trouble when you are in the middle of a translation.
+
+
+
+
+
+ Application files: These are included in the package you download.
+ Most of them are required in order for OmegaT to function properly. If
+ for some reason these files are lost or corrupted, simply download
+ and/or reinstall OmegaT to restore them all.
+
+
+
+
+ Translation project files
+
+
+ Project files
+
+ Translation project files
+
+
+ An OmegaT translation project consists of
+ a number of files and directories.
+
+ When you create a translation project, OmegaT automatically creates
+ a folder with the specified name, and a list of folders:
+
+
+ OmegaT project
+
+
+
+
+
+
+
+
+ Alternate locations for some of the folders can be chosen at project
+ creation or during the translation. It is therefore possible to select
+ existing folders or create folders in locations that reflect your work
+ flow and project management habits. To change the location of folders
+ after a project has been created, open Project >
+ Properties... in the menu or with
+ Ctrl+E and make the necessary changes.
+
+ In a file manager a translation project looks and acts just like any
+ other folder. In the foillowing example the folder my
+ projects contains three OmegaT projects:
+
+
+ OmegaT projects and subdirectories
+
+
+
+
+
+
+
+
+ Double clicking the item with the OmegaT icon is sufficient to open
+ the project. A translation project Example_Project created with the default settings
+ will be created as a new subfolder with the following structure:
+
+
+ Top folder<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>File omegat.project</secondary>
+ </indexterm>
+
+ Top folder of a project always contains the file
+ OmegaT.Project, containing project parameters as defined in
+ the Project properties window (File >
+ Properties). While the translation is progressing,
+ additional files
+ (project_name-omegat.tmx,
+ project_name-level1.tmx and project_name-level2.tmx) are
+ created (and updated during the process of translation) in thes folder.
+ They contain the one and the same translation memory contents in
+ different forms, to be sued in future projects.
+
+
+
+ Subfolder dictionary
+
+ Initially empty, this folder with contain dictionaries you have
+ added to the project. See chapter
+ Dictionaries for more on this subject.
+
+
+
+ Subfolder glossary
+
+ This folder is nitially empty. It will contain glossaries you will
+ be using in the project. See chapter
+ Glossaries for more on this subject.
+
+
+
+ Subfolder omegat<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>Subfolder omegat</secondary>
+ </indexterm>
+
+ The omegat subfolder contains at
+ least one and possibly several other files. The most important file here
+ is the project_save.tmx, that is the working
+ translation memory for the project. Backups of this file (with extension
+ bak) are added progressively to this subfolder, first at the beginning
+ of the translation session, at its end, and while the translation
+ progresses. This way an inadvertent loss of is averted - see Preventing
+ Data Loss in chapter Miscellanea.
+
+ During translation additional files may get created in this
+ subdirectory as follows
+
+
+
+
+
+
+
+ stats.txt
+
+
+ Project files
+
+ statistics file
+ contains the current statistics of the current
+ project. You can view it by selecting Tools >
+ Statistics
+
+
+
+ ignored_words.txt. learned_words.txt
+
+
+ Project files
+
+ ignored_words and learned_words
+ are created and used by the spell checker. If
+ you already have collected words you wish the spell checker to
+ ignore / accept, you just need to copy the corresponding two
+ files into the omegatsubfolder of your
+ current project.
+
+
+
+ project_stats_match.txt
+
+ contains the latest project match statistics, generated
+ by Tools > Match
+ Statistics
+
+
+
+ segmentation.conf
+
+ if existing, it contains project-specific segmentation
+ rules, if requested in Project > Properties
+ ... See Chapter Project
+ properties
+
+
+
+ filters.xml
+
+ if existing, it contains project-specific file filters,
+ if requested in Project > Properties ...
+ See Chapter Project
+ properties
+
+
+
+
+
+
+
+ Subfolder source<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>Source subfolder</secondary>
+ </indexterm>
+
+ The source subfolder contains files to be translated. You can add
+ the files to it later. Note that the structure of the source subfolder
+ may take any form you like. If the files to be translated are parts of a
+ tree structure (as in a website), you need only specify the top-level
+ subfolder and OmegaT will maintain the entire contents, while keeping
+ the tree structure intact.
+
+
+
+ Subfolder target<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>Target subfolder</secondary>
+ </indexterm>
+
+ This subfolder is initially empty. To add contents to it, select
+
+
+
+ Ctrl
+
+ D
+
+
+
+ Project
+
+ Create Translated Documents
+ . Files within the source directory,
+ whether translated or not, are then generated here, with the same
+ hierarchy as present in the source subfolder. The contents of the target
+ subfolder will reflect the current state of the translation, as present
+ in the project translation memory, saved in the current /omegat/project_save.tmx. Untranslated segments
+ will hereby remain in the source language.
+
+
+
+
+ User settings files<indexterm
+ class="singular">
+ <primary>Project files</primary>
+
+ <secondary>User settings files</secondary>
+ </indexterm>
+
+ User files contain the information, applicable to all the projects
+ for a given user;
+
+
+
+
+
+
+
+ logs/OmegaT.log
+
+ This file records Java error messages while
+ OmegaT is running. Should OmegaT appear
+ to be behaving erratically, it is important to include this file
+ or the relevant part in any bug report
+
+
+
+ script/
+
+ folder, containing script files for the script plugin, if
+ installed
+
+
+
+ filters.xml
+
+ user's default file filters
+
+
+
+ omegat.prefs
+
+ OmegaT preferences
+
+
+
+ segmentation.conf
+
+ user's default segmentation rules
+
+
+
+ uiLayout.xml
+
+ An xml file with all the GUI accessible option
+ settings
+
+
+
+
+
+ Note that default segmentation rules and file filters can be
+ overridden by project-specific setup (see above).The location of user
+ files depends upon the platform you use:
+
+
+
+
+
+
+
+ Windows 2000 and XP
+
+ Documents and Settings\<User
+ Name>\Application
+ Data\OmegaT
+
+
+
+ Windows Vista and 7
+
+ Users\<User
+ Name>\AppData\Roaming\OmegaT
+
+
+
+ Windows other
+
+ <Something>\OmegaT
+ (<Something> corresponds to the location of the "home"
+ folder as determined by Java)
+
+
+
+ Linux/Solaris/FreeBSD
+
+ <User Home>/.omegat (.omegat is a
+ directory, the dot preceding its name makes it invisible unless
+ you type ls -a or an equivalent command)
+
+
+
+ MAC OSX
+
+ <User
+ Home>/Library/Preferences/OmegaT
+
+
+
+ Other
+
+ <User Home>
+
+
+
+
+
+
+
+ Application files<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>Application files</secondary>
+ </indexterm>
+
+ OmegaT is supplied as a package that can be downloaded from
+ SourceForge. Here a platform-independent package in a standard Java form
+ is considered. Alternatives include include a Linux .tar package, a
+ Windows installer – with or without a Java Runtime Environment –, a MacOSX
+ installer, and a source code package for developers.
+
+ The platform-independent package can be used on any platform with a
+ working Java 1.5 runtime environment, including the platforms for which a
+ specific package also exists. It is provided as a compressed file (zip or
+ tar archive) that you must extract to the folder of your choice for
+ installation. The file can usually be extracted by double-clicking on the
+ downloaded package. Once the archive has been extracted, a folder
+ containing the following contents is created:
+
+
+
+
+
+
+
+ File/ subfolder
+
+ Contents
+
+
+
+ /docs/
+
+ All the user manual files can be found in this folder. You
+ can open them in An Internet browser to obtain access to external
+ links.
+
+
+
+ /images/
+
+ Icons and logo graphics
+
+
+
+ /lib/
+
+ Contains Java files, necessary to the operation of
+ OmegaT.
+
+
+
+ join.html
+
+ This is an ordinary html file that, when opened in your
+ Internet browser, directs you to the OmegaT user group hosted on
+ Yahoo Groups. Joining is not necessary, but will provide you with
+ access to additional services, such as files, questionnaires, and
+ the opportunity to take part in OmegaT-related discussions. The
+ group archives are public and can be viewed without subscription
+ to the group.
+
+
+
+ changes.txt
+
+ A relatively detailed list of modifications between this
+ version and the preceding versions.
+
+
+
+ license.txt
+
+ The GNU GENERAL PUBLIC LICENSE. This license allows you to
+ do certain things with OmegaT,
+ including modifying and distributing it. If you are interested in
+ modifying or distributing OmegaT, read
+ this document carefully and ensure you understand its implications
+ before doing anything. If in doubt, don't hesitate to ask project
+ members directly either by sending them an e-mail from the
+ SourceForge page or by sending a public mail to the user
+ group.
+
+
+
+ doc-license.txt
+
+ The GNU GENERAL PUBLIC LICENSE. This license covers the
+ documentation. See above.
+
+
+
+ readme.txt
+
+ This file is very important and you should make sure you
+ read it before launching OmegaT. It includes general information
+ on OmegaT, where to find more information, how to contribute, etc.
+ It has been translated into a number of languages.
+
+
+
+ OmegaT
+
+ A text file containing two lines:
+
+
+
+
+
+ #!/bin/bash java
+
+
+
+
+
+ java -jar
+ OmegaT.jar $*
+
+
+
+
+
+ Linux and OSX users may find this file useful. Make it
+ executable (chmod +x OmegaT) from the command line after making
+ sure you are in the /OmegaT_2.5/ directory. You will then be able
+ to launch OmegaT by executing this file from the command
+ line
+
+
+
+ OmegaT.bat
+
+ A batch file, used to launch
+ OmegaT from the Windows command line.
+ It contains just the following line:
+
+
+
+
+
+ java -jar OmegaT.jar
+ %*
+
+
+
+ OmegaT.jar
+
+ The main OmegaT application. To launch OmegaT, you must
+ launch this file either from the command line or from your file
+ manager, usually by double-clicking it.
+
+
+
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/FilesToTranslate.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/FilesToTranslate.xml
new file mode 100644
index 0000000..ff8b496
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/FilesToTranslate.xml
@@ -0,0 +1,441 @@
+
+
+
+ Files to translate
+
+
+ File formats<indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>File formats</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>File formats</secondary>
+ </indexterm>
+
+ You can use OmegaT to translate files in
+ a number of file formats. There are basically two types of file formats,
+ plain text and formatted text.
+
+
+ Plain text files<indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Plain text files</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Plain text files</secondary>
+ </indexterm>
+
+ Plain text files contain text only, so their translation is as
+ simple as typing the translation. There are several methods to specify
+ the file's encoding so that its contents are not garbled when opened in
+ OmegaT. Such files do not contain any
+ formatting information beyond the "white space" used to align text,
+ indicate paragraphs or insert page breaks. They are not able to contain
+ or retain information regarding the color, font etc of the text.
+ Currently, OmegaT supports the following
+ plain text formats:
+ File formats
+
+ Unformatted
+
+ Source files
+
+
+
+
+ ASCII text (.txt, etc.)
+
+
+
+
+
+ Encoded text (*.UTF8)
+
+
+
+
+
+ Java resource bundles (*.properties)
+
+
+
+
+
+ PO files (*.po)
+
+
+
+
+
+ INI (key=value) files (*.ini)
+
+
+
+
+
+ DTD files (*.DTD)
+
+
+
+ DocuWiki files (*.txt)
+
+
+
+
+
+ SubRip title files (*.srt)
+
+
+
+
+
+ Magento CE Locale CSV files (*.csv)
+
+
+
+ Other plain text file types can be handled by
+ OmegaT by associating their file extension to
+ a supported file type (for example, .pod files can be associated to the
+ ASCII text filter) and by pre-processing them with specific segmentation
+ rules.
+
+
+
+ Formatted text files<indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Formatted text files</secondary>
+
+ <seealso>Tagged text</seealso>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Formatted text files</secondary>
+ </indexterm>
+
+ Formatted text files contain information such as font type, size,
+ color etc. as well as text. They are commonly created in word processors
+ or HTML editors. Such file formats are designed to hold formatting
+ information. The formatting information can be as simple as “this is
+ bold”, or as complex as table data with different font sizes, colors,
+ positions, etc. In most translation jobs, it is considered important for
+ the formatting of the original text to be retained in the translation.
+ OmegaT allows you to do this by marking the characters/words that have a
+ special formatting with easy-to-handle tags. Simplifying the original
+ text formatting greatly contributes to reducing the number of tags.
+ Where possible, unifying the fonts, font sizes, colors, etc. used in the
+ document simplifies the task of translation and reduces the possible
+ number of tag errors. Each file type is handled differently in OmegaT.
+ Specific behavior can be set up in the file filters. At the time of
+ writing, OmegaT supports the following formatted text formats:
+
+ File formats
+
+ formatted
+
+ Source files
+
+
+
+
+ OpenOffice.org / OpenDocument (*.ods, *.ots, *.odt, *.ott,
+ *.odp, *.otp)
+
+
+
+ Microsoft Office Open XML (*.docx, *.dotx, *.xlsx, *.xltx,
+ *.pptx)
+
+
+
+ (X)HTML (*.html, *.xhtml,*.xht)
+
+
+
+ HTML Help Compiler (*.hhc, *.hhk)
+
+
+
+ DocBook (*.xml)
+
+
+
+ XLIFF (*.xlf, *.xliff, *.sdlxliff) - monolingual, i.e. one
+ language combination possible for a given project
+
+
+
+ QuarkXPress CopyFlowGold (*.tag, *.xtg)
+
+
+
+ ResX files (*.resx)
+
+
+
+ Android resource (*.xml)
+
+
+
+ LaTex (*.tex, *.latex)
+
+
+
+ Help (*.xml) and Manual (*.hmxp) files
+
+
+
+ Typo3 LocManager (*.xml)
+
+
+
+ WiX Localization (*.wxl)
+
+
+
+ Iceni Infix (*.xml)
+
+
+
+ Flash XML export (*.xml)
+
+
+ Wordfast TXML (*.txml)
+
+
+ Camtasia for Windows (*.camproj)
+
+
+
+
+ Other formatted text file types may also be handled by OmegaT by
+ associating their file extensions to a supported file type, assuming
+ that the corresponding segmentation rules will segment them
+ correctly.
+
+
+
+
+ Other file formats<indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Other file formats</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Other file formats</secondary>
+ </indexterm>
+
+ Other plain text or formatted text file formats suitable for
+ processing in OmegaT may also exist.
+
+
+ Target files
+
+ File conversion tools
+ External tools can be used to convert files to supported
+ formats. The translated files will then need to be converted back to the
+ original format. For example, if you have an outdated Microsoft Word
+ version, that does not handle the ODT format, here's a round trip for Word
+ files with the DOC extension:
+
+
+
+ import the file into OpenOffice.org writer
+
+
+
+
+
+ save the file in ODT format
+
+
+
+
+
+ translate it into the target ODT file
+
+
+
+
+
+ load the target file in OpenOffice.org writer
+
+
+
+
+
+ save the file as a DOC file
+
+
+
+ The quality of formatting of the translated file will depend on the
+ quality of the round-trip conversion. Before proceeding with such
+ conversions, be sure to test all options. Check the OmegaT home page for an up-to-date
+ listing of auxiliary translation tools.
+
+
+
+ Right to left languages<indexterm class="singular">
+ <primary>Right to left languages</primary>
+ </indexterm><indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Right to left languages</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Right to left languages</secondary>
+ </indexterm>
+
+ Justification of source and target segments depends upon the project
+ languages. By default, left justification is used for Left-To-Right (LTR)
+ languages and right justification for Right-To-Left (RTL) languages. You
+ can toggle between different display modes by pressing
+ Shift
+
+ Ctrl
+
+ O
+ (this is the letter O and not the numeral 0). The
+ Shift
+
+ Ctrl
+
+ O
+ toggle has three states:
+
+
+
+ default justification, that is as defined by the language
+
+
+
+
+
+ left justification
+
+
+
+
+
+ right justification
+
+
+
+ Using the RTL mode in OmegaT has no
+ influence whatsoever on the display mode of the translated documents
+ created in OmegaT. The display mode of the
+ translated documents must be modified within the application (such as
+ Microsoft Word) commonly used to display or modify them (check the
+ relevant manuals for details). Using
+ Shift
+
+ Ctrl
+
+ O
+ causes both text input and display in
+ OmegaT to change. It can be used separately for
+ all three panes (Editor, Fuzzy Matches and Glossary) by clicking on the
+ pane and toggling the display mode. It can also be used in all the input
+ fields found in OmegaT - in the search window,
+ for segmentation rules etc.
+
+ Mac OS X users, note: use
+ Shift
+
+ Ctrl
+
+ O
+ shortcut and not
+ cmd+Ctrl+O.
+
+
+ Mixing RTL and LTR strings in segments<indexterm class="singular">
+ <primary>Right to left languages</primary>
+
+ <secondary>Mixing RTL and LTR strings</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Mixing RTL and LTR strings</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Mixing RTL and LTR strings</secondary>
+ </indexterm>
+
+ When writing purely RTL text, the default (LTR) view may be used.
+ In many cases, however, it is necessary to embed LTR text in RTL text.
+ For example, in OmegaT tags, product names that must be left in the LTR
+ source language, place holders in localization files, and numbers in
+ text. In cases like these it becomes necessary to switch to RTL mode, so
+ that the RTL (in fact bidirectional) text is displayed correctly. It
+ should be noted that when OmegaT is in RTL
+ mode, both source and target are displayed in RTL mode. This means that
+ if the source language is LTR and the target language is RTL, or vice
+ versa, it may be necessary to toggle back and forth between RTL and LTR
+ modes to view the source and enter the target easily in their respective
+ modes.
+
+
+
+ <application>OmegaT</application> tags in RTL segments<indexterm
+ class="singular">
+ <primary>Right to left languages</primary>
+
+ <secondary>OmegaT tags in RTL languages</secondary>
+ </indexterm>
+
+ As stated above, OmegaT tags are LTR strings. When translating
+ between RTL and LTR languages, correctly reading the tags from the
+ source and entering them properly in the target may require the
+ translator to toggle between LTR and RTL modes numerous times.
+
+ If the document allows, the translator is strongly encouraged to
+ remove style information from the original document so that as few tags
+ as possible appear in the OmegaT interface. Follow the indications given
+ in Hints for tags management. Frequently validate tags (see Tag
+ validation) and produce translated documents (see below and Menu) at
+ regular intervals to make it easier to catch any problems that arise. A
+ hint: translating a plain text version of the text and adding the
+ necessary style in the relevant application at a later stage may turn
+ out to be less hassle.
+
+
+
+ Creating translated RTL documents<indexterm class="singular">
+ <primary>Right to left languages</primary>
+
+ <secondary>Creating RTL target files</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Right to left languages</primary>
+
+ <secondary>Target files</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Right to left languages</primary>
+
+ <secondary>Creating RTL target text</secondary>
+ </indexterm>
+
+ When the translated document is created, its display direction
+ will be the same as that of the original document. If the original
+ document was LTR, the display direction of the target document must be
+ changed manually to RTL in its viewing application. Each output format
+ has specific ways of dealing with RTL display; check the relevant
+ application manuals for details.
+
+ To avoid changing the target files display parameters each time
+ the files are opened, it may be possible to change the source file
+ display parameters such that such parameters are inherited by the target
+ files. Such modifications are possible in OpenOffice.org files for
+ example.
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/FormattedText.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/FormattedText.xml
new file mode 100644
index 0000000..ed07b85
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/FormattedText.xml
@@ -0,0 +1,334 @@
+
+
+
+ Working with formatted text<indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Formatted text</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Formatted text</secondary>
+ </indexterm>
+
+ Formatting information present in the source file usually needs to be
+ reproduced in the target file. The in-line formatting information made
+ possible by the supported formats (in particular DocBook, HTML, XHTML, Open
+ Document (OpenOffice.org) and Office Open XML (MS Office 2007 and later) at
+ the time of writing) is presented as tags in OmegaT. Normally tags are
+ ignored when considering the similarity between different texts for matching
+ purposes. Tags reproduced in the translated segment will be present in the
+ translated document.
+
+
+ Formatting tags<indexterm class="singular">
+ <primary>Tags</primary>
+ </indexterm>
+
+
+ Tags
+
+ Naming
+ Tag naming:
+
+ The tags consist of one to three characters and a number. Unique
+ numbering allows tags, corresponding to each other to be grouped together
+ and differentiates between tags, that have the same shortcut character,
+ but are in fact different. The shortcut characters used try to reflect the
+ underlying meaning of the tag (e.g. b for bold, i for italics,
+ etc.)
+
+
+ Tags
+
+ Numbering
+ Tag numbering:
+
+ Tags are numbered incrementally by tag group. "Tag groups" in this
+ context are a single tag (such as <i0> and </i0>). Within a
+ segment, the first group (pair or single) receives the number 0, the
+ second the number 1 etc. The first example below has 3 tag groups (a pair,
+ a single, and then another pair), the second example has one group only (a
+ pair).
+
+
+ Tags
+
+ Pairs and singles
+ Pairs and singles:
+
+ Tags are always either singles or paired. Single tags indicate
+ formatting information that does not affect the surrounding text (an extra
+ space or line break for example).
+
+ <b0><Ctr+N></b0>,
+ <br1><b2><Enter></b2><segment 2132>
+
+
+ <br1> is a single tag and does not affect any surrounding
+ text. Paired tags usually indicate style information that applies to the
+ text between the opening tag and the closing tag of a pair. <b0> and
+ </b0> below are paired and affect the text log.txt. Note that the
+ opening tag must always come before the corresponding closing tag:
+
+ <Log file (<b0>log.txt</b0>) for tracking
+ operations and errors.<segment 3167>
+
+ OmegaT creates its tags before the
+ process of sentence segmenting. Depending upon the segmenting rules, the
+ pair of tags may get separated into two consecutive segments and the tag
+ validation will err on the side of caution and mark the two
+ segments.
+
+
+
+ Tag operations<indexterm class="singular">
+ <primary>Tags</primary>
+
+ <secondary>Operations</secondary>
+ </indexterm>
+
+ Care must be exercised with tags. If they are accidentally changed,
+ the formatting of the final file may be corrupted. The basic rule is that
+ the sequence of tags must be preserved in the same order. However, it is
+ possible, if certain rules are strictly followed, to deviate from this
+ basic rule.
+
+
+ Tags
+
+ Duplication
+ Tag duplication:
+
+ To duplicate tag groups, just copy them in the position of your
+ choice. Keep in mind that in a pair group, the opening tag must come
+ before the closing tag. The formatting represented by the group you have
+ duplicated will be applied to both sections.
+
+ Example:
+
+ <b0>This formatting</b0> is going to be
+ duplicated here.<segment 0001>
+
+ After duplication:
+
+ <b0>This formatting</b0> has been
+ <b0>duplicated here</b0>.<segment 0001>
+
+
+
+ Tags
+
+ Group deletion
+ Tag group deletion:
+
+ To delete tag groups, just remove them from the segment. Keep in
+ mind that a pair group must have both its opening and its closing tag
+ deleted to ensure that all traces of the formatting are properly erased,
+ otherwise the translated file may become corrupted. By deleting a tag
+ group you will remove the related formatting from the translated
+ file.
+
+ Example:
+
+ <b0>This formatting</b0> is going to be
+ deleted.<segment 0001>
+
+ After deletion:
+
+ This formatting has been deleted.<segment 0001>
+
+
+
+
+ Tag group nesting<indexterm class="singular">
+ <primary>Tags</primary>
+
+ <secondary>Group nesting</secondary>
+ </indexterm>
+
+ Modifying tag group order may result in the nesting of a tag group
+ within another tag group. This is acceptable, provided the enclosing group
+ totally encloses the enclosed group. In other words, when moving paired
+ tags, ensure that both the opening and the closing tag are both either
+ inside or outside other tag pairs, or the translated file may be corrupted
+ and fail to open.
+
+ Example:
+
+ <b0>Formatting</b0> <b1>one</b1> is
+ going to be nested inside formatting zero.<segment 0001>
+
+
+ After nesting:
+
+ <b0>Formatting <b1>one</b1></b0>
+ has been nested inside formatting zero.<segment
+ 0001>
+
+
+
+ Tag group overlapping<indexterm class="singular">
+ <primary>Tags</primary>
+
+ <secondary>Group overlapping</secondary>
+ </indexterm>
+
+ Overlapping is the result of bad manipulations of tag pairs and is
+ guaranteed to result in formatting corruption and sometimes in the
+ translated file not opening at all.
+
+ Example:
+
+ <b0>Formatting</b0> <b1>one</b1> is
+ going to be messed up.<segment 0001>
+
+ After a bad manipulation:
+
+ <b0>Formatting <b1>one</b0> </b1>is
+ very messed up now.<end segment 0001>
+
+
+
+ Tag validation options
+
+ To customize the work with tags, one can set down some of the rules
+ in the Options > Tag validation...
+ window:
+
+
+
+
+
+
+
+ The behaviour, stated here, applies to all the source files and not
+ just to some of the file types, like formatted text.
+
+
+
+ Printf variables
+
+ OmegaT can check that programming variables (like %s for
+ instance) in the source exist in the translation. You can decide not
+ to check at all, check for simple printf variables (like %s %d etc) or
+ for print variables of all types. .
+
+
+
+
+
+ check simple java MessageFormat patterns
+
+ Activating this check box will cause OmegaT to check if simple
+ java MessageFormat tags (like {0}) are processed correctly.
+
+
+
+
+
+ Text field Custom tags
+
+ Entering a regular expression here will cause OmegaT treat the
+ detected instances as a customer tag. It is checked if the number of
+ tags and their order is identical, just like it is the case for
+ omegat-tags.
+
+
+
+
+
+ Fragments that should be removed from the translation
+
+ One can enter a regular expression which will remove any of its
+ instances from the source segment - after it has been extracted from
+ the file and before it is shown in the editor window.
+
+
+
+
+
+ Tag group validation<indexterm class="singular">
+ <primary>Tags</primary>
+
+ <secondary>Group validation</secondary>
+ </indexterm>
+
+ The validate tags function detects changes to tag sequences (whether
+ deliberate or accidental), and shows the affected segments. Launching this
+ function – Ctrl+T
+ Shortcuts
+
+ Ctrl+T - Tag validation
+ - opens a window containing all segments in
+ the file containing suspected broken or bad tags in the translation.
+ Repairing the tags and recreating the target documents is easy with the
+ validate tags function. The window that opens when
+ Ctrl+T is pressed features a 3-column table
+ with a link to the segment, the original segment and the target
+ segment
+
+
+ Tag validation entry
+
+
+
+
+
+
+
+
+
+
+
+
+ The tags are highlighted in bold blue for easy comparison between
+ the original and the translated contents. Click on the link to activate
+ the segment in the Editor. Correct the error if necessary (in the case
+ above it is the missing <i2></i2> pair) and press
+ Ctrl+T to return to the tag validation window
+ to correct other errors. Tag errors are tag sequences in the translation
+ in which the same tag order and number as in the original segment is not
+ reproduced. Some tag manipulations are necessary and are benign, others
+ will cause problems when the translated document is created.
+
+
+
+ Hints for tags management<indexterm class="singular">
+ <primary>Tags</primary>
+
+ <secondary>Hints</secondary>
+ </indexterm>
+
+ Simplify the original text
+
+ Tags generally represent formatting in some form of the original
+ text. Simplifying the original formatting greatly contributes to reducing
+ the number of tags. Where circumstances permit, unifying used fonts, font
+ sizes, colors, etc. should be considered, as it could simplify the
+ translation and reduce the potential for tag errors. Read the tag
+ operations section to see what can be done with tags. Remember that if you
+ find tags a problem in OmegaT and formatting is not extremely relevant for
+ the current translation, removing tags may be the easiest way out of
+ problems.
+
+ Pay extra attention to tag
+ pairs
+
+ If you need to see tags in OmegaT but do not need to retain most of
+ the formatting in the translated document you are free not to include tags
+ in the translation. In this case pay extra attention to tag pairs since
+ deleting one side of the pair but forgetting to delete the other is
+ guaranteed to corrupt your document's formatting. Since tags are included
+ in the text itself, it is possible to use segmentation rules to create
+ segments with fewer tags. This is an advanced feature and some experience
+ is required in order for it to be applied properly.
+
+ OmegaT is not yet able to detect mistakes in formatting fully
+ automatically, so it will not prompt you if you make an error or change
+ formatting to fit your target language better. Sometimes, however, your
+ translated file may look strange, and – in the worst case – may even
+ refuse to open.
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Glossaries.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Glossaries.xml
new file mode 100644
index 0000000..11045fe
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Glossaries.xml
@@ -0,0 +1,291 @@
+
+
+
+ Glossaries<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Glossary pane</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Glossaries</primary>
+ </indexterm>
+
+ Glossaries are files created and updated manually for use in
+ OmegaT.
+
+ If an OmegaT project contains one or more
+ glossaries, any terms in the glossary which are also found in the current
+ segment will be automatically displayed in the Glossary viewer.
+
+ You define its location and name in the project properties dialog. The
+ extension must be .txt (if not, it will be added). The
+ location of the file must be within the /glossary
+ folder, but it can be in a deeper directory (e.g.,
+ glossary/sub/glossary.txt). The file does not need to
+ exist when setting it, it will be created (if necessary) when adding a
+ glossary entry. If the file already exists, not attempt is done to verify
+ the format or the character set of the file: the new entries will always be
+ in tab-separated format and UTF-8. As the existing content will not be
+ touched, damaged to an existing file would be limited.
+
+
+ Usage
+
+ To use an existing glossary, simply place it in the
+ Project files
+
+ Glossary subfolder
+ /glossary folder after creating the
+ project. OmegaT automatically detects glossary
+ files in this folder when a project is opened. Terms in the current
+ segment which OmegaT finds in the glossary
+ file(s) are displayed in the Glossary pane:
+
+
+ Glossary pane
+
+
+
+ Glossary pane
+
+
+
+
+
+
+
+
+
+
+
+
+ The word before the = sign is the source term, and its translation
+ is (or are) the words after =. The vocabulary entry can have a comment
+ added (see "transitive verb" for the second item). The glossary function
+ only finds exact matches with the glossary entry (e.g. does not find
+ inflected forms etc.). New terms can be added manually to the glossary
+ file(s) during translation (for example in a text editor), but newly added
+ terms will not be recognized until the project is reloaded.
+
+ The source term does not have to be a single-word item, as the next
+ example shows:
+
+
+ multiple words entries in glossaries - example<indexterm
+ class="singular">
+ <primary>Glossary pane - multiple-words entries</primary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+ The underlined item "pop-up menu" can be found in the glossary pane
+ as "pojavni menu". Highlighting it in the Glossary pane and then
+ rightclicking insets at the cursor position in the target
+ segment.
+ Note that in the above case, this is just half (or even less) of
+ the story, as the target language (Slovenian) uses declension. So the
+ inserted "pojavni meni" has to be changed to "pojavnem meniju". In
+ other words, typing the term correctly without bothering with
+ highlighting and rightclicking is probably faster.
+
+
+
+
+ <indexterm class="singular">
+ <primary>Glossaries</primary>
+
+ <secondary>File format</secondary>
+ </indexterm>File format<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>User files</secondary>
+
+ <seealso>Glossaries</seealso>
+ </indexterm>
+
+ Glossary files are simple plain text files containing three-column,
+ tab-delimited lists with the source and target terms in the first and
+ second columns respectively. The third column can be used for additional
+ information. You can have entries with the target column missing, i.e.
+ just containing the source term and the comment.
+
+ Glossary files can be either in system default encoding (and
+ indicated by the extension .tab) or in UTF-8 (the extension .utf8). The
+ Unicode encoding (UTF8) is preferred for obvious reasons. Also supported
+ is the CSV format. This format is the same as the tab separated one:
+ source term, target term. Comment fields are separated by a comma ','.
+ Strings can be enclosed by quotes ", which allows having a comma inside a
+ string:
+
+ "This is a source term, which contains a comma","c'est un
+ terme, qui contient une virgule"
+
+ In addition to the plain text format, TBX format
+ Glossaries
+
+ TBX format
+ is also supported. TBX - Term Base eXchange - is the open,
+ XML-based standard for exchanging structured terminological data, TBX has
+ been approved as an international standard by LISA
+ LISA -
+
+ File format
+ and ISO. If you have an existing terminology handling
+ system - MultiTerm for example - it is quite possible it offers the export
+ of terminology data via TBX format. Microsoft
+ Terminology Collection
+ Glossaries
+
+ Microsoft Terminology collection
+ can be downloaded in nearly 100 languages and can serve as
+ a cornerstone IT glossary.
+
+
+
+ How to create glossaries<indexterm class="singular">
+ <primary>Glossaries</primary>
+
+ <secondary>Creating a glossary</secondary>
+ </indexterm>
+
+ The project setting allows one can enter a name for a writable
+ glossary file (see beginning of this chapter). Adding new entries is done
+ by using the keyboard shortcut Ctrl+Shift+G . A dialog
+ opens, allowing you to enter the source term, target term and any comments
+ you may have:
+
+
+
+
+
+
+
+
+
+
+
+ The contents of glossary files are kept in memory and are loaded
+ when the project is opened or reloaded. Updating a glossary file is thus
+ rather simple: press Ctrl+Shift+G and enter the new
+ term, its translation and any comments you may have (ensuring you press
+ tab between the fields) and save the file. The contents of the glossary
+ pane will be updated accordingly.
+
+
+ Glossaries
+
+ Location of the writable glossary file
+ The location of the writable glossary file can be set in the
+ Project > Properties ... dialog. The recognized extensions are
+ TXT and UTF8
+
+ Note: Of course there are other
+ ways and means to create a simple file with tab delimited entries. Nothing
+ speaks against using Notepad++ on Windows, GEdit on Linux for instance or
+ some spreadsheet program for this purpose: any application, that can
+ handle UTF8 and that can show white space (so that you do not miss the
+ required TAB characters) can be used.
+
+
+
+ <indexterm class="singular">
+ <primary>Glossaries</primary>
+
+ <secondary>Trados MultiTerm</secondary>
+ </indexterm>Using Trados MultiTerm
+
+ Data exported from Trados MultiTerm can be used as
+ OmegaT glossaries without further modification,
+ provided they are given the file extension .tab and
+ the source and target term fields are the first two fields respectively.
+ If you export using the system option "Tab-delimited export", you will
+ need to delete the first 5 columns (Seq. Nr, Date created etc). The newer
+ versions of MultiTerm support exporting to TBX format.
+
+
+
+ <indexterm class="singular">
+ <primary>Glossaries</primary>
+
+ <secondary>Problems with glossaries</secondary>
+ </indexterm>Common glossary problems
+
+ Problem: No glossary terms are displayed -
+ possible causes:
+
+
+
+ No glossary file found in the "glossary" folder.
+
+
+
+
+
+ The glossary file is empty.
+
+
+
+
+
+ The items are not separated with a TAB character.
+
+
+
+
+
+ The glossary file does not have the correct extension (.tab or
+ .utf8).
+
+
+
+
+
+ There is no EXACT match between the glossary entry and the
+ source text in your document - for instance plurals.
+
+
+
+
+
+ The glossary file does not have the correct encoding.
+
+
+
+
+
+ There are no terms in the current segment which match any terms
+ in the glossary.
+
+
+
+
+
+ One or more of the above problems may have been fixed, but the
+ project has not been reloaded.
+
+
+
+ Problem: In the glossary pane, some characters
+ are not displayed properly
+
+
+
+ ...but the same characters are displayed properly in the Editing
+ pane: the extension and the file encoding do not match.
+
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/InstallingAndRunning.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/InstallingAndRunning.xml
new file mode 100644
index 0000000..fe178dd
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/InstallingAndRunning.xml
@@ -0,0 +1,1086 @@
+
+
+
+ Installing and running <application>OmegaT</application>
+
+
+ Windows Users<indexterm class="singular">
+ <primary>Installing OmegaT</primary>
+
+ <secondary>Windows</secondary>
+ </indexterm>
+
+
+ Downloading the
+ package
+
+ Do you have a Java implementation compatible with Oracle's Java
+ 1.5 JRE?
+
+
+
+ Yes: download
+ OmegaT_2.5.x_Windows_without_JRE.exe.
+
+
+
+ No / I don't know:
+ download OmegaT_2.5.x_Windows.exe.
+
+ This package is bundled with Oracle's Java Runtime
+ Environment. This JRE will not interfere with other Java
+ implementations that may already be installed on your system.
+
+
+
+
+
+ <application>Installing OmegaT</application>
+
+ To install OmegaT, double-click on the
+ program you have downloaded, and follow the instructions
+
+
+
+ Adding <application>OmegaT</application> to the start menu or
+ desktop<indexterm class="singular">
+ <primary>Customizing OmegaT</primary>
+
+ <secondary>Windows</secondary>
+ </indexterm>
+
+ During the installation, the setup program asks you whether you
+ wish to create a folder in the start menu, and
+ whether you wish to create a shortcut on the desktop and in the quick
+ launch bar.
+
+ You can still create a shortcut later by dragging
+ OmegaT.exe to the
+ desktop or start menu to link it from there.
+
+
+
+ Running <application>OmegaT<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Windows</secondary>
+ </indexterm></application>
+
+ Once OmegaT is installed, you can click
+ on OmegaT.jar to launch
+ it directly or you can launch it directly from the command line.
+
+ The simplest way to launch OmegaT, however, is to execute
+ theOmegaT.exe program.
+
+ Running OmegaT
+
+ Windows
+
+ INI file
+ The options for the program start-up in this case will be
+ read from the OmegaT.l4J.ini
+ file, which resides in the same folder as the exe file and
+ which you can edit to reflect your setup. The following example for the
+ INI file reserves 1GB of memory, requests French as the user language
+ and Canada as the country:
+
+ # OmegaT.exe runtime configuration
+# To use a parameter, remove the '#' before the '-'
+# Memory
+-Xmx1024M
+# Language
+-Duser.language=FR
+# Country
+-Duser.country=CA
+
+
+
+ Upgrading OmegaT <indexterm class="singular">
+ <primary>Upgrading OmegaT</primary>
+
+ <secondary>Windows</secondary>
+ </indexterm>
+
+ This information applies only to the "Traditional"
+ Windows versions of OmegaT. It does not apply to the Web Start versions,
+ which are upgraded automatically, nor to cross-platform versions
+ installed on Windows.
+
+ If you already have a version of OmegaT installed on your PC and
+ wish to upgrade to a more recent version, you have two options:
+
+
+
+ Install over the existing installation.
+ To do this, simply select the same installation folder as
+ the existing installation when installing the new version. The "old"
+ version of OmegaT will be overwritten, but any settings from it will
+ be retained. This includes preferences set from within OmegaT, any
+ changes you have made to your OmegaT.l4J.ini
+ file, and also your launch script (.bat file), if you are using
+ one.
+
+
+
+ With this method, you may also download the "Windows without JRE"
+ version, since the new installation will use your existing JRE.
+
+
+
+ Install to a new folder. This
+ will enable you to keep both versions side-by-side, which you may
+ wish to do until you feel comfortable with the new version. This
+ method will also use preferences and settings you have made from
+ within OmegaT. In this case, however:
+
+
+
+ If you have made changes to your OmegaT.l4J.ini
+ file and/or are using a .bat file, you must copy
+ these over.
+
+
+
+
+
+ If your existing OmegaT installation is a "Windows with
+ JRE" version, the new version must also be a "Windows with JRE"
+ version.
+
+
+
+
+
+
+
+
+ Linux (Intel) Users<indexterm class="singular">
+ <primary>Installing OmegaT</primary>
+
+ <secondary>Linux</secondary>
+ </indexterm>
+
+
+ Downloading the right package
+
+ Do you have a Java implementation compatible with Oracle's Java
+ 1.5 JRE?
+
+
+
+ Yes: download
+ OmegaT_2.5.x_Without_JRE.zip.
+
+
+
+ No / I don't know: download
+ OmegaT_2.5.x_Linux.tar.bz2.
+
+ This package is bundled with Oracle's Java Runtime
+ Environment. This JRE will not interfere with other Java
+ implementations that may already be installed on your system.
+
+
+
+
+
+ <application>Installing OmegaT</application>
+
+ Unpack/untar the downloaded file. This will create an omegat/
+ folder in the working folder in which you will find all the files needed
+ to run OmegaT. To untar the
+ .tar.gz file:
+
+ $ tar xf downloaded_file.tar.gz
+
+
+
+ Adding <application>OmegaT</application> to your menus (KDE) or
+ panels (Gnome)
+
+
+ KDE 4 Users<indexterm class="singular">
+ <primary>Customizing OmegaT</primary>
+
+ <secondary>KDE 4</secondary>
+ </indexterm>
+
+ You can add OmegaT to your menus as
+ follows:
+
+
+
+ Press Alt+F2
+ to show KRunner. Type
+ kmenuedit+enter to run the command. The
+ KMenuEditor appears. In KMenuEditor select File ->
+ New Item.
+
+
+
+ Then, after selecting a suitable menu, add a submenu/item
+ with File - New Submenu and File -
+ New Item. Enter OmegaT as
+ the name of the new item.
+
+
+
+ In the "Command" field, use the navigation button to find
+ your OmegaT launch script (the file
+ named OmegaT in the unpacked folder),
+ and select it.
+
+
+
+ Click on the icon button (to the right of the
+ Name/Description/Comment fields)
+
+
+
+ Other Icons - Browse, and navigate to the /images subfolder
+ in the OmegaT application folder.
+ Select the OmegaT.png icon.
+
+
+
+ Finally, save the changes with File -
+ Save.
+
+
+
+
+
+ GNOME Users<indexterm class="singular">
+ <primary>Customizing OmegaT</primary>
+
+ <secondary>GNOME</secondary>
+ </indexterm>
+
+ You can add OmegaT to your menus as
+ follows:
+
+
+
+ Right-click on the panel - Add New
+ Launcher.
+
+
+
+ Enter "OmegaT" in the "Name"
+ field; in the "Command" field, use the navigation button to find
+ your OmegaT launch script (the file
+ named OmegaT in the unpacked folder).
+ Select it and confirm with OK.
+
+
+
+ Click on the icon button, then hit
+ Browse... and navigate to the /images
+ subfolder in the OmegaT application
+ folder. Select the
+ OmegaT.png icon.
+ GNOME may fail to display the icon files in the available formats
+ and initially appear to expect an SVG file, but if the folder is
+ selected, the files should appear and
+ OmegaT.png can be selected.
+
+
+
+
+
+
+ Running <application>OmegaT<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Linux</secondary>
+ </indexterm></application>
+
+ You can launch OmegaT from the command line with a script that
+ includes start-up options or you can click on
+ OmegaT.jar to launch it
+ directly. Methods differ depending on the distribution. Make sure that
+ your PATH settings are correct and that
+ .jar files are properly associated with a Java
+ launcher. Check "Command line launching" below for more
+ information.
+
+
+
+
+ Mac OS X Users<indexterm class="singular">
+ <primary>OS X</primary>
+
+ <secondary>Installing OmegaT</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Installing OmegaT</primary>
+
+ <secondary>OS X</secondary>
+ </indexterm>
+
+
+ Downloading the package
+
+ OmegaT 2.5 requires Java 1.5 to run.
+ Use "Software Update..." from the Apple menu to update your Java
+ version.
+
+ Download OmegaT_2.5.x_Mac.zip.
+
+
+
+ <application>Installing OmegaT </application>
+
+ Double click on OmegaT_2.5.x_Mac.zip to
+ unpack it. This creates a folder called
+ OmegaT. The folder contains 2
+ files: index.html and
+ OmegaT.app. Copy the
+ folder to a suitable folder (e.g. Applications). Once you have done
+ this, you can delete the OmegaT_2.5.x_Mac.zip file,
+ it is no longer needed.
+
+
+
+ Adding <application>OmegaT</application> to the Dock<indexterm
+ class="singular">
+ <primary>OS X</primary>
+
+ <secondary>Adding OmegaT to the Dock</secondary>
+
+ <seealso>Customizing OmegaT</seealso>
+ </indexterm>
+
+ Drag and drop
+ OmegaT.app onto the
+ Dock.
+
+
+
+ Running <application>OmegaT<indexterm class="singular">
+ <primary>OS X</primary>
+
+ <secondary>Running OmegaT</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>OS X</secondary>
+ </indexterm></application>
+
+ Double-click on
+ OmegaT.app or click on its
+ location in the Dock.
+
+ To access
+ Info.plist, right-click
+ on OmegaT.app and select
+ "Show Package Contents", then open the file by right-clicking on it and
+ selecting your text editor of choice. You can also "cd" there directly
+ from the command line and open
+ Info.plist in a command line editor
+ like emacs or vi.
+ OS X
+
+ Customizing OmegaT
+
+ Launch parameters
+
+ OS X
+
+ Customizing OmegaT
+
+
+ You can modify the Properties as well as the
+ VMOptions part.
+
+ If you wish to add values to VMOptions, put a
+ space between them. For example, -Xmx1024M
+ -Duser.language=ja will launch
+ OmegaT with 1024MB of memory and with the
+ user interface in Japanese.
+
+ To launch multiple instances of
+ OmegaT.app, double-click
+ the file JavaApplicationStub located in
+ OmegaT.app/
+ Contents/MacOS/.
+
+ Use
+ OmegaT.jar file located
+ in
+ OmegaT.app/Contents/Resources/Java/
+ to launch OmegaT from the command line. Check
+ "Command line launching" below for more information.
+
+
+
+ Mac OS X goodies
+
+ OmegaT.app can be
+ accessed from the Mac OS X Services. You can thus select a word anywhere
+ in OmegaT and use Services to check this
+ word, for instance in Spotlight or in Google. You can also use
+ AppleScript or Automator to create Services or scripts that will
+ automate frequent actions
+
+
+
+
+ Other Systems<indexterm class="singular">
+ <primary>Installing OmegaT</primary>
+
+ <secondary>Other systems</secondary>
+ </indexterm>
+
+ This information applies to systems such as Solaris SPARC/x86/x64,
+ Linux x64/PowerPC, Windows x64
+
+
+ Downloading the right
+ package
+
+ OmegaT is available bundled with a
+ Oracle Java JRE for Linux (Intel x86) and Windows platforms. Users of
+ other platforms (Linux PowerPC, Linux x64, Solaris SPARC/x86/x64,
+ Windows x64 etc) must have a running compatible Java JRE on their system
+ to be able to use OmegaT.
+
+ Do you have a Java implementation compatible with Oracle's Java
+ 1.5 JRE?
+
+
+
+ Yes: download
+ OmegaT_2.5.x_Windows_without_JRE.zip. This
+ package can be used on any platform where a Java 1.5 JRE compatible
+ JRE is installed.
+
+
+
+ I don't know: open a terminal
+ and type "java -version". If a "command not found" or similar
+ message is returned, it is likely that Java is not installed on your
+ system
+
+
+
+ No: obtain a Java JRE for
+ your system (see below) and download
+ OmegaT_2.5.x_Without_JRE.zip.
+
+ Oracle provides JREs for Solaris SPARC/x86 (Java 1.5) and for
+ Linux x64, Solaris x64, Windows x64 (Java 1.5) at http://www.oracle.com/technetwork/java/archive-139210.html
+
+ IBM provides JREs for Linux PowerPC at http://www.ibm.com/developerworks/java/jdk/linux/download.htm
+
+ Follow the installation instructions of the package you
+ need.
+
+
+
+
+
+ <application>Installing OmegaT</application><indexterm
+ class="singular">
+ <primary>Installing OmegaT</primary>
+
+ <secondary>Other systems</secondary>
+ </indexterm>
+
+ To install OmegaT, simply unpack the
+ OmegaT_2.5.x_Without_JRE.zip file. This
+ creates an ./OmegaT_2.5.x_Without_JRE/ directory in
+ the working folder with all the files necessary to run
+ OmegaT.
+
+
+
+ Installing convenient shortcuts
+
+ Follow your system's instructions to install
+ OmegaT shortcuts in convenient places of your
+ choosing.
+
+
+
+ Running <application>OmegaT<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Other systems</secondary>
+ </indexterm></application>
+
+ Once OmegaT is installed, you can
+ launch it directly from the command line, you can create a script that
+ includes launch parameters for the command line or you can click on
+ OmegaT.jar to launch it
+ directly. Methods differ depending on the distribution. Make sure that
+ your PATH settings are correct and that
+ .jar files are properly associated with a Java
+ launcher. Check "Command line launching" below for more
+ information.
+
+
+
+
+ Using Java Web Start<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Using Java Web Start</secondary>
+ </indexterm>
+
+ Java Web Start technology (part of Java 1.5 and above) can be used
+ to deploy standalone Java software applications with a single click over
+ the network. Java Web Start ensures that the latest version of the
+ application will be deployed, as well as the correct version of the Java
+ Runtime Environment (JRE) used. To start OmegaT for the first time with
+ Java Web Start, load the following URL in your browser:
+
+ http://omegat.sourceforge.net/webstart/OmegaT.jnlp
+
+ Download the file
+ OmegaT.jnlp and then click on it.
+ During the installation, depending on your operating system, you may
+ receive several security warnings. The permissions you give to this
+ version (which may appear as "unrestricted access to the computer") are
+ identical to the permissions you give to the local version, i.e., they
+ allow access to the hard drive of the computer. Subsequent clicks on
+ OmegaT.jnlp will check for
+ any upgrades, install them, if there are any, and then start
+ OmegaT. After the initial installation you can,
+ of course, also use
+ OmegaT.jnlp also when you
+ are offline.
+
+ Privacy:
+ OmegaT Java Web Start does not save any of your
+ information beyond the computer on which you are running it. The
+ application runs on your machine only. Your documents and translation
+ memories remain on your computer, and the
+ OmegaT project will have no access to your work
+ or information.
+
+ Note that if you need or wish to use any of the launch command
+ arguments (see above), you must use the normal installation.
+
+
+
+ Starting OmegaT from the command line<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Command line launching</secondary>
+ </indexterm>
+
+ Normally, it is not necessary to start
+ OmegaT from the command line. However, the
+ command-line alternative allows the user to control and modify the
+ program's behavior. There are two ways of launching
+ OmegaT using the command line.
+
+
+ Opening a command line window
+
+ A command line window is also referred to as a "terminal window".
+ On Windows it is called an "MS-DOS window" and is available from the
+ Start Menu, inside Programs, through the "MS-DOS" item. The Mac OS X
+ equivalent is the application Terminal located in Applications →
+ Utilities.
+
+ To launch OmegaT, you must normally
+ type two commands. The first of these is:
+
+ cd {folder}
+
+ where {folder} is the name of the folder,
+ with complete path, in which your OmegaT
+ program - specifically, the file
+ OmegaT.jar - is located.
+ In practice, this command will therefore be something like this:
+
+ On Windows
+
+ cd C:\Program
+ Files\OmegaT
+
+ On Mac OS X
+
+ cd <OmegaT.app
+ location>/OmegaT.app/Contents/Resources/Java/
+
+
+ On Linux
+
+ cd /usr/local/omegat
+
+ This command changes the folder to the folder containing the
+ executable OmegaT file. The second command is
+ the command which actually launches OmegaT.
+ In its most basic form, this command is:
+
+ java -jar
+ OmegaT.jar
+
+ Pay attention to the capitalization - the program will not start,
+ if you enter omegat instead of OmegaT
+ !
+
+ This method has a particular benefit of being suitable for finding
+ causes of problems: if an error occurs during use of the program, an
+ error message is output in the terminal window which may contain useful
+ information on the cause of the error.
+
+ The above method somewhat impractical way of launching a program
+ routinely. For this reason, the two commands described above are
+ contained in a file (a "script", also called a ".bat file" on Windows
+ systems).
+
+ When this file is executed, the commands within it are
+ automatically carried out. Consequently, to make changes to the launch
+ command, it is sufficient to modify the file.
+
+
+
+ Launch command arguments<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Launch script arguments</secondary>
+ </indexterm>
+
+ The basic command has already been mentioned above. Changes to
+ this command involve the addition of "arguments" to it. Arguments are
+ added after the initial "java", and before the
+ "-jar OmegaT.jar". Note
+ that in Windows you can change the
+ OmegaT.l4J.ini file to
+ reflect your preferences. On Mac OS X, you can change the
+ Info.plist located in
+ OmegaT.app/Contents/ to
+ do the same.
+
+ A list of possible arguments is given below. Advanced users can
+ obtain more information on the arguments by typing man
+ java in the terminal window.
+
+
+
+ User interface language
+
+
+ -Duser.language=XX
+ Running OmegaT
+
+ Launch script arguments
+
+ User.language
+ Normally, i.e. when OmegaT
+ is launched without any arguments, the program first detects the
+ language of the user's operating system. If a user interface in this
+ language is available, OmegaT uses it.
+ So, if the user's operating system is Russian and
+ OmegaT has been localized in Russian,
+ OmegaT is displayed with a Russian user
+ interface, Russian menus, etc. If the language of the user's system
+ is not available, OmegaT defaults to
+ English. This is the standard behavior.
+
+ The "-Duser.language=XX" argument causes
+ OmegaT to use the language specified
+ rather than the language of the user's operating system. "XX" in the
+ command stands for the two-digit code of the desired language. To
+ launch OmegaT with a French interface
+ (for example on a Russian operating system), the command would
+ therefore be:
+
+ java -Duser.language=fr -jar
+ OmegaT.jar
+
+
+
+
+
+ User country setup
+
+ -Duser.country=XX
+ Running OmegaT
+
+ Launch script arguments
+
+ User.country
+ Besides the language, you can also specify the
+ country, for example CN or TW in case of the Chinese language. To
+ display the instant start guide in the desired language, you need to
+ specify both the language and the country. This is necessary even if
+ there's only one combination available, like pt_BR in case of
+ Portuguese / Brazil.
+
+
+
+
+
+ Font antialiasing - (Java 1.5
+ only)
+
+ -Dswing.aatext=true
+ Running OmegaT
+
+ Launch script arguments
+
+ Font antialiasing
+ This argument effects anti-aliasing of the
+ fonts, thereby improving their appearance.
+
+
+
+ Memory assignment
+
+ -XmxZZM
+ Running OmegaT
+
+ Launch script arguments
+
+ Memory assignment
+ This command assigns more memory to
+ OmegaT. By default, 512 MB are assigned,
+ so there is no advantage in assigning less than this figure. "ZZ"
+ stands for the amount of memory assigned, in megabytes. The command
+ to launch OmegaT with assignment of 1024
+ MB (1 gigabyte) of memory is therefore:
+
+ java -Xmx1024M -jar
+ OmegaT.jar
+
+
+
+ Proxy host IP address
+
+ -Dhttp.proxyHost=nnn.nnn.nnn.nnn
+ Running OmegaT
+
+ Launch script arguments
+
+ Proxy server IP address
+ The IP address of your proxy server, if
+ your system uses a proxy.
+
+
+
+ Proxy Server Port
+ Number
+
+ -Dhttp.proxyPort=NNNN
+
+ Running OmegaT
+
+ Launch script arguments
+
+ Proxy server - Port Number
+ The port number your system uses to access the proxy
+ server.
+
+
+
+ Google Translate V2
+
+ -Dgoogle.api.key=A123456789B123456789C123456789D12345678
+
+ Running OmegaT
+
+ Launch script arguments
+
+ Google Translate V2
+ If you have signed up for the Google
+ Translate services, enter your private Google API key here. Note
+ that the key is 38 characters long.
+
+
+
+ Arguments can be combined: to launch
+ OmegaT with all the examples described above,
+ the command would be:
+
+ java -Dswing.aatext=true -Duser.language=pt
+ -Duser.country=BR -Xmx1024M -DDhttp.proxyHost=192.168.1.1
+ -Dhttp.proxyport=3128 -jar
+ -OmegaT.jar
+
+
+
+ OmegaT in the command line mode<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Command line mode</secondary>
+ </indexterm>
+
+ The purpose of the console mode is to use OmegaT as a translation
+ tool in a scripting environment. When started in console mode, no GUI is
+ loaded (so it will work on any console) and the given project is
+ automatically processed as requested.
+
+
+ Prerequisites
+
+ To run OmegaT in the command line
+ mode, a valid OmegaT project must be
+ present. The location does not matter, since you have to add it to the
+ command line at the start-up anyway.
+
+ If you need altered settings, the configuration files must be
+ available. This can be achieved in two ways:
+
+
+
+ Run OmegaT normally (with the
+ GUI) and specify the settings. If you start
+ OmegaT in console mode, it will use the
+ same settings.
+
+
+
+ If you can't run OmegaT normally
+ (no graphical environment available): copy the settings files from
+ some other OmegaT installation on
+ another machine to a specific directory. The location does not
+ matter, since you can add it to the command line at startup. The
+ relevant files are filters.conf and
+ segmentation.conf and can be found in the user
+ home directory (e.g. C:\Documents and
+ Settings\%User%\OmegaT under
+ Windows, %user%/.omegat/ under Linux)
+
+
+
+
+
+ Starting in console mode
+
+ To start OmegaT in console mode, some
+ extra parameters have to be passed to it on startup. The most
+ important is <project-dir>, and
+ optionally --config-dir=<config-dir>.
+ Example:
+
+ java -jar OmegaT.jar
+ /path/to/project \
+
+ --config-dir=/path/to/config-files/ \
+
+
+ --mode=console-translate|console-createpseudotranslatetmx|console-align
+
+ --source-pattern={regexp}
+
+ Note that all parameters start with a double - character.
+
+ Explanation:
+
+
+
+ <project-dir> tells
+ OmegaT where to find the project to
+ translate. If given, OmegaT starts in
+ console mode and will translate the given project.
+
+
+
+
+
+ --config-dir=<config-dir> tells
+ OmegaT in which directory the
+ configuration files are stored. If not given,
+ OmegaT reverts to default values
+ (OmegaT dir under user home, or if not
+ available, the current working directory). Note double -
+ character
+
+
+
+
+
+ --mode=...-
+ OmegaT starts in console mode to
+ perform one of the following services automatically
+
+
+
+ --mode=console-translate
+
+ In this mode, OmegaT will attempt to translate the files
+ in /source/ with the available translation memories. This is
+ useful to run OmegaT on a server with TMX files automatically
+ fed to a project.
+
+
+
+ --mode=console-createpseudotranslatetmx
+
+ In this mode OmegaT will create a TMX for the whole
+ project, based on the source files only. You specify the TMX
+ file to be created with
+
+ --pseudotranslatetmx=allsegments.tmx
+ --pseudotranslatetype=[equal|empty]
+
+ The argument pseudotranslatetype
+ specifies, whether the target segments are to be equal to the
+ source, or left empty.
+
+
+
+ --mode=console-align
+
+ In this mode, OmegaT will align the Java properties
+ files found in the /source/ folder of the
+ project to the contents found at the specified location. The
+ resulting TMX is stored in the /omegat/
+ folder under the name align.tmx.
+
+ Additional parameter is required in this case,
+ specifying the location of the target data:
+
+ --alignDir={location of translated
+ files}
+
+ alignDir must contain a translation
+ in the target language of the project. For instance, if the
+ project is EN->FR, alignDir must contain a bundle ending
+ with _fr. The resulting tmx is stored in the
+ omegat folder under the name
+ align.tmx.
+
+
+
+
+
+ --source-pattern={regexp}
+
+ When mode has been used, this option will specify the files
+ to be processed automatically.. If the parameter is not specified,
+ all files will be processed. Here's few typical examples to limit
+ your choice:
+
+
+
+ .*\.html
+
+ All HTML files will be translated - note that the period
+ in the usual *.html has to be escaped (\.) as specified by the
+ rules for regular expressions
+
+
+
+ test\.html
+
+ Only the file test.html at the root of the source
+ directory will be translated. If there are other files named
+ test.html in other directories, they will be ignored.
+
+
+
+ dir-10\\test\.html
+
+ Only the file test.html in the directory dir-10 will be
+ processed. Again note that the backslash is escaped as
+ well.
+
+
+
+
+
+ --output-tag-validation-={regexp}
+
+ When mode has been used, this option will specify the files
+ to be processed automatically.. If the parameter is not specified,
+ all files will be processed. Here's few typical examples to limit
+ your choice:
+
+
+
+ .*\.html
+
+ All HTML files will be translated - note that the period
+ in the usual *.html has to be escaped (\.) as specified by the
+ rules for regular expressions
+
+
+
+ test\.html
+
+ Only the file test.html at the root of the source
+ directory will be translated. If there are other files named
+ test.html in other directories, they will be ignored.
+
+
+
+ dir-10\\test\.html
+
+ Only the file test.html in the directory dir-10 will be
+ processed. Again note that the backslash is escaped as
+ well.
+
+
+
+
+
+
+
+ Quiet option
+
+ An extra command line parameter specific to console mode:
+ --quiet. In the quiet mode, less info is logged to
+ the screen. The messages you would usually find in the status bar are
+ not displayed.
+
+ Usage: java -jar OmegaT.jar
+ /path/to/project --mode=console-translate --quiet
+
+
+
+ Tag validation option
+
+ Another extra command line parameter specific to console mode:
+ --tag-validation=[abort|warn]. When this parameter
+ is added, tag validation is done prior to translation/aligning. If the
+ value is abort, then on tag errors the errors are
+ printed and the program stops. If the value is warn
+ then the errors are printed but OmegaT continues.
+
+ Usage: java -jar OmegaT.jar
+ /path/to/project --mode=console-translate
+ --tag-validation=abort
+
+
+
+
+
+ Building <application>OmegaT</application> From Source<indexterm
+ class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Building OmegaT from source</secondary>
+ </indexterm>
+
+ Note that you will need the ant program
+ (http://ant.apache.org/bindownload.cgi) to build your
+ own version of OmegaT. Unpack the
+ OmegaT_2.5.x_Source.zip file and enter the
+ OmegaT_2.5.x_Source directory or enter the ./omegat/
+ directory of the SVN checked out code. Please make sure that a build.xml
+ file is present in that folder. Then, on the command line, type:
+
+ $ ant jar release
+
+ This will create a full distribution of
+ OmegaT in the ./dist/ folder, where you will
+ find all the files necessary to run
+ OmegaT.
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/InstantStartGuide.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/InstantStartGuide.xml
new file mode 100644
index 0000000..a36902b
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/InstantStartGuide.xml
@@ -0,0 +1,183 @@
+
+
+
+ Learn to use OmegaT in 5 minutes!
+
+
+ Set up a new project<indexterm class="singular">
+ <primary>Project</primary>
+
+ <secondary>Create / open new</secondary>
+ </indexterm>
+
+ Note:On an Apple Mac, use the Cmd
+ or Apple key instead of the Ctrl
+ key
+
+ To start using OmegaT, first create a project that will hold all
+ your files, such as your source file, translation memories, glossaries,
+ and eventually your translated file. In the Project
+ menu, select
+
+
+ New...
+
+ Menu Project
+
+ New...
+ type a name for your project. Remember where you create the
+ project, because you will later need to return to it.
+
+ After you give your project a name, the Create New Project dialog
+ will open. At the top of that dialog, select your source file's language
+ and the language that your translated file will be, and click
+ OK to continue
+
+ If you are interested in other settings of this dialog,
+ you can return to it any time by pressing
+ Ctrl+E.
+
+ Next, the Project Files dialog opens. Click the Import source
+ files... to select your source file. OmegaT will then copy the selected
+ file to the /source/subfolder of your newly created
+ project. After the source file has loaded in the Editor pane, you can
+ close the Project files dialog.
+
+
+
+ Translate the file
+
+ OmegaT will present one segment at a time for you to translate.
+ After you have translated each segment, press Ctrl+U to
+ move to the next untranslated segment. Whenever you want to see what your
+ translation will look like in its final format, press
+ Ctrl+D to generate the translated document, which will be
+ created in the /target/ subfolder of your project folder. During
+ translation, use the Edit and Go To
+ menus to perform various useful functions..
+
+
+
+ Validate your tags
+
+ If your source file is a formatted file, e.g. Microsoft Word,
+ LibreOffice Writer or HTML, OmegaT will convert the formatting into tags
+ that surround the text that you translate. Often documents will also have
+ tags that have nothing to do with formatting, but which are also
+ important.In the source file (and in the translated file), A source
+ sentence might look like
+
+
+
+
+
+
+
+
+
+
+
+ OmegaT, however, will present this sentence in the following
+ fashion:
+
+
+
+
+
+
+
+
+
+
+
+ The tags in OmegaT are greyed, so they are easy to recognise. They
+ are not protected, so that you can delete them, enter them by hand or move
+ them around in the target sentence. However, if you made mistakes when you
+ typed the formatting tags, your translated file might fail to open.
+ Therefore, press Ctrl+T before you generate your
+ translated file, to validate that your tags are correct.
+
+
+
+ Generate the translated file
+
+ Once you have made certain that there are no tag errors in your
+ translation, press Ctrl+D to generate the target file,
+ which will be created in the /target/subfolder of
+ your project folder.
+
+
+
+ Few more things to remember
+
+
+
+ If a file does not loads into the Editor pane, then it could be
+ that your source file is in a format that doesn't work in OmegaT. See
+ Chapter 7: File Filters in the User Manual for a list of file formats
+ that OmegaT can handle. If a file does not loads into the Editor pane,
+ then it could be that your source file is in a format that doesn't
+ work in OmegaT. See Chapter 7: File Filters in the User Manual for a
+ list of file formats that OmegaT can handle.
+
+
+
+
+
+ You can create a new project for each new job, and you can add
+ several source files to a project at a time.
+
+
+
+
+
+ To remind yourself of the project's initial settings, open the
+ Project Settings dialog by pressing Ctrl+E. To see a
+ list of files in the project, open the Project Files dialog by
+ pressing Ctrl+L..
+
+
+
+
+
+ At the end of your translation, OmegaT exports three translation
+ memories called "level1", "level2" and "omegat" to your project
+ folder. The "level1" and "level2" memories can be shared with users of
+ other translation programs. The memory named "omegat" can be used in
+ OmegaT itself, in future projects that you create. If you place
+ translation memory files in the /tm/ subfolder of your project folder,
+ OmegaT will automatically search them for similar segments, called
+ "fuzzy matches". .
+
+
+
+
+
+ You can create a glossary by pressing
+ Ctrl+Shift+G, or copy existing glossaries to
+ the/glossary/subfolder of your project folder,
+ and OmegaT will automatically look up words in them.
+
+
+
+
+
+ It is often useful to search for words and phrases in the source
+ text and in your translation, so press Ctrl+F for the
+ "Text Search" dialog at any time.
+
+
+
+
+
+ For a more comprehensive introduction see OmegaT
+ for beginners on the OmegaT web site. If you need assistance
+ with any aspect of OmegaT, feel free to join the OmegaT users
+ group.
+
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/MachineTranslation.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/MachineTranslation.xml
new file mode 100644
index 0000000..9ed1848
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/MachineTranslation.xml
@@ -0,0 +1,221 @@
+
+
+
+ Machine Translation<indexterm class="singular">
+ <primary>Machine Translation</primary>
+ </indexterm>
+
+
+ Introduction<indexterm class="singular">
+ <primary>Machine Translation</primary>
+
+ <secondary>Introduction</secondary>
+ </indexterm>
+
+ As opposed to user-generated translation memories (as in the case of
+ OmegaT) Machine translation (MT) tools use
+ rule-based linguistic tools to create a translation of the source segment
+ without the need for a translation memory. Statistical learning
+ techniques, based on source and target texts, are used to build a
+ translation model. Machine translation services have been achieving good
+ and steadfastly improving results in research evaluations.
+
+ To activate any of the Machine Translation services, go to
+ Options > Machine Translate ... and activate
+ the service desired. Note that they are all web-based: you will have to be
+ on-line if you want to use them.
+
+
+
+ Google Translate<indexterm class="singular">
+ <primary>Machine Translation</primary>
+
+ <secondary>Google Translate</secondary>
+ </indexterm>
+
+ Google Translate is a payable service offered by Google, for
+ translating sentences, web sites and complete texts between an
+ ever-growing number of languages. At the time of writing the list includes
+ more than 50 languages, from Albanian to Yiddish, including of course all
+ the major languages. The current version of the service is based on usage,
+ with the price of 20 USD per million characters at the time of writing.
+
+
+ Important: Google Translate API v2
+ requires billing information for all accounts before you can start using
+ the service (see Pricing
+ and Terms of Service for more). To identify yourself as a valid
+ user for the Google services, you use your private unique key sent to you
+ by Google, when you have registered for the service. See chapter Installing and Running,
+ section Launch command arguments, for details on how to add this key to
+ the OmegaT environment.
+
+ The quality of the Google Translate translation depends on one side
+ on the reservoir of target-language texts and the availability of their
+ bilingual versions, on the other hand on the quality of the models built.
+ It is pretty much certain that while the quality may be insufficient in
+ some cases, it will definitely get better with time and not worse.
+
+
+
+ <application>OmegaT</application> users and Google
+ Translate
+
+ The OmegaT user is not forced to use
+ Google Translate. If used, neither the user's decision to accept the
+ translation nor the final translation are made available to Google. The
+ following window shows an example of a) the English source b) Spanish and
+ c) Slovenian Google Translate translation.
+
+
+ Google Translate - example
+
+
+
+
+
+
+
+
+
+
+
+
+ The Spanish translation is better than the Slovenian. Note
+ interesar and navegar in
+ Spanish, are correctly translated as the verbs interest and sail
+ respectively. In the Slovenian version both words have been translated as
+ nouns. It is actually quite probable that the Spanish translation is based
+ at least partially on the actual translation of the book.
+
+ Once you have activated the service, a suggestion for the
+ translation will appear in the Machine Translate pane every time a new
+ source segment is opened. If you find the suggestion acceptable, press
+
+
+ Shortcuts
+
+ Ctrl+M - Machine Translate
+ Ctrl
+
+ M
+ to replace the target part of the opened segment with the
+ suggestion. In the above segment, for instance,
+ Ctrl
+
+ M
+ would replace the Spanish version with the Slovenian
+ suggestion.
+
+ If you do not wish OmegaT to send your
+ source segments to Google to get translated, untick the Google Translate
+ menu entry in Options.
+
+ Note that nothing but your source segment is sent to the MT service.
+ The online version of Google Translate allows the user to correct the
+ suggestion and send the corrected segment in. This feature, however, is
+ not implemented in OmegaT.
+
+
+
+ Belazar<indexterm class="singular">
+ <primary>Machine Translation</primary>
+
+ <secondary>Belazar</secondary>
+ </indexterm>
+
+ Belazar is a
+ Machine language translation tool for the Russian-Belarusian language
+ pair.
+
+
+
+ Apertium<indexterm class="singular">
+ <primary>Machine Translation</primary>
+
+ <secondary>Apertium</secondary>
+ </indexterm>
+
+ Apertium is a
+ free/open-source machine translation platform, initially aimed at
+ related-language pairs, like CA, ES, GA, PT, OC and FR but recently
+ expanded to deal with more divergent language pairs (such as
+ English-Catalan). Check the web site for the latest list of implemented
+ language pairs.
+
+ The platform provides
+
+
+
+ a language-independent machine translation engine
+
+
+
+ tools to manage the linguistic data necessary to build a machine
+ translation system for a given language pair and
+
+
+
+
+
+ linguistic data for a growing number of language pairs
+
+
+
+ Apertium uses a shallow-transfer machine translation engine which
+ processes the input text in stages, as in an assembly line: de-formatting,
+ morphological analysis, part-of-speech disambiguation, shallow structural
+ transfer, lexical transfer, morphological generation, and
+ re-formatting.
+
+ It is possible to use Apertium to build machine translation systems
+ for a variety of language pairs; to that end, Apertium uses simple
+ XML-based standard formats to encode the linguistic data needed (either by
+ hand or by converting existing data), which are compiled using the
+ provided tools into the high-speed formats used by the engine.
+
+
+
+ Machine translation - trouble shooting<indexterm class="singular">
+ <primary>Machine Translation</primary>
+
+ <secondary>Troubleshooting</secondary>
+ </indexterm>
+
+ If there's nothing appearing in the Machine Translate pane, then
+ check the following:
+
+
+
+ Are you online? You need to be online to be able to use an MT
+ tool.
+
+
+
+
+
+ What is the language pair you need? Check if the selected
+ service offers it.
+
+
+
+ Google Translate does not work: check Options > Machine
+ Translate: the Google Translate service is labelled Google Translate
+ V2. The older version of the service, labelled "Google Translate" and
+ available in outdated OmegaT versions, is deprecated and does not work
+ anymore.
+
+
+
+ "Google Translate returned HTTP response code: 403 ...": check
+ that the 38-characters key, entered in the pinfo.list file, is
+ correct. Check that Translate API
+ service has been activated.
+
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Menu.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Menu.xml
new file mode 100644
index 0000000..09c5b6d
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Menu.xml
@@ -0,0 +1,1509 @@
+
+
+
+ Menu and Keyboard shortcuts
+
+
+ <indexterm class="singular">
+ <primary>Main menu</primary>
+ </indexterm>Main Menu
+
+
+ Shortcuts
+
+ Main menu
+
+
+ All of OmegaT's functions are available through the menu bar at the
+ top of the Editor window. Most functions are also available via keyboard
+ shortcuts. Shortcuts are activated by pressing Ctrl and a
+ letter. Some shortcuts involve other keys. For readability purposes,
+ letters are written in uppercase here. Ctrl is used on
+ Windows, UNIX and UNIX-like operating systems with keyboards featuring a
+ Ctrl or Control key. Mac users should
+ instead use
+ Cmd
+
+ key
+ instead. The "Cmd" key either has a "command" label or an
+ apple symbol on Apple keyboards.
+
+ You can customize existing shortcuts or add new ones according to
+ your needs. See Appendix -
+ Shortcuts Customization
+
+
+ Main Menu
+
+
+
+
+ Project
+
+ Edit
+
+ Go to
+
+ View
+
+ Tools
+
+ Options
+
+ Help
+
+
+
+
+ Project menu
+
+
+
+
+
+
+
+
+ New
+
+
+
+ Creates and opens a new project. The dialog to create a
+ project is the same as to edit the project. See
+
+
+
+ Open
+
+
+ Ctrl
+
+ O
+
+
+ Opens a previously created project.
+
+
+
+ Import Source Files...
+
+
+
+ Copies the selected files to the
+ source folder and reloads the project to
+ load the new files.
+
+
+
+ Import From
+ MediaWiki...
+
+
+
+ Imports units from MediaWiki pages, based on the URL
+ entered.
+
+
+
+ Reload
+
+ F5
+
+ Reloads the project to take external changes in source
+ files, legacy translation memories, glossaries and project
+ settings into account.
+
+
+
+ Close
+
+
+ Ctrl
+
+ Shift
+
+ W
+
+
+ Saves the translation and closes the project.
+
+
+
+ Save
+
+
+ Ctrl
+
+ S
+
+
+ Saves the internal translation memory to the hard disk.
+ OmegaT automatically saves translations every 10 minutes as well
+ as when you close the project or quit OmegaT.
+
+
+
+ Create translated
+ documents
+
+
+ Ctrl
+
+ D
+
+
+ Creates the target documents based on your translation of
+ the documents' text. The created target documents are located in
+ the target folder.
+
+
+
+ Properties...
+
+
+ Ctrl
+
+ E
+
+
+ Displays Project properties
+ dialog to edit project languages and folder locations.
+
+
+
+ Project Files...
+
+
+ Ctrl
+
+ L
+
+
+ Closes or opens the Project files window
+ (depending on whether it is open or closed).
+
+
+
+ Quit
+
+
+ Ctrl
+
+ Q
+
+
+ Saves the project and quits
+ OmegaT. If you haven't yet saved the
+ project, this manually confirms whether you really wish to
+ quit.
+
+
+
+
+
+
+
+ Edit<indexterm class="singular">
+ <primary>Main menu</primary>
+
+ <secondary>Edit</secondary>
+ </indexterm>
+
+ Note: Items that are found in most applications (copy/cut/paste)
+ are not displayed in this menu, but are available using your system
+ shortcuts. For example:
+
+
+ Copy/cut/paste shortcuts
+
+
+
+
+
+
+
+
+ Copy
+
+
+ Ctrl
+
+ C
+
+
+ Copies the selected text to the clipboard.
+
+
+
+ Cut
+
+
+ Ctrl
+
+ X
+
+
+ Copies the selected text to the clipboard and deletes the
+ selected text.
+
+
+
+ Paste
+
+
+ Ctrl
+
+ V
+
+
+ Pastes the text from the clipboard at the cursor
+ position.
+
+
+
+
+
+ The Edit menu itself contains the following items:
+
+
+ Edit menu
+
+
+
+
+
+
+
+
+ Undo Last Action
+
+
+ Ctrl
+
+ Z
+
+
+ Restores the status before the last editing action was
+ taken. This command does not work once the modified segment has
+ been validated.
+
+
+
+ Redo Last Action
+
+
+ Ctrl
+
+ Y
+
+
+ Restores the status before the last editing action was
+ cancelled. This command does not work once the modified segment
+ has been validated.
+
+
+
+ Replace With Match
+
+
+ Ctrl
+
+ R
+
+
+ Replaces the whole target segment with the currently
+ selected fuzzy match (by default the first match is
+ selected).
+
+
+
+ Insert Match
+
+
+ Ctrl
+
+ I
+
+
+ Inserts the currently selected fuzzy match at the cursor
+ position. If part of the target segment has been selected, this
+ function overwrites the selected portion.
+
+
+
+ Replace with Machine
+ Translation
+
+
+ Ctrl
+
+ M
+
+
+ Replaces the target segment with the translation,
+ provided by the selected Machine Translation service. No action
+ is taken, if no Machine Translation service has been activated
+ (see Menu > Options below).
+
+
+
+ Replace With Source
+
+
+ Shift
+
+ Ctrl
+
+ R
+
+
+ Replaces the whole target segment with the
+ source.
+
+
+
+ Insert Source
+
+
+ Shift
+
+ Ctrl
+
+ I
+
+
+ Inserts the source at the cursor position.
+
+
+
+ Insert Source Tags
+
+
+ Shift
+
+ Ctrl
+
+ T
+
+
+
+ Tags
+
+ Inserting source tags
+ Inserts the source tags at the cursor position.
+ All the relevant tags in the source - i.e. OmegaT as well as
+ custom, Java, printf etc tags - will be inserted into the
+ current target, regardless of whether they are already there or
+ not. Texts, bracketed by tags, are replaced by spaces:.
+ <f0><f1>This is
+ text</f0></f1> thus will be copied as
+ <f0><f1>one_space</f0></f1>
+
+
+
+ Export Selection
+
+
+ Shift
+
+ Ctrl
+
+ C
+
+
+ Exports the current selection to a text file for
+ processing. If no text has been selected, the current source
+ segment is written to this file. When the user exits
+ OmegaT, this file is not emptied, in
+ order to be consistent with usual clipboard behavior. The
+ exported contents are copied to the file
+ selection.txt located in the User's
+ preference files folder (see ).
+
+
+
+ Create Glossary Entry
+
+
+ Shift
+
+ Ctrl
+
+ G
+
+
+ Allows the user create an entry in the default glossary
+ file.
+
+
+
+ Search Project...
+
+
+ Ctrl
+
+ F
+
+
+ Opens a new Search
+ window.
+
+
+
+ Switch case to...
+
+
+ Shift
+
+ F3
+ (see text)
+
+ Changes the case of the highlighted text in the target
+ segment to the selected option (Lower case, Upper case or Title
+ case). Use Shift+F3
+ Shortcuts
+
+ Shift+F3 - Case selection
+ to cycle through the three alternatives. If no
+ text is selected, OmegaT selects the
+ word that contains the letter immediately to the right of the
+ cursor.
+
+
+
+ Select Fuzzy Match #N
+
+
+ Ctrl
+
+ #N
+
+
+ (#N is a digit from 1 to 5) - Selects the Nth fuzzy match
+ displayed in the match viewer to replace or insert it to the
+ segment. The describes the color
+ coding in detail.
+
+
+
+ Use as Default
+ Translation
+
+
+
+ If there's several alternative translations available
+ active segment, you can label the alternative selected as the
+ default translation. The entry will be greyed, if there's just
+ one translation available.
+
+
+
+ Create Alternative
+ Translation
+
+
+
+ The one and the same segment may, depending on the
+ context, require different translations. Select this menu item,
+ if the current translation does not apply and enter the
+ alternative translation.
+
+
+
+
+ Go To menu
+
+
+
+
+
+
+
+
+ Next Untranslated
+ Segment
+
+
+ Ctrl
+
+ U
+
+
+ Moves to the next segment that has no equivalent in the
+ translation memory.
+
+
+
+ Next Segment
+
+
+ Ctrl
+
+ N
+ or Enter or
+ Tab
+
+ Moves to the next segment. If the current segment is the
+ last segment in a file, it moves to the first segment of the
+ next file.
+
+
+
+ Previous Segment
+
+
+ Ctrl
+
+ P
+ or
+ Ctrl
+
+ Enter
+ or
+ Ctrl
+
+ Tab
+
+
+ Moves to the previous segment. If the current segment is
+ the first one in a file, it moves to the last segment of the
+ previous file.
+
+
+
+ Segment number...
+
+
+ Ctrl
+
+ J
+
+
+ The segment is opened when its segment number is
+ entered..
+
+
+
+ Next Note
+
+
+
+ The next segment with a note attached to it, will
+ open.
+
+
+
+ Previous Note
+
+
+
+ The previous segment with a note will open.
+
+
+
+ Forward in history...
+
+
+ Ctrl
+
+ Shift
+
+ N
+
+
+ OmegaT remembers the segments
+ executed. With this command you can step forward to the segment,
+ you have previously left by the Back in
+ history...command.
+
+
+
+ Back in history...
+
+
+ Ctrl
+
+ Shift
+
+ P
+
+
+ With this command you can move backward one segment at a
+ time, to return later to the current segment using
+ Forward in history... command
+ below.
+
+
+
+
+ View menu
+
+
+
+
+
+
+ Mark Translated
+ Segments
+
+ If checked, the translated segments will be marked in
+ yellow.
+
+
+
+ Mark Untranslated
+ Segments
+
+ If checked, the untranslated segments will be marked in
+ violet.
+
+
+
+ Display Source
+ Segments
+
+ If checked, source segments will be shown and marked in
+ green. If not checked, source segments will not be
+ shown.
+
+
+
+ Mark Non-Unique
+ Segments
+
+ If checked, non-unique segments will be marked in pale
+ grey.
+
+
+
+ Mark Segments with
+ Notes
+
+ If checked, segments with notes will be marked in cyan.
+ This marking has priority over Mark Translated Segments and Mark
+ Untranslated Segments.
+
+
+
+ Mark Non-breakable
+ Spaces
+
+ If checked, non-breakable spaces in the segment will be
+ displayed with a grey background.
+
+
+
+ Modification Info
+
+ Setting the Display Modification option to
+ Selected will display the time and the
+ author of the last change in the current segment. Setting it
+ to All shows this information for all
+ segments and None turns this option
+ off.
+
+
+
+
+ Tools menu
+
+
+ Matches
+
+ Matches statistics
+
+
+
+ Project
+
+ Match statistics
+
+
+
+ Project
+
+ Statistics
+
+
+
+
+
+
+
+ Validate Tags
+
+ Ctrl+T: Checks for missing or
+ displaced tags in formatted files. Will display a list of
+ segments with tag errors and possible inconsistencies. See Tag Validation and .
+
+
+
+ Remove Tags
+
+ When enabled, all the formatting tags are removed from
+ source segments. This is useful when dealing with texts where
+ inline formatting has no real use (e.g., OCRed PDF, bad
+ converted .odt or .docx, etc.) Only inline tags are removed, so
+ normally there should be no problem with opening the target
+ documents. Non-visible formatting (i.e., which doesn't appear as
+ tags in the OmegaT editor) is kept in the target
+ document.
+
+
+
+ Statistics
+
+ Opens a new window and displays the project statistics,
+ i.e. the project totals and totals for every file in the
+ project.
+
+
+
+ Match Statistics
+
+ Displays the Match Statistics for the project: the number
+ of repetitions, exact matches, fuzzy matches and no-matches, for
+ segments, words and in characters.
+
+
+
+
+ Options menu
+
+
+
+
+
+
+ Use TAB To Advance
+
+ Sets segment validation key to
+ Tab instead of the default
+ Enter. This option is useful for some
+ Chinese, Japanese or Korean character input systems.
+
+
+
+ Always Confirm Quit
+
+ The program will see confirmation before closing
+ down.
+
+
+
+ Machine Translate
+
+ Allows you to activate/deactivate the Machine Translation
+ tools offered. When active,
+ Ctrl
+
+ M
+ will insert the suggestion into the target part of
+ the current segment.
+
+
+
+ Glossary
+
+ reserved for future use by plugins
+
+
+
+ TransTips
+
+ Allows you to activate/deactivate TransTips
+ feature and set its option Exact
+ Match. With TransTips activated
+ a right click on a highlighted word in the source will open a
+ popup menu with the glossary entries for the word you clicked.
+ You can then click on the preferred translation to insert it
+ into the target segment at the current position. With
+ TransTips/Exact Match checked, only
+ complete words will be checked, otherwise parts of words will be
+ matched as well.
+
+
+
+ Font...
+
+ Shows the dialogue to modify the text display font. Users
+ of old computers who feel window resizing is very slow can try
+ changing the font. See font settings in Miscellanea
+
+
+
+ File Filters...
+
+ Displays the File
+ filters dialogue to configure file handling and
+ parsing.
+
+
+
+ Segmentation...
+
+ Opens the Source
+ segmentation dialogue to configure text
+ segmentation.
+
+
+
+ Spell checking...
+
+ Displays the Spell
+ checker setup window to install, configure and activate
+ the spell checker.
+
+
+
+ Editing Behavior...
+
+ Displays the Translation editing
+ dialog to configure.
+
+
+
+ Tag Validation...
+
+ For programmers: Allows you to configure the Tag
+ Validator options to also check programming (%...)
+ variables.
+
+
+
+ Team...
+
+ Enter your name here and it will be attached to all
+ segments translated by you.
+
+
+
+ External TMXs...
+
+ Allows the user decide, how tags in foreign TMX files
+ (i.e. not generated by OmegaT) are to be treated.
+
+
+
+ View...
+
+ Contains the option to have all source segments in bold
+ and to mark the first non-unique segment.
+
+
+
+ Proxy login...
+
+ Enter your user name and your password, if you use a
+ proxy to access your projects.
+
+
+
+ Restore Main Window
+
+ Restores the components of the main OmegaT window to
+ their default state. Use this feature when you have undocked,
+ moved, or hidden one or more components and you are unable to
+ restore the desired arrangement. It can also be used when panes
+ do not appear as expected following an OmegaT upgrade.
+
+
+
+
+ Help menu
+
+
+
+
+
+
+ User Manual...
+
+ F1: Opens Help browser displaying this
+ manual in a separate window.
+
+
+
+ About...
+
+ Displays copyright, credits and license
+ information.
+
+
+
+
+
+
+
+
+ Keyboard shortcuts<indexterm class="singular">
+ <primary>Keyboard shortcuts</primary>
+ </indexterm>
+
+ The following shortcuts are available from the main window. When
+ another window is on the foreground, click on the main window to bring it
+ to the foreground or press Esc to close the other
+ window.
+
+ Shortcuts are activated by pressing Ctrl and a
+ letter. Some shortcuts involve other keys. For readability purposes,
+ letters are written in uppercase here.
+
+ Ctrl is used on Windows, UNIX and UNIX-like operating systems with
+ keyboards featuring a Ctrl / Control
+ key. Mac users should instead use the
+ cmd+key. On Apple keyboards the
+ cmd key either has a command label or an Apple
+ icon on it.
+
+
+
+ Project management
+
+
+
+
+
+ Editing
+
+
+
+
+
+ Moving around
+
+
+
+
+
+ Reference windows
+
+
+
+
+
+ Other
+
+
+
+
+ <indexterm class="singular">
+ <primary>Keyboard shortcuts</primary>
+
+ <secondary>Project</secondary>
+ </indexterm>Project management<indexterm class="singular">
+ <primary>Project</primary>
+
+ <secondary>Project management shortcuts</secondary>
+ </indexterm>
+
+
+ Project management shortcuts
+
+
+
+
+
+
+
+
+ Open project
+
+
+ Ctrl
+
+ O
+
+
+ Displays a dialogue to locate an existing
+ project.
+
+
+
+ Save
+
+
+ Ctrl
+
+ S
+
+
+ Saves the current work to the internal translation memory
+ (file project_save.tmx located in the project's
+ omegat folder).
+
+
+
+ Close Project
+
+
+ Shift
+
+ Ctrl
+
+ W
+
+
+ Closes the current project.
+
+
+
+ Create Translated Documents
+
+
+ Ctrl
+
+ D
+
+
+ Creates the translated documents in the project's Target
+ folder and creates translation memory files (level1, level2 and
+ omegat tmx files) in the project's root folder.
+
+
+
+ Project properties
+
+
+ Ctrl
+
+ E
+
+
+ Displays the project's settings for modification, if
+ required.
+
+
+
+
+ Editing shortcuts
+
+
+
+
+
+
+
+
+ Undo last action
+
+
+ Ctrl
+
+ Z
+
+
+ Undoes the last editing actions in the current target
+ segment
+
+
+
+ Redo last action
+
+
+ Ctrl
+
+ Y
+
+
+ Redoes the last editing actions in the current target
+ segment
+
+
+
+ Select match #N
+
+
+ Ctrl
+
+ #N
+
+
+ #N is a digit from 1 to 5. The shortcut selects the Nth
+ match displayed in the match window (the first match is selected
+ by default)
+
+
+
+ Replace with match
+
+
+ Ctrl
+
+ R
+
+
+ Replaces the current target segment contents with the
+ selected match (the first match is selected by default)
+
+
+
+ Insert match
+
+
+ Ctrl
+
+ I
+
+
+ Inserts the selected match at the cursor position in the
+ current target segment (the first match is inserted by
+ default)
+
+
+
+ Replace with source
+
+
+ Ctrl
+
+ Shift+R
+
+
+ Replaces the current target segment contents with the
+ source text contents
+
+
+
+ Insert source
+
+
+ Ctrl
+
+ Shift+I
+
+
+ Inserts the source text contents into the target segment
+ at the cursor position
+
+
+
+ Insert Source Tags
+
+
+ Ctrl
+
+ Shift+T
+
+
+ Inserts the source tags into the target segment at the
+ cursor position
+
+
+
+ Search project
+
+
+ Ctrl
+
+ F
+
+
+ Displays a dialogue to conduct searches in the
+ project
+
+
+
+ Replace with Machine Translation
+
+
+ Ctrl
+
+ M
+
+
+ Replaces the target segment with the machine translation
+ of the source. No action, if machine tools are deactivated (see
+ Menu > Options > Machine Translate)
+
+
+
+ Export Selection
+
+
+ Shift
+
+ Ctrl
+
+ C
+
+
+ Exports the current selection to a text file for
+ processing.
+
+
+
+ Create Glossary Entry
+
+
+ Shift
+
+ Ctrl
+
+ G
+
+
+ Allows the user create an entry in the default glossary
+ file.
+
+
+
+
+ Moving around shortcuts
+
+
+
+
+
+
+
+
+ Next Untranslated Segment
+
+
+ Ctrl
+
+ U
+
+
+ Moves the editing field to the next segment that is not
+ registered in the project's translation memory
+
+
+
+ Next Segment
+
+
+ Ctrl
+
+ N
+ , Enter or
+ Return
+
+ Moves the editing field to the next segment.
+
+
+
+ Previous Segment
+
+
+ Ctrl
+
+ P
+
+
+ Moves the editing field to the previous segment
+
+
+
+ Segment number...
+
+
+ Ctrl
+
+ J
+
+
+ Moves to the segment number entered
+
+
+
+ Back in history...
+
+
+ Ctrl
+
+ Shift+P
+
+
+ Moves one segment back in history
+
+
+
+ Forward in history...
+
+
+ Ctrl
+
+ Shift+N
+
+
+ Moves one segment forward in history
+
+
+
+
+ Various shortcuts
+
+
+
+
+
+
+
+
+ Project files listing
+
+
+ Ctrl
+
+ L
+
+
+ Displays the Project files listing
+
+
+
+ Validate Tags
+
+
+ Ctrl
+
+ T
+
+
+ Opens the Tag validation window.
+
+
+
+ Export Selection
+
+
+ Shift
+
+ Ctrl+C
+
+
+ Exports the current selection or the current source, if
+ no text has been selected. The text is exported to a plain text
+ file.
+
+
+
+ Search Project
+
+
+ Ctrl
+
+ F
+
+
+ Opens a new Search window.
+
+
+
+ Help files
+
+ F1
+
+ Displays the OmegaT help files
+ in a separate window
+
+
+
+
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Miscelanea.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Miscelanea.xml
new file mode 100644
index 0000000..43d3ed9
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Miscelanea.xml
@@ -0,0 +1,334 @@
+
+
+
+ Miscellaneous subjects<indexterm class="singular">
+ <primary>Miscellanea</primary>
+ </indexterm>
+
+
+ <application><indexterm class="singular">
+ <primary>OmegaT console mode</primary>
+
+ <seealso>Miscellanea</seealso>
+ </indexterm>OmegaT</application> Console Mode<indexterm class="singular">
+ <primary>Miscellanea</primary>
+
+ <secondary>OmegaT console mode</secondary>
+ </indexterm>
+
+
+ Of interest for advanced users only!
+
+
+ The purpose of the console (i.e. command line) mode is to permit the
+ use of OmegaT as translation tool in a
+ scripting environment. When launched in console mode, no GUI is loaded (
+ it will work therefore on any console) and the given project is
+ automatically translated. An example would be a software project, with GUI
+ localized in a number of languages. Using the console mode, one can make
+ generating a localized interface a part of the build process.
+
+
+ Prerequisites
+
+ To run OmegaT, a valid OmegaT project must be available. The
+ location is irrelevant, since it must be specified explicitly on the
+ command-line at launch..
+
+ If you need non-standard settings, the corresponding configuration
+ files (filters.conf and
+ segmentation.conf) must be present. This can be
+ achieved in two ways:
+
+
+
+ Run OmegaT normally (with the GUI)
+ and set the settings. If you start OmegaT
+ in console mode, it will use the settings you configured.
+
+
+
+ If you are unable to run OmegaT
+ normally (no graphical environment available): copy the settings
+ files from some other OmegaT installation
+ on another machine to a specific directory. The location does not
+ matter, since you can add it to the command line at launch (see
+ below). The relevant files filters.conf and
+ segmentation.conf can be found in the user home
+ directory (E.g. C:\Documents and
+ Settings\%User%\OmegaT under
+ Windows, %user%/.omegat/ under Linux)
+
+
+
+
+
+ Launching OmegaT in console mode
+
+ To launch OmegaT in console mode, additional parameters must be
+ specified at launch. The most important of these is
+ <project-dir>, and
+ optionally--config-dir=<config-dir>.
+ Example:
+
+ $> java -jar OmegaT.jar
+ /path/to/project \
+
+ --config-dir=/path/to/config-files/ \
+
+ --mode=console-translate \
+
+ --source-pattern={regexp} \
+
+ --tag-validation=[block|warn]
+
+ Explanation:
+
+
+
+ <project-dir> tells
+ OmegaT where to find the project to be
+ translated. If given, OmegaT launches in
+ console mode and translates the given project.
+
+
+
+
+
+ --config-dir=<config-dir> enables
+ OmegaT to be instructed in which folder the configuration files are
+ stored. If not specified, OmegaT reverts to default values (the
+ OmegaT folder in the user home folder, or if not available: the
+ current working directory).
+
+
+
+
+
+ --mode=console-translate
+ OmegaT launches in console mode and
+ translates the given project
+
+
+
+ --source-pattern={regexp} The files to be
+ translated can be specified this way. Here is an example of the
+ regular expression: test\.html
+
+
+
+ --tag-validation=[abort|warn] On abort,
+ the program is aborted when tag validation finds errors. On warn the
+ errors are printed but the program continues. In all other cases no
+ tag validation is done.
+
+
+
+
+
+ Quiet option
+
+ An extra command line parameter specific to console mode:
+ --quiet. In the quiet mode, less info is logged to
+ the screen. The messages you would usually find in the status bar are
+ not displayed.
+
+ Usage: java -jar OmegaT.jar
+ /path/to/project --mode=console-translate --quiet
+
+
+
+ Tag validation option
+
+ Another extra command line parameter specific to console mode:
+ --tag-validation=[abort|warn]. When this parameter is
+ added, tag validation is done prior to translation/aligning. If the
+ value is abort, then on tag errors the errors are
+ printed and the program stops. If the value is warn
+ then the errors are printed but OmegaT continues.
+
+ Usage: java -jar OmegaT.jar
+ /path/to/project --mode=console-translate
+ --tag-validation=abort
+
+
+
+
+ Automatic Java Properties Aligner<indexterm class="singular">
+ <primary>Miscellanea</primary>
+
+ <secondary>Automatic aligner for Java properties</secondary>
+
+ <seealso>Miscelanea</seealso>
+ </indexterm>
+
+ OmegaT can align Java .properties in console mode. If you have the
+ source and the target Properties files for one and the same contents in
+ your language pair, this procedure will create a corresponding tmx file
+ for these contents. Usage:
+
+ java -jar OmegaT.jar --mode=console-align /my-project-dir
+ --alignDir=/translatedFiles/
+
+ alignDir must contain a translation in the
+ target language of the project. E.g., if the project is EN->FR,
+ alignDir must contain a bundle ending with _fr. The resulting tmx is
+ stored in the omegat folder under the name
+ align.tmx.
+
+
+
+ Font settings<indexterm class="singular">
+ <primary>Miscellanea</primary>
+
+ <secondary>Font settings</secondary>
+ </indexterm>
+
+ In this dialog one can define the font used by
+ OmegaT in the following windows:
+
+
+
+ OmegaT main window (Editor, Match
+ viewer, Glossary viewer)
+
+
+
+
+
+ Search window
+
+
+
+
+
+ Tag validation window
+
+
+
+ The dialog can be accessed via the
+ Menu Options
+
+ Font...
+
+ Options
+
+ Font...
+ item in the Main menu. The dialog contains:
+
+
+
+ Font: drop-down to select one
+ of the fonts available on your machine
+
+
+
+
+
+ Size: edit to change font
+ size
+
+
+
+
+
+ Sample text: field for
+ immediate preview of the selected font
+
+
+
+ Note: In some cases it may take
+ quite some time for OmegaT to update the display after the font setting
+ has been changed. This is especially the case when a large file containing
+ many segments is open in the editor, and/or slow hardware is used. Note
+ also that some fonts behave better for some language pairs than for
+ others. In particular, if you are translating between two languages with
+ different alphabets/writing systems (such as Russian and Japanese), select
+ a font that can be used for both.
+
+
+
+ Preventing data loss<indexterm class="singular">
+ <primary>Miscellanea</primary>
+
+ <secondary>Preventing data Loss</secondary>
+ </indexterm>
+
+ OmegaT is a robust application. However,
+ you should take precautions against data loss when using
+ OmegaT, just as with any other application.
+ When you translate your files, OmegaT stores
+ all your progress in the translation memory
+ project_save.tmx that resides in the project's
+ /omegat subfolder.
+
+ OmegaT also backs up the translation memory to
+ project_save.tmx.YEARMMDDHHNN.bak in the same subfolder each time a
+ project is opened or reloaded. YEAR is the 4-digit year, MM is the month,
+ DD the day of the month, and HH and NN are the hours and minutes when the
+ previous translation memory was saved.
+
+ If you believe that you have lost translation data, you can use the
+ following procedure to restore the project to its most recently saved
+ state, usually not older than approximately 10 minutes or so:
+
+
+
+ close the project
+
+
+
+ rename the current project_save.tmx file
+ (e.g. to project_save.tmx.temporary)
+
+
+
+ select the backup translation memory that is the most likely to
+ contain the data you are looking for
+
+
+
+ rename it project_save.tmx
+
+
+
+ open the project
+
+
+
+ To avoid losing important data:
+
+
+
+ Make regular copies of the file /omegat/project_save.tmx to
+ backup media, such as CD or DVD.
+
+
+
+ Until you are familiar with OmegaT,
+ create translated files at regular intervals and check that the
+ translated file contains the latest version of your
+ translation.
+
+
+
+ Take particular care when making changes to the files in
+ /source while in the middle of a project. If the
+ source file is modified after you have begun translating,
+ OmegaT may be unable to find a segment that
+ you have already translated.
+
+
+
+
+
+ Use these Help texts to get started. Should you run into
+ problems, post a message in the OmegaT
+ user group. Do not hesitate to post in the language you feel
+ the most familiar with.
+
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/OmegaT.css b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/OmegaT.css
new file mode 100644
index 0000000..1893c29
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/OmegaT.css
@@ -0,0 +1,78 @@
+body {
+ font-family: sans-serif;
+ margin: 1em;
+}
+
+h1, h2, table, dt {
+ color: navy;
+}
+
+h3, h4, ul a {
+ color: green;
+}
+
+code, .code {
+ color: black;
+ background: #ffffcc;
+ border-style: solid;
+ border-width: 1px;
+ border-color: #ffff66;
+ vertical-align: top;
+}
+
+.new {
+ font-size: x-small;
+ color: red;
+ background: yellow;
+}
+
+.updated {
+ font-size: x-small;
+ color: orange;
+}
+
+.note {
+ font-size: small;
+ color: black;
+ background: silver;
+}
+
+.warning {
+ color: red;
+ background: yellow;
+}
+
+.chapter {
+ color: black;
+}
+
+.navbar-top, .navbar-bottom {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.rel-p {
+ width: 9%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.rel-n {
+ width: 6%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.nav-link {
+ width: 39%;
+ align: left;
+ valign: center;
+}
+
+.toc-link {
+ width: 7%;
+ align: left;
+ valign: center;
+}
\ No newline at end of file
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/OmegaTUsersManual_xinclude full.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/OmegaTUsersManual_xinclude full.xml
new file mode 100644
index 0000000..e9d7a5d
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/OmegaTUsersManual_xinclude full.xml
@@ -0,0 +1,97 @@
+
+
+
+
+ OmegaT - User's Guide
+
+ vs
+ Vito
+Smolej
+
+
+
+
+
+ This document is the official user's guide to OmegaT, the free Computer Aided Translation tool. It also contains installation instructions.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/PlainText.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/PlainText.xml
new file mode 100644
index 0000000..44c0b60
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/PlainText.xml
@@ -0,0 +1,178 @@
+
+
+
+ Working with plain text<indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Plain text files</secondary>
+ </indexterm>
+
+
+ Default encoding<indexterm class="singular">
+ <primary>Default encoding</primary>
+
+ <secondary>Plain text files</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Default encoding</secondary>
+ </indexterm>
+
+ Plain text files - in most cases files with a txt extension -
+ contain just textual information and offer no clearly defined way to
+ inform the computer which language they contain. The most that OmegaT can
+ do in such a case, is to assume that the text is written in the same
+ language the computer itself uses. This is no problem for files encoded in
+ Unicode using a 16 bit character encoding set. If the text is encoded in 8
+ bits, however, one can be faced with the following awkward situation:
+ instead of displaying the text, for Japanese characters...
+
+
+
+
+
+
+
+
+
+
+
+ ...the system will display it like this for instance:
+
+
+
+
+
+
+
+
+
+
+
+ The computer, running OmegaT, has Russian as the default language,
+ and thus shows the characters in the Cyrillic alphabet and not in
+ Kanji.
+
+
+
+ The <application>OmegaT</application> solution<indexterm
+ class="singular">
+ <primary>Default encoding</primary>
+
+ <secondary>OmegaT solution</secondary>
+ </indexterm>
+
+ There are basically three ways to address this problem in
+ OmegaT. They all involve the application of
+ file filters in the Options menu.
+
+
+
+ Change the encoding of your files to Unicode
+
+
+ open your source file in a text editor that correctly
+ interprets its encoding and save the file in "UTF-8" encoding. Change the file extension
+ from .txt to
+ .utf8.OmegaT will
+ automatically interpret the file as a UTF-8 file. This is the most
+ common-sense alternative, sparing you problems in the long
+ run.
+
+
+
+
+
+
+ Specify the encoding for your plain text files
+
+
+ - i.e. files with a .txt extension - : in
+ the Text files section of the file
+ filters dialog, change the Source File
+ Encoding from <auto> to the encoding that
+ corresponds to your source .txt file, for
+ instance to .jp for the above example.
+
+
+
+
+
+
+ Change the extensions of your plain text source files
+
+
+ for instance from .txt to
+ .jp for Japanese plain texts: in the Text files section of the file filters
+ dialog, add new Source Filename
+ Pattern (*.jp for this example) and
+ select the appropriate parameters for the source and target
+ encoding
+
+
+
+
+ OmegaT has by default the following short
+ list available to make it easier for you to deal with some plain text
+ files:
+
+
+
+ .txt files are automatically (<auto>)
+ interpreted by OmegaT as being encoded in
+ the computer's default encoding.
+
+
+
+
+
+ .txt1 files are files in ISO-8859-1, covering
+ most Western Europe
+ languages.
+ Default encoding
+
+ Western
+
+
+
+
+
+
+ .txt2 files are files in ISO-8859-2, that
+ covers most Central and Eastern
+ Europe languages
+ Default encoding
+
+ Central and Eastern European
+
+
+
+
+
+
+ .utf8 files are interpreted by
+ OmegaT as being encoded in UTF-8 (an
+ encoding that covers almost all languages in the world).
+ Default encoding
+
+ Unicode
+
+
+
+
+ You can check that yourself by selecting the item File Filters in the menu Options. For example, when you have a Czech text
+ file (very probably written in the ISO-8859-2 code) you just need to change the
+ extension .txt to .txt2 and
+ OmegaT will interpret its contents correctly.
+ And of course, if you wish to be on the safe side, consider converting
+ this kind of file to Unicode, i.e. to the .utf8 file
+ format.
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/ProjectProperties.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/ProjectProperties.xml
new file mode 100644
index 0000000..7c3065d
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/ProjectProperties.xml
@@ -0,0 +1,173 @@
+
+
+
+ Project properties<indexterm class="singular">
+ <primary>Project</primary>
+
+ <secondary>Properties</secondary>
+ </indexterm>
+
+
+
+
+ Properties dialog
+
+ The
+
+
+ Ctrl
+
+ E
+
+
+
+ Project
+
+ Properties...
+ dialog is used to define and modify the project folders
+ and languages.
+
+ It is possible to modify the project properties during a translation
+ session. Note that changes to the project setup may have some
+ consequences, especially, when the project has already been started. Until
+ you have some experience with OmegaT, it is safest to consider all
+ settings final once the translation has started – unless of course you
+ realize a major mistake has been made. See the section Preventing data
+ loss for ways and means of protecting your work.
+
+
+ Project properties window
+
+
+
+
+
+
+
+
+
+
+
+
+ It contains:
+
+
+
+ An area for setting project source and target languages with
+ drop-down menus
+
+ You can either enter the source and target languages by hand or
+ use the drop down menu. Bear in mind that changing the languages may
+ render the currently used translation memories useless since their
+ language pair may not longer match the new languages.
+
+
+
+
+
+ the Enable Sentence-level segmentation
+ check box
+
+
+ Project
+
+ Enable Sentence-level segmentation
+
+
+ The segmentation settings only address the way the source files
+ are handled by OmegaT. The predominant way
+ of segmenting the sources is the sentence-level segmenting, so this
+ check box should in a normal case be left checked.
+
+ In some seldom cases the alternative, i.e. segmenting by
+ paragraphs, may be preferred. Changing this flag does not modify the
+ segmentation of already existing translation memories. If you decide
+ mid-translation to switch from sentence to paragraph translation, the
+ internal translation memory of the project will not be changed (OmegaT
+ may upgrade old translation memories that did not use sentence
+ segmentation, but not vice versa).
+
+ Changing segmentation settings may cause some already translated
+ segments to be split or merged. This will effectively return them to
+ the "untranslated" status, as they will no longer match segments
+ recorded in the project memory, even though their original translation
+ is still there.
+
+
+
+
+
+ Segmentation... button
+ Segmentation
+
+ global vs project rules
+
+
+ The segmentation rules are generally valid across all the
+ projects. The user, however, may need to generate a set of rules,
+ specific to the project in question. Use this button to open a
+ dialog,activate the check box Project specific
+ segmentation rules, then proceed to adjust the
+ segmentation rules as desired . The new set of rules will be stored
+ together with the project and will not interfere with the general set
+ of segmentation rules. To delete project specific Segmentation rules,
+ uncheck the check box. See chapter Source Segmentation for more
+ information on segmentation rules.
+
+ Hint: the set of segmentation rules for a
+ given project is stored as
+ project/omegat/segmentation.conf.
+
+
+
+ File Filters... button
+ File Filters
+
+ global vs project file filters
+
+
+ In a similar fashion as above the user can create
+ project-specific File filters, which will be stored together with the
+ project and will be valid for the current project only. To create a
+ project-specific set of file filters, click on the File
+ filter ... button, then activate Enable
+ project specific filters check box in the window, that
+ opens. A copy of the changed filters configuration will be stored with
+ the project. To delete project specific file filters, uncheck the
+ check box. Note that in the menu Options->File
+ Filters, the global user filters are changed, not the
+ project filters. See chapter File
+ filters for more on the subject.
+
+ Hint: the set of file filters for a given
+ project is stored as
+ project/omegat/filters.xml.
+
+
+
+
+
+ An area for setting project folders
+ Glossary
+
+ Location of the writable glossary file
+
+
+
+ Project
+
+ Changing the folder structure
+
+
+ if you enter names of folders that do not exist yet,
+ OmegaT creates them for you. In case you
+ decide to modify project folders, keep in mind that this will not move
+ the contained files from old folders to the new location.
+
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Regexp.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Regexp.xml
new file mode 100644
index 0000000..38a7f3b
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Regexp.xml
@@ -0,0 +1,610 @@
+
+
+
+ Regular expressions<indexterm class="singular">
+ <primary>Regular expressions</primary>
+
+ <seealso>Segmentation</seealso>
+
+ <seealso>Searching</seealso>
+ </indexterm>
+
+ The regular expressions (or regex for short) used in searches and
+ segmentation rules are those supported by Java. Should you need more
+ specific information, consult the Java
+ Regex documentation. See additional references and examples
+ below.
+
+
+ This chapter is intended for advanced users, who need to define
+ their own variants of segmentation rules or devise more complex and
+ powerful key search items.
+
+
+
+ Regex - Flags
+
+
+
+
+
+
+ The construct
+
+ ... matches the following
+
+
+
+
+
+ (?i)
+
+ Enables case-insensitive matching (by default, the pattern is
+ case-sensitive).
+
+
+
+
+
+
+ Regex - Character
+
+
+
+
+
+
+ The construct
+
+ ... matches the following
+
+
+
+
+
+ x
+
+ The character x, except the following...
+
+
+
+ \uhhhh
+
+ The character with hexadecimal value 0xhhhh
+
+
+
+ \t
+
+ The tab character ('\u0009')
+
+
+
+ \n
+
+ The newline (line feed) character ('\u000A')
+
+
+
+ \r
+
+ The carriage-return character ('\u000D')
+
+
+
+ \f
+
+ The form-feed character ('\u000C')
+
+
+
+ \a
+
+ The alert (bell) character ('\u0007')
+
+
+
+ \e
+
+ The escape character ('\u001B')
+
+
+
+ \cx
+
+ The control character corresponding to x
+
+
+
+ \0n
+
+ The character with octal value 0n (0 <= n <= 7)
+
+
+
+ \0nn
+
+ The character with octal value 0nn (0 <= n <=
+ 7)
+
+
+
+ \0mnn
+
+ The character with octal value 0mnn (0 <= m <= 3, 0
+ <= n <= 7)
+
+
+
+ \xhh
+
+ The character with hexadecimal value 0xhh
+
+
+
+
+
+
+ Regex - Quotation
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ \
+
+ Nothing, but quotes the following character. This is required
+ if you would like to enter any of the meta characters
+ !$()*+.<>?[\]^{|} to match as themselves.
+
+
+
+ \\
+
+ For example, this is the backslash character
+
+
+
+ \Q
+
+ Nothing, but quotes all characters until \E
+
+
+
+ \E
+
+ Nothing, but ends quoting started by \Q
+
+
+
+
+
+
+ Regex - Classes for Unicode blocks and categories
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ \p{InGreek}
+
+ A character in the Greek block (simple
+ block)
+
+
+
+ \p{Lu}
+
+ An uppercase letter (simple
+ category)
+
+
+
+ \p{Sc}
+
+ A currency symbol
+
+
+
+ \P{InGreek}
+
+ Any character except one in the Greek block
+ (negation)
+
+
+
+ [\p{L}&&[^\p{Lu}]]
+
+ Any letter except an uppercase letter (subtraction)
+
+
+
+
+
+
+ Regex - Character classes
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ [abc]
+
+ a, b, or c (simple class)
+
+
+
+ [^abc]
+
+ Any character except a, b, or c (negation)
+
+
+
+ [a-zA-Z]
+
+ a through z or A through Z, inclusive (range)
+
+
+
+
+
+
+ Regex - Predefined character classes
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ .
+
+ Any character (except for line terminators)
+
+
+
+ \d
+
+ A digit: [0-9]
+
+
+
+ \D
+
+ A non-digit: [^0-9]
+
+
+
+ \s
+
+ A whitespace character: [ \t\n\x0B\f\r]
+
+
+
+ \S
+
+ A non-whitespace character: [^\s]
+
+
+
+ \w
+
+ A word character: [a-zA-Z_0-9]
+
+
+
+ \W
+
+ A non-word character: [^\w]
+
+
+
+
+
+
+ Regex - Boundary matchers
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ ^
+
+ The beginning of a line
+
+
+
+ $
+
+ The end of a line
+
+
+
+ \b
+
+ A word boundary
+
+
+
+ \B
+
+ A non-word boundary
+
+
+
+
+
+
+ Regex - Greedy quantifiers
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ X?
+
+ X, once or not at all
+
+
+
+ X*
+
+ X, zero or more times
+
+
+
+ X+
+
+ X, one or more times
+
+
+
+
+
+
+ greedy quantifiers will match as much as they can. For example,
+ a+? will match the aaa in
+ aaabbb
+
+
+
+ Regex - Reluctant (non-greedy) quantifiers
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ X??
+
+ X, once or not at all
+
+
+
+ X*?
+
+ X, zero or more times
+
+
+
+ X+?
+
+ X, one or more times
+
+
+
+
+
+
+ non-greedy quantifiers will match as little as they can. For
+ example, a+? will match the first
+ a in aaabbb
+
+
+
+ Regex - Logical operators
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ XY
+
+ X followed by Y
+
+
+
+ X|Y
+
+ Either X or Y
+
+
+
+ (XY)
+
+ XY as a single group
+
+
+
+
+
+
+ <indexterm class="singular">
+ <primary>Regular expressions</primary>
+
+ <secondary>Tools</secondary>
+ </indexterm>Regex tools and examples of use<indexterm class="singular">
+ <primary>Regular expressions</primary>
+
+ <secondary>Examples of use</secondary>
+ </indexterm>
+
+ A number of interactive tools are available to develop and test
+ regular expressions. They generally follow much the same pattern (for an
+ example from the Regular Expression Tester see below): the regular
+ expression (top entry) analyzes the search text (Text box in the middle) ,
+ yielding the hits, shown in the result Text box.
+
+
+ Regex Tester
+
+
+
+
+
+
+
+
+
+
+
+
+ See The Regex
+ Coach for Windows,Linux, FreeBSD versions of a stand-alone tool.
+ This is much the same as the above example.
+
+ A nice collection of useful regex cases can be found in
+ OmegaT itself (see Options > Segmentation).
+ The following list includes expressions you may find useful when searching
+ through the translation memory:
+
+
+ Regex - Examples of regular expressions in translations
+
+
+
+
+
+
+ Regular expression
+
+ Finds the following:
+
+
+
+
+
+ (\b\w+\b)\s\1\b
+
+ double words
+
+
+
+ [\.,]\s*[\.,]+
+
+ comma or a period, followed by spaces and yet another comma
+ or period
+
+
+
+ \. \s+$
+
+ extra spaces after the period at the end of the
+ line
+
+
+
+ \s+a\s+[aeiou]
+
+ English: words, beginning with vowels, should generally be
+ preceded by "an", not "a"
+
+
+
+ \s+an\s+[^aeiou]
+
+ English: the same check as above, but concerning consonants
+ ("a", not "an")
+
+
+
+ \s\s+
+
+ more than one space
+
+
+
+ \.[A-Z]
+
+ Period, followed by an upper-case letter - possibly a space
+ is missing between the period and the start of a new
+ sentence?
+
+
+
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Searches.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Searches.xml
new file mode 100644
index 0000000..89c78ab
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Searches.xml
@@ -0,0 +1,226 @@
+
+
+
+ Searches<indexterm class="singular">
+ <primary>Searches</primary>
+ </indexterm>
+
+
+ Search window
+
+
+ Text search Window<indexterm class="singular">
+ <primary>Search window</primary>
+
+ <secondary>Example</secondary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The above search finds all target segments where two or more white
+ spaces - \s\s+ - occur.
+
+
+
+ Searching<indexterm class="singular">
+ <primary>Shortcuts</primary>
+
+ <secondary>Ctrl+F - Search</secondary>
+ </indexterm>
+
+ OmegaT provides a powerful range of
+ search functions. Open the Search window with
+ Ctrl
+
+ F
+ and enter the word or phrase you wish to search for in the
+ Search for box. Alternatively, in the Editor window, select a word or
+ phrase in the editing field (target text of the current segment) and hit
+
+ Ctrl
+
+ F
+ . The word or phrase is entered in the Search for box
+ automatically. You can have several Search windows open at the same
+ time, but close them when they are no longer needed so that they do not
+ clutter your desktop.
+
+
+
+ Search location
+
+ Searches are performed by default in both the source and target
+ sections of the project, but you can limit your search to just the
+ source or the target text. You may search in
+
+
+
+ the project only (default setting)
+
+
+
+
+
+ both the project and the reference translation memories in
+ /tm/ (check Search TMs)
+
+
+
+
+
+ a single file or a folder containing a set of files (check
+ Search files)
+
+
+
+ When searching through files (as opposed to translation memories),
+ OmegaT restricts the search to files in
+ source file formats. Consequently, although OmegaT is quite able to
+ handle tmx files, it does not include them in the
+ Search files search. If you turn on
+ Searches
+
+ Advanced Options
+ Advanced Options, you can combine the search
+ with the name of the author of the translation and time of the last
+ change made.
+
+
+
+
+ Using wild cards<indexterm class="singular">
+ <primary>Searches</primary>
+
+ <secondary>Using wild cards</secondary>
+ </indexterm>
+
+ In both exact and keyword searches, the wild card search characters
+ '*' and '?' can be used. To use wild cards, the regular expressions option
+ should not be selected, as '*' and '?' have special meaning in regular
+ expressions.
+
+
+
+ '*' matches zero or more characters, from the current position
+ in a given word to its end. The search term'run*'
+ for example would match words 'run',
+ 'runs' and 'running'.
+
+
+
+
+
+ '?' matches any single character. For instance, 'run?'
+ would match the word 'runs' and
+ 'runn' in the word
+ 'running'.
+
+
+
+ The matches will be displayed in bold blue.
+
+
+
+ Search methods<indexterm class="singular">
+ <primary>Searches</primary>
+
+ <secondary>Methods</secondary>
+ </indexterm>
+
+ Select the method using the radio buttons. You can choose between
+ two methods to search:
+
+
+
+ exact search
+
+
+ Search for segments containing the exact string you specified.
+ An exact search looks for a phrase, i.e. if several words are
+ entered, they are found only if they occur in exactly that sequence.
+ Searching for open file will thus find all
+ occurrences of the string open
+ file, but not file
+ opened or open input
+ file.
+
+
+
+
+ keyword search
+
+
+ Search for segments containing all keywords you specified, in
+ any order. Select keyword search to search for any number of
+ individual full words, in any order. OmegaT displays a list of all
+ segments containing all of the words specified. Keyword searches are
+ similar to a search "with all of the words" in an Internet search
+ engine such as Google (AND logic). Using keyword search with
+ open file will thus find all
+ occurrences of the string open
+ file, as well as file
+ opened, open input file, file
+ may not be safe to open, etc.
+
+
+
+
+ For either of these two methods you can select the following three
+ options:
+
+
+
+ case sensitive: the search will
+ be performed for the exact string specified; i.e. capitalization is
+ observed.
+
+
+
+ regular expressions: The search
+ string will be treated as a regular expression. A regular expression
+ search is a powerful way to look for instances of a string. It is
+ similar to a wild card search, but allows far more flexibility. The
+ regular expressions used in searches are those supported by Java. See
+ more in the chapter on regular Expressions.
+
+
+
+ search TMs: translation
+ memories in the tm folder are included in the
+ search.
+
+
+
+
+
+ Search results display
+
+ Pressing the search button after entering a string in the search
+ field displays all the segments in the project that include the entered
+ string. As OmegaT handles identical segments as
+ one single entity, only the first unique segment is shown. The segments
+ are displayed in order of appearance in the project. Translated segments
+ are displayed with the original text at the top and the translated text at
+ the bottom, untranslated segments are displayed as the source only.
+
+ Clicking on a segment opens it in the Editor for modifications. You
+ can then switch back to the Search window for the next segment found, for
+ instance to check and, if necessary, correct the terminology.
+
+ You may have several Search windows open at the same time. You can
+ quickly see their contents by looking at their title: it will contain the
+ search term used.
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Segmentation.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Segmentation.xml
new file mode 100644
index 0000000..283af90
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Segmentation.xml
@@ -0,0 +1,286 @@
+
+
+
+ Source segmentation
+
+ Translation memory tools work with textual units called segments.
+ OmegaT has two ways to segment a text: by
+ paragraph or by sentence segmentation (also referred to as “rule-based
+ segmentation”). In order to select the type of segmentation, select
+
+
+ Project
+
+ Properties
+ Project
+
+ Properties...
+ from the main menu and tick or untick the check box
+ provided. Paragraph segmentation is advantageous in certain cases, such as
+ highly creative or stylistic translations in which the translator may wish
+ to change the order of entire sentences; for the majority of projects,
+ however, sentence segmentation is a choice to be preferred, since it
+ delivers better matches from previous translations. If sentence segmentation
+ has been selected, you can setup the rules by selecting
+
+ Project
+
+ Options
+ Options
+
+ Segmentation...
+ from the main menu.
+
+ Dependable segmentation rules are already available for many
+ languages, so it is likely that you will not need to get involved with
+ writing your own segmentation rules. On the other hand this functionality
+ can be very useful in special cases, where you can increase your
+ productivity by tuning the segmentation rules to the text to be
+ translated.
+
+ Warning: because the text will
+ segment differently after filter options have been changed, so you may have
+ to start translating from scratch. At the same time the previous valid
+ segments in the project translation memory will turn into orphan segments.
+ If you change segmentation options when a project is open, you must reload
+ the project in order for the changes to take effect.
+
+ OmegaT uses the following sequence of
+ steps:
+
+
+
+
+ Segmentation
+
+ Source level segmentation
+ Structure level segmentation
+
+
+ OmegaT first parses the text for
+ structure-level segmentation. During this process it is only the
+ structure of the source file that is used to produce segments.
+
+ For example, text files may be segmented on line breaks, empty
+ lines, or not be segmented at all. Files containing formatting
+ (OpenOffice.org documents, HTML documents, etc.) are segmented on the
+ block-level (paragraph) tags. Translatable object attributes in XHTML
+ or HTML files can be extracted as separate segments.
+
+
+
+
+
+ Segmentation
+
+ Sentence level segmentation
+ Sentence level segmentation
+
+
+ After segmenting the source file into structural units,
+ OmegaT will segment these blocks further
+ into sentences.
+
+
+
+
+
+ Segmentation rules<indexterm class="singular">
+ <primary>Segmentation</primary>
+
+ <secondary>Rules</secondary>
+ </indexterm>
+
+ The process of segmenting can be pictured as follows: the cursor
+ moves along the text, one character at a time. At each cursor position
+ rules, consisting of a Before and
+ After pattern, are applied in their given
+ order to see if any of the Before
+ patterns are valid for the text on the left and the corresponding
+ After pattern for the text on the right
+ of the cursor. If the rule matches, either the cursor moves on without
+ inserting a segment break (for an exception rule) or a new segment break
+ is created at the current cursor position (for the break rule).
+
+ The two types of rules behave as follows:
+
+
+
+
+ Segmentation
+
+ Rules
+
+ Break rule
+ Break rule
+
+
+ Separates the source text into segments. For example,
+ "Did it make sense? I was not sure." should be
+ split into two segments. For this to happen, there should be a break
+ rule for "?", when followed by spaces and a capitalized word. To
+ define a rule as a break rule, tick the Break/Exception check
+ box.
+
+
+
+
+
+
+
+ Segmentation
+
+ Rules
+
+ Exception rule
+ Exception rule
+
+
+ specify what parts of text should NOT be separated. In spite
+ of the period, "Mrs. Dalloway " should not be
+ split in two segments, so an exception rule should be established
+ for Mrs (and for Mr, for Dr, for prof etc), followed by a period. To
+ define a rule as an exception rule, leave the Break/Exception check
+ box unticked.
+
+
+
+
+ The predefined break rules should be sufficient for most European
+ languages and Japanese. In view of the flexibility, you may consider
+ defining more exception rules for your source language in order to provide
+ more meaningful and coherent segments.
+
+
+
+ Rule priority<indexterm class="singular">
+ <primary>Segmentation</primary>
+
+ <secondary>Rules priority</secondary>
+ </indexterm>
+
+ All segmentation rule sets for a matching language pattern are
+ active and are applied in the given order of priority, so rules for
+ specific language should be higher than default ones. For example, rules
+ for Canadian French (FR-CA) should be set higher than rules for French
+ (FR.*), and higher than Default (.*) ones. Thus, when translating from
+ Canadian French the rules for Canadian French - if any - will be applied
+ first, followed by the rules for French and lastly, by the Default
+ rules.
+
+
+
+ Creating a new rule<indexterm class="singular">
+ <primary>Segmentation</primary>
+
+ <secondary>Creating a new rule</secondary>
+
+ <seealso>Regular expressions</seealso>
+ </indexterm>
+
+ Major changes to the segmentation rules should be generally avoided,
+ especially after completion of the first draft, but minor changes, such as
+ the addition of a recognized abbreviation, can be advantageous.
+
+ In order to edit or expand an existing set of rules, simply click on
+ it in the top table. The rules for that set will appear in the bottom half
+ of the window.
+
+ In order to create an empty set of rules for a new language pattern
+ click Add in the upper half of the
+ dialog. An empty line will appear at the bottom of the upper table (you
+ may have to scroll down to see it). Change the name of the rule set and
+ the language pattern to the language concerned and its code (see for a list of language codes).
+ The syntax of the language pattern conforms to regular expression syntax.
+ If your set of rules handles a language-country pair, we advise you to
+ move it to the top using the Move Up
+ button.
+
+ Add the Before and After patterns. To check their syntax and their
+ applicability, it is advisable to use tools which allow you to see their
+ effect directly. See the chapter on Regular
+ expressions. A good starting point will always be the existing
+ rules.
+
+
+
+ <indexterm class="singular">
+ <primary>Segmentation</primary>
+
+ <secondary>Examples</secondary>
+ </indexterm>A few simple examples
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Intention
+
+ Before
+
+ After
+
+ Note
+
+
+
+
+
+ Set a segment after a period ('.') and before a
+ space
+
+ \.
+
+ \s
+
+ "\." means the character "." "\s" means any white space
+ character ((space, tab, new page etc.)
+
+
+
+ Do not segment after Mr.
+
+ Mr\.
+
+ \s
+
+ This an exception rule, so the rule check box must not be
+ ticked
+
+
+
+ Set a segment after "。" (Japanese period)
+
+ 。
+
+
+
+ Note that after is empty
+
+
+
+ Do not segment after M. Mr. Mrs. and Ms.
+
+ Mr??s??\.
+
+ \s
+
+ Exception rule - see the use of ? in regular
+ expressions
+
+
+
+
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Spellchecker.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Spellchecker.xml
new file mode 100644
index 0000000..d09265f
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/Spellchecker.xml
@@ -0,0 +1,165 @@
+
+
+
+ Spell checker<indexterm class="singular">
+ <primary>Spell checker</primary>
+ </indexterm>
+
+ OmegaT has a built-in spell checker based on the spelling checker used
+ in OpenOffice.org, Firefox and Thunderbird. It is consequently able to use
+ the huge range of free spelling dictionaries available for these
+ applications.
+
+
+ Installing spelling dictionaries
+
+ Before the spell check function can be used, a suitable dictionary
+ or dictionaries (i.e. for your target language) must be installed. To
+ install spelling dictionaries, follow this procedure:
+
+
+
+ In your file manager, create a new folder in a suitable location
+ in which to store spelling dictionaries (D:\Translations\spellcheckers
+ in the example below).
+
+
+
+
+
+ In OmegaT, select
+ Menu Options
+
+ Spell checking..
+ Options > Spell
+ Checking, then click Choose
+ beside the Dictionary file folder field. Navigate to and
+ select the folder you created for dictionaries.
+
+
+
+
+
+ Place the dictionary files you wish to use in this folder. There
+ are essentially two ways in which you can do this. You can either copy
+ files manually, i.e. from elsewhere on your system, using your file
+ manager; or you can use OmegaT's "Install new
+ dictionary" function to provide a list of available
+ dictionaries to select from. Note that the "Install" function requires
+ an Internet connection. The selected languages will then be installed
+ and will eventually appear in your spell checker setup window (this
+ may take a while).
+
+
+
+ Copying the files manually makes sense if you already have suitable
+ dictionary files on your system, for instance as part of your
+ OpenOffice.org or Thunderbird installation. It is simpler, however, to
+ look foir dictionaries online, using the URL of
+ online dictionaries field:
+
+
+ <indexterm class="singular">
+ <primary>Spell checker setup</primary>
+
+ <secondary>Spell checker setup - figure</secondary>
+ </indexterm>Spellchecker setup
+
+
+
+
+
+
+
+
+
+
+
+
+ Clicking on Install new dictionary button
+ will open the Dictionary installer window, where you can select the
+ dictionaries zou want to install.Make sure the language code of your
+ target files corresponds to the dictionary's language code: an FR-FR
+ dictionary will not work with an FR target setting. You need to change the
+ setting to FR-FR to have the spell checker recognize the correct
+ dictionary for your target. Look for files with the name, indicating the
+ language used and having extensions aff and
+ dic.
+
+
+
+ Using spelling dictionaries
+
+ There is no need to instruct OmegaT to use a particular spelling
+ dictionary; OmegaT will use the correct language dictionary based upon the
+ language codes of your project. Check however that the language codes are
+ exactly the same: an FR-FR dictionary will not work with an FR target
+ setting, for example. If necessary, edit the file names of the dictionary
+ or change your project's language settings.
+
+ To enable the spell checker, select Options > Spell
+ Checking and tick the Automatically check the
+ spelling of text checkbox (see above).
+
+
+ <indexterm class="singular">
+ <primary>Spell checker</primary>
+
+ <secondary>Spell checker - figure</secondary>
+ </indexterm>Spellchecker in action
+
+
+
+
+
+
+
+
+
+
+
+
+ Right-clicking on an underlined word (Artund in the figure above)
+ opens a drop-down menu listing suggestions for the correction (Art und).
+ You can also instruct the spell checker to ignore all the occurrences of
+ the mis-spelled word, or add it to the dictionary.
+
+
+
+ Hints<indexterm class="singular">
+ <primary>Spell checker</primary>
+
+ <secondary>Hints</secondary>
+ </indexterm>
+
+ If the spell checker is not working, then make sure first that the
+ check box "Automatically check the spelling of text"
+ in the spell checker dialog (Options > Spell
+ checking...) is checked.
+
+ Also check that the target language code of your project against the
+ available vocabularies in the setup window. The spell checker uses the
+ target language code to determine the language to be used : if the target
+ language is Brazilian Portuguese (PT_BR), the subfolder with vocabularies
+ must contain the two vocabulary files, called
+ pt_br.aff and pt_br.dic.
+
+ If you have already translated a large body of text, and then
+ realize the target language code of the project does not match the spell
+ checker's language code (you specified pt_BR as the language, but there
+ are no pt_BR vocabularies, for instance) you can simply copy the two
+ corresponding files and rename them (e.g. from
+ pt_PT.arr and pt_PT.dic to
+ pt._BR.arr and pt_BR.dic). Of
+ course it is much wiser, to take a short break and download the correct
+ versions of the spell checker.
+
+ Note that Remove physically removes the
+ selected vocabularies. If they are used bz some other application on your
+ system, they will disappear from that application, too. If, for whatever
+ reason, you need to do this from time to time, it may make sense to copy
+ the files involved to a different folder, reserved just for use by
+ OmegaT.
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/TranslationMemories.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/TranslationMemories.xml
new file mode 100644
index 0000000..851d2a0
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/TranslationMemories.xml
@@ -0,0 +1,492 @@
+
+
+
+ Translation memories<indexterm class="singular">
+ <primary>Translation memories</primary>
+ </indexterm>
+
+
+ Translation memories in OmegaT
+
+
+ tmx folders - location and purpose
+
+ OmegaT projects can have translation
+ memory files - i.e. files with the extension tmx - in four different
+ places:
+
+
+
+
+ Translation memories
+
+ Subfolder omegat
+
+ Project files
+ omegat folder
+
+
+ The omegat folder contains the
+ project_save.tmx and possibly a number of
+ backup TMX files. The project_save.tmx file
+ contains all the segments that have been recorded in memory since
+ you started the project. This file always exists in the project.
+ Its contents will always be sorted alphabetically by the source
+ segment.
+
+
+
+
+
+ Translation memories
+
+ Project main folder
+ main project folder
+
+
+ The main project folder contains 3 tmx files,
+ project_name-omegat.tmx,
+ project_name-level1.tmx and
+ project_name-level2.tmx (project_name being
+ the name of your project).
+
+
+
+ The level1 file contains only textual
+ information.
+
+
+
+ The level2 file encapsulates
+ OmegaT specific tags in correct tmx
+ tags so that the file can be used with its formatting
+ information in a translation tool that supports tmx level 2
+ memories, or OmegaT itself.
+
+
+
+ The OmegaT file includes
+ OmegaT specific formatting tags so
+ that the file can be used in other
+ OmegaT projects
+
+
+
+ These files are copies of the file
+ project_save.tmx, i.e. of the project's main
+ translation memory, excluding the so-called orphan segments. They
+ carry appropriately changed names, so that its contents still
+ remain identifiable, when used elsewhere, for instance in
+ the tm subfolder of some other project (see
+ below).
+
+
+
+
+
+ Translation memories
+
+ Subfolder tm
+
+ Project files
+ tm folder
+
+
+ The /tm/ folder can contain any number of ancillary
+ translation memories - i.e. tmx files. Such files can be created
+ in any of the three varieties indicated above. Note that other CAT
+ tools can export (and import as well) tmx files, usually in all
+ three forms. The best thing of course is to use OmegaT-specific
+ TMX files (see above), so that the in-line formatting within the
+ segment is retained.
+
+ The contents of translation memories in the tm subfolder
+ serve to generate suggestions for the text(s) to be translated.
+ Any text, already translated and stored in those files, will
+ appear among the fuzzy matches, if it is sufficiently similar to
+ the text currently being translated.
+
+ If the source segment in one of the ancillary TMs is
+ identical to the text being translated, OmegaT acts as defined in
+ the
+ Options
+
+ Editing Behavior...
+ dialogue window. For instance (if the default is
+ accepted), the translation from the ancillary TM is accepted and
+ prefixed with [fuzzy], so that the translator
+ can review the translations at a later stage and check whether the
+ segments tagged this way, have been translated correctly (see the
+ Editing
+ behavior chapter)
+ .
+
+
+
+
+
+
+ Translation memories
+
+ Subfolder tm/auto
+
+ Project files
+ tm/auto folder
+ Project
+
+ Pretranslation
+
+
+
+ If it is clear from the very start, that translations in a
+ given TM (or TMs) are all correct, one can put them into
+ the tm/auto folder and avoid
+ confirming a lot of [fuzzy] cases. This will
+ effectively pre-translate the
+ source text: all the segments in the source text, for which
+ translations can be found in those "auto" TMs, will land in the
+ main TM of the project without any user intervention.
+
+
+
+
+ Optionally, you can let OmegaT have an
+ additional tmx file (OmegaT-style) anywhere
+ you specify, containing all translatable segments of the project. See
+ pseudo-translated memory below.
+
+ Note that all the translation memories are loaded into memory when
+ the project is opened. Back-ups are produced regularly of the project
+ translation memory (see next chapter), and
+ project_save.tmx is also saved/updated when the
+ project is closed or loaded again. This means for instance that you do
+ not need to exit a project you are currently working on if you decide to
+ add another ancillary TM to it: you simply reload the project, and the
+ changes you have made will be included.
+
+ The locations of the various different translation memories for a
+ given project are user-defined (see Project dialog window in Instant start guide)
+
+ Depending on the situation, different strategies are thus
+ possible, for instance:
+
+ several projects on the same subject:
+ keep the project structure, and change source and target
+ directories (Source = source/order1, target = target/order1 etc). Note
+ that you segments from order1, that are not present in order2 and other
+ subsequent jobs, will be tagged as orphan segments; however, they will
+ still be useful for getting fuzzy matches.
+
+ several translators working on the same
+ project: split the source files into source/Alice,
+ source/Bob... and allocate them to team members (Alice, Bob ...). They
+ can then create their own projects and, deliver their own
+ project_save.tmx, when finished or when a given
+ milestone has been reached. The project_save.tmx
+ files are then collected and possible conflicts as regards terminology
+ for instance get resolved. A new version of the master TM is then
+ created, either to be put in team members'
+ tm/autosubdirectories or to replace their
+ project_save.tmx files. The team can also use the
+ same subfolder structure for the target files. This allows them for
+ instance to check at any moment, whether the target version for the
+ complete project is still OK
+
+
+
+ tmx backup<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Backup</secondary>
+ </indexterm>
+
+ As you translate your files, OmegaT
+ stores your work continually in project_save.tmx in
+ the project's /omegat subdirectory.
+
+ OmegaT also backups translation memory
+ to project_save.tmx.YEARMMDDHHNN.bak in the same
+ subfolder whenever a project is opened or reloaded. YEAR is 4-digit
+ year, MM is a month, DD day of the month, HH and NN are hours and
+ minutes when the previous translation memory was saved.
+
+ If you believe you have lost translation data, follow the
+ following procedure:
+
+
+
+ Close the project
+
+
+
+ Rename the current project_save.tmx file
+ ( e.g. to project_save.tmx.temporary)
+
+
+
+ Select the backup translation memory that is most likely -
+ e.g. the most recent one, or the last version from the day before)
+ to contain the data you are looking for
+
+
+
+ Copy it to project_save.tmx
+
+
+
+ Open the project
+
+
+
+
+
+ tmx files and language<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Language</secondary>
+ </indexterm>
+
+ tmx files contain translation units, made of a number of
+ equivalent segments in several languages. A translation unit comprises
+ at least two translation unit variations (TUV). Either can be used as
+ the source or target.
+
+ The settings in your project indicate which is the source and
+ which the target language. OmegaT thus takes the TUV segments
+ corresponding to the project's source and target language codes and uses
+ them as the source and target segments respectively. OmegaT recognizes
+ the language codes using the following two standard conventions :
+
+
+
+ 2 letters (e.g. JA for Japanese), or
+
+
+
+ 2- or 3-letter language code followed by the 2-letter country
+ code (e.g. EN-US - See for a
+ partial list of language and country codes).
+
+
+
+ If the project language codes and the tmx language codes fully
+ match, the segments are loaded in memory. If languages match but not the
+ country, the segments still get loaded. If neither the language code not
+ the country code match, the segments will be ignored.
+
+
+ Translation memories
+
+ multilingual, handling of
+ TMX files can generally contain translation units with
+ several candidate languages. If for a given source segment there is no
+ entry for the selected target language, all other target segments are
+ loaded, regardless of the language. This avoids loading unwanted
+ non-project languages from multilingual TMXs, while still allowing the
+ use of monolingual TMXs with other target languages than the project
+ target language selected. For instance if the language pair of the
+ project is DE-FR, it can be still be of some help to have access to a
+ DE-EN translation, if there's no match in the DE-FR pair.
+
+
+
+ Orphan segments<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Orphan segments</secondary>
+ </indexterm>
+
+ The file project_save.tmx contains all the
+ segments that have been translated since you started the project. If you
+ modify the project segmentation or delete files from the source, some
+ matches may appear as orphan strings in
+ the Match Viewer: such matches refer to segments that do not exist any
+ more in the source documents, as they correspond to segments translated
+ and recorded before the modifications took place.
+
+
+
+
+ Reusing translation memories<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Import and export</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Reusing translation memories</secondary>
+ </indexterm>
+
+ Initially, that is when the project is created, the main TM of the
+ project, project_save.tmx is empty. This TM gradually
+ becomes filled during the translation. To speed up this process, existing
+ translations can be reused. If a given sentence has already been
+ translated once, and translated correctly, there is no need for it to be
+ retranslated. Translation memories may also contain reference
+ translations: multinational legislation, such as that of the European
+ Community, is a typical example.
+
+ When you create the target documents in an
+ OmegaT project, the translation memory of the
+ project is outputted in the form of three files in the root folder of your
+ OmegaT project (see the above description). You
+ can regard these three tmx files (-omegat.tmx,
+ -level1.tmx and -level2.tmx) as
+ an "export translation memory", i.e. as an export of your current
+ project's content in bilingual form.
+
+ Should you wish to reuse a translation memory from a previous
+ project (for example because the new project is similar to the previous
+ project, or uses terminology which might have been used before), you can
+ use these translation memories as "input translation memories", i.e. for
+ import into your new project. In this case, place the translation memories
+ you wish to use in the \tm or
+ \tm\auto folder of your new project: in the former
+ case you will get hits from these translation memories in the fuzzy
+ matches viewer, and in the latter case these TMs will be used to
+ pre-translate your source text.
+
+ By default, the \tm folder is below the project's root folder (e.g.
+ ...\MyProject\tm), but you can choose a different
+ folder in the project properties dialog if you wish. This is useful if you
+ frequently use translation memories produced in the past, for example
+ because they are on the same subject or for the same customer. In this
+ case, a useful procedure would be:
+
+
+
+ Create a folder (a "repository folder") in a convenient location
+ on your hard drive for the translation memories for a particular
+ customer or subject.
+
+
+
+
+
+ Whenever you finish a project, copy one of the three "export"
+ translation memory files from the root folder of the project to the
+ repository folder.
+
+
+
+
+
+ When you begin a new project on the same subject or for the same
+ customer, navigate to the repository folder in the
+ Project > Properties > Edit Project
+ dialog and select it as the translation memory
+ folder.
+
+
+
+ Note that all the tmx files in the /tm repository are parsed when
+ the project is opened, so putting all different TMs you may have on hand
+ into this folder may unnecessarily slow OmegaT down. You may even consider
+ removing those that are not required any more, once you have used their
+ contents to fill up the project-save.tmx file.
+
+
+ Importing and exporting translation memories
+
+ OmegaT supports imported tmx versions 1.1-1.4b (both level 1 and
+ level 2). This enables the translation memories produced by other tools
+ to be read by OmegaT. However, OmegaT does not fully support imported
+ level 2 tmx files (these store not only the translation, but also the
+ formatting). Level 2 tmx files will still be imported and their textual
+ content can be seen in OmegaT, but the quality of fuzzy matches will be
+ somewhat lower.
+
+ OmegaT follows very strict procedures when loading translation
+ memory (tmx) files. If an error is found in such a file, OmegaT will
+ indicate the position within the defective file at which the error is
+ located.
+
+ Some tools are known to produce invalid tmx files under certain
+ conditions. If you wish to use such files as reference translations in
+ OmegaT, they must be repaired, or OmegaT will report an error and fail
+ to load them. Fixes are trivial operations and OmegaT assists
+ troubleshooting with the related error message. You can ask the user
+ group for advice if you have problems.
+
+ OmegaT exports version 1.4 TMX files (both level 1
+ and level 2). The level 2 export is not fully compliant with the level 2
+ standard, but is sufficiently close and will generate correct matches in
+ other translation memory tools supporting TMX Level 2. If you only need
+ textual information (and not formatting information), use the level 1
+ file that OmegaT has created.
+
+
+
+
+ Pseudo-translated memory<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Pseudotranslation</secondary>
+ </indexterm>
+
+
+ Of interest for advanced users only!
+
+
+ Before segments get translated, you may wish to pre-process them or
+ address them in some other way than is possible with OmegaT. For example,
+ if you wish to create a pseudo-translation for testing purposes, OmegaT
+ enables you to create an additional tmx file that contains all segments of
+ the project. The translation in this tmx can be either
+
+
+
+ translation equals source (default)
+
+
+
+
+
+ translation segment is empty
+
+
+
+ The tmx file can be given any name you specify. A pseudo-translated
+ memory can be generated with the following command line parameters:
+
+ java -jar omegat.jar --pseudotranslatetmx=<filename>
+ [pseudotranslatetype=[equal|empty]]
+
+ Replace <filename> with the name of the
+ file you wish to create, either absolute or relative to the working
+ directory (the directory you start OmegaT
+ from). The second argument --pseudotranslatetype is
+ optional. Its value is either equal (default value, for
+ source=target) or empty (target segment is empty). You
+ can process the generated tmx with any tool you want. To reuse it in
+ OmegaT rename it to project_save.tmx
+ and place it in the omegat-folder of your
+ project.
+
+
+
+ Upgrading translation memories<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Upgrading to sentence segmentation</secondary>
+ </indexterm>
+
+ Very early versions of OmegaT were
+ capable of segmenting source files into paragraphs only and were
+ inconsistent when numbering formatting tags in HTML and Open Document
+ files. OmegaT 2.5 can detect and upgrade such
+ tmx files on the fly to increase fuzzy matching quality and leverage your
+ existing translation better, saving you the work of doing this
+ manually.
+
+ A project's tmx will be upgraded only once, and will be written in
+ upgraded form into the project-save.tmx; legacy tmx
+ files will be upgraded on the fly each time the project is loaded. Note
+ that in some cases changes in file filters in
+ OmegaT 2.5 may lead to totally different
+ segmentation; as a result, you will have to upgrade your translation
+ manually in such rare cases.
+
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/UserInterface.xml b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/UserInterface.xml
new file mode 100644
index 0000000..e7c7eb2
--- /dev/null
+++ b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Full/source/doc_src/en/UserInterface.xml
@@ -0,0 +1,1089 @@
+
+
+
+ The user interface
+
+
+ User interface items
+
+
+ Frequently used windows<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+ </indexterm>
+
+
+
+ OmegaT main window
+
+
+ contains the main menu, status bar and several panes:
+
+
+
+ Editor - where you type and edit the translation
+
+
+
+ Match Viewer - displays the most similar segments from
+ translation memories
+
+
+
+ Glossary Viewer - displays terminology
+
+
+
+ Dictionary Viewer - displays information provided by
+ dictionaries
+
+
+
+ Machine Translation - displays the translation, provided
+ by MT services, like Google Translate
+
+
+
+ Multiple Translations - shows translation alternatives -
+ if any entered - for the current segment
+
+
+
+ Notes viewer - notes by the translator, regarding the
+ current segment
+
+
+
+ Comments - comments by the translator, regarding the
+ current segment
+
+
+
+
+
+
+
+ Shortcuts
+
+ Ctrl+L - Project files window
+ Project Files window
+
+
+ The list of your translatable files (open with
+ Ctrl
+
+ L
+ , close with Esc)
+
+
+
+
+
+ Shortcuts
+
+ Ctrl+F - Search window
+ Search window
+
+
+ Used to search for specific segments in the project (open
+ with
+ Ctrl
+
+ F
+ , close with Esc)
+
+
+
+
+
+
+ Less frequently used
+
+
+
+
+ Shortcuts
+
+ Ctrl+T - Tag validation window
+ Tag Validation window
+
+
+ Used to check for tag mistakes in translations (open with
+
+ Ctrl
+
+ T
+ close with Esc)
+
+
+
+
+
+ Shortcuts
+
+ F1 - Help
+ Help browser
+
+
+ Used to read the user manual (open with F1,
+ close with Esc)
+
+
+
+
+ Statistics window
+
+
+ Used to open the window with the statistics of the project,
+ display it, using
+
+ Menu Tools
+
+ statistics
+ Tools
+
+ Statistics.
+
+
+
+
+
+ Match statistics window
+
+
+ Used to display the match statistics of the project, select
+
+
+ Menu Tools
+
+ Match statistics
+ Tools
+
+ Match statistics
+ to open it.
+
+
+
+
+
+
+ Project settings dialogs <indexterm class="singular">
+ <primary>Project</primary>
+
+ <secondary>Project Settings</secondary>
+ </indexterm>
+
+ The dialogs below are used to change OmegaT project settings. Each
+ is described in detail in a separate section; the information below
+ summarizes their use and how they are invoked:
+
+
+
+
+ Shortcuts
+
+ Ctrl+E - Project properties
+
+ Menu Project
+
+ Properties
+ Project Properties
+
+
+ Used to modify the project folders and languages, (access
+ via
+
+
+ Ctrl
+
+ E
+
+
+
+ Project
+
+ properties...
+ , close via Esc)
+
+
+
+
+
+ Project Settings
+
+ Font
+ Font
+ Menu Options
+
+ Font
+
+
+
+ Used to modify the font used by
+ OmegaT to display source, translation, matches and
+ glossary terms, (access via
+ Options
+
+ Font...
+ , close via
+ Esc)
+
+
+
+
+
+ Project Settings
+
+ File filters
+ File filters
+ Menu Options
+
+ File filters
+
+
+
+ Used to adjust the handling of supported file formats
+ (access via
+ Options
+
+ File Filters...
+ , close via Esc)
+
+
+
+
+
+ Project Settings
+
+ Segmentation
+ Segmentation
+ Menu Options
+
+ Segmentation
+
+
+
+ Used to change the way your text is segmented into sentences
+ (access via
+ Options
+
+ Segmentation
+ , close via Esc)
+
+
+
+
+
+ Project Settings
+
+ Editing Behavior
+ Editing Behavior
+ Menu Options
+
+ Editing Behavior
+
+
+
+ Used to change how OmegaT behaves
+ when you iterate between the segments (access via
+ Options
+
+ Behavior...
+ , close via Esc)
+
+
+
+
+
+
+
+ <application>OmegaT</application> main window<indexterm
+ class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Main window</secondary>
+
+ <tertiary>- figure</tertiary>
+ </indexterm><indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Main window</secondary>
+ </indexterm>
+
+
+ OmegaT panes
+
+
+
+
+
+
+
+
+
+
+
+
+ The main window consists of several panes, the main menu and a
+ status bar. You can change the position of any pane or even undock it to a
+ separate window by clicking and dragging the pane by its name. Depending
+ on the pane status, different signs can appear at its top right
+ corner:
+
+
+ Pane widgets<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Pane widgets</secondary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ minimizes the pane, so that only its name is shown at the
+ bottom of the window.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ maximizes the pane
+
+
+
+
+
+
+
+
+
+
+
+
+
+ undocks the pane from the main window.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ puts the pane back within the main window.
+
+
+
+
+
+ You can overlap panes if desired. When this is done the panes
+ display a tab at the top. The separators between the panes can be dragged
+ to resize panes. Should you lose track of your changes to the user
+ interface, you can use
+ OmegaT windows
+
+ Windows and panes in OmegaT
+
+ OmegaT windows
+
+ Restoring to factory setup
+ Options → Restore the main window any time to
+ return to the original layout.
+
+ The counters in the lower right corner keep track of the progress of
+ the translation (numbers in the left hand column refer to the figure
+ above):
+
+
+ Main Window - counters<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Counters</secondary>
+ </indexterm>
+
+
+
+
+
+
+ 33/33
+
+ number of segments - translated vs total for the current
+ file
+
+
+
+ 2780/2780
+
+ number of unique segments - translated vs total in the
+ project
+
+
+
+ 3760
+
+ total number of segments (including repeats) in the
+ project
+
+
+
+ 126/127
+
+ number of source and target characters in the current
+ segment
+
+
+
+
Your page is not found
+
+HF_HAIKU_3=Bartender yells loud:
Your page cannot be found, boy
Buy another drink.
+
+HF_HAIKU_4=Page slips through fingers
Pulse pounding hard and frantic
Vanishing like mist.
+
+HF_HAIKU_5=These three are certain:
Death, taxes, and page not found.
You, victim of one.
+
+HF_HAIKU_6=The help page you seek
Lies beyond our perception
But others await
+
+HF_HAIKU_7=Emptiness of soul
Forever aching blackness
Your help page not found
+
+HF_HAIKU_8=Ephemeral page
I am the Blue Screen of Death
No one hears your screams.
+
+HF_HAIKU_9=Rather than beep
Or a rude error message
These words: 'Page not found'
+
+HF_HAIKU_10=Mourning and sorrow
404 not with us now
Lost to paradise
+
+HF_HAIKU_11=Help you are seeking
From your path it is fleeing
Its winter has come
+
+# CommandThread
+CT_FUZZY_X_OF_Y=Analyzing strings - {0} of {1} completed
+
+CT_LOADING_PROJECT=Loading project...
+
+CT_LOADING_GLOSSARIES=Loading glossaries
+
+CT_CANCEL_LOAD=Project load cancelled by user
+
+CT_ERROR_SAVING_PROJ=Error saving project file!
+
+CT_ERROR_CREATE=Error creating project!
+
+CT_FATAL_ERROR=Fatal error encountered - saving project file with '.recover' backup extension.\n\
+ Please consult the documentation about your recovery options and\n\
+ return the information below to the software manufacturer with\n\
+ a description of how this error was produced.\n
+
+# 0 - Name of file being loaded
+CT_LOAD_FILE_MX=Loading: {0}
+
+CT_LOAD_SRC_COMPLETE=Source file loading complete
+
+CT_LOAD_TMX=Loading TMX files...
+
+# 0 - Name of target document
+CT_COMPILE_FILE_MX=Creating translated documents: {0}
+
+CT_COMPILE_DONE_MX=Translated documents created
+
+CT_ERROR_CREATING_TMX=Unable to build new TMX file!
+
+CT_ERROR_CREATING_PROJECT=Failed to create project!
+
+CT_ERROR_LOADING_PROJECT_FILE=Problem encountered loading project file!
+
+CT_ERROR_ACCESS_GLOSSARY_DIR=Cannot access glossary folder!
+
+CT_ERROR_CREATING_TARGET_DIR=Cannot create folder for translated files:
+
+# 0 - Name of TMX file
+CT_ERROR_CANNOT_FIND_TMX=Cannot find saved TMX: {0}
+
+CT_ERROR_ACCESS_PROJECT_FILE=Security error encountered loading project file!
+
+CT_ORPHAN_STRINGS=Orphan segments
+
+# CommandThread.buildProjectStats()
+
+CT_STATS_Project_Statistics=Project Statistics
+
+CT_STATS_Total=Total:
+
+CT_STATS_Segments=Segments
+
+CT_STATS_Words=Words
+
+CT_STATS_Characters_NOSP=Characters (without spaces)
+
+CT_STATS_Characters=Characters (including spaces)
+
+CT_STATS_Remaining=Remaining:
+
+CT_STATS_Unique_Remaining=Unique Remaining:
+
+CT_STATS_Unique=Unique:
+
+CT_STATS_FILE_Statistics=Individual File Statistics:
+
+CT_STATS_FILE_Name=File Name
+
+CT_STATS_FILE_Total_Segments=Total Segments
+
+CT_STATS_FILE_Remaining_Segments=Remaining Segments
+
+CT_STATS_FILE_Unique_Segments=Unique Segments
+
+CT_STATS_FILE_Unique_Remaining_Segments=Unique Remaining Segments
+
+CT_STATS_FILE_Total_Words=Total Words
+
+CT_STATS_FILE_Remaining_Words=Remaining Words
+
+CT_STATS_FILE_Unique_Words=Unique Words
+
+CT_STATS_FILE_Unique_Remaining_Words=Unique Remaining Words
+
+CT_STATS_FILE_Total_Characters_NOSP=Total Characters (without spaces)
+
+CT_STATS_FILE_Remaining_Characters_NOSP=Remaining Characters (without spaces)
+
+CT_STATS_FILE_Unique_Characters_NOSP=Unique Characters (without spaces)
+
+CT_STATS_FILE_Unique_Remaining_Characters_NOSP=Unique Remaining Characters (without spaces)
+
+CT_STATS_FILE_Total_Characters=Total Characters (including spaces)
+
+CT_STATS_FILE_Remaining_Characters=Remaining Characters (including spaces)
+
+CT_STATS_FILE_Unique_Characters=Unique Characters (including spaces)
+
+CT_STATS_FILE_Unique_Remaining_Characters=Unique Remaining Characters (including spaces)
+
+
+CT_STATSSTANDARD_WindowHeader=Statistics
+
+CT_STATSMATCH_WindowHeader=Match Statistics
+
+CT_STATSMATCH_RowRepetitions=Repetitions:
+CT_STATSMATCH_RowExactMatch=Exact match:
+CT_STATSMATCH_RowMatch95=95%-100%:
+CT_STATSMATCH_RowMatch85=85%-94%:
+CT_STATSMATCH_RowMatch75=75%-84%:
+CT_STATSMATCH_RowMatch50=50%-74%:
+CT_STATSMATCH_RowNoMatch=No match:
+
+
+# org.omegat.core.matching.LevenshteinDistance
+LD_NULL_ARRAYS_ERROR=Arrays must not be null
+
+# org.omegat.gui.ProjectProperties
+
+PP_SENTENCE_SEGMENTING=E&nable Sentence-level Segmenting
+
+PP_EDIT_PROJECT=Edit Project
+
+PP_MESSAGE_EDITPROJ=Edit project properties here.
+
+PP_LANGUAGES=Languages
+
+PP_OPTIONS=Options
+
+PP_DIRECTORIES=File locations
+
+PP_CHECKBOX_PROJECT_SPECIFIC_SEGMENTATION_RULES=&Project specific segmentation rules
+
+PP_CREATE_PROJ=Create New Project
+
+PP_OPEN_PROJ=Open Project
+
+PP_SRC_ROOT=Source Files Folder:
+
+PP_LOC_ROOT=Translated Files Folder:
+
+PP_GLOS_ROOT=Glossary Folder:
+PP_WRITEABLE_GLOS=Writeable Glossary File:
+
+PP_TM_ROOT=Translation Memory Folder:
+
+PP_SRC_LANG=&Source Files Language:
+
+PP_LOC_LANG=&Translated Files Language:
+
+PP_DICT_ROOT=Dictionary Folder:
+
+PP_ALLOW_DEFAULTS=&Auto-propagation of translations
+
+PP_BUTTON_BROWSE_SRC=&Browse
+
+PP_BUTTON_BROWSE_TAR=B&rowse
+
+PP_BUTTON_BROWSE_GL=Bro&wse
+PP_BUTTON_BROWSE_WG=Browse
+
+PP_BUTTON_BROWSE_TM=Brows&e
+
+PP_BUTTON_BROWSE_DICT=Browse
+
+PP_BROWSE_TITLE_SOURCE=Source Files Folder
+
+PP_BROWSE_TITLE_TARGET=Translated Files Folder
+
+PP_BROWSE_TITLE_GLOS=Glossary Files Folder
+
+PP_BROWSE_TITLE_TM=Translation Memory Files Folder
+
+PP_BROWSE_TITLE_DICT=Dictionary Files Folder
+
+PP_BROWSE_W_GLOS=Writeable Glossary File
+
+PP_MESSAGE_BADPROJ=\
+ Some project folders seem to have been moved. \n\
+ You should specify their new location or recreate\n\
+ them.
+
+PP_MESSAGE_CONFIGPROJ=\
+ Please select the language of your source files and the target \n\
+ language you would like to translate to. \n\
+ Here you may also specify custom location of project folders.
+
+PP_SAVE_PROJECT_FILE=Create a New Project
+
+PP_PROJECT_FILES_DESC=OmegaT Project Files
+
+PP_ERROR_UNABLE_TO_READ_PROJECT_FILE=Unable to read project file! \n
+
+# NewProjectDialog.java
+NP_INVALID_SOURCE_LOCALE=The source file language entered is invalid!\n
+
+NP_LOCALE_SUGGESTION=The language code should be in the form xx-YY, xxx-YY, xx_YY or xxx_YY, where \n\
+xx or xxx is the language code and YY is the region or country code (optional).
+
+NP_INVALID_TARGET_LOCALE=The translated file language entered is invalid!\n
+
+NP_SOURCEDIR_DOESNT_EXIST=Source files folder entered does not exist!
+
+NP_TRANSDIR_DOESNT_EXIST=Translated files folder entered does not exist!
+
+NP_GLOSSDIR_DOESNT_EXIST=Glossary files folder entered does not exist!
+NP_W_GLOSSDIR_DOESNT_EXIST=Writeable glossary file folder entered does not exist!
+NP_W_GLOSDIR_NOT_INSIDE_GLOS=The writeable glossary file must be inside the glossary folder
+
+NP_TMDIR_DOESNT_EXIST=Translation memory files folder entered does not exist!
+
+NP_DICTDIR_DOESNT_EXIST=Dictionary files folder entered does not exist!
+
+#LogDisplay
+
+# 0 - the error
+LD_ERROR=ERROR: {0}
+
+#ProjectFileChooser
+
+PFC_OMEGAT_PROJECT=OmegaT Project Folder
+
+#NewFileChooser
+
+NDC_SELECT_UNIQUE=Filename already exists. Please select a different name.
+
+NDC_SELECT_UNIQUE_TITLE=Error
+
+#OmegaTFileChooser
+
+OFC_NEW_DIR_ERROR=An error occurred while trying to create a new folder
+
+#SearchWindow
+SW_SEARCH_TEXT=Search for:
+
+SW_WORD_SEARCH=&Keyword search
+
+SW_EXACT_SEARCH=&Exact search
+
+SW_REGEXP_SEARCH=&Regular expressions
+
+SW_SEARCH_SOURCE=In so&urce
+
+SW_SEARCH_TARGET=In tra&nslations
+
+SW_SEARCH_NOTES=In no&tes
+
+SW_ADVANCED_OPTIONS=Advanced &Options
+
+SW_AUTHOR=Aut&hor:
+
+SW_NOW=Now
+
+SW_CHANGED_AFTER=Chan&ged after:
+
+SW_CHANGED_BEFORE=Changed &before:
+
+SW_CASE_SENSITIVE=C&ase sensitive
+
+SW_SEARCH_TM=Search T&Ms
+SW_ALL_RESULTS=Dis&play all results
+
+SW_LOCATION=Location
+
+SW_BROWSE=Select Fol&der
+
+SW_DIR_SEARCH=Search &files
+
+SW_DIR_RECURSIVE=Recursi&ve search
+
+SW_TITLE=Text Search
+
+SW_NUMBER=Number of results:
+
+SW_VIEWER_TEXT=Searches can be performed in the source and/or in the translation and/or in notes.\n\n\
+ Searches are done within the current project or in any folder or folder structure.\n\n\
+ Exact searches look for the entire specified query string.\n\n\
+ Keyword searches regard the specified query string as a set of search \
+ keywords (separated by space) and return all segments \
+ which contain all of the query words, in any order.\n\n\
+ Both search types support the wildcard characters * and ?. \
+ The '*' character matches zero or more characters (the search term \
+ 'run*' would match 'run', 'runs', and 'running', for example). \
+ The '?' character matches exactly one character ('run?' \
+ would match 'runs' and 'rung', for example, but not 'run' or 'running').
+
+# 0 - Maximun number of finds/hits
+SW_MAX_FINDS_REACHED=Maximum number of finds has been reached ({0})
+
+ST_FILE_SEARCH_ERROR=Error searching directory tree!
+
+ST_REGEXP_ERROR=Bad regular expression!
+
+SW_ERROR_BAD_DIR=Bad folder name {0}
+
+ST_FATAL_ERROR=Search thread died unexpectedly! Please close search window.
+
+ST_NOTHING_FOUND=No matches returned by search.
+
+# 0 - Nr of hits
+SW_NR_OF_RESULTS=Nr of results: {0}
+
+
+# XMLStreamReader
+XSR_ERROR_UNABLE_INIT_READ_XML=Unable to initialize read of XML file!
+
+# {0} - the version, which we can't support
+XSR_ERROR_UNSUPPORTED_XML_VERSION=Unsupported XML version {0}!
+
+XSR_ERROR_NONVALID_XML=Not a valid XML file!
+
+XSR_ERROR_CANNOT_LOAD_XML=Cannot load specified XML file! \n
+
+XSR_ERROR_IOEXCEPTION=IOException encountered:
+
+# {0} - character
+# {1} - stream reader state
+XSR_ERROR_UNEXPECTED_CHAR=Unexpected char {0} ({1})!
+
+XSR_ERROR_CONFUSED=Confused by false start of comment tag!
+
+XSR_ERROR_TAG_NAME=\nTag name:
+
+XSR_ERROR_COMMENT_TAG=(comment tag)
+
+XSR_ERROR_FLOATING_QUESTION_MARK=Floating '?' character not tied to '>'!
+
+XSR_ERROR_EMPTY_TAG=(empty tag)
+
+XSR_ERROR_CLOSE_TAG=(close tag)
+
+XSR_ERROR_LOADED=loaded
+
+XSR_ERROR_ATTRIBUTES= attributes.
+
+XSR_ERROR_END_OF_STREAM=End of stream encountered without finding close block!
+
+XSR_ERROR_UNTERMINATED_ESCAPE_CHAR=Escaped character never terminated!
+
+# {0} - bad hex value
+XSR_ERROR_BAD_BINARY_CHAR=Escaped binary char contains malformed data ({0})!
+
+# {0} - bad decimal value
+XSR_ERROR_BAD_DECIMAL_CHAR=Escaped decimal char contains malformed data ({0})!
+
+# LFileCopy
+LFC_ERROR_FILE_DOESNT_EXIST=File {0} does not exist!
+
+# PreferenceManager
+
+PM_ERROR_SAVE=Preferences system save operation failed!
+
+PM_WARNING_PARSEERROR_ON_READ=Parse error encountered reading preferences file!
+
+PM_UNSUPPORTED_ENCODING=Unsupported file encoding
+
+PM_ERROR_READING_FILE=Unable to read file
+
+# ProjectFileReader
+
+# {0} - the version, which we don't support
+PFR_ERROR_UNSUPPORTED_PROJECT_VERSION=Unsupported project file version ({0})!
+
+# TMXReader
+
+# {0} - the name of the TMX file
+TMXR_INFO_READING_FILE=\nReading TMX file {0}
+
+TMXR_INFO_READING_COMPLETE=Reading of TMX file complete
+
+# 0 - Name of the tool that created the TMX file
+TMXR_INFO_CREATION_TOOL=Created by: {0}
+
+# 0 - Version of the creation tool
+TMXR_INFO_CREATION_TOOL_VERSION=Version: {0}
+
+# 0 - Segmentation method
+TMXR_INFO_SEG_TYPE=Segmentation method: {0}
+
+# 0 - Source language
+TMXR_INFO_SOURCE_LANG=Source language: {0}
+
+# 0 - Variant languages
+TMXR_INFO_VARIANT_LANGUAGES_DISPLAYED=Variants in the following languages will be displayed: {0}
+
+# {0} - the exception
+TMXR_EXCEPTION_WHILE_PARSING=Exception while parsing:
+
+# {0} - the name of the TMX file
+# {1} - location of the log file
+TMXR_EXCEPTION_WHILE_PARSING__DISPLAY=An exception occurred while parsing the TMX file\n{0}\n\
+ The TMX file will not be loaded. Please consult the log\n\
+ ({1})\n\
+ to determine the source of the error and try again.
+
+# {0} - the line number
+# {1} - the column number
+# {2} - the warning
+TMXR_WARNING_WHILE_PARSING=Warning on line {0}, column {1} while parsing:
+
+# {0} - the line number
+# {1} - the column number
+# {2} - the error
+TMXR_RECOVERABLE_ERROR_WHILE_PARSING=Recoverable error on line {0}, column {1} while parsing:
+
+# {0} - the line number
+# {1} - the column number
+# {2} - the error
+TMXR_FATAL_ERROR_WHILE_PARSING=Fatal error on line {0}, column {1} while parsing:
+
+# {0} - the name of the TMX file
+# {1} - the line number
+# {2} - the column number
+TMXR_FATAL_ERROR_WHILE_PARSING__DISPLAY=Unrecoverable error while parsing TMX file\n{0}\n\
+ on line {1}, column {2}.\n\n\
+ The TMX file will not be loaded\n\
+ Please try to correct the error and reload the project.\n
+
+TMXR_ERROR_TU_BEFORE_HEADER=Translation unit encountered before TMX header.
+
+TMXR_WARNING_TUV_NOT_IN_TU=Translation unit variant encountered outside translation unit. Variant skipped.
+
+TMXR_WARNING_TUV_LANG_NOT_SPECIFIED=Language not specified for translation unit variant. Variant skipped.
+
+TMXR_WARNING_SEG_NOT_IN_TUV=Segment encountered outside translation unit variant. Segment skipped.
+
+TMXR_WARNING_SOURCE_NOT_FOUND=Source segment could not be located \
+ for certain translation units. These units have been skipped.
+
+# {0} - TMX source language
+# {1} - Project source language
+TMXR_WARNING_INCORRECT_SOURCE_LANG=The TMX source language ({0}) is different \
+ from the project source language ({1}). The TMX file will continue to be loaded.
+
+TMXR_WARNING_UPGRADE_14X=TMX file was created by OmegaT 1.4.x or earlier. Upgrading...
+
+TMXR_WARNING_UPGRADE_SENTSEG=Your current project uses sentence segmentation, \
+ but TMX file was created using paragraph segmentation. OmegaT will try to resegment the TMX file...
+
+TMX_ERROR_READING_LEVEL2=Error reading TMX level2 at line {0} column {1}
+
+# org.omegat.core.glossary.GlossaryManager
+
+# 0 - Name of glossary file
+CT_LOADING_GLOSSARY=Loading glossary {0}
+
+
+# org.omegat.Main
+MAIN_ERROR_CANT_INIT_OSLF=Could not initialize OS look and feel!
+
+# PluginUtils.java
+PLUGIN_UNKNOWN=Unknown plugin type in '{0}'
+
+PLUGIN_MARKER_INITIALIZE=Error initializing marker '{0}'
+
+# FilterMaster.java
+
+#not important actually
+FILTERMASTER_ERROR_LOADING_FILTERS_CONFIG=Unable to parse filters configuration file
+
+#pretty important
+FILTERMASTER_ERROR_SAVING_FILTERS_CONFIG=Unable to save filters configuration file
+
+# 0 - filter class name
+# 1 - class file location
+FILTERMASTER_ERROR_LOADING_FILTER=Filter '{0}' could not be loaded from '{1}'
+
+# Filters.java
+
+FILTERS_FILE_FORMAT=File Format
+
+FILTERS_ON=Enabled
+
+FILTERS_ERROR_COLUMN_INDEX_NOT_1=Column Index must be equal to 1
+
+# OneFilter.java
+
+ONEFILTER_SOURCE_FILENAME_MASK=Source Filename Pattern
+
+ONEFILTER_SOURCE_FILE_ENCODING=Source File Encoding
+
+ONEFILTER_TARGET_FILE_ENCODING=Translated File Encoding
+
+ONEFILTER_TARGET_FILENAME_ENCODING=Translated Filename Pattern
+
+# LatexFilter.java
+
+LATEXFILTER_FILTER_NAME=LaTeX Files
+
+# PoFilter.java
+
+POFILTER_FILTER_NAME=PO Files
+POFILTER_OPTIONS_TITLE=PO Filter Options
+POFILTER_ALLOW_BLANK=Allow blank translations in the target files
+POFILTER_EXCEPTION=The PO filter threw an exception:
+POFILTER_INVALID_FORMAT=Invalid file format
+
+# RcFilter.java
+
+RCFILTER_FILTER_NAME=Windows Resource Files
+
+# MozillaDTDFilter.java
+
+MOZDTD_FILTER_NAME=Mozilla DTD files
+
+# XtagFilter.java
+XTAGFILTER_FILTER_NAME=QuarkXPress CopyFlow Gold Files
+
+# TextFilter.java
+
+TEXTFILTER_FILTER_NAME=Text Files
+
+TEXTFILTER_OPTIONS_DIALOG_TITLE=Text Filter Options
+
+TEXTFILTER_OPTIONS_DIALOG_DESCRIPTION=Segment source text into paragraphs on\:
+
+TEXTFILTER_OPTION_SEGMENT_ON_LINE_BREAKS=&Line breaks
+
+TEXTFILTER_OPTION_SEGMENT_ON_EMPTY_LINES=&Empty lines
+
+TEXTFILTER_OPTION_NEVER_SEGMENT=&Never
+
+# ResourceBundleFilter.java
+
+RBFILTER_FILTER_NAME=Java(TM) Resource Bundles
+
+RBFH_ERROR_ILLEGAL_U_SEQUENCE=Encountered illegal \\u sequence
+
+# XLIFFFilter.java
+XLIFF_FILTER_NAME=XLIFF Files
+
+# RESXFilter.java
+RESX_FILTER_NAME=ResX Files
+
+# HelpAndManualFilter.java
+HELPANDMANUAL_FILTER_NAME=Help & Manual Files
+
+# CamtasiaWindowsFilter.java
+CAMTASIAWINDOWS_FILTER_NAME=Camtasia for Windows Files
+
+# Typo3Filter.java
+TYPO3_FILTER_NAME=Typo3 LocManager Files
+
+# L10nmgrFilter.java
+L10NMGR_FILTER_NAME=Typo3 l10nmgr Files
+
+# WixFilter.java
+WIX_FILTER_NAME=WiX Localization Files
+
+# SvgFilter.java
+SVG_FILTER_NAME=SVG Image Files
+
+# Infix filter
+INFIX_FILTER_NAME=Infix Files
+
+# Flash filter
+FLASH_FILTER_NAME=Flash XML export
+
+# TXML filter
+TXML_FILTER_NAME=Wordfast TXML Files
+
+# org.omegat.filters3.xml.Handler
+XML_FATAL_ERROR=Error in file {0}, line {1}
+
+# org.omegat.filters3.xml.docbook.DocBookFilter
+DocBook_FILTER_NAME=DocBook Files
+
+DocBook_HINT=Note\: DocBook files are recognized not only by file extension, but they also must have a DOCTYPE declaration\: <\!DOCTYPE book PUBLIC \\"-//OASIS//DTD DocBook XML... for DocBook 4, or a Namespace\: xmlns="http\://docbook.org/ns/docbook" for DocBook 5
+
+# SrtFilter.java
+SRTFILTER_FILTER_NAME=SubRip Subtitles Files
+
+# AndroidFilter.java
+Android_FILTER_NAME=Android Resource Files
+
+# INIFilter.java
+
+INIFILTER_FILTER_NAME=Key\=Value Text Files
+
+# DokuWikiFilter.java
+
+DWFILTER_FILTER_NAME=DokuWiki Files
+
+# MagentoFilter.java
+MAGENTOFILTER_FILTER_NAME=Magento CE Locale CSV Files
+
+# org.omegat.filters3.xml.opendoc.OpenDocFilter
+
+OpenDoc_FILTER_NAME=OpenDocument/OpenOffice.org Files
+OpenDoc_FILTER_OPTIONS=OpenDocument Filter Options
+OpenDoc_TRANSLATE_ELEMENTS=Translate the following elements:
+OpenDoc_TRANSLATE_INDEXES=&Index entries
+OpenDoc_TRANSLATE_BOOKMARKS=&Bookmarks
+OpenDoc_TRANSLATE_BOOKMARKREFS=Bookmark &references
+OpenDoc_TRANSLATE_NOTES=&Notes
+OpenDoc_TRANSLATE_COMMENTS=&Comments
+OpenDoc_TRANSLATE_PRES_NOTES=&Presentation notes
+OpenDoc_TRANSLATE_LINKS=Links (&URL)
+OpenDoc_TRANSLATE_SHEET_NAMES=&Sheet Names
+OpenDoc_ERROR_IN_FILE=Error in file
+
+# org.omegat.filters3.xml.openxml.OpenXMLFilter
+
+OpenXML_FILTER_NAME=Microsoft Open XML Files
+OpenXML_FILTER_OPTIONS=Open XML Filter Options
+OpenXML_WORD=Word
+OpenXML_TRANSLATE_HIDDEN_TEXT=Non-visible Instruction Te&xt
+OpenXML_TRANSLATE_COMMENTS=Co&mments
+OpenXML_TRANSLATE_FOOTNOTES=&Footnotes
+OpenXML_TRANSLATE_ENDNOTES=&Endnotes
+OpenXML_TRANSLATE_HEADERS=He&aders
+OpenXML_TRANSLATE_FOOTERS=Foote&rs
+OpenXML_EXCEL=Excel
+OpenXML_TRANSLATE_EXCEL_COMMENTS=Comme&nts
+OpenXML_TRANSLATE_EXCEL_SHEET_NAMES=&Sheet Names
+OpenXML_POWER_POINT=Power Point
+OpenXML_TRANSLATE_SLIDE_COMMENTS=S&lide Comments
+OpenXML_TRANSLATE_SLIDE_MASTERS=Sli&de Masters
+OpenXML_TRANSLATE_SLIDE_LAYOUTS=Slide La&youts
+OpenXML_GLOBAL=Global
+OpenXML_TRANSLATE_CHARTS=C&harts
+OpenXML_TRANSLATE_DIAGRAMS=D&iagrams
+OpenXML_TRANSLATE_DRAWINGS=Dra&wings
+OpenXML_TRANSLATE_WORDART=WordAr&t
+OpenXML_GENERIC_OPTIONS=Other Options:
+OpenXML_AGGREGATE_TAGS=A&ggregate Tags
+OpenXML_PRESERVE_SPACES=&Preserve spaces for all tags
+
+OpenXML_ERROR_IN_FILE=Error in file
+
+# AboutDialog.java
+
+ABOUTDIALOG_VERSION=OmegaT version {0}
+
+ABOUTDIALOG_VERSION_UPDATE=OmegaT version {0}, update {1}
+
+ABOUTDIALOG_TITLE=About OmegaT
+ABOUTDIALOG_COPYRIGHT=Copyright \u00a9 2000-2012 Keith Godfrey, Maxym Mykhalchuk and others
+
+ABOUTDIALOG_LICENSE_BUTTON=&License
+ABOUTDIALOG_CONTRIBUTORS=\
+ OmegaT is a free and open source multiplatform Computer Assisted Translation tool with fuzzy matching, translation memory, keyword search, glossaries, and translation leveraging into updated projects.\n\nOmegaT is the original work of Keith Godfrey.\nMarc Prior is the coordinator of the OmegaT project.\n\nCode has been contributed by: \nZoltan Bartko, Volker Berlin, Didier Briel (development manager), Kim Bruning, Alex Buloichik (lead developer), Thomas Cordonnier, Sandra Jean Chua, Martin Fleurke, Wildrich Fourie, Jean-Christophe Helary, Thomas Huriaux, Hans-Peter Jacobs, Ibai Lakunza Velasco, Guido Leenders, Fabi\u00e1n Mandelbaum, John Moran, Maxym Mykhalchuk, Arno Peters, Henry Pijffers, Briac Pilpr\u00e9, Tiago Saboga, Andrzej Sawu\u0142a, Benjamin Siband, Rashid Umarov, Antonio Vilei, Martin Wunderlich and Michael Zakharov\n\nOther contributions are detailed in the readme.txt file\n\nOmegaT uses the following libraries:\n HTMLParser 1.6 by Somik Raha, Derrick Oswald and others (LGPL License)\n MRJ Adapter 1.0.8 by Steve Roy (LGPL License)\n VLDocking Framework 2.1.4 by VLSolutions (CeCILL License)\n Hunspell by L\u00e1szl\u00f3 N\u00e9meth and others (LGPL License)\n JNA by Todd Fast, Timothy Wall and others (LGPL License)\n Swing-Layout 1.0.2 (LGPL License)\n Jmyspell 2.1.4 (LGPL License) \n JAXB (GPLv2 + classpath exception)
+
+# LicenseDialog.java
+
+LICENSEDIALOG_TITLE=OmegaT license
+
+#Not sure if this should be translated or not.
+#In any case translated version should contain English original.
+LICENSEDIALOG_PREFACE=\
+ This program is free software; you can redistribute it and/or modify it \
+ under the terms of the GNU General Public License \
+ as published by the Free Software Foundation; either \
+ version 2 of the License, or (at your option) any later version.\n\n\
+ This program is distributed in the hope that it will be useful, \
+ but WITHOUT ANY WARRANTY; without even the implied warranty of \
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+
+# FilterEditor.java
+
+FILTEREDITOR_Edit_a_single_file_filter=Edit Filter
+
+FILTEREDITOR_really_delete_filter_instance=Confirm removal of pattern {0}
+
+FILTEREDITOR_Confirm_deletion_TITLE=Remove pattern?
+
+FILTEREDITOR_ERROR_Reverting_To_Def=Cannot reset the filter to default patterns.\n\n\
+ Exception occurred:\n
+
+FILTEREDITOR_BUTTON_To_Defaults=&Defaults
+
+FILTEREDITOR_File_Format=File &Format
+
+FILTEREDITOR_DESC=Here you may setup the source filename patterns of files \
+ the filter will process, customize the filenames of translated files, \
+ and select what encodings it will use for loading the file and saving \
+ its translated counterpart.\n\
+ Note: not all filters allow you to select an encoding.
+
+# FiltersCustomizer.java
+
+FILTERSCUSTOMIZER_TITLE=File Filters
+FILTERSCUSTOMIZER_TITLE_PROJECTSPECIFIC=Project Specific File Filters
+
+FILTERSCUSTOMIZER_CHECKBOX_PROJECTSPECIFIC=Enable project specific filters
+
+FILTERSCUSTOMIZER_DESCRIPTION=View or edit file filters. \
+ To edit what files in what encodings the filter will process, \
+ select the filter from the list and click Edit. \
+ If the filter has any options, you may change them by clicking Options.
+
+FILTERSCUSTOMIZER_BUTTON_EDIT_HINT=Edit Filter Patterns
+
+FILTERSCUSTOMIZER_BUTTON_OPTIONS=O&ptions...
+
+# InstanceEditor.java
+
+INSTANCEEDITOR_TITLE_ADD=Add Pattern
+
+INSTANCEEDITOR_TITLE_UPDATE=Edit Pattern
+
+INSTANCEEDITOR_SOURCE_MASK=Source Filename Pattern:
+
+INSTANCEEDITOR_SOURCE_ENCODING=Source File Encoding:
+
+INSTANCEEDITOR_Target_Encoding=Translated File Encoding:
+
+INSTANCEEDITOR_Substituted_Variable=Filename Variables:
+
+INSTANCEEDITOR_Target_Filename_Pattern=Translated Filename Pattern
+
+# org.omegat.core.threads.SaveThread
+#{0} -- hours, {1} -- minutes when the autosave happened
+ST_PROJECT_AUTOSAVED=Project autosaved on {0}
+
+# org.omegat.filters2.html2.*
+
+HTML__FILE_TOO_BIG=Too big HTML file!
+HTML__INVALID_HTML=Invalid HTML file
+
+HTML__FILTER_NAME=HTML and XHTML files
+
+HTML_NOTE=Note: Source File Encoding setting affects only the HTML files that \
+ have no encoding declaration inside. If HTML file has the encoding declaration, \
+ it will be used disregarding any value you set in this dialog.
+
+HTML_Filter_Options=(X)HTML Filter Options
+
+HTML_OPTION_REWRITE_ENC=Add or rewrite encoding declaration in HTML and XHTML files\:
+
+HTML_REWRITE_ENC_ALWAYS=&Always
+
+HTML_REWRITE_ENC_IF_HAS_HEADER=Only if (X)HTML file has a &header
+
+HTML_SKIPREGEXP=Skip text matching regular expression:
+
+HTML_ERROR_CUSTOMREGEXP_TITLE=Bad regular expression
+
+HTML_SKIPMETA=Do not translate the content attribute of meta-tags with \
+the following attribute key-value pairs (separate with commas):
+
+HTML_IGNORE_TAGS=Ignore the content of tags with \
+the following attribute key-value pairs (separate with commas):
+
+HTML_REWRITE_ENC_IF_HAS_META=Only if (X)HTML file has an &encoding declaration
+
+HTML_REWRITE_ENC_NEVER=&Never
+
+HTML_TRANSLATE_ATTRIBUTES=Translate the following attributes:
+HTML_TRANSLATE_HREF=href (URL of &links)
+HTML_TRANSLATE_SRC=src (URL of &images)
+HTML_TRANSLATE_LANG=lan&g (language attribute)
+HTML_TRANSLATE_HREFLANG=h&reflang (language of links)
+HTML_TRANSLATE_VALUE=&value (of form input, including button, submit and reset)
+HTML_TRANSLATE_BUTTON_VALUE=value (of button, &submit and reset input)
+
+HTML_PARAGRAPH_ON=Start a new paragraph on:
+HTML_PARAGRAPH_ON_BR=<&br> (breaks)
+
+HTML_EXC_EDIT_OPTIONS=Exception while editing options:
+
+# org.omegat.filters2.hhc
+
+HHC__FILTER_NAME=HTML Help Compiler files
+HHC__FILE_TOO_BIG=HHC file too big!
+HHC_NOTE=Note: Source File Encoding setting affects only the HHC and HHK files that \
+ do not contain an encoding declaration. If a HHC or HHK file has an encoding \
+ declaration, it will be used regardless of any value you specify in this dialog.
+
+# org.omegat.filters3.xml.xhtml
+
+XHTML_FILTER_NAME=XHTML Files
+XHTML_Filter_Options=XHTML Filter Options
+
+# org.omegat.core.segmentation.*
+
+# 0 - exceptions
+CORE_SRX_EXC_LOADING_SEG_RULES=Exceptions occurred while loading segmentation rules:
+
+CORE_SRX_ERROR_SAVING_SEGMENTATION_CONFIG=Error saving segmentation rules configuration:
+
+CORE_SRX_TABLE_HEADER_Language_Name=Language Name
+
+CORE_SRX_TABLE_HEADER_Language_Pattern=Language Pattern
+
+CORE_SRX_TABLE_COLUMN_Break=Break/Exception
+
+CORE_SRX_TABLE_COLUMN_Before_Break=Pattern Before
+
+CORE_SRX_TABLE_COLUMN_After_Break=Pattern After
+
+CORE_SRX_RULES_LANG_CATALAN=Catalan
+CORE_SRX_RULES_LANG_ENGLISH=English
+CORE_SRX_RULES_LANG_SPANISH=Spanish
+CORE_SRX_RULES_LANG_GERMAN=German
+CORE_SRX_RULES_LANG_ITALIAN=Italian
+CORE_SRX_RULES_LANG_JAPANESE=Japanese
+CORE_SRX_RULES_LANG_DUTCH=Dutch
+CORE_SRX_RULES_LANG_POLISH=Polish
+CORE_SRX_RULES_LANG_RUSSIAN=Russian
+CORE_SRX_RULES_LANG_DEFAULT=Default
+CORE_SRX_RULES_FORMATTING_TEXT=Text files segmentation
+CORE_SRX_RULES_FORMATTING_HTML=HTML, XHTML, ODF and Infix segmentation
+
+
+# org.omegat.segmentation.SegmentationCustomizer
+
+GUI_SEGMENTATION_TITLE=Segmentation Setup
+GUI_SEGMENTATION_TITLE_PROJECTSPECIFIC=Project Specific Segmentation Setup
+
+GUI_SEGMENTATION_NOTE=Note: All of the segmentation rule sets with a matching \
+ Language Pattern are applied in the given order.\n\
+ Thus, for example, rules for Canadian French (FR-CA) should be higher \
+ than rules for French (FR.*), and higher than Default (.*) ones. \
+ Then while translating from Canadian French your project \
+ will use all the rules defined for all the language chain \
+ in the correct order.
+
+GUI_SEGMENTATION_BUTTON_UP_2=Move U&p
+
+GUI_SEGMENTATION_BUTTON_DOWN_2=Move Do&wn
+
+GUI_SEGMENTATION_BUTTON_UP_1=Move &Up
+
+GUI_SEGMENTATION_BUTTON_DOWN_1=&Move Down
+
+GUI_SEGMENTATION_RULESETS=Sets of segmentation rules:
+
+GUI_SEGMENTATION_RULEORDER=Segmentation rules are applied in the following order:
+
+SEG_CONFIRM_REMOVE_SENTSEG_SET=Are you sure you want to remove the {0} set of segmentation rules?
+
+SEG_NEW_LN_CO=New Language and Country
+
+# org.omegat.gui.dialogs.TeamOptionsDialog
+
+GUI_TITLE_Team_Options=Team Options
+
+GUI_TEAM_DESCRIPTION=Please enter your name/ID. It is used to mark your translations.
+
+WF_OPTION_INSERT_AUTHOR_PREFIX=&Name/ID:
+
+# org.omegat.gui.dialogs.WorkflowOptionsDialog
+
+GUI_TITLE_Workflow_Options=Editing Behaviour Options
+
+GUI_WORKFLOW_DESCRIPTION=Please select what text you would like to be inserted \
+ into the segment that is not translated yet, when you move to it.
+
+WF_OPTION_INSERT_SOURCE=The &source text
+
+WF_OPTION_INSERT_NOTHTHING=&Leave the segment empty
+
+WF_OPTION_INSERT_FUZZY_MATCH=Insert the &best fuzzy match
+
+GUI_WORKFLOW_OPTION_Minimal_Similarity=&Minimal similarity:
+
+WF_OPTION_INSERT_FUZZY_PREFIX=&Prefix:
+
+WF_DEFAULT_PREFIX=[fuzzy]\
+
+WF_OPTION_ALLOW_TRANS_EQ_TO_SRC=&Allow translation to be equal to source
+WF_OPTION_EXPORT__CURRENT_SEGMENT=Export the segment to text files
+WF_OPTION_GOTO_NEXT_UNTRANSLATED=&Go To Next Untranslated Segment stops when there is at least one \
+ alternative translation
+WF_OPTION_CONVERT_NUMBERS=Attempt to convert &numbers when inserting a fuzzy match
+
+# org.omegat.gui.dialogs.ExternalTMXMatchesDialog.java
+EXT_TMX_TITLE=External TMX Options
+EXT_TMX_DESCRIPTION=Please select how tags of non-OmegaT TMXs should be displayed.
+EXT_TMX_SHOW_LEVEL2=&Display tags
+EXT_TMX_USE_XML=Use &XML for standalone tags (e.g., )
+
+# org.omegat.gui.dialogs.ViewOptionsDialog.java
+VIEW_OPTION_TITLE=View Options
+VIEW_OPTION_SOURCE=Display all &source segments in bold
+VIEW_OPTION_UNIQUE=Include the first non-&unique segment when marking non-unique segments
+
+# org.omegat.gui.dialogs.CreateGlossaryEntry.java
+CREATE_GLOSSARY_TITLE=Create Glossary Entry
+CREATE_GLOSSARY_DESCRIPTION=Enter a source term, a target term and a comment:
+CREATE_GLOSSARY_SOURCE=Source term:
+CREATE_GLOSSARY_TARGET=Target term:
+CREATE_GLOSSARY_COMMENT=Comment:
+CREATE_GLOSSARY_FILE=Glossary file: {0}
+
+# org.omegat.gui.dialogs.ProxyLoginDialog.java
+PROXY_LOGIN_TITLE=Proxy User and Password
+PROXY_LOGIN_DESCRIPTION=If you are using an authenticated proxy, please enter here your user and password.
+PROXY_LOGIN_USER=User:
+PROXY_LOGIN_PASSWORD=Password:
+LOG_DECODING_ERROR=Error decoding user and password.
+
+# org.omegat.gui.dialogs.TagValidationOptionsDialog
+
+GUI_TITLE_TagValidation_Options=Tag Validation Options
+
+GUI_TAGVALIDATION_DESCRIPTION=OmegaT can also check for programming variables (printf-function variables) like '%s'. \
+Please select which behaviour is appropriate. Full checking can lead to false positives in normal texts.
+
+TV_OPTION_NO_CHECK=&Do not check printf-variables
+
+TV_OPTION_SIMPLE_CHECK=&Check simple printf-variables (e.g., %s, %d)
+
+TV_OPTION_FULL_CHECK=Check &all printf-variables (e.g., %s, %-s)
+
+TV_OPTION_JAVA_PATTERN=Check simple &java MessageFormat patterns (e.g. \{0\})
+
+TV_OPTION_CUSTOMPATTERN=Custom tag(s) regular expression:
+
+TV_OPTION_REMOVEPATTERN=Fragment(s) that should be removed from translation regular expression:
+
+TV_OPTION_ERROR_CUSTOMREGEXP_TITLE=Bad regular expression
+
+# org.omegat.gui.main.MainWindow / Docking
+
+GUI_MATCHWINDOW_SUBWINDOWTITLE_Fuzzy_Matches=Fuzzy Matches
+
+GUI_MATCHWINDOW_explanation=Displays the translation memories segments that match the source segment. Matches can be found in your current translation or in the TMX files that you have put in the /tm/ folder.
+
+GUI_MATCHWINDOW_SUBWINDOWTITLE_Glossary=Glossary
+
+GUI_GLOSSARYWINDOW_explanation=Displays the glossary entries found in the glossary files located in the /glossary/ folder if they are present in the source segment. You can create glossary entries with Create Glossary Entry in the Edit menu.
+
+GUI_MATCHWINDOW_SUBWINDOWTITLE_Dictionary=Dictionary
+
+GUI_DICTIONARYWINDOW_explanation=Displays the dictionary entries found in the dictionary files located in the /dictionary/ folder if they are present in the source segment.
+
+GUI_MATCHWINDOW_SUBWINDOWTITLE_MachineTranslate=Machine Translation
+
+GUI_MACHINETRANSLATESWINDOW_explanation=Displays the translation of the source segment by the machine translation services you have selected in Options > Machine Translate, if those services are available.
+
+GUI_NOTESWINDOW_SUBWINDOWTITLE_Notes=Notes
+
+GUI_NOTESWINDOW_explanation=Allows to view, add, remove or edit a note in the active segment. A note is just a comment regarding this set of source text and translation.
+
+GUI_COMMENTSWINDOW_SUBWINDOWTITLE_Comments=Comments
+
+GUI_COMMENTSWINDOW_explanation=Displays comments in the active segment if they exist in the source file and the file filter supports it (e.g. PO-filter).
+
+GUI_COMMENTSWINDOW_FIELD_ID=Key:
+
+GUI_COMMENTSWINDOW_FIELD_Path=Path:
+
+GUI_COMMENTSWINDOW_FIELD_Comment=Comment:
+
+GUI_COMMENTSWINDOW_FIELD_Translation=Translation:
+
+# 0 - filename
+GUI_SUBWINDOWTITLE_Editor=Editor - {0}
+
+DOCKING_HINT_DOCK=Dock
+
+DOCKING_HINT_MINIMIZE=Minimize
+
+DOCKING_HINT_MAXIMIZE=Maximize
+
+DOCKING_HINT_RESTORE=Restore
+
+DOCKING_HINT_UNDOCK=Undock
+
+DOCKING_INSTANT_START_TITLE=Instant Start
+
+
+# StaticUtils
+
+SU_USERHOME_PROP_ACCESS_ERROR=OmegaT is refused access to the system property containing\n\
+ the name of your OS and/or the system property containing\n\
+ your home folder. Therefore, the location of OmegaT's\n\
+ configuration folder cannot be reliably determined. The\n\
+ current folder will be used instead. As a result of this,\n\
+ all settings will be at their defaults, due to which you\n\
+ may experience unexpected, but correct behaviour.
+
+SU_CONFIG_DIR_CREATE_ERROR=Your operating system refused to let OmegaT\n\
+ create its configuration folder. The current folder will be used\n\
+ instead. If later access to the desired location is granted\n\
+ that location will be used and all settings will return to\n\
+ their defaults as a result of the location change.
+
+SU_SCRIPT_DIR_CREATE_ERROR=It was not possible to create the script folder\n\
+ inside the configuration folder. The configuration folder will be used\n\
+ instead.
+
+# Log
+
+LOG_LEVEL_SEVERE=Error
+
+LOG_LEVEL_WARNING=Warning
+
+LOG_LEVEL_INFO=Info
+
+LOG_STARTUP_INFO=Java: {0} ver. {1}, executed from '{2}'
+
+LOG_MENU_CLICK=Click on '{0}' menu item
+
+
+LOG_INFO_EVENT_PROJECT_CHANGE=Event: project change - "{0}"
+LOG_INFO_EVENT_APPLICATION_STARTUP=Event: application startup
+LOG_INFO_EVENT_APPLICATION_SHUTDOWN=Event: application shutdown
+LOG_INFO_EVENT_ENTRY_NEWFILE=Event: new file activated ({0})
+LOG_INFO_EVENT_ENTRY_ACTIVATED=Event: new entry activated
+LOG_INFO_EVENT_FONT_CHANGED=Event: font changed
+LOG_ERROR_MUST_BE_SWING_THREAD=This call MUST be in swing thread
+LOG_ERROR_MUSTNOT_BE_SWING_THREAD=This call MUST NOT be in swing thread
+
+LOG_DATAENGINE_LOAD_START=Project loading start
+LOG_DATAENGINE_LOAD_END=Project loading end
+LOG_DATAENGINE_SAVE_START=Project saving start
+LOG_DATAENGINE_SAVE_END=Project saving end
+LOG_DATAENGINE_SAVE_NONEED=No need to save project, because no changes were made
+LOG_DATAENGINE_CLOSE=Project closed
+LOG_DATAENGINE_COMPILE_START=Project compiling start
+LOG_DATAENGINE_COMPILE_END=Project compiling end
+LOG_DATAENGINE_CREATE_START=Project creating start
+LOG_DATAENGINE_CREATE_END=Project creating end
+
+
+# Spellchecker
+
+SC_NO_SUGGESTIONS=No Suggestions
+
+SC_IGNORE_ALL=Ignore All
+
+SC_ADD_TO_DICTIONARY=Add To Dictionary
+
+# org.omegat.gui.dialogs.Spellchecker[Configuration]Dialog
+
+GUI_SPELLCHECKER_TITLE=Spellchecker Setup
+
+GUI_SPELLCHECKER_AUTOSPELLCHECKCHECKBOX=&Automatically check the spelling of text
+
+GUI_SPELLCHECKER_AVAILABLE_LABEL=Dictionaries already installed:
+
+GUI_SPELLCHECKER_DICTIONARYLABEL=Dictionary file folder:
+
+GUI_SPELLCHECKER_FILE_CHOOSER_TITLE=Dictionary File Folder
+
+GUI_SPELLCHECKER_DIRECTORYCHOOSERBUTTON=&Choose...
+
+GUI_SPELLCHECKER_INSTALLBUTTON=&Install new dictionary...
+
+GUI_SPELLCHECKER_UNINSTALLBUTTON=&Remove
+GUI_SPELLCHECKER_URL_LABEL=URL of online dictionaries:
+
+GUI_SPELLCHECKER_UNINSTALL_CURRENT=You are uninstalling the spellchecking dictionary that your project currently uses. Proceed?
+
+GUI_SPELLCHECKER_UNINSTALL_CURRENT_TITLE=Confirm uninstalling
+
+GUI_SPELLCHECKER_UNINSTALL_UNABLE=Unable to uninstall the selected dictionary
+
+GUI_SPELLCHECKER_UNINSTALL_UNABLE_TITLE=Uninstalling failed
+
+GUI_SPELLCHECKER_INSTALL_UNABLE_TITLE=Installing failed
+
+GUI_SPELLCHECKER_INSTALL_UNABLE=Please select a dictionary file folder first
+
+# {0} is the segment number
+GUI_SPELLCHECKER_SOURCE_LABEL=&Source (segment {0}):
+
+# org.omegat.gui.dialogs.DictionaryInstallerDialog
+
+GUI_DICTIONARY_INSTALLER_TITLE=Dictionary Installer
+
+GUI_DICTIONARY_INSTALLER_TEXT_GO=Please select the dictionaries you want to install and press the Install button.
+
+GUI_DICTIONARY_INSTALLER_TEXT_NOTHING=No new dictionaries available at the remote server.
+
+GUI_DICTIONARY_INSTALLER_INSTALL=Install
+
+
+GUI_DICTIONARY_INSTALLER_AVAILABLE=Available dictionaries:
+
+# switch case
+
+TF_EDIT_MENU_SWITCH_CASE=S&witch Case To
+
+TF_EDIT_MENU_SWITCH_CASE_TO_LOWER=&Lower Case
+
+TF_EDIT_MENU_SWITCH_CASE_TO_UPPER=&Upper Case
+
+TF_EDIT_MENU_SWITCH_CASE_TO_TITLE=&Title Case
+
+TF_EDIT_MENU_SWITCH_CASE_CYCLE=&Cycle
+
+# view menu
+
+MW_VIEW_MENU=&View
+
+MW_VIEW_MENU_DISPLAY_SEGMENT_SOURCES=Display &Source Segments
+
+MW_VIEW_MENU_MARK_NON_UNIQUE_SEGMENTS=Mark Non-&Unique Segments
+
+MW_VIEW_MENU_MARK_NOTED_SEGMENTS=Mark Segments &with Notes
+
+MW_VIEW_MENU_MODIFICATION_INFO=&Modification Info
+
+MW_VIEW_MENU_MODIFICATION_INFO_NONE=Display &None
+
+MW_VIEW_MENU_MODIFICATION_INFO_SELECTED=Display for Current &Segment
+
+MW_VIEW_MENU_MODIFICATION_INFO_ALL=Display for &All Segments
+
+MW_VIEW_MENU_MARK_NBSP=Mark &Non-breakable Spaces
+
+# matches text area popup menu
+
+MATCHES_GO_TO_SEGMENT_SOURCE=Go To Segment Source
+
+MATCHES_INSERT=Insert Match Into Translation
+
+MATCHES_REPLACE=Replace Translation with Match
+
+MATCHES_FUZZY_MARK=[Fuzzy]
+
+# Dictionary area popup menu
+DICTIONARY_HIDE=Hide '{0}'
+
+STARTUP_ERRORBOX_TITLE=Error on application startup
+STARTUP_JAXB_LINKAGE_ERROR=You need to update your JDK 1.6 to the latest version, or just remove the jaxb-*.jar files from the OmegaT /lib dir
+
+# Cut, Copy, Paste Popup menu
+CCP_CUT=Cut
+CCP_COPY=Copy
+CCP_PASTE=Paste
+
+# Machine translation engines
+MT_ENGINE_GOOGLE2=Google Translate v2
+MT_ENGINE_BELAZAR=Belazar
+MT_ENGINE_APERTIUM=Apertium
+
+APERTIUM_ERROR=Error {0}: {1}
+GOOGLE_API_KEY_NOTFOUND=Google Api key not available. See OmegaT manual for instructions.
+
+# LanguageTool
+LT_OPTIONS_MENU_ENABLED=Language Checker
+
+# org.omegat.gui.dialogs.TeamOptionsDialog
+PROXY_LOGIN_DIALOG=Proxy User and Password
+
+# Multiple translations
+MULT_TITLE=Multiple Translations
+GUI_MULTIPLETRANSLATIONSWINDOW_explanation=Displays alternative translations that you have created for segments that are repeated in the project.
+
+MULT_MENU_DEFAULT=Use as Default Translation
+MULT_MENU_MULTIPLE=Create Alternative Translation
+MULT_POPUP_DEFAULT=Use as Default Translation
+MULT_POPUP_REPLACE=Replace Translation with Text
+MULT_POPUP_GOTO=Go To Segment Source
+
+# Manage translation popup menu
+TRANS_POP_EMPTY_TRANSLATION=Set empty translation
+TRANS_POP_REMOVE_TRANSLATION=Remove translation
+
+# Empty translation display in the Editor
+EMPTY_TRANSLATION=
+
+# ScriptWindow
+SCW_TITLE=Scripting
+SCW_SCRIPT_FILE=&File
+SCW_LOAD_FILE=&Open Script...
+SCW_SCRIPT=Script &Language
+SCW_RUN_SCRIPT=&Run
+SCW_RESULT=Result:
+SCW_RUNNING_SCRIPT=The script "{0}" is running...
+SCW_SCRIPT_ERROR=An error occured
+SCW_CLOSE=&Quit
+SCW_LIST_ENGINES=Available script engines:
+SCW_BEAN_ERROR=ERROR: (declaring bean)
+SCW_SCRIPT_LOADED={0} loaded.
+SCW_SCRIPTS_FOLDER=Scripts Folder:
+SCW_SCRIPTS_FOLDER_CHOOSE=&Choose...
+SCW_SCRIPTS_FOLDER_CHOOSE_TITLE=Scripts Folder
+SCW_NO_SCRIPT_SELECTED=No script selected.
+SCW_CANNOT_READ_SCRIPT=Cannot read selected script file.
+SCW_SELECTED_LANGUAGE=Selected Engine: {0}
+SCW_REFRESH_SCRIPT_DIR=Refreshing script directory "{0}"
+SCW_SAVE_SCRIPT=Save Script
+SCW_SAVE_ERROR=Error while trying to save script.
+SCW_SAVE_OK=Script "{0}" saved.
+SCW_QUICK_RUN=Run script on slot #{0}.
+SCW_NO_SCRIPT_SET=No script set.
+SCW_NO_SCRIPT_BOUND=No script bound in slot #{0}.
+SCW_ADD_SCRIPT=Add Script
+SCW_REMOVE_SCRIPT=Remove Script
+SCW_SAVE_QUICK_SCRIPT=Script "{0}" bound to slot #{1}.
+SCW_REMOVED_QUICK_SCRIPT=Script "{0}" unbound from slot #{1}.
+SCW_SCRIPTS_NONE=
+
+
+# PO-Filter
+POFILTER_TRANSLATOR_COMMENTS=Translator comments:
+POFILTER_EXTRACTED_COMMENTS=Extracted comments:
+POFILTER_REFERENCES=References:
+
+# HTML-Filter
+HTMLFILTER_TAG=Tag:
+HTMLFILTER_ATTRIBUTE=Attribute:
+
+# Console output:
+CONSOLE_INITIALIZING=Initializing
+CONSOLE_TAGVALIDATION_FAIL=Tag validation failed
+CONSOLE_TRANSLATING=Translating Project
+CONSOLE_FINISHED=Finished
+CONSOLE_VALIDATING_TAGS=Validating tags
+CONSOLE_TAGVALIDATION_ABORT=Aborted.
+CONSOLE_CREATE_PSEUDOTMX=Create pseudo-translate TMX
+CONSOLE_TRANSLATED_FILES_LOC_UNDEFINED=Translated files location not defined
+CONSOLE_ALIGN_AGAINST=Align project against {0}
+CONSOLE_LOADING_PROJECT=Loading Project
+CONSOLE_PROJECT_NOT_VERIFIED=The project cannot be verified
+
+# Project exceptions
+PROJECT_SOURCE_FOLDER=Source folder {0} does not exist.
+PROJECT_TARGET_FOLDER=Target folder {0} does not exist.
+PROJECT_GLOSSARY_FOLDER=Glossary folder {0} does not exist.
+PROJECT_TM_FOLDER=Translation memory folder {0} does not exist.
+PROJECT_W_GLOSSARY=The writeable glossary file is not in the glossary folder.
+
+# Save options
+SAVE_DIALOG_TITLE=Save Options
+SAVE_DIALOG_DESCRIPTION=Please select the interval at which the project should be saved automatically, in minutes and seconds.
+SAVE_DIALOG_MINUTES=Minutes:
+SAVE_DIALOG_SECONDS=Seconds:
+
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Minimal/target/.ignoreme b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Minimal/target/.ignoreme
new file mode 100644
index 0000000..e69de29
diff --git a/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Minimal/tm/.ignoreme b/OmegaT/build/l10n/OmegaT_2.5.4_01_L10N_Minimal/tm/.ignoreme
new file mode 100644
index 0000000..e69de29
diff --git a/OmegaT/dist2/OmegaT_2.5.4_01_L10N_Full.zip b/OmegaT/dist2/OmegaT_2.5.4_01_L10N_Full.zip
new file mode 100644
index 0000000..dceec56
Binary files /dev/null and b/OmegaT/dist2/OmegaT_2.5.4_01_L10N_Full.zip differ
diff --git a/OmegaT/dist2/OmegaT_2.5.4_01_L10N_Minimal.zip b/OmegaT/dist2/OmegaT_2.5.4_01_L10N_Minimal.zip
new file mode 100644
index 0000000..c65f5f1
Binary files /dev/null and b/OmegaT/dist2/OmegaT_2.5.4_01_L10N_Minimal.zip differ
diff --git a/OmegaT/dist2/OmegaT_2.5.4_01_Source.zip b/OmegaT/dist2/OmegaT_2.5.4_01_Source.zip
new file mode 100644
index 0000000..3c3c16e
Binary files /dev/null and b/OmegaT/dist2/OmegaT_2.5.4_01_Source.zip differ
diff --git a/OmegaT/doc_src/Readme.txt b/OmegaT/doc_src/Readme.txt
new file mode 100644
index 0000000..f05f450
--- /dev/null
+++ b/OmegaT/doc_src/Readme.txt
@@ -0,0 +1,116 @@
+***License***
+
+All the files in this directory and below are under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
+
+***Installation***
+
+The creation of the documentation requires a number of tools:
+
+- DocBook XSL Stylesheets 1.75.2 ("dbk")
+- DocBook XML 4.5
+- fop 0.95
+- libxml2 2-2.7.7
+- Saxon 6-5-5
+- Ant 1.7.1 or above
+
+For efficiency reason, the path to the DTD in the DocBook files (e.g., AboutOmegaT.xml) has been changed to a local path (../../../docbook-xml-4.5/docbookx.dtd instead of an http:// reference). Depending on the actual configuration, it might be changed to a standard reference ("http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd") or to another local reference.
+
+***Windows***
+
+dbk must be installed at the root of c:\
+
+c:\dbk\common
+c:\dbk\docsrc
+etc.
+
+Docbook-xml-4.5 must be installed at the same level as your OmegaT development folder.
+
+So, if you have
+
+c:\dev\omegat-trunk
+c:\dev\omegat-trunk\src
+c:\dev\omegat-trunk\doc_src
+etc.
+
+you would have
+
+c:\dev\docbook-xml-4.5\ent
+c:\dev\docbook-xml-4.5\calstblx.dtd
+etc.
+
+libxml2-2.7.7 and apache-ant must be installed where a path can find them, usually in Program Files.
+C:\Program Files\libxml2-2.7.7.win32
+C:\Program Files\apache-ant\bin
+
+Corresponding path:
+path=C:\Program Files\libxml2-2.7.7.win32\bin;C:\Program Files\apache-ant\bin
+
+fop-0.95 can be installed anywhere, usually in Program Files.
+C:\Program Files\fop-0.95
+
+The location of fop-0.95, dbk and Saxon must be set in build.xml, in the corresponding properties:
+
+
+
+
+The location of dbk must also be set in docbook-utf8.xsl:
+
+
+***Mac OSX***
+
+All the dependencies can be installed through Macports except for Saxon 6-5-5
+
+Macports:
+http://www.macports.org/
+
+Saxon 6-5-5
+https://sourceforge.net/projects/saxon/files/saxon6/6.5.5/
+Unzip the downloaded package and put it in your prefered location. The example below uses the /Applications/ folder.
+
+If you use Macports, the build.xml settings are:
+
+
+
+
+
+and the docbook-utf8.xsl settings are:
+
+
+
+The DocBook 4.5 DTD is located here:
+/opt/local/var/macports/software/docbook-xml-4.5/4.5_0/opt/local/share/xml/docbook/4.5/
+
+Copy the /4.5/ folder to the folder that is three folders "higher" than the DocBook documentation source files in your folder tree and rename it /docbook-xml-4.5/.
+
+So, if you have your DocBook documentation source files in:
+/path/to/omegat/branches/release-2-3/doc_src/hu/
+
+The /docbook-xml-4.5/ folder should be copied inside /branches/:
+/path/to/omegat/branches/docbook-xml-4.5/
+
+
+***Usage***
+
+All the scripts require the language folder as argument.
+
+E.g.:
+Building Instant Start only
+ant -Dlanguage=en instant-start
+
+Building everything except Javahelp:
+ant -Dlanguage=en
+
+Building HTML
+ant -Dlanguage=en html
+
+Building PDF
+ant -Dlanguage=en pdf
+
+Building Javahelp
+ant -Dlanguage=en javahelp
+
+***Scripts***
+
+build.xml: Main script.
+
+docbook-utf8.xsl: Allows to issue the Instant Start Guide in UTF-8.
\ No newline at end of file
diff --git a/OmegaT/doc_src/build.xml b/OmegaT/doc_src/build.xml
new file mode 100644
index 0000000..1fea585
--- /dev/null
+++ b/OmegaT/doc_src/build.xml
@@ -0,0 +1,191 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/OmegaT/doc_src/docbook-utf8.xsl b/OmegaT/doc_src/docbook-utf8.xsl
new file mode 100644
index 0000000..cb10187
--- /dev/null
+++ b/OmegaT/doc_src/docbook-utf8.xsl
@@ -0,0 +1,12 @@
+
+
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/en/AboutOmegaT.xml b/OmegaT/doc_src/en/AboutOmegaT.xml
new file mode 100644
index 0000000..705d57c
--- /dev/null
+++ b/OmegaT/doc_src/en/AboutOmegaT.xml
@@ -0,0 +1,229 @@
+
+
+
+ About <application>OmegaT</application> - introduction
+
+
+ OmegaT highlights
+
+ OmegaT is a free multi platform Computer
+ Aided Translation tool, with the following highlights:
+
+
+
+ Translation
+ memory:OmegaT stores your
+ translations in a translation memory file. At the same time, it can
+ use memories files from previous translations for reference.
+ Translation memories can be very useful in a translation where there
+ are numerous repetitions or reasonably similar segments of text.
+ OmegaT uses translation memories to store your previous translations
+ and then suggest likely translations for the text you are currently
+ working on.
+
+ These translation memories can be very useful when a document
+ that has already been translated needs to be updated. Unchanged
+ sentences are automatically translated, while updated sentences are
+ shown with the translation of the most similar, older sentence.
+ Modifications to the original document are thus handled with greater
+ ease. If you are supplied with previously created translation memories
+ , for example by your translation agency or your client, OmegaT is
+ able to use these as reference memories.
+
+ OmegaT uses the standard tmx file format to store and access
+ translation memories, which guarantees that you can exchange your
+ translation material with other CAT applications supporting this file
+ format.
+
+
+
+
+
+ Terminology management:
+ Terminology management is important for translation consistency.
+ OmegaT uses glossaries containing translations of single words or
+ small phrases: a simplified bilingual dictionary for a specific
+ domain. For your reference, OmegaT displays the translation of any
+ words that happen to be present in the segment that currently has
+ focus.
+
+
+
+
+
+ Translation process: Imagine
+ having to translate something; from a single file to a folder
+ containing subfolders each with a number of files in a variety of
+ formats. When you let OmegaT know the files that you need to
+ translate, it looks for the files it understands based on file
+ filtering rules, recognizes the textual parts within them, splits up
+ the text groups according to the segmentation rules, and displays the
+ segments one by one so that you can proceed with the translation.
+ OmegaT stores your translations and proposes possible translations
+ from similar segments in previous memory files. When you are ready to
+ view the final product, you can export the translated files, open them
+ in the appropriate application and view the translation in the final
+ format...
+
+
+
+
+
+ Summary of chapters
+
+ This documentation is intended both as a tutorial and as a reference
+ guide. Here is a short summary of the chapters and their contents.
+
+
+
+ Instant start guide: this
+ chapter is intended as an Instant Start Guide for beginners and “tyre
+ kickers”, showing the complete procedure from opening a new
+ translation project through to completing the translation.
+
+
+
+
+
+ Installing and running OmegaT:
+ this chapter is useful when you first begin using OmegaT.
+ It contains the specific instructions on how to install OmegaT and run
+ it on Windows, Mac OS X and Linux. For advanced users, the chapter
+ describes the command line mode and its possibilities.
+
+
+
+
+
+ The user interface,Main Menu and Keyboard Shortcuts: these two
+ chapters are likely to be heavily consulted, since they explain the
+ user interface of OmegaT and the functions available via the main menu
+ and the keyboard shortcuts.
+
+
+
+
+
+ Project properties, OmegaT Files and
+ Directories: a project in the context of OmegaT is the
+ piece of work that OmegaT as a CAT tool is able to handle. This
+ chapter describes the project properties, such as the source and
+ target languages. The second of these chapters describes the various
+ subfolders and files in a translation project and their role as well
+ as other user and application files associated with OmegaT.
+
+
+
+
+
+ Editing field behavior: a short
+ chapter describing how to set up the editing behavior of the segment
+ being translated.
+
+
+
+
+
+ Working with plain text and
+ Working with formatted text: these
+ two chapters explain certain important points concerning texts to be
+ translated, such as the encoding set (in the case of plain text files)
+ and tag handling (in the case of formatted text).
+
+
+
+
+
+ Translation memories: explains
+ the role of the various subdirectories containing translation
+ memories, and provides information on other important aspects relating
+ to translation memories.
+
+
+
+ Segmentation:translation memory
+ tools work with textual units called segments. In OmegaT, segments can
+ be based on paragraphs or on segmentation rules. Paragraph
+ segmentation is less frequently used, but can be useful in cases of
+ so-called "creative" texts, The rule-based segmentation is usually
+ synonymous with sentence-based segmentation. A number of rule sets are
+ provided while additional rules can be defined by the user, as
+ described in this chapter.
+
+
+
+ Searches andRegular
+ expressions: Searches in OmegaT can be as simple as
+ "list segments with the word 'kangaroo'
+ ". They can also be complex, allowing for instance to
+ search for segments with two or more consecutive spaces. In this case
+ the regular expression ^s^s+ would be used to find and list the
+ offending segments. Regular expressions are also used extensively in
+ the segmentation rules.
+
+
+
+ Dictionaries, Glossaries,
+ Machine translation and Spellchecker: OmegaT enables the extensive of
+ dictionaries and glossaries. If an Internet connection is available,
+ various MT services such as Google Translate can be utilized from
+ within OmegaT. If spell checking is activated, spelling mistakes and
+ typos are recognized and can be corrected during translation.
+
+
+
+ Miscellanea: deals with other
+ issues of interest, such as how to avoid losing data.
+
+
+
+ Appendices contain the
+ following information
+
+
+
+ OmegaT on the web:
+ information regarding on-line OmegaT resources
+
+
+
+
+
+ Languages: contains the ISO
+ list of languages and language codes
+
+
+
+
+
+ Keyboard shortcuts in the
+ editor: the list of shortcuts used in the editor
+
+
+
+ Shortcuts
+ customization:shortcuts can be customized to suit your
+ personal preferences
+
+
+
+
+
+ Legal notices
+
+
+
+
+
+ Keyword index: an extensive
+ keyword index is provided to help the reader find the relevant
+ information.
+
+
+
+
diff --git a/OmegaT/doc_src/en/App_Aknowledgements.xml b/OmegaT/doc_src/en/App_Aknowledgements.xml
new file mode 100644
index 0000000..50b72f2
--- /dev/null
+++ b/OmegaT/doc_src/en/App_Aknowledgements.xml
@@ -0,0 +1,60 @@
+
+
+
+ Acknowledgements
+
+
+ Thank you all!
+
+ Whatever the inconsistencies, omissions and straightforward errors
+ you may find in the present version, I declare them all my own. This
+ manual, however, would not be possible without the help and support from a
+ number of people. Explicit thanks to:
+
+
+
+ Mark Prior: correcting my first draft was an act of love for
+ OmegaT and the English language.
+
+
+
+
+
+ Didier Briel: I could not do without Didier's patient and
+ persistent help with DocBook intricacies. Not to mention his care and
+ diligence, keeping repositories intact and in good order.
+
+
+
+ Samuel Murray: for the introductory chapter "Learn to use OmegaT
+ in 5 minutes" .
+
+
+
+
+
+ Will Helton: his final reading of the draft has spared me a lot
+ of embarrassment. One could only wonder, how many the and a
+ prepositions would still be missing without his invaluable
+ help.
+
+
+
+
+
+ Jean-Christophe Helary: special thanks to JC for his concise
+ description of OmegaT run, command line parameters and all other
+ details, I have yet to notice.
+
+
+
+ Last but not least: my thanks to all the contributors to
+ OmegaT documentation tracker for all the inconsistencies found
+ in the previous versions of the documentation. Keep up your good
+ work!
+
+
+
+
diff --git a/OmegaT/doc_src/en/App_Keyboard.xml b/OmegaT/doc_src/en/App_Keyboard.xml
new file mode 100644
index 0000000..7512fef
--- /dev/null
+++ b/OmegaT/doc_src/en/App_Keyboard.xml
@@ -0,0 +1,196 @@
+
+
+
+ Keyboard shortcuts in the editor
+
+ This short text describes key behavior in the editor pane. The term
+ "Move to inside segment" means, that the cursor moves to the beginning of
+ the segment if it was previously before the segment, and to the end of the
+ segment if it was previously after it.
+
+
+ Key behavior in the editor
+
+
+
+
+
+
+
+
+ Key combination
+
+ Action
+
+
+
+
+
+ Left:
+
+ one char left, but not further than the beginning of
+ segment
+
+
+
+ Right:
+
+ one char right, but not further than the end of
+ segment
+
+
+
+ Ctrl+Left:
+
+ one word left, but not further than the beginning of
+ segment
+
+
+
+ Ctrl+Right:
+
+ one word right, but not further than the end of
+ segment
+
+
+
+ PgUp:
+
+ page up through the document
+
+
+
+ PgDn:
+
+ page down through the document
+
+
+
+ Home*
+
+ move to the beginning of the line in the segment
+
+
+
+ End*
+
+ move to the end of the line in the segment
+
+
+
+ Ctrl+Home
+
+ move to the start of the segment
+
+
+
+ Ctrl+End
+
+ move to the end of the segment
+
+
+
+ Ctrl+PgUp
+
+ move to the start of the document (Mac: Cmd+PgUp)
+
+
+
+ Ctrl+PgDn
+
+ move to the end of the document (Mac: Cmd+PgDn)
+
+
+
+ Backspace*
+
+ remove char before cursor
+
+
+
+ Delete*
+
+ remove char after cursor
+
+
+
+ Ctrl+Backspace
+
+ remove chars up to the start of the current word (Mac:
+ Alt+Backspace)
+
+
+
+ Ctrl+Delete
+
+ remove chars up to the start of next word (Mac: Alt+Delete)
+
+
+
+ Ctrl+Enter
+
+ open previous segment (Mac: Cmd+Enter)
+
+
+
+ Ctrl+A
+
+ select complete segment (Mac: Cmd+A)
+
+
+
+ Ctrl+Shift+O
+
+ RTL-LTR switch
+
+
+
+
+
+ * These keys behave differently when the cursor is outside the
+ editable segment:
+
+
+
+ Home: cursor to the beginning of
+ the active segment
+
+
+
+ End: cursor to the end of the
+ active segment
+
+
+
+ Backspace: nothing
+
+
+
+ Delete: nothing
+
+
+
+ Any char key, if clicked outside
+ editable segment, will be ignored.
+
+
+
+ The "Shift" key doesn't exhibit any special behavior per se: when the
+ "Shift" key is pressed, all keys move the cursor in their usual
+ manner.
+
+ System-wide commands: Paste (Ctrl+V
+ or Ctrl+Insert), Cut (Ctrl+X or Ctrl+C),
+ Insert match (Ctrl+I) and Insert source
+ (Ctrl+Shift+I) act in principle on any
+ selection, including those that extend beyond the current segment. In such a
+ case the selection will of course be pared down to segment
+ boundaries.
+
diff --git a/OmegaT/doc_src/en/App_Languages.xml b/OmegaT/doc_src/en/App_Languages.xml
new file mode 100644
index 0000000..2d1365e
--- /dev/null
+++ b/OmegaT/doc_src/en/App_Languages.xml
@@ -0,0 +1,961 @@
+
+
+
+ Languages - ISO 639 code list
+ <indexterm class="singular">
+ <primary>Languages</primary>
+ </indexterm>
+ <indexterm class="singular">
+ <primary>ISO language codes</primary>
+ </indexterm>
+ <indexterm class="singular">
+ <primary>Project</primary>
+ <secondary>Properties</secondary>
+ <seealso>Languages</seealso>
+ </indexterm>
+
+
+ Please check the
+ ISO 639 Code Tables for further and up-to-date information about
+ language codes.
+
+
+ ISO 639-1/639-2 Language code list
+
+
+
+
+
+
+ Language name
+ ISO 639-1
+ ISO 639-2
+
+
+
+
+ Abkhaz
+ ab
+ abk
+
+
+ Afar
+ aa
+ aar
+
+
+ Afrikaans
+ af
+ afr
+
+
+ Akan
+ ak
+ aka
+
+
+ Albanian
+ sq
+ sqi
+
+
+ Amharic
+ am
+ amh
+
+
+ Arabic
+ ar
+ ara
+
+
+ Aragonese
+ an
+ arg
+
+
+ Armenian
+ hy
+ hye
+
+
+ Assamese
+ as
+ asm
+
+
+ Avaric
+ av
+ ava
+
+
+ Avestan
+ ae
+ ave
+
+
+ Aymara
+ ay
+ aym
+
+
+ Azerbaijani
+ az
+ aze
+
+
+ Bambara
+ bm
+ bam
+
+
+ Bashkir
+ ba
+ bak
+
+
+ Basque
+ eu
+ eus
+
+
+ Belarusian
+ be
+ bel
+
+
+ Bengali
+ bn
+ ben
+
+
+ Bihari
+ bh
+ bih
+
+
+ Bislama
+ bi
+ bis
+
+
+ Bosnian
+ bs
+ bos
+
+
+ Breton
+ br
+ bre
+
+
+ Bulgarian
+ bg
+ bul
+
+
+ Burmese
+ my
+ mya
+
+
+ Catalan
+ ca
+ cat
+
+
+ Chamorro
+ ch
+ cha
+
+
+ Chechen
+ ce
+ che
+
+
+ Chichewa, Chewa, Nyanja
+ ny
+ nya
+
+
+ Chinese
+ zh
+ zho
+
+
+ Chuvash
+ cv
+ chv
+
+
+ Cornish
+ kw
+ cor
+
+
+ Corsican
+ co
+ cos
+
+
+ Cree
+ cr
+ cre
+
+
+ Croatian
+ hr
+ hrv
+
+
+ Czech
+ cs
+ ces
+
+
+ Danish
+ da
+ dan
+
+
+ Divehi, Dhivehi, Maldivian
+ dv
+ div
+
+
+ Dutch
+ nl
+ nld
+
+
+ Dzongkha
+ dz
+ dzo
+
+
+ English
+ en
+ eng
+
+
+ Esperanto
+ eo
+ epo
+
+
+ Estonian
+ et
+ est
+
+
+ Ewe
+ ee
+ ewe
+
+
+ Faroese
+ fo
+ fao
+
+
+ Fijian
+ fj
+ fij
+
+
+ Finnish
+ fi
+ fin
+
+
+ French
+ fr
+ fra
+
+
+ Fula, Fulah, Pulaar, Pular
+ ff
+ ful
+
+
+ Galician
+ gl
+ glg
+
+
+ Georgian
+ ka
+ kat
+
+
+ German
+ de
+ deu
+
+
+ Greek, Modern
+ el
+ ell
+
+
+ Guaraní
+ gn
+ grn
+
+
+ Gujarati
+ gu
+ guj
+
+
+ Haitian, Haitian Creole
+ ht
+ hat
+
+
+ Hausa
+ ha
+ hau
+
+
+ Hebrew (modern)
+ he
+ heb
+
+
+ Herero
+ hz
+ her
+
+
+ Hindi
+ hi
+ hin
+
+
+ Hiri Motu
+ ho
+ hmo
+
+
+ Hungarian
+ hu
+ hun
+
+
+ Interlingua
+ ia
+ ina
+
+
+ Indonesian
+ id
+ ind
+
+
+ Interlingue
+ ie
+ ile
+
+
+ Irish
+ ga
+ gle
+
+
+ Igbo
+ ig
+ ibo
+
+
+ Inupiaq
+ ik
+ ipk
+
+
+ Ido
+ io
+ ido
+
+
+ Icelandic
+ is
+ isl
+
+
+ Italian
+ it
+ ita
+
+
+ Inuktitut
+ iu
+ iku
+
+
+ Japanese
+ ja
+ jpn
+
+
+ Javanese
+ jv
+ jav
+
+
+ Kalaallisut, Greenlandic
+ kl
+ kal
+
+
+ Kannada
+ kn
+ kan
+
+
+ Kanuri
+ kr
+ kau
+
+
+ Kashmiri
+ ks
+ kas
+
+
+ Kazakh
+ kk
+ kaz
+
+
+ Khmer
+ km
+ khm
+
+
+ Kikuyu, Gikuyu
+ ki
+ kik
+
+
+ Kinyarwanda
+ rw
+ kin
+
+
+ Kirghiz, Kyrgyz
+ ky
+ kir
+
+
+ Komi
+ kv
+ kom
+
+
+ Kongo
+ kg
+ kon
+
+
+ Korean
+ ko
+ kor
+
+
+ Kurdish
+ ku
+ kur
+
+
+ Kwanyama, Kuanyama
+ kj
+ kua
+
+
+ Latin
+ la
+ lat
+
+
+ Luxembourgish, Letzeburgesch
+ lb
+ ltz
+
+
+ Luganda
+ lg
+ lug
+
+
+ Limburgish, Limburgan, Limburger
+ li
+ lim
+
+
+ Lingala
+ ln
+ lin
+
+
+ Lao
+ lo
+ lao
+
+
+ Lithuanian
+ lt
+ lit
+
+
+ Luba-Katanga
+ lu
+ lub
+
+
+ Latvian
+ lv
+ lav
+
+
+ Manx
+ gv
+ glv
+
+
+ Macedonian
+ mk
+ mkd
+
+
+ Malagasy
+ mg
+ mlg
+
+
+ Malay
+ ms
+ msa
+
+
+ Malayalam
+ ml
+ mal
+
+
+ Maltese
+ mt
+ mlt
+
+
+ Māori
+ mi
+ mri
+
+
+ Marathi (Marāṭhī)
+ mr
+ mar
+
+
+ Marshallese
+ mh
+ mah
+
+
+ Mongolian
+ mn
+ mon
+
+
+ Nauru
+ na
+ nau
+
+
+ Navajo, Navaho
+ nv
+ nav
+
+
+ Norwegian Bokmål
+ nb
+ nob
+
+
+ North Ndebele
+ nd
+ nde
+
+
+ Nepali
+ ne
+ nep
+
+
+ Ndonga
+ ng
+ ndo
+
+
+ Norwegian Nynorsk
+ nn
+ nno
+
+
+ Norwegian
+ no
+ nor
+
+
+ Nuosu
+ ii
+ iii
+
+
+ South Ndebele
+ nr
+ nbl
+
+
+ Occitan
+ oc
+ oci
+
+
+ Ojibwe, Ojibwa
+ oj
+ oji
+
+
+ Old Church Slavonic, Church Slavic, Church Slavonic, Old
+ Bulgarian, Old Slavonic
+ cu
+ chu
+
+
+ Oromo
+ om
+ orm
+
+
+ Oriya
+ or
+ ori
+
+
+ Ossetian, Ossetic
+ os
+ oss
+
+
+ Panjabi, Punjabi
+ pa
+ pan
+
+
+ Pāli
+ pi
+ pli
+
+
+ Persian
+ fa
+ fas
+
+
+ Polish
+ pl
+ pol
+
+
+ Pashto, Pushto
+ ps
+ pus
+
+
+ Portuguese
+ pt
+ por
+
+
+ Quechua
+ qu
+ que
+
+
+ Romansh
+ rm
+ roh
+
+
+ Kirundi
+ rn
+ run
+
+
+ Romanian, Moldavian, Moldovan
+ ro
+ ron
+
+
+ Russian
+ ru
+ rus
+
+
+ Sanskrit (Saṁskṛta)
+ sa
+ san
+
+
+ Sardinian
+ sc
+ srd
+
+
+ Sindhi
+ sd
+ snd
+
+
+ Northern Sami
+ se
+ sme
+
+
+ Samoan
+ sm
+ smo
+
+
+ Sango
+ sg
+ sag
+
+
+ Serbian
+ sr
+ srp
+
+
+ Scottish Gaelic, Gaelic
+ gd
+ gla
+
+
+ Shona
+ sn
+ sna
+
+
+ Sinhala, Sinhalese
+ si
+ sin
+
+
+ Slovak
+ sk
+ slk
+
+
+ Slovene
+ sl
+ slv
+
+
+ Somali
+ so
+ som
+
+
+ Southern Sotho
+ st
+ sot
+
+
+ Spanish, Castilian
+ es
+ spa
+
+
+ Sundanese
+ su
+ sun
+
+
+ Swahili
+ sw
+ swa
+
+
+ Swati
+ ss
+ ssw
+
+
+ Swedish
+ sv
+ swe
+
+
+ Tamil
+ ta
+ tam
+
+
+ Telugu
+ te
+ tel
+
+
+ Tajik
+ tg
+ tgk
+
+
+ Thai
+ th
+ tha
+
+
+ Tigrinya
+ ti
+ tir
+
+
+ Tibetan Standard, Tibetan, Central
+ bo
+ bod
+
+
+ Turkmen
+ tk
+ tuk
+
+
+ Tagalog
+ tl
+ tgl
+
+
+ Tswana
+ tn
+ tsn
+
+
+ Tonga (Tonga Islands)
+ to
+ ton
+
+
+ Turkish
+ tr
+ tur
+
+
+ Tsonga
+ ts
+ tso
+
+
+ Tatar
+ tt
+ tat
+
+
+ Twi
+ tw
+ twi
+
+
+ Tahitian
+ ty
+ tah
+
+
+ Uighur, Uyghur
+ ug
+ uig
+
+
+ Ukrainian
+ uk
+ ukr
+
+
+ Urdu
+ ur
+ urd
+
+
+ Uzbek
+ uz
+ uzb
+
+
+ Venda
+ ve
+ ven
+
+
+ Vietnamese
+ vi
+ vie
+
+
+ Volapük
+ vo
+ vol
+
+
+ Walloon
+ wa
+ wln
+
+
+ Welsh
+ cy
+ cym
+
+
+ Wolof
+ wo
+ wol
+
+
+ Western Frisian
+ fy
+ fry
+
+
+ Xhosa
+ xh
+ xho
+
+
+ Yiddish
+ yi
+ yid
+
+
+ Yoruba
+ yo
+ yor
+
+
+ Zhuang, Chuang
+ za
+ zha
+
+
+ Zulu
+ zu
+ zul
+
+
+
+
+ Help Menu
+
+
+ Shortcuts Customization
+
+ Help Menu
+
+
+
+
+
+
+
+
+
+
+
+ Menu Item
+
+ Default shortcut
+
+ Menu Item Code
+
+
+
+
+
+ User Manual...
+
+ F1
+
+ helpContentsMenuItem
+
+
+
+ About...
+
+
+
+ helpAboutMenuItem
+
+
+
+
+
+
diff --git a/OmegaT/doc_src/en/App_Using_tokenizers_in_OmegaT.xml b/OmegaT/doc_src/en/App_Using_tokenizers_in_OmegaT.xml
new file mode 100644
index 0000000..d8dd66a
--- /dev/null
+++ b/OmegaT/doc_src/en/App_Using_tokenizers_in_OmegaT.xml
@@ -0,0 +1,122 @@
+
+
+
+ Using tokenizers in OmegaT
+
+
+ Introduction
+
+ Tokenizers (or stemmers) improve the quality of matches by
+ recognizing inflected words in source and translation memory data. They
+ also improve glossary matching.
+
+ A stemmer for English, for example, should identify the string
+ "cats" (and possibly "catlike", "catty" etc.) as based on the root "cat",
+ and "stemmer", "stemming", "stemmed" as based on "stem". A stemming
+ algorithm reduces the words "fishing", "fished", "fish", and "fisher" to
+ the root word, "fish". This especially useful in case of languages that
+ use pre- and postfix forms for the stem words. Borrowing an example from
+ Slovenian, here "good" in all possible grammatically correct forms:
+
+
+
+ lep, lepa, lepo - singular, masculine, feminine, neutral
+
+
+
+
+
+ lepši, lepša, lepše . - comparative, nominative, masculine,
+ feminine, neutral, resp. Plural form of the adjective
+
+
+
+
+
+ najlepših - superlative, plural, genitive for M,F,N
+
+
+
+
+
+ Installation and command line use
+
+ A tokenizer package adapted from the Lucene project is distributed
+ as an OmegaT plug-in at
+ http://sourceforge.net/projects/omegat-plugins/files/. Download the most
+ recent files (OmegaT-tokenizers_0.4_2-2.1.zip at the time of this
+ writing).
+
+ To install the tokenizer, create a folder with the name "plugins" in
+ the folder where OmegaT.jar is found and unpack the above files within
+ that folder.
+
+ To run OmegaT with the tokenizer you need to specify which tokenizer
+ you'll use for the source language and which tokenizer you'll use for the
+ target language. The syntax is as follows:
+
+ java -jar OmegaT.jar --ITokenizer=[source language
+ tokenizer name] --ITokenizerTarget=[target language tokenizer
+ name]
+
+ The tokenizer names are given in the Readme.txt file distributed
+ with the tokenizer files. For example, if you wish to use the Lucene CJK
+ tokenizer in source and the Lucene French tokenizer in target, your
+ command will look like this:
+
+ java -jar OmegaT.jar
+ --ITokenizer=org.omegat.plugins.tokenizer.LuceneCJKTokenizer
+ --ITokenizerTarget=org.omegat.plugins.tokenizer.LuceneFrenchTokenizer
+
+
+
+ Mac OSX specifics
+
+ If you wish to use the tokenizers with the Mac OSX OmegaT.app
+ package, the tokenizer installation described above applies (right-click
+ on OmegaT.app to find the location of OmegaT.jar), but you'll need to
+ specify the tokenizer names in the info.plist that
+ contains the Java launch options. Follow the instructions above to access
+ the info.plist file and edit it so that it looks as
+ follows for the example we just gave:
+
+
+<key>VMOptions</key>
+<string>-Xmx1024M</string>
+
+<key>Arguments</key>
+<array>
+ <string>--ITokenizer=org.omegat.plugins.tokenizer.LuceneCJKTokenizer</string>
+ <string>--ITokenizerTarget=org.omegat.plugins.tokenizer.LuceneFrenchTokenizer</string>
+</array>
+
+
+
+ Troubleshooting
+
+ To make sure that the tokenizers are being used, open a project and
+ check the log information from the console. With the example above it
+ should look like that:
+
+
+84528: Info: Source tokenizer: org.omegat.plugins.tokenizer.LuceneCJKTokenizer
+84528: Info: Target tokenizer: org.omegat.plugins.tokenizer.LuceneFrenchTokenizer
+
+
+ The numbers on the left are likely to be different on your system so
+ make sure that the source and target tokenizer names,specified in the
+ start-up options, correspond to what the log is showing. If the tokenizers
+ are not properly launched, the log will look like this:
+
+
+12719: Info: Source tokenizer: org.omegat.core.matching.Tokenizer
+12719: Info: Target tokenizer: org.omegat.core.matching.Tokenizer
+
+
+ With the Mac OSX OmegaT.app package, you'll need to double-click on
+ the JavaApplicationStub located in
+ /OmegaT.app/Contents/MacOS/ (see above to access it) to launch OmegaT from
+ the console and have immediate access to the log.
+
+
diff --git a/OmegaT/doc_src/en/App_Website.xml b/OmegaT/doc_src/en/App_Website.xml
new file mode 100644
index 0000000..765003b
--- /dev/null
+++ b/OmegaT/doc_src/en/App_Website.xml
@@ -0,0 +1,127 @@
+
+
+
+ <application><indexterm class="singular">
+ <primary>OmegaT on the web</primary>
+ </indexterm>OmegaT</application> on the web
+
+
+ <application>OmegaT</application> sites and
+ <application>OmegaT</application> SourceForge project<indexterm
+ class="singular">
+ <primary>OmegaT on the web</primary>
+
+ <secondary>SourceForge Project</secondary>
+ </indexterm>
+
+ The
+ OmegaT web site contains links to
+ numerous OmegaT resources. User support is
+ provided on a volunteer basis at the OmegaT
+ Yahoo User Group. The FAQ
+ is a good starting point for finding answers to questions you may
+ have. For the latest version of OmegaT, refer to the downloads page at
+ www.omegat.org. You can also file bug
+ reports and requests
+ for enhancements.
+
+
+
+ Bug reports<indexterm class="singular">
+ <primary>OmegaT on the web</primary>
+
+ <secondary>Reporting bugs</secondary>
+ </indexterm>
+
+ Remember that every good bug report needs just three things:
+
+
+
+ Steps to reproduce
+
+
+
+ What you expected to see
+
+
+
+ What you saw instead
+
+
+
+ More can be found in the Painless
+ Bug Tracking article by Joel Spolsky.
+
+ You should add copies of files, portions of the log, screenshots, and
+ anything else that you think will help the developers to find and fix your
+ bug. Note that bug reports and requests for enhancements are publicly
+ visible, so you should not add any sensitive files. If you wish to keep
+ track of what is happening to the report, register as a SourceForge user,
+ login and file a bug report or simply click Monitor at the top of the
+ report.
+
+
+
+ Contributing to <application>OmegaT</application> project<indexterm
+ class="singular">
+ <primary>OmegaT on the web</primary>
+
+ <secondary>Contributing to OmegaT</secondary>
+ </indexterm>
+
+ To contribute to
+ OmegaT:
+
+ first join the user group (via web or
+ by sending an email to OmegaT-subscribe@yahoogroups.com).
+ To get involved in the OmegaT development
+ effort you can join the developer group, via the web or by sending an
+ email to omegat-development-request@lists.sourceforge.net
+ with "subscribe" as the subject line.
+
+ To translate
+ OmegaT's user interface, user manual or other
+ related documents:
+
+ first read the Localizing
+ and Customizing OmegaT guide, and join
+ the OmegaT translators' group via web or by
+ sending an email to omegat-l10n-request@lists.sourceforge.net
+ with subject "subscribe".
+
+
+ OmegaT on the web
+
+ Development, Localizing
+
+
+ To support the OmegaT project financially
+ OmegaT on the web
+
+ Financial support
+
+
+ If you would like to help support the continued development of
+ OmegaT, it would be very much appreciated - click on this link to go to
+ the
+ OmegaT PayPal account.
+
+
+ OmegaT on the web
+
+ Donating to OmegaT
+
+
+
diff --git a/OmegaT/doc_src/en/Dictionaries.xml b/OmegaT/doc_src/en/Dictionaries.xml
new file mode 100644
index 0000000..91365bf
--- /dev/null
+++ b/OmegaT/doc_src/en/Dictionaries.xml
@@ -0,0 +1,161 @@
+
+
+
+ <indexterm class="singular">
+ <primary>Dictionaries</primary>
+ </indexterm>Dictionaries
+
+
+
+
+ How to download and install dictionaries<indexterm class="singular">
+ <primary>Dictionaries</primary>
+
+ <secondary>Downloading and installing</secondary>
+ </indexterm>
+
+ Dictionaries in OmegaT are based on the
+ StartDict Platform. To install the necessary files, proceed as
+ follows:
+
+
+
+ Search for the required language combination - for instance on
+ the
+ FreeDict
+
+ Dictionaries
+ StartDict Platform above or on FreeDict
+ Stardict
+
+ Dictionaries
+
+
+
+
+
+
+ Download the file - it should be a tarball
+ archive (extension tar.bz or
+ tar.bz2).
+
+
+
+
+
+ Use untar utility (or its equivalent, for instance
+ winrar in Windows) to extract its contents into the project
+ folder "Dictionary". There should be three files, with extensions
+ dz, idx and ifo.
+
+
+
+ Note that in addition to "source-target" dictionaries you can, using
+ the Dictionary feature, obtain access to information such as:
+
+
+
+
+ Webster
+
+ Dictionaries
+ Webster's Revised Unabridged Dictionary (1913)
+
+
+
+
+
+
+ Longman
+
+ Dictionaries
+ Longman Dictionary of Contemporary English
+
+
+
+
+
+
+ Britannica
+
+ Dictionaries
+ The Britannica Concise Encyclopedia
+
+
+
+
+
+ etc...
+
+
+
+ Some of the dictionaries have no strings attached - i.e. are "Free
+ to use", and others, like the selection above, are under the GPL license.
+ The following example shows Merriam Webster 10th dictionary "in
+ action":
+
+
+ <indexterm class="singular">
+ <primary>Dictionary</primary>
+
+ <secondary>Merriam Webster - figure</secondary>
+
+ <seealso>Dictionaries</seealso>
+ </indexterm>Merriam Webster dictionary - use
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ <indexterm class="singular">
+ <primary>Dictionaries</primary>
+
+ <secondary>Problems with</secondary>
+ </indexterm>Problems with dictionaries
+
+
+
+ Check that your dict files are in the correct folder (or in a subfolder
+ below it). Check in
+
+
+
+ Shortcuts
+
+ Ctrl+E - Project properties
+ Ctrl
+
+ E
+
+
+
+ Project
+
+ Properties
+ .
+
+
+
+
+
+ Does the folder contain three files of the same name, with
+ extensions ? If only one file is present, check its extension. If it
+ is tar.bz, you have forgotten to unpack (untar)
+ it.
+
+
+
+
diff --git a/OmegaT/doc_src/en/EditingBehavior.xml b/OmegaT/doc_src/en/EditingBehavior.xml
new file mode 100644
index 0000000..be5531b
--- /dev/null
+++ b/OmegaT/doc_src/en/EditingBehavior.xml
@@ -0,0 +1,160 @@
+
+
+
+ Editing behavior<indexterm class="singular">
+ <primary>Menu options</primary>
+
+ <secondary>Editing behavior...</secondary>
+ </indexterm>
+
+ The dialog in
+ Options
+
+ Editing Behavior...
+ enables the user to select, how the current segment in the
+ editing field is to be initialized and handled:
+
+
+ Editing behavior options
+
+
+
+
+
+
+
+
+
+ Editing behaviour - options<indexterm class="singular">
+ <primary>Editing behaviour</primary>
+
+ <secondary>Options</secondary>
+ </indexterm>
+
+ You translate your files by moving from segment to segment, editing
+ each current segment in turn. When moving between segments, you may wish
+ to populate the editing field with an existing translation in the fuzzy
+ match pane or with the source text. In
+ Options
+
+ Editing Behavior...
+ OmegaT offers you the following
+ alternatives:
+
+
+
+ The source text
+
+
+ You can have the source text inserted automatically into the
+ editing field. This is useful for texts containing many trade marks
+ or other proper nouns you which must be left unchanged.
+
+
+
+
+ Leave the segment empty
+ Editing behaviour
+
+ Empty translation
+
+
+
+ OmegaT leaves the editing field blank. This option allows you
+ to enter the translation without the need to remove the source text,
+ thus saving you two keystrokes (Ctrl+A
+ and Del). Empty
+ translations are now allowed. They are displayed as <EMPTY> in
+ the Editor. To create one, right-click in a segment, and select
+ "Set empty translation". The entry
+ Remove translation in the same
+ popup menu also allows to delete the existing translation of the
+ current segment. You achieve the same by clearing the target segment
+ and pressing Enter.
+
+
+
+
+ Insert the best fuzzy match
+ Editing behaviour
+
+ Inserting fuzzy matches
+
+
+
+ OmegaT inserts the translation of the string most similar to
+ the current source, if it is above the similarity threshold that you
+ have selected in this dialog. The prefix (per default empty) can be
+ used to tag translations, done via fuzzy matches. If you add a
+ prefix (for instance [fuzzy]), you can trace those translations
+ later to see they are correct.
+
+
+
+
+
+
+ Allow the translation to be equal to source<indexterm
+ class="singular">
+ <primary>Editing behaviour</primary>
+
+ <secondary>Translation equal to source</secondary>
+ </indexterm>
+
+ Documents for translation may contain trade marks, names or other
+ proper nouns that will be the same in translated documents. There are two
+ strategies for segments that contain only such invariable text.
+
+ You can decide not to translate such segments at all. OmegaT will
+ then report these segments as not translated. This is the default. The
+ alternative is to enter a translation that is identical to the source
+ text. OmegaT is able to recognize that you have done this. To make this
+ possible, go to
+ Options
+
+ Editing Behavior...
+ and check the box Allow translation
+ to be equal to source.
+
+
+
+ Export the segment to text files<indexterm class="singular">
+ <primary>Editing behaviour</primary>
+
+ <secondary>Exporting the current segment</secondary>
+ </indexterm>
+
+ The text export function exports data from within the current
+ OmegaT project to plain text files. The data
+ are exported when the segment is opened. The files appear in the /script
+ subfolder in the OmegaT user files folder, and include:
+
+
+
+ The content of the segment source text
+ (source.txt).
+
+
+
+ The content of the segment target text
+ (target.txt).
+
+
+
+ The text highlighted by the user, when
+ Ctrl-Shift-C is pressed or Edit >
+ Export Selection is selected
+ (selection.txt).
+
+
+
+ The content of the files is overwritten either when a new segment is
+ opened (source.txt and target.txt) or when a new selection is exported
+ (selection.txt). The files are unformatted plain text files. The whole
+ process can be steered and controlled via Tck/Tcl-based scripting. See
+ Using the
+ OmegaT text export function for specifics, examples and
+ suggestions.
+
+
diff --git a/OmegaT/doc_src/en/FileFilters.xml b/OmegaT/doc_src/en/FileFilters.xml
new file mode 100644
index 0000000..2644eb8
--- /dev/null
+++ b/OmegaT/doc_src/en/FileFilters.xml
@@ -0,0 +1,518 @@
+
+
+
+ File Filters
+
+ OmegaT features highly customizable filters, enabling you to configure
+ numerous aspects. File filters are pieces of code capable of:
+
+
+
+ Reading the document in some specific file format. For instance,
+ plain text files.
+
+
+
+
+
+ Extracting the translatable content out of the file.
+
+
+
+
+
+ Automating modifications of the translated document file names by
+ replacing translatable contents with its translation.
+
+
+
+ To see which file formats can be handled by OmegaT, see the menu
+ Options > File Filters ...
+
+ Most users will find the default file filter options sufficient. If
+ this is not the case, open the main dialog by selecting Options → File Filters... from the main menu. You
+ can also enable project-specific file filters, which will only be used on
+ the current project, by selecting the File
+ Filters... option in Project Properties.
+
+ You can enable project specific filters via the Options → Properties... . Klick on File
+ Filters button and activate the check box Enable
+ project specific filters
+ File filters
+
+ project specific file filters
+ . A copy of the filters configuration will be stored with the
+ project in this case. If you later change filters, only the project filters
+ will be updated, while the user filters stay unchanged.
+
+ Warning! Should you change filter
+ options whilst a project is open, you must reload the project in order for
+ the changes to take effect.
+
+
+ File filters dialog<indexterm class="singular">
+ <primary>File filters</primary>
+
+ <secondary>Dialog</secondary>
+ </indexterm>
+
+ This dialog lists available file filters. Should you wish not to use
+ OmegaT to translate files of a certain type, you can turn off the
+ corresponding filter by deactivating the check box beside its name. OmegaT
+ will then omit the appropriate files while loading projects, and will copy
+ them unmodified when creating target documents. When you wish to use the
+ filter again, just tick the check box. Click Defaults to reset the file filters to the default
+ settings. To edit which files in which encodings the filter is to process,
+ select the filter from the list and click Edit.
+
+
+
+ Filter options<indexterm class="singular">
+ <primary>File filters</primary>
+
+ <secondary>Options</secondary>
+ </indexterm>
+
+ Five filters (Text files, XHTML files, HTML and XHTML files,
+ OpenDocument/OpenOffice.org files and Microsoft Open XML files) have one
+ or more specific options. To modify the options select the filter from the
+ list and click on Options. The available
+ options are:
+
+ Text files
+
+
+
+ Paragraph segmentation on line breaks, empty lines or
+ never:
+
+ if sentence segmentation rules are active, the text will further
+ be segmented according to the option selected here.
+
+
+
+ PO files
+
+
+
+ Allow blank translations in the target
+ file:
+
+ If on, when a PO segment (which may be a whole paragraph) is not
+ translated, the translation will be empty in the target file.
+ Technically speaking, the msgstr segment in the PO target
+ file, if created, will be left empty. As this is the standard behavior
+ for PO files, it is on by default. If the option is off, the source
+ text will be copied to the target segment.
+
+
+
+ XHTML Files
+
+
+
+ Translate the following attributes - the
+ selected attributes will appear as segments in the Editor
+ window.
+
+
+
+
+
+ Start a new paragraph on: the <br>
+ HTML tag will constitute a paragraph for segmentation purposes.
+
+
+
+
+
+ Skip text matching regular expression: the
+ text matching the regular expression gets skipped. It is shown
+ rendered red in the tag validator. Text in source segment that matches
+ is shown in italic.
+
+
+
+
+
+ Do not translate the content attribute of meta-tags
+ ... :
+
+ It is sometimes useful to be able make some tags untranslatable
+ based on the value of attributes. E.g., <div
+ class="hide"> <span translate="no"> You can define
+ key-value pairs for tags to be left untranslated. For the example
+ above, the field would contain: class=hide, translate=no
+
+
+
+
+ Microsoft Office Open XML
+ files
+
+ You can select which elements are to be translated. They will appear
+ as separate segments in the translation.
+
+
+
+ Word: non-visible instruction
+ text, comments, footnotes, endnotes, footers
+
+
+
+
+
+ Excel: comments, sheet
+ names
+
+
+
+
+
+ Power Point: slide comments,
+ slide masters, slide layouts
+
+
+
+
+
+ Global: charts, diagrams,
+ drawings, WordArt
+
+
+
+
+
+ Other Options:
+
+
+
+ Aggregate tags: if checked, tags
+ without translatable text between them will be aggregated into
+ single tags.
+
+
+
+ Preserve spaces for all tags: if
+ checked, "white space" (i.e., spaces and newlines) will be
+ preserved, even if not set technically in the document
+
+
+
+
+
+ HTML and XHTML files
+
+
+
+ Add or rewrite encoding declaration in HTML and XHTML
+ files: Always (default), Only if (X)HTML file has a header,
+ Only if (X)HTML file has an encoding declaration, Never
+
+
+
+
+
+ Translate the following attributes: the
+ selected attributes will appear as segments in the Editor
+ window.
+
+
+
+
+
+ Start a new paragraph on: the <br>
+ HTML tag will constitute a paragraph for segmentation purposes.
+
+
+
+
+
+ Skip text matching regular expression: The
+ text, matching the regular expression, will be skipped.
+
+
+
+
+
+ Do not translate the content attribute of
+ meta-tags ... : the attribute key-value pairs, separated by
+ commas, will be left untranslated
+
+
+
+ Text files
+
+
+
+ Paragraph segmentation on line breaks, empty lines or
+ never:
+
+ if sentence segmentation rules are active, the text will further
+ be segmented according to the option selected here.
+
+
+
+ OpenDocument/OpenOffice.org
+ files
+
+
+
+ You can select which of the following items are to be
+ translated:
+
+ index entries, bookmarks, bookmark references, notes, comments,
+ presentation notes, links (URL), sheet names
+
+
+
+
+
+ Edit filter dialog<indexterm class="singular">
+ <primary>File filters</primary>
+
+ <secondary>Editing</secondary>
+ </indexterm>
+
+ This dialog enables you to set up the source filename patterns of
+ files to be processed by the filter, customize the filenames of translated
+ files, and select which encodings should be used for loading the file and
+ saving its translated counterpart. To modify a file filter pattern, either
+ modify the fields directly or click Edit.
+ To add a new file filter pattern, click Add. The same dialog is used to add a pattern or to
+ edit a particular pattern. The dialog is useful because it includes a
+ special target filename pattern editor with which you can customize the
+ names of output files.
+
+
+ <indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>File type, filename pattern</secondary>
+ </indexterm>Source file type, filename pattern<indexterm
+ class="singular">
+ <primary>File filters</primary>
+
+ <secondary>Source file type, filename</secondary>
+ </indexterm>
+
+ When OmegaT encounters a file in its source folder, it attempts to
+ select the filter based upon the file's extension. More precisely,
+ OmegaT attempts to match each filter's source filename patterns against
+ the filename. For example, the pattern *.xhtml
+ matches any file with the .xhtml extension.
+ If the appropriate filter is found, the file is assigned to it for
+ processing. For example, by default, XHTML filters are used for
+ processing files with the .xhtml extension. You can change or add
+ filename patterns for files to be handled by each file. Source filename
+ patterns use wild card characters similar to those used in Searches. The '*' character matches zero or more
+ characters. The '?' character matches exactly one character. All other
+ characters represent themselves. For example, if you wish the text
+ filter to handle readme files (readme, read.me, and
+ readme.txt) you should use the pattern
+ read*.
+
+
+
+ Source and Target file encoding
+
+
+ Source files
+
+ Encoding
+
+
+
+ Target files
+
+ Encoding
+
+
+
+ File filters
+
+ Source, target encoding
+
+
+ Only a limited number of file formats specify a mandatory
+ encoding. File formats that do not specify their encoding will use the
+ encoding you set up for the extension that matches their name. For
+ example, by default .txt files will be loaded using
+ the default encoding of your operating system. You may change the source
+ encoding for each different source filename pattern. Such files may also
+ be written out in any encoding. By default, the translated file encoding
+ is the same as the source file encoding. Source and target encoding
+ fields use combo boxes with all supported encodings included.
+ <auto> leaves the encoding choice to
+ OmegaT. This is how it works:
+
+
+
+ OmegaT identifies the source file encoding by using its
+ encoding declaration, if present (HTML files, XML based
+ files)
+
+
+
+
+
+ OmegaT is instructed to use a mandatory encoding for certain
+ file formats (Java properties etc)
+
+
+
+
+
+ OmegaT uses the default encoding of
+ the operating system for text files.
+
+
+
+
+
+ Target filename<indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Filenames</secondary>
+ </indexterm>
+
+ Sometimes you may wish to rename the files you translate
+ automatically, for example adding a language code after the file name.
+ The target filename pattern uses a special syntax, so if you wish to
+ edit this field, you must click Edit...and use the
+ File filters
+
+ Dialog
+ Edit Pattern Dialog. If you wish to revert to default
+ configuration of the filter, click Defaults. You may also modify the name directly
+ in the target filename pattern field of the file filters dialog. The
+ Edit Pattern Dialog offers among others the following options:
+
+
+
+ Default is ${filename}– full filename of
+ the source file with extension: in this case the name of the
+ translated file is the same as that of the source file.
+
+
+
+
+
+ ${nameOnly}– allows you to insert only the
+ name of the source file without the extension.
+
+
+
+ ${extension} - the original file
+ extension
+
+
+
+
+
+ ${targetLocale}– target locale code (of a
+ form "xx_YY").
+
+
+
+
+
+ ${targetLanguage}– the target language and
+ country code together (of a form "XX-YY").
+
+
+
+
+
+ ${targetLanguageCode} – the target language
+ - only "XX"
+
+
+
+
+
+ ${targetCountryCode}– the target country -
+ only "YY"
+
+
+
+ $(timestamp-????) - system date time at
+ generation time in various patterns
+
+ See Oracle
+ documentation for examples of the "SimpleDateFormat"
+ patterns
+
+
+
+ ${system-os-name} - operating system of the computer
+ used
+
+
+
+ ${system-user-name) - system user name
+
+
+
+ ${system-host-name} - system host name
+
+
+
+ ${file-source-encoding} - source file encoding
+
+
+
+ ${file-target-encoding} - target file encoding
+
+
+
+ ${targetLocaleLCID) - Microsoft target locale
+
+
+
+ Additional variants are available for variables ${nameOnly} and
+ ${Extension}. In case the file name has ambivalent name, one can apply
+ variables of the form $(name only-number of
+ extensions) and
+ ${extension-number of extensions}
+ . If for example the original file is named Document.xx.docx,
+ the following variables will give the following results:
+
+
+
+ ${nameOnly-0} Document
+
+
+
+ ${nameOnly-1} Document.xx
+
+
+
+ ${nameOnly-2} Document.xx.docx
+
+
+
+ ${extension-0} docx
+
+
+
+ ${extension-1} xx.docx
+
+
+
+ ${extension-2} Document.xx.docx
+
+
+
+
+
diff --git a/OmegaT/doc_src/en/FilesAndDirectories.xml b/OmegaT/doc_src/en/FilesAndDirectories.xml
new file mode 100644
index 0000000..a200b63
--- /dev/null
+++ b/OmegaT/doc_src/en/FilesAndDirectories.xml
@@ -0,0 +1,527 @@
+
+
+
+ <application>OmegaT</application> Files and Directories
+
+ OmegaT works with three types of
+ files.
+
+
+
+ Translation project files: These constitute a translation project.
+ Losing them may affect the project's integrity and your ability to
+ complete a job. Project files are the most important files in
+ OmegaT. They are the files you deal with on a
+ daily basis while translating.
+
+
+
+
+
+ User settings files: These are created when OmegaT's behavior is
+ modified by user preference settings. Losing them usually results in
+ OmegaT reverting to its "factory settings". This can sometimes cause a
+ little trouble when you are in the middle of a translation.
+
+
+
+
+
+ Application files: These are included in the package you download.
+ Most of them are required in order for OmegaT to function properly. If
+ for some reason these files are lost or corrupted, simply download
+ and/or reinstall OmegaT to restore them all.
+
+
+
+
+ Translation project files
+
+
+ Project files
+
+ Translation project files
+
+
+ An OmegaT translation project consists of
+ a number of files and directories.
+
+ When you create a translation project, OmegaT automatically creates
+ a folder with the specified name, and a list of folders:
+
+
+ OmegaT project
+
+
+
+
+
+
+
+
+ Alternate locations for some of the folders can be chosen at project
+ creation or during the translation. It is therefore possible to select
+ existing folders or create folders in locations that reflect your work
+ flow and project management habits. To change the location of folders
+ after a project has been created, open Project >
+ Properties... in the menu or with
+ Ctrl+E and make the necessary changes.
+
+ In a file manager a translation project looks and acts just like any
+ other folder. In the foillowing example the folder my
+ projects contains three OmegaT projects:
+
+
+ OmegaT projects and subdirectories
+
+
+
+
+
+
+
+
+ Double clicking the item with the OmegaT icon is sufficient to open
+ the project. A translation project Example_Project created with the default settings
+ will be created as a new subfolder with the following structure:
+
+
+ Top folder<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>File omegat.project</secondary>
+ </indexterm>
+
+ Top folder of a project always contains the file
+ OmegaT.Project, containing project parameters as defined in
+ the Project properties window (File >
+ Properties). While the translation is progressing,
+ additional files
+ (project_name-omegat.tmx,
+ project_name-level1.tmx and project_name-level2.tmx) are
+ created (and updated during the process of translation) in thes folder.
+ They contain the one and the same translation memory contents in
+ different forms, to be sued in future projects.
+
+
+
+ Subfolder dictionary
+
+ Initially empty, this folder with contain dictionaries you have
+ added to the project. See chapter
+ Dictionaries for more on this subject.
+
+
+
+ Subfolder glossary
+
+ This folder is nitially empty. It will contain glossaries you will
+ be using in the project. See chapter
+ Glossaries for more on this subject.
+
+
+
+ Subfolder omegat<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>Subfolder omegat</secondary>
+ </indexterm>
+
+ The omegat subfolder contains at
+ least one and possibly several other files. The most important file here
+ is the project_save.tmx, that is the working
+ translation memory for the project. Backups of this file (with extension
+ bak) are added progressively to this subfolder, first at the beginning
+ of the translation session, at its end, and while the translation
+ progresses. This way an inadvertent loss of is averted - see Preventing
+ Data Loss in chapter Miscellanea.
+
+ During translation additional files may get created in this
+ subdirectory as follows
+
+
+
+
+
+
+
+ stats.txt
+
+
+ Project files
+
+ statistics file
+ contains the current statistics of the current
+ project. You can view it by selecting Tools >
+ Statistics
+
+
+
+ ignored_words.txt. learned_words.txt
+
+
+ Project files
+
+ ignored_words and learned_words
+ are created and used by the spell checker. If
+ you already have collected words you wish the spell checker to
+ ignore / accept, you just need to copy the corresponding two
+ files into the omegatsubfolder of your
+ current project.
+
+
+
+ project_stats_match.txt
+
+ contains the latest project match statistics, generated
+ by Tools > Match
+ Statistics
+
+
+
+ segmentation.conf
+
+ if existing, it contains project-specific segmentation
+ rules, if requested in Project > Properties
+ ... See Chapter Project
+ properties
+
+
+
+ filters.xml
+
+ if existing, it contains project-specific file filters,
+ if requested in Project > Properties ...
+ See Chapter Project
+ properties
+
+
+
+
+
+
+
+ Subfolder source<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>Source subfolder</secondary>
+ </indexterm>
+
+ The source subfolder contains files to be translated. You can add
+ the files to it later. Note that the structure of the source subfolder
+ may take any form you like. If the files to be translated are parts of a
+ tree structure (as in a website), you need only specify the top-level
+ subfolder and OmegaT will maintain the entire contents, while keeping
+ the tree structure intact.
+
+
+
+ Subfolder target<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>Target subfolder</secondary>
+ </indexterm>
+
+ This subfolder is initially empty. To add contents to it, select
+
+
+
+ Ctrl
+
+ D
+
+
+
+ Project
+
+ Create Translated Documents
+ . Files within the source directory,
+ whether translated or not, are then generated here, with the same
+ hierarchy as present in the source subfolder. The contents of the target
+ subfolder will reflect the current state of the translation, as present
+ in the project translation memory, saved in the current /omegat/project_save.tmx. Untranslated segments
+ will hereby remain in the source language.
+
+
+
+
+ User settings files<indexterm
+ class="singular">
+ <primary>Project files</primary>
+
+ <secondary>User settings files</secondary>
+ </indexterm>
+
+ User files contain the information, applicable to all the projects
+ for a given user;
+
+
+
+
+
+
+
+ logs/OmegaT.log
+
+ This file records Java error messages while
+ OmegaT is running. Should OmegaT appear
+ to be behaving erratically, it is important to include this file
+ or the relevant part in any bug report
+
+
+
+ script/
+
+ folder, containing script files for the script plugin, if
+ installed
+
+
+
+ filters.xml
+
+ user's default file filters
+
+
+
+ omegat.prefs
+
+ OmegaT preferences
+
+
+
+ segmentation.conf
+
+ user's default segmentation rules
+
+
+
+ uiLayout.xml
+
+ An xml file with all the GUI accessible option
+ settings
+
+
+
+
+
+ Note that default segmentation rules and file filters can be
+ overridden by project-specific setup (see above).The location of user
+ files depends upon the platform you use:
+
+
+
+
+
+
+
+ Windows 2000 and XP
+
+ Documents and Settings\<User
+ Name>\Application
+ Data\OmegaT
+
+
+
+ Windows Vista and 7
+
+ Users\<User
+ Name>\AppData\Roaming\OmegaT
+
+
+
+ Windows other
+
+ <Something>\OmegaT
+ (<Something> corresponds to the location of the "home"
+ folder as determined by Java)
+
+
+
+ Linux/Solaris/FreeBSD
+
+ <User Home>/.omegat (.omegat is a
+ directory, the dot preceding its name makes it invisible unless
+ you type ls -a or an equivalent command)
+
+
+
+ MAC OSX
+
+ <User
+ Home>/Library/Preferences/OmegaT
+
+
+
+ Other
+
+ <User Home>
+
+
+
+
+
+
+
+ Application files<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>Application files</secondary>
+ </indexterm>
+
+ OmegaT is supplied as a package that can be downloaded from
+ SourceForge. Here a platform-independent package in a standard Java form
+ is considered. Alternatives include include a Linux .tar package, a
+ Windows installer – with or without a Java Runtime Environment –, a MacOSX
+ installer, and a source code package for developers.
+
+ The platform-independent package can be used on any platform with a
+ working Java 1.5 runtime environment, including the platforms for which a
+ specific package also exists. It is provided as a compressed file (zip or
+ tar archive) that you must extract to the folder of your choice for
+ installation. The file can usually be extracted by double-clicking on the
+ downloaded package. Once the archive has been extracted, a folder
+ containing the following contents is created:
+
+
+
+
+
+
+
+ File/ subfolder
+
+ Contents
+
+
+
+ /docs/
+
+ All the user manual files can be found in this folder. You
+ can open them in An Internet browser to obtain access to external
+ links.
+
+
+
+ /images/
+
+ Icons and logo graphics
+
+
+
+ /lib/
+
+ Contains Java files, necessary to the operation of
+ OmegaT.
+
+
+
+ join.html
+
+ This is an ordinary html file that, when opened in your
+ Internet browser, directs you to the OmegaT user group hosted on
+ Yahoo Groups. Joining is not necessary, but will provide you with
+ access to additional services, such as files, questionnaires, and
+ the opportunity to take part in OmegaT-related discussions. The
+ group archives are public and can be viewed without subscription
+ to the group.
+
+
+
+ changes.txt
+
+ A relatively detailed list of modifications between this
+ version and the preceding versions.
+
+
+
+ license.txt
+
+ The GNU GENERAL PUBLIC LICENSE. This license allows you to
+ do certain things with OmegaT,
+ including modifying and distributing it. If you are interested in
+ modifying or distributing OmegaT, read
+ this document carefully and ensure you understand its implications
+ before doing anything. If in doubt, don't hesitate to ask project
+ members directly either by sending them an e-mail from the
+ SourceForge page or by sending a public mail to the user
+ group.
+
+
+
+ doc-license.txt
+
+ The GNU GENERAL PUBLIC LICENSE. This license covers the
+ documentation. See above.
+
+
+
+ readme.txt
+
+ This file is very important and you should make sure you
+ read it before launching OmegaT. It includes general information
+ on OmegaT, where to find more information, how to contribute, etc.
+ It has been translated into a number of languages.
+
+
+
+ OmegaT
+
+ A text file containing two lines:
+
+
+
+
+
+ #!/bin/bash java
+
+
+
+
+
+ java -jar
+ OmegaT.jar $*
+
+
+
+
+
+ Linux and OSX users may find this file useful. Make it
+ executable (chmod +x OmegaT) from the command line after making
+ sure you are in the /OmegaT_2.5/ directory. You will then be able
+ to launch OmegaT by executing this file from the command
+ line
+
+
+
+ OmegaT.bat
+
+ A batch file, used to launch
+ OmegaT from the Windows command line.
+ It contains just the following line:
+
+
+
+
+
+ java -jar OmegaT.jar
+ %*
+
+
+
+ OmegaT.jar
+
+ The main OmegaT application. To launch OmegaT, you must
+ launch this file either from the command line or from your file
+ manager, usually by double-clicking it.
+
+
+
+
+
+
diff --git a/OmegaT/doc_src/en/FilesToTranslate.xml b/OmegaT/doc_src/en/FilesToTranslate.xml
new file mode 100644
index 0000000..ff8b496
--- /dev/null
+++ b/OmegaT/doc_src/en/FilesToTranslate.xml
@@ -0,0 +1,441 @@
+
+
+
+ Files to translate
+
+
+ File formats<indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>File formats</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>File formats</secondary>
+ </indexterm>
+
+ You can use OmegaT to translate files in
+ a number of file formats. There are basically two types of file formats,
+ plain text and formatted text.
+
+
+ Plain text files<indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Plain text files</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Plain text files</secondary>
+ </indexterm>
+
+ Plain text files contain text only, so their translation is as
+ simple as typing the translation. There are several methods to specify
+ the file's encoding so that its contents are not garbled when opened in
+ OmegaT. Such files do not contain any
+ formatting information beyond the "white space" used to align text,
+ indicate paragraphs or insert page breaks. They are not able to contain
+ or retain information regarding the color, font etc of the text.
+ Currently, OmegaT supports the following
+ plain text formats:
+ File formats
+
+ Unformatted
+
+ Source files
+
+
+
+
+ ASCII text (.txt, etc.)
+
+
+
+
+
+ Encoded text (*.UTF8)
+
+
+
+
+
+ Java resource bundles (*.properties)
+
+
+
+
+
+ PO files (*.po)
+
+
+
+
+
+ INI (key=value) files (*.ini)
+
+
+
+
+
+ DTD files (*.DTD)
+
+
+
+ DocuWiki files (*.txt)
+
+
+
+
+
+ SubRip title files (*.srt)
+
+
+
+
+
+ Magento CE Locale CSV files (*.csv)
+
+
+
+ Other plain text file types can be handled by
+ OmegaT by associating their file extension to
+ a supported file type (for example, .pod files can be associated to the
+ ASCII text filter) and by pre-processing them with specific segmentation
+ rules.
+
+
+
+ Formatted text files<indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Formatted text files</secondary>
+
+ <seealso>Tagged text</seealso>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Formatted text files</secondary>
+ </indexterm>
+
+ Formatted text files contain information such as font type, size,
+ color etc. as well as text. They are commonly created in word processors
+ or HTML editors. Such file formats are designed to hold formatting
+ information. The formatting information can be as simple as “this is
+ bold”, or as complex as table data with different font sizes, colors,
+ positions, etc. In most translation jobs, it is considered important for
+ the formatting of the original text to be retained in the translation.
+ OmegaT allows you to do this by marking the characters/words that have a
+ special formatting with easy-to-handle tags. Simplifying the original
+ text formatting greatly contributes to reducing the number of tags.
+ Where possible, unifying the fonts, font sizes, colors, etc. used in the
+ document simplifies the task of translation and reduces the possible
+ number of tag errors. Each file type is handled differently in OmegaT.
+ Specific behavior can be set up in the file filters. At the time of
+ writing, OmegaT supports the following formatted text formats:
+
+ File formats
+
+ formatted
+
+ Source files
+
+
+
+
+ OpenOffice.org / OpenDocument (*.ods, *.ots, *.odt, *.ott,
+ *.odp, *.otp)
+
+
+
+ Microsoft Office Open XML (*.docx, *.dotx, *.xlsx, *.xltx,
+ *.pptx)
+
+
+
+ (X)HTML (*.html, *.xhtml,*.xht)
+
+
+
+ HTML Help Compiler (*.hhc, *.hhk)
+
+
+
+ DocBook (*.xml)
+
+
+
+ XLIFF (*.xlf, *.xliff, *.sdlxliff) - monolingual, i.e. one
+ language combination possible for a given project
+
+
+
+ QuarkXPress CopyFlowGold (*.tag, *.xtg)
+
+
+
+ ResX files (*.resx)
+
+
+
+ Android resource (*.xml)
+
+
+
+ LaTex (*.tex, *.latex)
+
+
+
+ Help (*.xml) and Manual (*.hmxp) files
+
+
+
+ Typo3 LocManager (*.xml)
+
+
+
+ WiX Localization (*.wxl)
+
+
+
+ Iceni Infix (*.xml)
+
+
+
+ Flash XML export (*.xml)
+
+
+ Wordfast TXML (*.txml)
+
+
+ Camtasia for Windows (*.camproj)
+
+
+
+
+ Other formatted text file types may also be handled by OmegaT by
+ associating their file extensions to a supported file type, assuming
+ that the corresponding segmentation rules will segment them
+ correctly.
+
+
+
+
+ Other file formats<indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Other file formats</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Other file formats</secondary>
+ </indexterm>
+
+ Other plain text or formatted text file formats suitable for
+ processing in OmegaT may also exist.
+
+
+ Target files
+
+ File conversion tools
+ External tools can be used to convert files to supported
+ formats. The translated files will then need to be converted back to the
+ original format. For example, if you have an outdated Microsoft Word
+ version, that does not handle the ODT format, here's a round trip for Word
+ files with the DOC extension:
+
+
+
+ import the file into OpenOffice.org writer
+
+
+
+
+
+ save the file in ODT format
+
+
+
+
+
+ translate it into the target ODT file
+
+
+
+
+
+ load the target file in OpenOffice.org writer
+
+
+
+
+
+ save the file as a DOC file
+
+
+
+ The quality of formatting of the translated file will depend on the
+ quality of the round-trip conversion. Before proceeding with such
+ conversions, be sure to test all options. Check the OmegaT home page for an up-to-date
+ listing of auxiliary translation tools.
+
+
+
+ Right to left languages<indexterm class="singular">
+ <primary>Right to left languages</primary>
+ </indexterm><indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Right to left languages</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Right to left languages</secondary>
+ </indexterm>
+
+ Justification of source and target segments depends upon the project
+ languages. By default, left justification is used for Left-To-Right (LTR)
+ languages and right justification for Right-To-Left (RTL) languages. You
+ can toggle between different display modes by pressing
+ Shift
+
+ Ctrl
+
+ O
+ (this is the letter O and not the numeral 0). The
+ Shift
+
+ Ctrl
+
+ O
+ toggle has three states:
+
+
+
+ default justification, that is as defined by the language
+
+
+
+
+
+ left justification
+
+
+
+
+
+ right justification
+
+
+
+ Using the RTL mode in OmegaT has no
+ influence whatsoever on the display mode of the translated documents
+ created in OmegaT. The display mode of the
+ translated documents must be modified within the application (such as
+ Microsoft Word) commonly used to display or modify them (check the
+ relevant manuals for details). Using
+ Shift
+
+ Ctrl
+
+ O
+ causes both text input and display in
+ OmegaT to change. It can be used separately for
+ all three panes (Editor, Fuzzy Matches and Glossary) by clicking on the
+ pane and toggling the display mode. It can also be used in all the input
+ fields found in OmegaT - in the search window,
+ for segmentation rules etc.
+
+ Mac OS X users, note: use
+ Shift
+
+ Ctrl
+
+ O
+ shortcut and not
+ cmd+Ctrl+O.
+
+
+ Mixing RTL and LTR strings in segments<indexterm class="singular">
+ <primary>Right to left languages</primary>
+
+ <secondary>Mixing RTL and LTR strings</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Mixing RTL and LTR strings</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Mixing RTL and LTR strings</secondary>
+ </indexterm>
+
+ When writing purely RTL text, the default (LTR) view may be used.
+ In many cases, however, it is necessary to embed LTR text in RTL text.
+ For example, in OmegaT tags, product names that must be left in the LTR
+ source language, place holders in localization files, and numbers in
+ text. In cases like these it becomes necessary to switch to RTL mode, so
+ that the RTL (in fact bidirectional) text is displayed correctly. It
+ should be noted that when OmegaT is in RTL
+ mode, both source and target are displayed in RTL mode. This means that
+ if the source language is LTR and the target language is RTL, or vice
+ versa, it may be necessary to toggle back and forth between RTL and LTR
+ modes to view the source and enter the target easily in their respective
+ modes.
+
+
+
+ <application>OmegaT</application> tags in RTL segments<indexterm
+ class="singular">
+ <primary>Right to left languages</primary>
+
+ <secondary>OmegaT tags in RTL languages</secondary>
+ </indexterm>
+
+ As stated above, OmegaT tags are LTR strings. When translating
+ between RTL and LTR languages, correctly reading the tags from the
+ source and entering them properly in the target may require the
+ translator to toggle between LTR and RTL modes numerous times.
+
+ If the document allows, the translator is strongly encouraged to
+ remove style information from the original document so that as few tags
+ as possible appear in the OmegaT interface. Follow the indications given
+ in Hints for tags management. Frequently validate tags (see Tag
+ validation) and produce translated documents (see below and Menu) at
+ regular intervals to make it easier to catch any problems that arise. A
+ hint: translating a plain text version of the text and adding the
+ necessary style in the relevant application at a later stage may turn
+ out to be less hassle.
+
+
+
+ Creating translated RTL documents<indexterm class="singular">
+ <primary>Right to left languages</primary>
+
+ <secondary>Creating RTL target files</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Right to left languages</primary>
+
+ <secondary>Target files</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Right to left languages</primary>
+
+ <secondary>Creating RTL target text</secondary>
+ </indexterm>
+
+ When the translated document is created, its display direction
+ will be the same as that of the original document. If the original
+ document was LTR, the display direction of the target document must be
+ changed manually to RTL in its viewing application. Each output format
+ has specific ways of dealing with RTL display; check the relevant
+ application manuals for details.
+
+ To avoid changing the target files display parameters each time
+ the files are opened, it may be possible to change the source file
+ display parameters such that such parameters are inherited by the target
+ files. Such modifications are possible in OpenOffice.org files for
+ example.
+
+
+
diff --git a/OmegaT/doc_src/en/FormattedText.xml b/OmegaT/doc_src/en/FormattedText.xml
new file mode 100644
index 0000000..ed07b85
--- /dev/null
+++ b/OmegaT/doc_src/en/FormattedText.xml
@@ -0,0 +1,334 @@
+
+
+
+ Working with formatted text<indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Formatted text</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Formatted text</secondary>
+ </indexterm>
+
+ Formatting information present in the source file usually needs to be
+ reproduced in the target file. The in-line formatting information made
+ possible by the supported formats (in particular DocBook, HTML, XHTML, Open
+ Document (OpenOffice.org) and Office Open XML (MS Office 2007 and later) at
+ the time of writing) is presented as tags in OmegaT. Normally tags are
+ ignored when considering the similarity between different texts for matching
+ purposes. Tags reproduced in the translated segment will be present in the
+ translated document.
+
+
+ Formatting tags<indexterm class="singular">
+ <primary>Tags</primary>
+ </indexterm>
+
+
+ Tags
+
+ Naming
+ Tag naming:
+
+ The tags consist of one to three characters and a number. Unique
+ numbering allows tags, corresponding to each other to be grouped together
+ and differentiates between tags, that have the same shortcut character,
+ but are in fact different. The shortcut characters used try to reflect the
+ underlying meaning of the tag (e.g. b for bold, i for italics,
+ etc.)
+
+
+ Tags
+
+ Numbering
+ Tag numbering:
+
+ Tags are numbered incrementally by tag group. "Tag groups" in this
+ context are a single tag (such as <i0> and </i0>). Within a
+ segment, the first group (pair or single) receives the number 0, the
+ second the number 1 etc. The first example below has 3 tag groups (a pair,
+ a single, and then another pair), the second example has one group only (a
+ pair).
+
+
+ Tags
+
+ Pairs and singles
+ Pairs and singles:
+
+ Tags are always either singles or paired. Single tags indicate
+ formatting information that does not affect the surrounding text (an extra
+ space or line break for example).
+
+ <b0><Ctr+N></b0>,
+ <br1><b2><Enter></b2><segment 2132>
+
+
+ <br1> is a single tag and does not affect any surrounding
+ text. Paired tags usually indicate style information that applies to the
+ text between the opening tag and the closing tag of a pair. <b0> and
+ </b0> below are paired and affect the text log.txt. Note that the
+ opening tag must always come before the corresponding closing tag:
+
+ <Log file (<b0>log.txt</b0>) for tracking
+ operations and errors.<segment 3167>
+
+ OmegaT creates its tags before the
+ process of sentence segmenting. Depending upon the segmenting rules, the
+ pair of tags may get separated into two consecutive segments and the tag
+ validation will err on the side of caution and mark the two
+ segments.
+
+
+
+ Tag operations<indexterm class="singular">
+ <primary>Tags</primary>
+
+ <secondary>Operations</secondary>
+ </indexterm>
+
+ Care must be exercised with tags. If they are accidentally changed,
+ the formatting of the final file may be corrupted. The basic rule is that
+ the sequence of tags must be preserved in the same order. However, it is
+ possible, if certain rules are strictly followed, to deviate from this
+ basic rule.
+
+
+ Tags
+
+ Duplication
+ Tag duplication:
+
+ To duplicate tag groups, just copy them in the position of your
+ choice. Keep in mind that in a pair group, the opening tag must come
+ before the closing tag. The formatting represented by the group you have
+ duplicated will be applied to both sections.
+
+ Example:
+
+ <b0>This formatting</b0> is going to be
+ duplicated here.<segment 0001>
+
+ After duplication:
+
+ <b0>This formatting</b0> has been
+ <b0>duplicated here</b0>.<segment 0001>
+
+
+
+ Tags
+
+ Group deletion
+ Tag group deletion:
+
+ To delete tag groups, just remove them from the segment. Keep in
+ mind that a pair group must have both its opening and its closing tag
+ deleted to ensure that all traces of the formatting are properly erased,
+ otherwise the translated file may become corrupted. By deleting a tag
+ group you will remove the related formatting from the translated
+ file.
+
+ Example:
+
+ <b0>This formatting</b0> is going to be
+ deleted.<segment 0001>
+
+ After deletion:
+
+ This formatting has been deleted.<segment 0001>
+
+
+
+
+ Tag group nesting<indexterm class="singular">
+ <primary>Tags</primary>
+
+ <secondary>Group nesting</secondary>
+ </indexterm>
+
+ Modifying tag group order may result in the nesting of a tag group
+ within another tag group. This is acceptable, provided the enclosing group
+ totally encloses the enclosed group. In other words, when moving paired
+ tags, ensure that both the opening and the closing tag are both either
+ inside or outside other tag pairs, or the translated file may be corrupted
+ and fail to open.
+
+ Example:
+
+ <b0>Formatting</b0> <b1>one</b1> is
+ going to be nested inside formatting zero.<segment 0001>
+
+
+ After nesting:
+
+ <b0>Formatting <b1>one</b1></b0>
+ has been nested inside formatting zero.<segment
+ 0001>
+
+
+
+ Tag group overlapping<indexterm class="singular">
+ <primary>Tags</primary>
+
+ <secondary>Group overlapping</secondary>
+ </indexterm>
+
+ Overlapping is the result of bad manipulations of tag pairs and is
+ guaranteed to result in formatting corruption and sometimes in the
+ translated file not opening at all.
+
+ Example:
+
+ <b0>Formatting</b0> <b1>one</b1> is
+ going to be messed up.<segment 0001>
+
+ After a bad manipulation:
+
+ <b0>Formatting <b1>one</b0> </b1>is
+ very messed up now.<end segment 0001>
+
+
+
+ Tag validation options
+
+ To customize the work with tags, one can set down some of the rules
+ in the Options > Tag validation...
+ window:
+
+
+
+
+
+
+
+ The behaviour, stated here, applies to all the source files and not
+ just to some of the file types, like formatted text.
+
+
+
+ Printf variables
+
+ OmegaT can check that programming variables (like %s for
+ instance) in the source exist in the translation. You can decide not
+ to check at all, check for simple printf variables (like %s %d etc) or
+ for print variables of all types. .
+
+
+
+
+
+ check simple java MessageFormat patterns
+
+ Activating this check box will cause OmegaT to check if simple
+ java MessageFormat tags (like {0}) are processed correctly.
+
+
+
+
+
+ Text field Custom tags
+
+ Entering a regular expression here will cause OmegaT treat the
+ detected instances as a customer tag. It is checked if the number of
+ tags and their order is identical, just like it is the case for
+ omegat-tags.
+
+
+
+
+
+ Fragments that should be removed from the translation
+
+ One can enter a regular expression which will remove any of its
+ instances from the source segment - after it has been extracted from
+ the file and before it is shown in the editor window.
+
+
+
+
+
+ Tag group validation<indexterm class="singular">
+ <primary>Tags</primary>
+
+ <secondary>Group validation</secondary>
+ </indexterm>
+
+ The validate tags function detects changes to tag sequences (whether
+ deliberate or accidental), and shows the affected segments. Launching this
+ function – Ctrl+T
+ Shortcuts
+
+ Ctrl+T - Tag validation
+ - opens a window containing all segments in
+ the file containing suspected broken or bad tags in the translation.
+ Repairing the tags and recreating the target documents is easy with the
+ validate tags function. The window that opens when
+ Ctrl+T is pressed features a 3-column table
+ with a link to the segment, the original segment and the target
+ segment
+
+
+ Tag validation entry
+
+
+
+
+
+
+
+
+
+
+
+
+ The tags are highlighted in bold blue for easy comparison between
+ the original and the translated contents. Click on the link to activate
+ the segment in the Editor. Correct the error if necessary (in the case
+ above it is the missing <i2></i2> pair) and press
+ Ctrl+T to return to the tag validation window
+ to correct other errors. Tag errors are tag sequences in the translation
+ in which the same tag order and number as in the original segment is not
+ reproduced. Some tag manipulations are necessary and are benign, others
+ will cause problems when the translated document is created.
+
+
+
+ Hints for tags management<indexterm class="singular">
+ <primary>Tags</primary>
+
+ <secondary>Hints</secondary>
+ </indexterm>
+
+ Simplify the original text
+
+ Tags generally represent formatting in some form of the original
+ text. Simplifying the original formatting greatly contributes to reducing
+ the number of tags. Where circumstances permit, unifying used fonts, font
+ sizes, colors, etc. should be considered, as it could simplify the
+ translation and reduce the potential for tag errors. Read the tag
+ operations section to see what can be done with tags. Remember that if you
+ find tags a problem in OmegaT and formatting is not extremely relevant for
+ the current translation, removing tags may be the easiest way out of
+ problems.
+
+ Pay extra attention to tag
+ pairs
+
+ If you need to see tags in OmegaT but do not need to retain most of
+ the formatting in the translated document you are free not to include tags
+ in the translation. In this case pay extra attention to tag pairs since
+ deleting one side of the pair but forgetting to delete the other is
+ guaranteed to corrupt your document's formatting. Since tags are included
+ in the text itself, it is possible to use segmentation rules to create
+ segments with fewer tags. This is an advanced feature and some experience
+ is required in order for it to be applied properly.
+
+ OmegaT is not yet able to detect mistakes in formatting fully
+ automatically, so it will not prompt you if you make an error or change
+ formatting to fit your target language better. Sometimes, however, your
+ translated file may look strange, and – in the worst case – may even
+ refuse to open.
+
+
diff --git a/OmegaT/doc_src/en/Glossaries.xml b/OmegaT/doc_src/en/Glossaries.xml
new file mode 100644
index 0000000..11045fe
--- /dev/null
+++ b/OmegaT/doc_src/en/Glossaries.xml
@@ -0,0 +1,291 @@
+
+
+
+ Glossaries<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Glossary pane</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Glossaries</primary>
+ </indexterm>
+
+ Glossaries are files created and updated manually for use in
+ OmegaT.
+
+ If an OmegaT project contains one or more
+ glossaries, any terms in the glossary which are also found in the current
+ segment will be automatically displayed in the Glossary viewer.
+
+ You define its location and name in the project properties dialog. The
+ extension must be .txt (if not, it will be added). The
+ location of the file must be within the /glossary
+ folder, but it can be in a deeper directory (e.g.,
+ glossary/sub/glossary.txt). The file does not need to
+ exist when setting it, it will be created (if necessary) when adding a
+ glossary entry. If the file already exists, not attempt is done to verify
+ the format or the character set of the file: the new entries will always be
+ in tab-separated format and UTF-8. As the existing content will not be
+ touched, damaged to an existing file would be limited.
+
+
+ Usage
+
+ To use an existing glossary, simply place it in the
+ Project files
+
+ Glossary subfolder
+ /glossary folder after creating the
+ project. OmegaT automatically detects glossary
+ files in this folder when a project is opened. Terms in the current
+ segment which OmegaT finds in the glossary
+ file(s) are displayed in the Glossary pane:
+
+
+ Glossary pane
+
+
+
+ Glossary pane
+
+
+
+
+
+
+
+
+
+
+
+
+ The word before the = sign is the source term, and its translation
+ is (or are) the words after =. The vocabulary entry can have a comment
+ added (see "transitive verb" for the second item). The glossary function
+ only finds exact matches with the glossary entry (e.g. does not find
+ inflected forms etc.). New terms can be added manually to the glossary
+ file(s) during translation (for example in a text editor), but newly added
+ terms will not be recognized until the project is reloaded.
+
+ The source term does not have to be a single-word item, as the next
+ example shows:
+
+
+ multiple words entries in glossaries - example<indexterm
+ class="singular">
+ <primary>Glossary pane - multiple-words entries</primary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+ The underlined item "pop-up menu" can be found in the glossary pane
+ as "pojavni menu". Highlighting it in the Glossary pane and then
+ rightclicking insets at the cursor position in the target
+ segment.
+ Note that in the above case, this is just half (or even less) of
+ the story, as the target language (Slovenian) uses declension. So the
+ inserted "pojavni meni" has to be changed to "pojavnem meniju". In
+ other words, typing the term correctly without bothering with
+ highlighting and rightclicking is probably faster.
+
+
+
+
+ <indexterm class="singular">
+ <primary>Glossaries</primary>
+
+ <secondary>File format</secondary>
+ </indexterm>File format<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>User files</secondary>
+
+ <seealso>Glossaries</seealso>
+ </indexterm>
+
+ Glossary files are simple plain text files containing three-column,
+ tab-delimited lists with the source and target terms in the first and
+ second columns respectively. The third column can be used for additional
+ information. You can have entries with the target column missing, i.e.
+ just containing the source term and the comment.
+
+ Glossary files can be either in system default encoding (and
+ indicated by the extension .tab) or in UTF-8 (the extension .utf8). The
+ Unicode encoding (UTF8) is preferred for obvious reasons. Also supported
+ is the CSV format. This format is the same as the tab separated one:
+ source term, target term. Comment fields are separated by a comma ','.
+ Strings can be enclosed by quotes ", which allows having a comma inside a
+ string:
+
+ "This is a source term, which contains a comma","c'est un
+ terme, qui contient une virgule"
+
+ In addition to the plain text format, TBX format
+ Glossaries
+
+ TBX format
+ is also supported. TBX - Term Base eXchange - is the open,
+ XML-based standard for exchanging structured terminological data, TBX has
+ been approved as an international standard by LISA
+ LISA -
+
+ File format
+ and ISO. If you have an existing terminology handling
+ system - MultiTerm for example - it is quite possible it offers the export
+ of terminology data via TBX format. Microsoft
+ Terminology Collection
+ Glossaries
+
+ Microsoft Terminology collection
+ can be downloaded in nearly 100 languages and can serve as
+ a cornerstone IT glossary.
+
+
+
+ How to create glossaries<indexterm class="singular">
+ <primary>Glossaries</primary>
+
+ <secondary>Creating a glossary</secondary>
+ </indexterm>
+
+ The project setting allows one can enter a name for a writable
+ glossary file (see beginning of this chapter). Adding new entries is done
+ by using the keyboard shortcut Ctrl+Shift+G . A dialog
+ opens, allowing you to enter the source term, target term and any comments
+ you may have:
+
+
+
+
+
+
+
+
+
+
+
+ The contents of glossary files are kept in memory and are loaded
+ when the project is opened or reloaded. Updating a glossary file is thus
+ rather simple: press Ctrl+Shift+G and enter the new
+ term, its translation and any comments you may have (ensuring you press
+ tab between the fields) and save the file. The contents of the glossary
+ pane will be updated accordingly.
+
+
+ Glossaries
+
+ Location of the writable glossary file
+ The location of the writable glossary file can be set in the
+ Project > Properties ... dialog. The recognized extensions are
+ TXT and UTF8
+
+ Note: Of course there are other
+ ways and means to create a simple file with tab delimited entries. Nothing
+ speaks against using Notepad++ on Windows, GEdit on Linux for instance or
+ some spreadsheet program for this purpose: any application, that can
+ handle UTF8 and that can show white space (so that you do not miss the
+ required TAB characters) can be used.
+
+
+
+ <indexterm class="singular">
+ <primary>Glossaries</primary>
+
+ <secondary>Trados MultiTerm</secondary>
+ </indexterm>Using Trados MultiTerm
+
+ Data exported from Trados MultiTerm can be used as
+ OmegaT glossaries without further modification,
+ provided they are given the file extension .tab and
+ the source and target term fields are the first two fields respectively.
+ If you export using the system option "Tab-delimited export", you will
+ need to delete the first 5 columns (Seq. Nr, Date created etc). The newer
+ versions of MultiTerm support exporting to TBX format.
+
+
+
+ <indexterm class="singular">
+ <primary>Glossaries</primary>
+
+ <secondary>Problems with glossaries</secondary>
+ </indexterm>Common glossary problems
+
+ Problem: No glossary terms are displayed -
+ possible causes:
+
+
+
+ No glossary file found in the "glossary" folder.
+
+
+
+
+
+ The glossary file is empty.
+
+
+
+
+
+ The items are not separated with a TAB character.
+
+
+
+
+
+ The glossary file does not have the correct extension (.tab or
+ .utf8).
+
+
+
+
+
+ There is no EXACT match between the glossary entry and the
+ source text in your document - for instance plurals.
+
+
+
+
+
+ The glossary file does not have the correct encoding.
+
+
+
+
+
+ There are no terms in the current segment which match any terms
+ in the glossary.
+
+
+
+
+
+ One or more of the above problems may have been fixed, but the
+ project has not been reloaded.
+
+
+
+ Problem: In the glossary pane, some characters
+ are not displayed properly
+
+
+
+ ...but the same characters are displayed properly in the Editing
+ pane: the extension and the file encoding do not match.
+
+
+
+
diff --git a/OmegaT/doc_src/en/InstallingAndRunning.xml b/OmegaT/doc_src/en/InstallingAndRunning.xml
new file mode 100644
index 0000000..fe178dd
--- /dev/null
+++ b/OmegaT/doc_src/en/InstallingAndRunning.xml
@@ -0,0 +1,1086 @@
+
+
+
+ Installing and running <application>OmegaT</application>
+
+
+ Windows Users<indexterm class="singular">
+ <primary>Installing OmegaT</primary>
+
+ <secondary>Windows</secondary>
+ </indexterm>
+
+
+ Downloading the
+ package
+
+ Do you have a Java implementation compatible with Oracle's Java
+ 1.5 JRE?
+
+
+
+ Yes: download
+ OmegaT_2.5.x_Windows_without_JRE.exe.
+
+
+
+ No / I don't know:
+ download OmegaT_2.5.x_Windows.exe.
+
+ This package is bundled with Oracle's Java Runtime
+ Environment. This JRE will not interfere with other Java
+ implementations that may already be installed on your system.
+
+
+
+
+
+ <application>Installing OmegaT</application>
+
+ To install OmegaT, double-click on the
+ program you have downloaded, and follow the instructions
+
+
+
+ Adding <application>OmegaT</application> to the start menu or
+ desktop<indexterm class="singular">
+ <primary>Customizing OmegaT</primary>
+
+ <secondary>Windows</secondary>
+ </indexterm>
+
+ During the installation, the setup program asks you whether you
+ wish to create a folder in the start menu, and
+ whether you wish to create a shortcut on the desktop and in the quick
+ launch bar.
+
+ You can still create a shortcut later by dragging
+ OmegaT.exe to the
+ desktop or start menu to link it from there.
+
+
+
+ Running <application>OmegaT<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Windows</secondary>
+ </indexterm></application>
+
+ Once OmegaT is installed, you can click
+ on OmegaT.jar to launch
+ it directly or you can launch it directly from the command line.
+
+ The simplest way to launch OmegaT, however, is to execute
+ theOmegaT.exe program.
+
+ Running OmegaT
+
+ Windows
+
+ INI file
+ The options for the program start-up in this case will be
+ read from the OmegaT.l4J.ini
+ file, which resides in the same folder as the exe file and
+ which you can edit to reflect your setup. The following example for the
+ INI file reserves 1GB of memory, requests French as the user language
+ and Canada as the country:
+
+ # OmegaT.exe runtime configuration
+# To use a parameter, remove the '#' before the '-'
+# Memory
+-Xmx1024M
+# Language
+-Duser.language=FR
+# Country
+-Duser.country=CA
+
+
+
+ Upgrading OmegaT <indexterm class="singular">
+ <primary>Upgrading OmegaT</primary>
+
+ <secondary>Windows</secondary>
+ </indexterm>
+
+ This information applies only to the "Traditional"
+ Windows versions of OmegaT. It does not apply to the Web Start versions,
+ which are upgraded automatically, nor to cross-platform versions
+ installed on Windows.
+
+ If you already have a version of OmegaT installed on your PC and
+ wish to upgrade to a more recent version, you have two options:
+
+
+
+ Install over the existing installation.
+ To do this, simply select the same installation folder as
+ the existing installation when installing the new version. The "old"
+ version of OmegaT will be overwritten, but any settings from it will
+ be retained. This includes preferences set from within OmegaT, any
+ changes you have made to your OmegaT.l4J.ini
+ file, and also your launch script (.bat file), if you are using
+ one.
+
+
+
+ With this method, you may also download the "Windows without JRE"
+ version, since the new installation will use your existing JRE.
+
+
+
+ Install to a new folder. This
+ will enable you to keep both versions side-by-side, which you may
+ wish to do until you feel comfortable with the new version. This
+ method will also use preferences and settings you have made from
+ within OmegaT. In this case, however:
+
+
+
+ If you have made changes to your OmegaT.l4J.ini
+ file and/or are using a .bat file, you must copy
+ these over.
+
+
+
+
+
+ If your existing OmegaT installation is a "Windows with
+ JRE" version, the new version must also be a "Windows with JRE"
+ version.
+
+
+
+
+
+
+
+
+ Linux (Intel) Users<indexterm class="singular">
+ <primary>Installing OmegaT</primary>
+
+ <secondary>Linux</secondary>
+ </indexterm>
+
+
+ Downloading the right package
+
+ Do you have a Java implementation compatible with Oracle's Java
+ 1.5 JRE?
+
+
+
+ Yes: download
+ OmegaT_2.5.x_Without_JRE.zip.
+
+
+
+ No / I don't know: download
+ OmegaT_2.5.x_Linux.tar.bz2.
+
+ This package is bundled with Oracle's Java Runtime
+ Environment. This JRE will not interfere with other Java
+ implementations that may already be installed on your system.
+
+
+
+
+
+ <application>Installing OmegaT</application>
+
+ Unpack/untar the downloaded file. This will create an omegat/
+ folder in the working folder in which you will find all the files needed
+ to run OmegaT. To untar the
+ .tar.gz file:
+
+ $ tar xf downloaded_file.tar.gz
+
+
+
+ Adding <application>OmegaT</application> to your menus (KDE) or
+ panels (Gnome)
+
+
+ KDE 4 Users<indexterm class="singular">
+ <primary>Customizing OmegaT</primary>
+
+ <secondary>KDE 4</secondary>
+ </indexterm>
+
+ You can add OmegaT to your menus as
+ follows:
+
+
+
+ Press Alt+F2
+ to show KRunner. Type
+ kmenuedit+enter to run the command. The
+ KMenuEditor appears. In KMenuEditor select File ->
+ New Item.
+
+
+
+ Then, after selecting a suitable menu, add a submenu/item
+ with File - New Submenu and File -
+ New Item. Enter OmegaT as
+ the name of the new item.
+
+
+
+ In the "Command" field, use the navigation button to find
+ your OmegaT launch script (the file
+ named OmegaT in the unpacked folder),
+ and select it.
+
+
+
+ Click on the icon button (to the right of the
+ Name/Description/Comment fields)
+
+
+
+ Other Icons - Browse, and navigate to the /images subfolder
+ in the OmegaT application folder.
+ Select the OmegaT.png icon.
+
+
+
+ Finally, save the changes with File -
+ Save.
+
+
+
+
+
+ GNOME Users<indexterm class="singular">
+ <primary>Customizing OmegaT</primary>
+
+ <secondary>GNOME</secondary>
+ </indexterm>
+
+ You can add OmegaT to your menus as
+ follows:
+
+
+
+ Right-click on the panel - Add New
+ Launcher.
+
+
+
+ Enter "OmegaT" in the "Name"
+ field; in the "Command" field, use the navigation button to find
+ your OmegaT launch script (the file
+ named OmegaT in the unpacked folder).
+ Select it and confirm with OK.
+
+
+
+ Click on the icon button, then hit
+ Browse... and navigate to the /images
+ subfolder in the OmegaT application
+ folder. Select the
+ OmegaT.png icon.
+ GNOME may fail to display the icon files in the available formats
+ and initially appear to expect an SVG file, but if the folder is
+ selected, the files should appear and
+ OmegaT.png can be selected.
+
+
+
+
+
+
+ Running <application>OmegaT<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Linux</secondary>
+ </indexterm></application>
+
+ You can launch OmegaT from the command line with a script that
+ includes start-up options or you can click on
+ OmegaT.jar to launch it
+ directly. Methods differ depending on the distribution. Make sure that
+ your PATH settings are correct and that
+ .jar files are properly associated with a Java
+ launcher. Check "Command line launching" below for more
+ information.
+
+
+
+
+ Mac OS X Users<indexterm class="singular">
+ <primary>OS X</primary>
+
+ <secondary>Installing OmegaT</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Installing OmegaT</primary>
+
+ <secondary>OS X</secondary>
+ </indexterm>
+
+
+ Downloading the package
+
+ OmegaT 2.5 requires Java 1.5 to run.
+ Use "Software Update..." from the Apple menu to update your Java
+ version.
+
+ Download OmegaT_2.5.x_Mac.zip.
+
+
+
+ <application>Installing OmegaT </application>
+
+ Double click on OmegaT_2.5.x_Mac.zip to
+ unpack it. This creates a folder called
+ OmegaT. The folder contains 2
+ files: index.html and
+ OmegaT.app. Copy the
+ folder to a suitable folder (e.g. Applications). Once you have done
+ this, you can delete the OmegaT_2.5.x_Mac.zip file,
+ it is no longer needed.
+
+
+
+ Adding <application>OmegaT</application> to the Dock<indexterm
+ class="singular">
+ <primary>OS X</primary>
+
+ <secondary>Adding OmegaT to the Dock</secondary>
+
+ <seealso>Customizing OmegaT</seealso>
+ </indexterm>
+
+ Drag and drop
+ OmegaT.app onto the
+ Dock.
+
+
+
+ Running <application>OmegaT<indexterm class="singular">
+ <primary>OS X</primary>
+
+ <secondary>Running OmegaT</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>OS X</secondary>
+ </indexterm></application>
+
+ Double-click on
+ OmegaT.app or click on its
+ location in the Dock.
+
+ To access
+ Info.plist, right-click
+ on OmegaT.app and select
+ "Show Package Contents", then open the file by right-clicking on it and
+ selecting your text editor of choice. You can also "cd" there directly
+ from the command line and open
+ Info.plist in a command line editor
+ like emacs or vi.
+ OS X
+
+ Customizing OmegaT
+
+ Launch parameters
+
+ OS X
+
+ Customizing OmegaT
+
+
+ You can modify the Properties as well as the
+ VMOptions part.
+
+ If you wish to add values to VMOptions, put a
+ space between them. For example, -Xmx1024M
+ -Duser.language=ja will launch
+ OmegaT with 1024MB of memory and with the
+ user interface in Japanese.
+
+ To launch multiple instances of
+ OmegaT.app, double-click
+ the file JavaApplicationStub located in
+ OmegaT.app/
+ Contents/MacOS/.
+
+ Use
+ OmegaT.jar file located
+ in
+ OmegaT.app/Contents/Resources/Java/
+ to launch OmegaT from the command line. Check
+ "Command line launching" below for more information.
+
+
+
+ Mac OS X goodies
+
+ OmegaT.app can be
+ accessed from the Mac OS X Services. You can thus select a word anywhere
+ in OmegaT and use Services to check this
+ word, for instance in Spotlight or in Google. You can also use
+ AppleScript or Automator to create Services or scripts that will
+ automate frequent actions
+
+
+
+
+ Other Systems<indexterm class="singular">
+ <primary>Installing OmegaT</primary>
+
+ <secondary>Other systems</secondary>
+ </indexterm>
+
+ This information applies to systems such as Solaris SPARC/x86/x64,
+ Linux x64/PowerPC, Windows x64
+
+
+ Downloading the right
+ package
+
+ OmegaT is available bundled with a
+ Oracle Java JRE for Linux (Intel x86) and Windows platforms. Users of
+ other platforms (Linux PowerPC, Linux x64, Solaris SPARC/x86/x64,
+ Windows x64 etc) must have a running compatible Java JRE on their system
+ to be able to use OmegaT.
+
+ Do you have a Java implementation compatible with Oracle's Java
+ 1.5 JRE?
+
+
+
+ Yes: download
+ OmegaT_2.5.x_Windows_without_JRE.zip. This
+ package can be used on any platform where a Java 1.5 JRE compatible
+ JRE is installed.
+
+
+
+ I don't know: open a terminal
+ and type "java -version". If a "command not found" or similar
+ message is returned, it is likely that Java is not installed on your
+ system
+
+
+
+ No: obtain a Java JRE for
+ your system (see below) and download
+ OmegaT_2.5.x_Without_JRE.zip.
+
+ Oracle provides JREs for Solaris SPARC/x86 (Java 1.5) and for
+ Linux x64, Solaris x64, Windows x64 (Java 1.5) at http://www.oracle.com/technetwork/java/archive-139210.html
+
+ IBM provides JREs for Linux PowerPC at http://www.ibm.com/developerworks/java/jdk/linux/download.htm
+
+ Follow the installation instructions of the package you
+ need.
+
+
+
+
+
+ <application>Installing OmegaT</application><indexterm
+ class="singular">
+ <primary>Installing OmegaT</primary>
+
+ <secondary>Other systems</secondary>
+ </indexterm>
+
+ To install OmegaT, simply unpack the
+ OmegaT_2.5.x_Without_JRE.zip file. This
+ creates an ./OmegaT_2.5.x_Without_JRE/ directory in
+ the working folder with all the files necessary to run
+ OmegaT.
+
+
+
+ Installing convenient shortcuts
+
+ Follow your system's instructions to install
+ OmegaT shortcuts in convenient places of your
+ choosing.
+
+
+
+ Running <application>OmegaT<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Other systems</secondary>
+ </indexterm></application>
+
+ Once OmegaT is installed, you can
+ launch it directly from the command line, you can create a script that
+ includes launch parameters for the command line or you can click on
+ OmegaT.jar to launch it
+ directly. Methods differ depending on the distribution. Make sure that
+ your PATH settings are correct and that
+ .jar files are properly associated with a Java
+ launcher. Check "Command line launching" below for more
+ information.
+
+
+
+
+ Using Java Web Start<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Using Java Web Start</secondary>
+ </indexterm>
+
+ Java Web Start technology (part of Java 1.5 and above) can be used
+ to deploy standalone Java software applications with a single click over
+ the network. Java Web Start ensures that the latest version of the
+ application will be deployed, as well as the correct version of the Java
+ Runtime Environment (JRE) used. To start OmegaT for the first time with
+ Java Web Start, load the following URL in your browser:
+
+ http://omegat.sourceforge.net/webstart/OmegaT.jnlp
+
+ Download the file
+ OmegaT.jnlp and then click on it.
+ During the installation, depending on your operating system, you may
+ receive several security warnings. The permissions you give to this
+ version (which may appear as "unrestricted access to the computer") are
+ identical to the permissions you give to the local version, i.e., they
+ allow access to the hard drive of the computer. Subsequent clicks on
+ OmegaT.jnlp will check for
+ any upgrades, install them, if there are any, and then start
+ OmegaT. After the initial installation you can,
+ of course, also use
+ OmegaT.jnlp also when you
+ are offline.
+
+ Privacy:
+ OmegaT Java Web Start does not save any of your
+ information beyond the computer on which you are running it. The
+ application runs on your machine only. Your documents and translation
+ memories remain on your computer, and the
+ OmegaT project will have no access to your work
+ or information.
+
+ Note that if you need or wish to use any of the launch command
+ arguments (see above), you must use the normal installation.
+
+
+
+ Starting OmegaT from the command line<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Command line launching</secondary>
+ </indexterm>
+
+ Normally, it is not necessary to start
+ OmegaT from the command line. However, the
+ command-line alternative allows the user to control and modify the
+ program's behavior. There are two ways of launching
+ OmegaT using the command line.
+
+
+ Opening a command line window
+
+ A command line window is also referred to as a "terminal window".
+ On Windows it is called an "MS-DOS window" and is available from the
+ Start Menu, inside Programs, through the "MS-DOS" item. The Mac OS X
+ equivalent is the application Terminal located in Applications →
+ Utilities.
+
+ To launch OmegaT, you must normally
+ type two commands. The first of these is:
+
+ cd {folder}
+
+ where {folder} is the name of the folder,
+ with complete path, in which your OmegaT
+ program - specifically, the file
+ OmegaT.jar - is located.
+ In practice, this command will therefore be something like this:
+
+ On Windows
+
+ cd C:\Program
+ Files\OmegaT
+
+ On Mac OS X
+
+ cd <OmegaT.app
+ location>/OmegaT.app/Contents/Resources/Java/
+
+
+ On Linux
+
+ cd /usr/local/omegat
+
+ This command changes the folder to the folder containing the
+ executable OmegaT file. The second command is
+ the command which actually launches OmegaT.
+ In its most basic form, this command is:
+
+ java -jar
+ OmegaT.jar
+
+ Pay attention to the capitalization - the program will not start,
+ if you enter omegat instead of OmegaT
+ !
+
+ This method has a particular benefit of being suitable for finding
+ causes of problems: if an error occurs during use of the program, an
+ error message is output in the terminal window which may contain useful
+ information on the cause of the error.
+
+ The above method somewhat impractical way of launching a program
+ routinely. For this reason, the two commands described above are
+ contained in a file (a "script", also called a ".bat file" on Windows
+ systems).
+
+ When this file is executed, the commands within it are
+ automatically carried out. Consequently, to make changes to the launch
+ command, it is sufficient to modify the file.
+
+
+
+ Launch command arguments<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Launch script arguments</secondary>
+ </indexterm>
+
+ The basic command has already been mentioned above. Changes to
+ this command involve the addition of "arguments" to it. Arguments are
+ added after the initial "java", and before the
+ "-jar OmegaT.jar". Note
+ that in Windows you can change the
+ OmegaT.l4J.ini file to
+ reflect your preferences. On Mac OS X, you can change the
+ Info.plist located in
+ OmegaT.app/Contents/ to
+ do the same.
+
+ A list of possible arguments is given below. Advanced users can
+ obtain more information on the arguments by typing man
+ java in the terminal window.
+
+
+
+ User interface language
+
+
+ -Duser.language=XX
+ Running OmegaT
+
+ Launch script arguments
+
+ User.language
+ Normally, i.e. when OmegaT
+ is launched without any arguments, the program first detects the
+ language of the user's operating system. If a user interface in this
+ language is available, OmegaT uses it.
+ So, if the user's operating system is Russian and
+ OmegaT has been localized in Russian,
+ OmegaT is displayed with a Russian user
+ interface, Russian menus, etc. If the language of the user's system
+ is not available, OmegaT defaults to
+ English. This is the standard behavior.
+
+ The "-Duser.language=XX" argument causes
+ OmegaT to use the language specified
+ rather than the language of the user's operating system. "XX" in the
+ command stands for the two-digit code of the desired language. To
+ launch OmegaT with a French interface
+ (for example on a Russian operating system), the command would
+ therefore be:
+
+ java -Duser.language=fr -jar
+ OmegaT.jar
+
+
+
+
+
+ User country setup
+
+ -Duser.country=XX
+ Running OmegaT
+
+ Launch script arguments
+
+ User.country
+ Besides the language, you can also specify the
+ country, for example CN or TW in case of the Chinese language. To
+ display the instant start guide in the desired language, you need to
+ specify both the language and the country. This is necessary even if
+ there's only one combination available, like pt_BR in case of
+ Portuguese / Brazil.
+
+
+
+
+
+ Font antialiasing - (Java 1.5
+ only)
+
+ -Dswing.aatext=true
+ Running OmegaT
+
+ Launch script arguments
+
+ Font antialiasing
+ This argument effects anti-aliasing of the
+ fonts, thereby improving their appearance.
+
+
+
+ Memory assignment
+
+ -XmxZZM
+ Running OmegaT
+
+ Launch script arguments
+
+ Memory assignment
+ This command assigns more memory to
+ OmegaT. By default, 512 MB are assigned,
+ so there is no advantage in assigning less than this figure. "ZZ"
+ stands for the amount of memory assigned, in megabytes. The command
+ to launch OmegaT with assignment of 1024
+ MB (1 gigabyte) of memory is therefore:
+
+ java -Xmx1024M -jar
+ OmegaT.jar
+
+
+
+ Proxy host IP address
+
+ -Dhttp.proxyHost=nnn.nnn.nnn.nnn
+ Running OmegaT
+
+ Launch script arguments
+
+ Proxy server IP address
+ The IP address of your proxy server, if
+ your system uses a proxy.
+
+
+
+ Proxy Server Port
+ Number
+
+ -Dhttp.proxyPort=NNNN
+
+ Running OmegaT
+
+ Launch script arguments
+
+ Proxy server - Port Number
+ The port number your system uses to access the proxy
+ server.
+
+
+
+ Google Translate V2
+
+ -Dgoogle.api.key=A123456789B123456789C123456789D12345678
+
+ Running OmegaT
+
+ Launch script arguments
+
+ Google Translate V2
+ If you have signed up for the Google
+ Translate services, enter your private Google API key here. Note
+ that the key is 38 characters long.
+
+
+
+ Arguments can be combined: to launch
+ OmegaT with all the examples described above,
+ the command would be:
+
+ java -Dswing.aatext=true -Duser.language=pt
+ -Duser.country=BR -Xmx1024M -DDhttp.proxyHost=192.168.1.1
+ -Dhttp.proxyport=3128 -jar
+ -OmegaT.jar
+
+
+
+ OmegaT in the command line mode<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Command line mode</secondary>
+ </indexterm>
+
+ The purpose of the console mode is to use OmegaT as a translation
+ tool in a scripting environment. When started in console mode, no GUI is
+ loaded (so it will work on any console) and the given project is
+ automatically processed as requested.
+
+
+ Prerequisites
+
+ To run OmegaT in the command line
+ mode, a valid OmegaT project must be
+ present. The location does not matter, since you have to add it to the
+ command line at the start-up anyway.
+
+ If you need altered settings, the configuration files must be
+ available. This can be achieved in two ways:
+
+
+
+ Run OmegaT normally (with the
+ GUI) and specify the settings. If you start
+ OmegaT in console mode, it will use the
+ same settings.
+
+
+
+ If you can't run OmegaT normally
+ (no graphical environment available): copy the settings files from
+ some other OmegaT installation on
+ another machine to a specific directory. The location does not
+ matter, since you can add it to the command line at startup. The
+ relevant files are filters.conf and
+ segmentation.conf and can be found in the user
+ home directory (e.g. C:\Documents and
+ Settings\%User%\OmegaT under
+ Windows, %user%/.omegat/ under Linux)
+
+
+
+
+
+ Starting in console mode
+
+ To start OmegaT in console mode, some
+ extra parameters have to be passed to it on startup. The most
+ important is <project-dir>, and
+ optionally --config-dir=<config-dir>.
+ Example:
+
+ java -jar OmegaT.jar
+ /path/to/project \
+
+ --config-dir=/path/to/config-files/ \
+
+
+ --mode=console-translate|console-createpseudotranslatetmx|console-align
+
+ --source-pattern={regexp}
+
+ Note that all parameters start with a double - character.
+
+ Explanation:
+
+
+
+ <project-dir> tells
+ OmegaT where to find the project to
+ translate. If given, OmegaT starts in
+ console mode and will translate the given project.
+
+
+
+
+
+ --config-dir=<config-dir> tells
+ OmegaT in which directory the
+ configuration files are stored. If not given,
+ OmegaT reverts to default values
+ (OmegaT dir under user home, or if not
+ available, the current working directory). Note double -
+ character
+
+
+
+
+
+ --mode=...-
+ OmegaT starts in console mode to
+ perform one of the following services automatically
+
+
+
+ --mode=console-translate
+
+ In this mode, OmegaT will attempt to translate the files
+ in /source/ with the available translation memories. This is
+ useful to run OmegaT on a server with TMX files automatically
+ fed to a project.
+
+
+
+ --mode=console-createpseudotranslatetmx
+
+ In this mode OmegaT will create a TMX for the whole
+ project, based on the source files only. You specify the TMX
+ file to be created with
+
+ --pseudotranslatetmx=allsegments.tmx
+ --pseudotranslatetype=[equal|empty]
+
+ The argument pseudotranslatetype
+ specifies, whether the target segments are to be equal to the
+ source, or left empty.
+
+
+
+ --mode=console-align
+
+ In this mode, OmegaT will align the Java properties
+ files found in the /source/ folder of the
+ project to the contents found at the specified location. The
+ resulting TMX is stored in the /omegat/
+ folder under the name align.tmx.
+
+ Additional parameter is required in this case,
+ specifying the location of the target data:
+
+ --alignDir={location of translated
+ files}
+
+ alignDir must contain a translation
+ in the target language of the project. For instance, if the
+ project is EN->FR, alignDir must contain a bundle ending
+ with _fr. The resulting tmx is stored in the
+ omegat folder under the name
+ align.tmx.
+
+
+
+
+
+ --source-pattern={regexp}
+
+ When mode has been used, this option will specify the files
+ to be processed automatically.. If the parameter is not specified,
+ all files will be processed. Here's few typical examples to limit
+ your choice:
+
+
+
+ .*\.html
+
+ All HTML files will be translated - note that the period
+ in the usual *.html has to be escaped (\.) as specified by the
+ rules for regular expressions
+
+
+
+ test\.html
+
+ Only the file test.html at the root of the source
+ directory will be translated. If there are other files named
+ test.html in other directories, they will be ignored.
+
+
+
+ dir-10\\test\.html
+
+ Only the file test.html in the directory dir-10 will be
+ processed. Again note that the backslash is escaped as
+ well.
+
+
+
+
+
+ --output-tag-validation-={regexp}
+
+ When mode has been used, this option will specify the files
+ to be processed automatically.. If the parameter is not specified,
+ all files will be processed. Here's few typical examples to limit
+ your choice:
+
+
+
+ .*\.html
+
+ All HTML files will be translated - note that the period
+ in the usual *.html has to be escaped (\.) as specified by the
+ rules for regular expressions
+
+
+
+ test\.html
+
+ Only the file test.html at the root of the source
+ directory will be translated. If there are other files named
+ test.html in other directories, they will be ignored.
+
+
+
+ dir-10\\test\.html
+
+ Only the file test.html in the directory dir-10 will be
+ processed. Again note that the backslash is escaped as
+ well.
+
+
+
+
+
+
+
+ Quiet option
+
+ An extra command line parameter specific to console mode:
+ --quiet. In the quiet mode, less info is logged to
+ the screen. The messages you would usually find in the status bar are
+ not displayed.
+
+ Usage: java -jar OmegaT.jar
+ /path/to/project --mode=console-translate --quiet
+
+
+
+ Tag validation option
+
+ Another extra command line parameter specific to console mode:
+ --tag-validation=[abort|warn]. When this parameter
+ is added, tag validation is done prior to translation/aligning. If the
+ value is abort, then on tag errors the errors are
+ printed and the program stops. If the value is warn
+ then the errors are printed but OmegaT continues.
+
+ Usage: java -jar OmegaT.jar
+ /path/to/project --mode=console-translate
+ --tag-validation=abort
+
+
+
+
+
+ Building <application>OmegaT</application> From Source<indexterm
+ class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Building OmegaT from source</secondary>
+ </indexterm>
+
+ Note that you will need the ant program
+ (http://ant.apache.org/bindownload.cgi) to build your
+ own version of OmegaT. Unpack the
+ OmegaT_2.5.x_Source.zip file and enter the
+ OmegaT_2.5.x_Source directory or enter the ./omegat/
+ directory of the SVN checked out code. Please make sure that a build.xml
+ file is present in that folder. Then, on the command line, type:
+
+ $ ant jar release
+
+ This will create a full distribution of
+ OmegaT in the ./dist/ folder, where you will
+ find all the files necessary to run
+ OmegaT.
+
+
diff --git a/OmegaT/doc_src/en/InstantStartGuide.xml b/OmegaT/doc_src/en/InstantStartGuide.xml
new file mode 100644
index 0000000..a36902b
--- /dev/null
+++ b/OmegaT/doc_src/en/InstantStartGuide.xml
@@ -0,0 +1,183 @@
+
+
+
+ Learn to use OmegaT in 5 minutes!
+
+
+ Set up a new project<indexterm class="singular">
+ <primary>Project</primary>
+
+ <secondary>Create / open new</secondary>
+ </indexterm>
+
+ Note:On an Apple Mac, use the Cmd
+ or Apple key instead of the Ctrl
+ key
+
+ To start using OmegaT, first create a project that will hold all
+ your files, such as your source file, translation memories, glossaries,
+ and eventually your translated file. In the Project
+ menu, select
+
+
+ New...
+
+ Menu Project
+
+ New...
+ type a name for your project. Remember where you create the
+ project, because you will later need to return to it.
+
+ After you give your project a name, the Create New Project dialog
+ will open. At the top of that dialog, select your source file's language
+ and the language that your translated file will be, and click
+ OK to continue
+
+ If you are interested in other settings of this dialog,
+ you can return to it any time by pressing
+ Ctrl+E.
+
+ Next, the Project Files dialog opens. Click the Import source
+ files... to select your source file. OmegaT will then copy the selected
+ file to the /source/subfolder of your newly created
+ project. After the source file has loaded in the Editor pane, you can
+ close the Project files dialog.
+
+
+
+ Translate the file
+
+ OmegaT will present one segment at a time for you to translate.
+ After you have translated each segment, press Ctrl+U to
+ move to the next untranslated segment. Whenever you want to see what your
+ translation will look like in its final format, press
+ Ctrl+D to generate the translated document, which will be
+ created in the /target/ subfolder of your project folder. During
+ translation, use the Edit and Go To
+ menus to perform various useful functions..
+
+
+
+ Validate your tags
+
+ If your source file is a formatted file, e.g. Microsoft Word,
+ LibreOffice Writer or HTML, OmegaT will convert the formatting into tags
+ that surround the text that you translate. Often documents will also have
+ tags that have nothing to do with formatting, but which are also
+ important.In the source file (and in the translated file), A source
+ sentence might look like
+
+
+
+
+
+
+
+
+
+
+
+ OmegaT, however, will present this sentence in the following
+ fashion:
+
+
+
+
+
+
+
+
+
+
+
+ The tags in OmegaT are greyed, so they are easy to recognise. They
+ are not protected, so that you can delete them, enter them by hand or move
+ them around in the target sentence. However, if you made mistakes when you
+ typed the formatting tags, your translated file might fail to open.
+ Therefore, press Ctrl+T before you generate your
+ translated file, to validate that your tags are correct.
+
+
+
+ Generate the translated file
+
+ Once you have made certain that there are no tag errors in your
+ translation, press Ctrl+D to generate the target file,
+ which will be created in the /target/subfolder of
+ your project folder.
+
+
+
+ Few more things to remember
+
+
+
+ If a file does not loads into the Editor pane, then it could be
+ that your source file is in a format that doesn't work in OmegaT. See
+ Chapter 7: File Filters in the User Manual for a list of file formats
+ that OmegaT can handle. If a file does not loads into the Editor pane,
+ then it could be that your source file is in a format that doesn't
+ work in OmegaT. See Chapter 7: File Filters in the User Manual for a
+ list of file formats that OmegaT can handle.
+
+
+
+
+
+ You can create a new project for each new job, and you can add
+ several source files to a project at a time.
+
+
+
+
+
+ To remind yourself of the project's initial settings, open the
+ Project Settings dialog by pressing Ctrl+E. To see a
+ list of files in the project, open the Project Files dialog by
+ pressing Ctrl+L..
+
+
+
+
+
+ At the end of your translation, OmegaT exports three translation
+ memories called "level1", "level2" and "omegat" to your project
+ folder. The "level1" and "level2" memories can be shared with users of
+ other translation programs. The memory named "omegat" can be used in
+ OmegaT itself, in future projects that you create. If you place
+ translation memory files in the /tm/ subfolder of your project folder,
+ OmegaT will automatically search them for similar segments, called
+ "fuzzy matches". .
+
+
+
+
+
+ You can create a glossary by pressing
+ Ctrl+Shift+G, or copy existing glossaries to
+ the/glossary/subfolder of your project folder,
+ and OmegaT will automatically look up words in them.
+
+
+
+
+
+ It is often useful to search for words and phrases in the source
+ text and in your translation, so press Ctrl+F for the
+ "Text Search" dialog at any time.
+
+
+
+
+
+ For a more comprehensive introduction see OmegaT
+ for beginners on the OmegaT web site. If you need assistance
+ with any aspect of OmegaT, feel free to join the OmegaT users
+ group.
+
+
+
+
diff --git a/OmegaT/doc_src/en/MachineTranslation.xml b/OmegaT/doc_src/en/MachineTranslation.xml
new file mode 100644
index 0000000..9ed1848
--- /dev/null
+++ b/OmegaT/doc_src/en/MachineTranslation.xml
@@ -0,0 +1,221 @@
+
+
+
+ Machine Translation<indexterm class="singular">
+ <primary>Machine Translation</primary>
+ </indexterm>
+
+
+ Introduction<indexterm class="singular">
+ <primary>Machine Translation</primary>
+
+ <secondary>Introduction</secondary>
+ </indexterm>
+
+ As opposed to user-generated translation memories (as in the case of
+ OmegaT) Machine translation (MT) tools use
+ rule-based linguistic tools to create a translation of the source segment
+ without the need for a translation memory. Statistical learning
+ techniques, based on source and target texts, are used to build a
+ translation model. Machine translation services have been achieving good
+ and steadfastly improving results in research evaluations.
+
+ To activate any of the Machine Translation services, go to
+ Options > Machine Translate ... and activate
+ the service desired. Note that they are all web-based: you will have to be
+ on-line if you want to use them.
+
+
+
+ Google Translate<indexterm class="singular">
+ <primary>Machine Translation</primary>
+
+ <secondary>Google Translate</secondary>
+ </indexterm>
+
+ Google Translate is a payable service offered by Google, for
+ translating sentences, web sites and complete texts between an
+ ever-growing number of languages. At the time of writing the list includes
+ more than 50 languages, from Albanian to Yiddish, including of course all
+ the major languages. The current version of the service is based on usage,
+ with the price of 20 USD per million characters at the time of writing.
+
+
+ Important: Google Translate API v2
+ requires billing information for all accounts before you can start using
+ the service (see Pricing
+ and Terms of Service for more). To identify yourself as a valid
+ user for the Google services, you use your private unique key sent to you
+ by Google, when you have registered for the service. See chapter Installing and Running,
+ section Launch command arguments, for details on how to add this key to
+ the OmegaT environment.
+
+ The quality of the Google Translate translation depends on one side
+ on the reservoir of target-language texts and the availability of their
+ bilingual versions, on the other hand on the quality of the models built.
+ It is pretty much certain that while the quality may be insufficient in
+ some cases, it will definitely get better with time and not worse.
+
+
+
+ <application>OmegaT</application> users and Google
+ Translate
+
+ The OmegaT user is not forced to use
+ Google Translate. If used, neither the user's decision to accept the
+ translation nor the final translation are made available to Google. The
+ following window shows an example of a) the English source b) Spanish and
+ c) Slovenian Google Translate translation.
+
+
+ Google Translate - example
+
+
+
+
+
+
+
+
+
+
+
+
+ The Spanish translation is better than the Slovenian. Note
+ interesar and navegar in
+ Spanish, are correctly translated as the verbs interest and sail
+ respectively. In the Slovenian version both words have been translated as
+ nouns. It is actually quite probable that the Spanish translation is based
+ at least partially on the actual translation of the book.
+
+ Once you have activated the service, a suggestion for the
+ translation will appear in the Machine Translate pane every time a new
+ source segment is opened. If you find the suggestion acceptable, press
+
+
+ Shortcuts
+
+ Ctrl+M - Machine Translate
+ Ctrl
+
+ M
+ to replace the target part of the opened segment with the
+ suggestion. In the above segment, for instance,
+ Ctrl
+
+ M
+ would replace the Spanish version with the Slovenian
+ suggestion.
+
+ If you do not wish OmegaT to send your
+ source segments to Google to get translated, untick the Google Translate
+ menu entry in Options.
+
+ Note that nothing but your source segment is sent to the MT service.
+ The online version of Google Translate allows the user to correct the
+ suggestion and send the corrected segment in. This feature, however, is
+ not implemented in OmegaT.
+
+
+
+ Belazar<indexterm class="singular">
+ <primary>Machine Translation</primary>
+
+ <secondary>Belazar</secondary>
+ </indexterm>
+
+ Belazar is a
+ Machine language translation tool for the Russian-Belarusian language
+ pair.
+
+
+
+ Apertium<indexterm class="singular">
+ <primary>Machine Translation</primary>
+
+ <secondary>Apertium</secondary>
+ </indexterm>
+
+ Apertium is a
+ free/open-source machine translation platform, initially aimed at
+ related-language pairs, like CA, ES, GA, PT, OC and FR but recently
+ expanded to deal with more divergent language pairs (such as
+ English-Catalan). Check the web site for the latest list of implemented
+ language pairs.
+
+ The platform provides
+
+
+
+ a language-independent machine translation engine
+
+
+
+ tools to manage the linguistic data necessary to build a machine
+ translation system for a given language pair and
+
+
+
+
+
+ linguistic data for a growing number of language pairs
+
+
+
+ Apertium uses a shallow-transfer machine translation engine which
+ processes the input text in stages, as in an assembly line: de-formatting,
+ morphological analysis, part-of-speech disambiguation, shallow structural
+ transfer, lexical transfer, morphological generation, and
+ re-formatting.
+
+ It is possible to use Apertium to build machine translation systems
+ for a variety of language pairs; to that end, Apertium uses simple
+ XML-based standard formats to encode the linguistic data needed (either by
+ hand or by converting existing data), which are compiled using the
+ provided tools into the high-speed formats used by the engine.
+
+
+
+ Machine translation - trouble shooting<indexterm class="singular">
+ <primary>Machine Translation</primary>
+
+ <secondary>Troubleshooting</secondary>
+ </indexterm>
+
+ If there's nothing appearing in the Machine Translate pane, then
+ check the following:
+
+
+
+ Are you online? You need to be online to be able to use an MT
+ tool.
+
+
+
+
+
+ What is the language pair you need? Check if the selected
+ service offers it.
+
+
+
+ Google Translate does not work: check Options > Machine
+ Translate: the Google Translate service is labelled Google Translate
+ V2. The older version of the service, labelled "Google Translate" and
+ available in outdated OmegaT versions, is deprecated and does not work
+ anymore.
+
+
+
+ "Google Translate returned HTTP response code: 403 ...": check
+ that the 38-characters key, entered in the pinfo.list file, is
+ correct. Check that Translate API
+ service has been activated.
+
+
+
+
diff --git a/OmegaT/doc_src/en/Menu.xml b/OmegaT/doc_src/en/Menu.xml
new file mode 100644
index 0000000..09c5b6d
--- /dev/null
+++ b/OmegaT/doc_src/en/Menu.xml
@@ -0,0 +1,1509 @@
+
+
+
+ Menu and Keyboard shortcuts
+
+
+ <indexterm class="singular">
+ <primary>Main menu</primary>
+ </indexterm>Main Menu
+
+
+ Shortcuts
+
+ Main menu
+
+
+ All of OmegaT's functions are available through the menu bar at the
+ top of the Editor window. Most functions are also available via keyboard
+ shortcuts. Shortcuts are activated by pressing Ctrl and a
+ letter. Some shortcuts involve other keys. For readability purposes,
+ letters are written in uppercase here. Ctrl is used on
+ Windows, UNIX and UNIX-like operating systems with keyboards featuring a
+ Ctrl or Control key. Mac users should
+ instead use
+ Cmd
+
+ key
+ instead. The "Cmd" key either has a "command" label or an
+ apple symbol on Apple keyboards.
+
+ You can customize existing shortcuts or add new ones according to
+ your needs. See Appendix -
+ Shortcuts Customization
+
+
+ Main Menu
+
+
+
+
+ Project
+
+ Edit
+
+ Go to
+
+ View
+
+ Tools
+
+ Options
+
+ Help
+
+
+
+
+ Project menu
+
+
+
+
+
+
+
+
+ New
+
+
+
+ Creates and opens a new project. The dialog to create a
+ project is the same as to edit the project. See
+
+
+
+ Open
+
+
+ Ctrl
+
+ O
+
+
+ Opens a previously created project.
+
+
+
+ Import Source Files...
+
+
+
+ Copies the selected files to the
+ source folder and reloads the project to
+ load the new files.
+
+
+
+ Import From
+ MediaWiki...
+
+
+
+ Imports units from MediaWiki pages, based on the URL
+ entered.
+
+
+
+ Reload
+
+ F5
+
+ Reloads the project to take external changes in source
+ files, legacy translation memories, glossaries and project
+ settings into account.
+
+
+
+ Close
+
+
+ Ctrl
+
+ Shift
+
+ W
+
+
+ Saves the translation and closes the project.
+
+
+
+ Save
+
+
+ Ctrl
+
+ S
+
+
+ Saves the internal translation memory to the hard disk.
+ OmegaT automatically saves translations every 10 minutes as well
+ as when you close the project or quit OmegaT.
+
+
+
+ Create translated
+ documents
+
+
+ Ctrl
+
+ D
+
+
+ Creates the target documents based on your translation of
+ the documents' text. The created target documents are located in
+ the target folder.
+
+
+
+ Properties...
+
+
+ Ctrl
+
+ E
+
+
+ Displays Project properties
+ dialog to edit project languages and folder locations.
+
+
+
+ Project Files...
+
+
+ Ctrl
+
+ L
+
+
+ Closes or opens the Project files window
+ (depending on whether it is open or closed).
+
+
+
+ Quit
+
+
+ Ctrl
+
+ Q
+
+
+ Saves the project and quits
+ OmegaT. If you haven't yet saved the
+ project, this manually confirms whether you really wish to
+ quit.
+
+
+
+
+
+
+
+ Edit<indexterm class="singular">
+ <primary>Main menu</primary>
+
+ <secondary>Edit</secondary>
+ </indexterm>
+
+ Note: Items that are found in most applications (copy/cut/paste)
+ are not displayed in this menu, but are available using your system
+ shortcuts. For example:
+
+
+ Copy/cut/paste shortcuts
+
+
+
+
+
+
+
+
+ Copy
+
+
+ Ctrl
+
+ C
+
+
+ Copies the selected text to the clipboard.
+
+
+
+ Cut
+
+
+ Ctrl
+
+ X
+
+
+ Copies the selected text to the clipboard and deletes the
+ selected text.
+
+
+
+ Paste
+
+
+ Ctrl
+
+ V
+
+
+ Pastes the text from the clipboard at the cursor
+ position.
+
+
+
+
+
+ The Edit menu itself contains the following items:
+
+
+ Edit menu
+
+
+
+
+
+
+
+
+ Undo Last Action
+
+
+ Ctrl
+
+ Z
+
+
+ Restores the status before the last editing action was
+ taken. This command does not work once the modified segment has
+ been validated.
+
+
+
+ Redo Last Action
+
+
+ Ctrl
+
+ Y
+
+
+ Restores the status before the last editing action was
+ cancelled. This command does not work once the modified segment
+ has been validated.
+
+
+
+ Replace With Match
+
+
+ Ctrl
+
+ R
+
+
+ Replaces the whole target segment with the currently
+ selected fuzzy match (by default the first match is
+ selected).
+
+
+
+ Insert Match
+
+
+ Ctrl
+
+ I
+
+
+ Inserts the currently selected fuzzy match at the cursor
+ position. If part of the target segment has been selected, this
+ function overwrites the selected portion.
+
+
+
+ Replace with Machine
+ Translation
+
+
+ Ctrl
+
+ M
+
+
+ Replaces the target segment with the translation,
+ provided by the selected Machine Translation service. No action
+ is taken, if no Machine Translation service has been activated
+ (see Menu > Options below).
+
+
+
+ Replace With Source
+
+
+ Shift
+
+ Ctrl
+
+ R
+
+
+ Replaces the whole target segment with the
+ source.
+
+
+
+ Insert Source
+
+
+ Shift
+
+ Ctrl
+
+ I
+
+
+ Inserts the source at the cursor position.
+
+
+
+ Insert Source Tags
+
+
+ Shift
+
+ Ctrl
+
+ T
+
+
+
+ Tags
+
+ Inserting source tags
+ Inserts the source tags at the cursor position.
+ All the relevant tags in the source - i.e. OmegaT as well as
+ custom, Java, printf etc tags - will be inserted into the
+ current target, regardless of whether they are already there or
+ not. Texts, bracketed by tags, are replaced by spaces:.
+ <f0><f1>This is
+ text</f0></f1> thus will be copied as
+ <f0><f1>one_space</f0></f1>
+
+
+
+ Export Selection
+
+
+ Shift
+
+ Ctrl
+
+ C
+
+
+ Exports the current selection to a text file for
+ processing. If no text has been selected, the current source
+ segment is written to this file. When the user exits
+ OmegaT, this file is not emptied, in
+ order to be consistent with usual clipboard behavior. The
+ exported contents are copied to the file
+ selection.txt located in the User's
+ preference files folder (see ).
+
+
+
+ Create Glossary Entry
+
+
+ Shift
+
+ Ctrl
+
+ G
+
+
+ Allows the user create an entry in the default glossary
+ file.
+
+
+
+ Search Project...
+
+
+ Ctrl
+
+ F
+
+
+ Opens a new Search
+ window.
+
+
+
+ Switch case to...
+
+
+ Shift
+
+ F3
+ (see text)
+
+ Changes the case of the highlighted text in the target
+ segment to the selected option (Lower case, Upper case or Title
+ case). Use Shift+F3
+ Shortcuts
+
+ Shift+F3 - Case selection
+ to cycle through the three alternatives. If no
+ text is selected, OmegaT selects the
+ word that contains the letter immediately to the right of the
+ cursor.
+
+
+
+ Select Fuzzy Match #N
+
+
+ Ctrl
+
+ #N
+
+
+ (#N is a digit from 1 to 5) - Selects the Nth fuzzy match
+ displayed in the match viewer to replace or insert it to the
+ segment. The describes the color
+ coding in detail.
+
+
+
+ Use as Default
+ Translation
+
+
+
+ If there's several alternative translations available
+ active segment, you can label the alternative selected as the
+ default translation. The entry will be greyed, if there's just
+ one translation available.
+
+
+
+ Create Alternative
+ Translation
+
+
+
+ The one and the same segment may, depending on the
+ context, require different translations. Select this menu item,
+ if the current translation does not apply and enter the
+ alternative translation.
+
+
+
+
+ Go To menu
+
+
+
+
+
+
+
+
+ Next Untranslated
+ Segment
+
+
+ Ctrl
+
+ U
+
+
+ Moves to the next segment that has no equivalent in the
+ translation memory.
+
+
+
+ Next Segment
+
+
+ Ctrl
+
+ N
+ or Enter or
+ Tab
+
+ Moves to the next segment. If the current segment is the
+ last segment in a file, it moves to the first segment of the
+ next file.
+
+
+
+ Previous Segment
+
+
+ Ctrl
+
+ P
+ or
+ Ctrl
+
+ Enter
+ or
+ Ctrl
+
+ Tab
+
+
+ Moves to the previous segment. If the current segment is
+ the first one in a file, it moves to the last segment of the
+ previous file.
+
+
+
+ Segment number...
+
+
+ Ctrl
+
+ J
+
+
+ The segment is opened when its segment number is
+ entered..
+
+
+
+ Next Note
+
+
+
+ The next segment with a note attached to it, will
+ open.
+
+
+
+ Previous Note
+
+
+
+ The previous segment with a note will open.
+
+
+
+ Forward in history...
+
+
+ Ctrl
+
+ Shift
+
+ N
+
+
+ OmegaT remembers the segments
+ executed. With this command you can step forward to the segment,
+ you have previously left by the Back in
+ history...command.
+
+
+
+ Back in history...
+
+
+ Ctrl
+
+ Shift
+
+ P
+
+
+ With this command you can move backward one segment at a
+ time, to return later to the current segment using
+ Forward in history... command
+ below.
+
+
+
+
+ View menu
+
+
+
+
+
+
+ Mark Translated
+ Segments
+
+ If checked, the translated segments will be marked in
+ yellow.
+
+
+
+ Mark Untranslated
+ Segments
+
+ If checked, the untranslated segments will be marked in
+ violet.
+
+
+
+ Display Source
+ Segments
+
+ If checked, source segments will be shown and marked in
+ green. If not checked, source segments will not be
+ shown.
+
+
+
+ Mark Non-Unique
+ Segments
+
+ If checked, non-unique segments will be marked in pale
+ grey.
+
+
+
+ Mark Segments with
+ Notes
+
+ If checked, segments with notes will be marked in cyan.
+ This marking has priority over Mark Translated Segments and Mark
+ Untranslated Segments.
+
+
+
+ Mark Non-breakable
+ Spaces
+
+ If checked, non-breakable spaces in the segment will be
+ displayed with a grey background.
+
+
+
+ Modification Info
+
+ Setting the Display Modification option to
+ Selected will display the time and the
+ author of the last change in the current segment. Setting it
+ to All shows this information for all
+ segments and None turns this option
+ off.
+
+
+
+
+ Tools menu
+
+
+ Matches
+
+ Matches statistics
+
+
+
+ Project
+
+ Match statistics
+
+
+
+ Project
+
+ Statistics
+
+
+
+
+
+
+
+ Validate Tags
+
+ Ctrl+T: Checks for missing or
+ displaced tags in formatted files. Will display a list of
+ segments with tag errors and possible inconsistencies. See Tag Validation and .
+
+
+
+ Remove Tags
+
+ When enabled, all the formatting tags are removed from
+ source segments. This is useful when dealing with texts where
+ inline formatting has no real use (e.g., OCRed PDF, bad
+ converted .odt or .docx, etc.) Only inline tags are removed, so
+ normally there should be no problem with opening the target
+ documents. Non-visible formatting (i.e., which doesn't appear as
+ tags in the OmegaT editor) is kept in the target
+ document.
+
+
+
+ Statistics
+
+ Opens a new window and displays the project statistics,
+ i.e. the project totals and totals for every file in the
+ project.
+
+
+
+ Match Statistics
+
+ Displays the Match Statistics for the project: the number
+ of repetitions, exact matches, fuzzy matches and no-matches, for
+ segments, words and in characters.
+
+
+
+
+ Options menu
+
+
+
+
+
+
+ Use TAB To Advance
+
+ Sets segment validation key to
+ Tab instead of the default
+ Enter. This option is useful for some
+ Chinese, Japanese or Korean character input systems.
+
+
+
+ Always Confirm Quit
+
+ The program will see confirmation before closing
+ down.
+
+
+
+ Machine Translate
+
+ Allows you to activate/deactivate the Machine Translation
+ tools offered. When active,
+ Ctrl
+
+ M
+ will insert the suggestion into the target part of
+ the current segment.
+
+
+
+ Glossary
+
+ reserved for future use by plugins
+
+
+
+ TransTips
+
+ Allows you to activate/deactivate TransTips
+ feature and set its option Exact
+ Match. With TransTips activated
+ a right click on a highlighted word in the source will open a
+ popup menu with the glossary entries for the word you clicked.
+ You can then click on the preferred translation to insert it
+ into the target segment at the current position. With
+ TransTips/Exact Match checked, only
+ complete words will be checked, otherwise parts of words will be
+ matched as well.
+
+
+
+ Font...
+
+ Shows the dialogue to modify the text display font. Users
+ of old computers who feel window resizing is very slow can try
+ changing the font. See font settings in Miscellanea
+
+
+
+ File Filters...
+
+ Displays the File
+ filters dialogue to configure file handling and
+ parsing.
+
+
+
+ Segmentation...
+
+ Opens the Source
+ segmentation dialogue to configure text
+ segmentation.
+
+
+
+ Spell checking...
+
+ Displays the Spell
+ checker setup window to install, configure and activate
+ the spell checker.
+
+
+
+ Editing Behavior...
+
+ Displays the Translation editing
+ dialog to configure.
+
+
+
+ Tag Validation...
+
+ For programmers: Allows you to configure the Tag
+ Validator options to also check programming (%...)
+ variables.
+
+
+
+ Team...
+
+ Enter your name here and it will be attached to all
+ segments translated by you.
+
+
+
+ External TMXs...
+
+ Allows the user decide, how tags in foreign TMX files
+ (i.e. not generated by OmegaT) are to be treated.
+
+
+
+ View...
+
+ Contains the option to have all source segments in bold
+ and to mark the first non-unique segment.
+
+
+
+ Proxy login...
+
+ Enter your user name and your password, if you use a
+ proxy to access your projects.
+
+
+
+ Restore Main Window
+
+ Restores the components of the main OmegaT window to
+ their default state. Use this feature when you have undocked,
+ moved, or hidden one or more components and you are unable to
+ restore the desired arrangement. It can also be used when panes
+ do not appear as expected following an OmegaT upgrade.
+
+
+
+
+ Help menu
+
+
+
+
+
+
+ User Manual...
+
+ F1: Opens Help browser displaying this
+ manual in a separate window.
+
+
+
+ About...
+
+ Displays copyright, credits and license
+ information.
+
+
+
+
+
+
+
+
+ Keyboard shortcuts<indexterm class="singular">
+ <primary>Keyboard shortcuts</primary>
+ </indexterm>
+
+ The following shortcuts are available from the main window. When
+ another window is on the foreground, click on the main window to bring it
+ to the foreground or press Esc to close the other
+ window.
+
+ Shortcuts are activated by pressing Ctrl and a
+ letter. Some shortcuts involve other keys. For readability purposes,
+ letters are written in uppercase here.
+
+ Ctrl is used on Windows, UNIX and UNIX-like operating systems with
+ keyboards featuring a Ctrl / Control
+ key. Mac users should instead use the
+ cmd+key. On Apple keyboards the
+ cmd key either has a command label or an Apple
+ icon on it.
+
+
+
+ Project management
+
+
+
+
+
+ Editing
+
+
+
+
+
+ Moving around
+
+
+
+
+
+ Reference windows
+
+
+
+
+
+ Other
+
+
+
+
+ <indexterm class="singular">
+ <primary>Keyboard shortcuts</primary>
+
+ <secondary>Project</secondary>
+ </indexterm>Project management<indexterm class="singular">
+ <primary>Project</primary>
+
+ <secondary>Project management shortcuts</secondary>
+ </indexterm>
+
+
+ Project management shortcuts
+
+
+
+
+
+
+
+
+ Open project
+
+
+ Ctrl
+
+ O
+
+
+ Displays a dialogue to locate an existing
+ project.
+
+
+
+ Save
+
+
+ Ctrl
+
+ S
+
+
+ Saves the current work to the internal translation memory
+ (file project_save.tmx located in the project's
+ omegat folder).
+
+
+
+ Close Project
+
+
+ Shift
+
+ Ctrl
+
+ W
+
+
+ Closes the current project.
+
+
+
+ Create Translated Documents
+
+
+ Ctrl
+
+ D
+
+
+ Creates the translated documents in the project's Target
+ folder and creates translation memory files (level1, level2 and
+ omegat tmx files) in the project's root folder.
+
+
+
+ Project properties
+
+
+ Ctrl
+
+ E
+
+
+ Displays the project's settings for modification, if
+ required.
+
+
+
+
+ Editing shortcuts
+
+
+
+
+
+
+
+
+ Undo last action
+
+
+ Ctrl
+
+ Z
+
+
+ Undoes the last editing actions in the current target
+ segment
+
+
+
+ Redo last action
+
+
+ Ctrl
+
+ Y
+
+
+ Redoes the last editing actions in the current target
+ segment
+
+
+
+ Select match #N
+
+
+ Ctrl
+
+ #N
+
+
+ #N is a digit from 1 to 5. The shortcut selects the Nth
+ match displayed in the match window (the first match is selected
+ by default)
+
+
+
+ Replace with match
+
+
+ Ctrl
+
+ R
+
+
+ Replaces the current target segment contents with the
+ selected match (the first match is selected by default)
+
+
+
+ Insert match
+
+
+ Ctrl
+
+ I
+
+
+ Inserts the selected match at the cursor position in the
+ current target segment (the first match is inserted by
+ default)
+
+
+
+ Replace with source
+
+
+ Ctrl
+
+ Shift+R
+
+
+ Replaces the current target segment contents with the
+ source text contents
+
+
+
+ Insert source
+
+
+ Ctrl
+
+ Shift+I
+
+
+ Inserts the source text contents into the target segment
+ at the cursor position
+
+
+
+ Insert Source Tags
+
+
+ Ctrl
+
+ Shift+T
+
+
+ Inserts the source tags into the target segment at the
+ cursor position
+
+
+
+ Search project
+
+
+ Ctrl
+
+ F
+
+
+ Displays a dialogue to conduct searches in the
+ project
+
+
+
+ Replace with Machine Translation
+
+
+ Ctrl
+
+ M
+
+
+ Replaces the target segment with the machine translation
+ of the source. No action, if machine tools are deactivated (see
+ Menu > Options > Machine Translate)
+
+
+
+ Export Selection
+
+
+ Shift
+
+ Ctrl
+
+ C
+
+
+ Exports the current selection to a text file for
+ processing.
+
+
+
+ Create Glossary Entry
+
+
+ Shift
+
+ Ctrl
+
+ G
+
+
+ Allows the user create an entry in the default glossary
+ file.
+
+
+
+
+ Moving around shortcuts
+
+
+
+
+
+
+
+
+ Next Untranslated Segment
+
+
+ Ctrl
+
+ U
+
+
+ Moves the editing field to the next segment that is not
+ registered in the project's translation memory
+
+
+
+ Next Segment
+
+
+ Ctrl
+
+ N
+ , Enter or
+ Return
+
+ Moves the editing field to the next segment.
+
+
+
+ Previous Segment
+
+
+ Ctrl
+
+ P
+
+
+ Moves the editing field to the previous segment
+
+
+
+ Segment number...
+
+
+ Ctrl
+
+ J
+
+
+ Moves to the segment number entered
+
+
+
+ Back in history...
+
+
+ Ctrl
+
+ Shift+P
+
+
+ Moves one segment back in history
+
+
+
+ Forward in history...
+
+
+ Ctrl
+
+ Shift+N
+
+
+ Moves one segment forward in history
+
+
+
+
+ Various shortcuts
+
+
+
+
+
+
+
+
+ Project files listing
+
+
+ Ctrl
+
+ L
+
+
+ Displays the Project files listing
+
+
+
+ Validate Tags
+
+
+ Ctrl
+
+ T
+
+
+ Opens the Tag validation window.
+
+
+
+ Export Selection
+
+
+ Shift
+
+ Ctrl+C
+
+
+ Exports the current selection or the current source, if
+ no text has been selected. The text is exported to a plain text
+ file.
+
+
+
+ Search Project
+
+
+ Ctrl
+
+ F
+
+
+ Opens a new Search window.
+
+
+
+ Help files
+
+ F1
+
+ Displays the OmegaT help files
+ in a separate window
+
+
+
+
+
+
+
diff --git a/OmegaT/doc_src/en/Miscelanea.xml b/OmegaT/doc_src/en/Miscelanea.xml
new file mode 100644
index 0000000..43d3ed9
--- /dev/null
+++ b/OmegaT/doc_src/en/Miscelanea.xml
@@ -0,0 +1,334 @@
+
+
+
+ Miscellaneous subjects<indexterm class="singular">
+ <primary>Miscellanea</primary>
+ </indexterm>
+
+
+ <application><indexterm class="singular">
+ <primary>OmegaT console mode</primary>
+
+ <seealso>Miscellanea</seealso>
+ </indexterm>OmegaT</application> Console Mode<indexterm class="singular">
+ <primary>Miscellanea</primary>
+
+ <secondary>OmegaT console mode</secondary>
+ </indexterm>
+
+
+ Of interest for advanced users only!
+
+
+ The purpose of the console (i.e. command line) mode is to permit the
+ use of OmegaT as translation tool in a
+ scripting environment. When launched in console mode, no GUI is loaded (
+ it will work therefore on any console) and the given project is
+ automatically translated. An example would be a software project, with GUI
+ localized in a number of languages. Using the console mode, one can make
+ generating a localized interface a part of the build process.
+
+
+ Prerequisites
+
+ To run OmegaT, a valid OmegaT project must be available. The
+ location is irrelevant, since it must be specified explicitly on the
+ command-line at launch..
+
+ If you need non-standard settings, the corresponding configuration
+ files (filters.conf and
+ segmentation.conf) must be present. This can be
+ achieved in two ways:
+
+
+
+ Run OmegaT normally (with the GUI)
+ and set the settings. If you start OmegaT
+ in console mode, it will use the settings you configured.
+
+
+
+ If you are unable to run OmegaT
+ normally (no graphical environment available): copy the settings
+ files from some other OmegaT installation
+ on another machine to a specific directory. The location does not
+ matter, since you can add it to the command line at launch (see
+ below). The relevant files filters.conf and
+ segmentation.conf can be found in the user home
+ directory (E.g. C:\Documents and
+ Settings\%User%\OmegaT under
+ Windows, %user%/.omegat/ under Linux)
+
+
+
+
+
+ Launching OmegaT in console mode
+
+ To launch OmegaT in console mode, additional parameters must be
+ specified at launch. The most important of these is
+ <project-dir>, and
+ optionally--config-dir=<config-dir>.
+ Example:
+
+ $> java -jar OmegaT.jar
+ /path/to/project \
+
+ --config-dir=/path/to/config-files/ \
+
+ --mode=console-translate \
+
+ --source-pattern={regexp} \
+
+ --tag-validation=[block|warn]
+
+ Explanation:
+
+
+
+ <project-dir> tells
+ OmegaT where to find the project to be
+ translated. If given, OmegaT launches in
+ console mode and translates the given project.
+
+
+
+
+
+ --config-dir=<config-dir> enables
+ OmegaT to be instructed in which folder the configuration files are
+ stored. If not specified, OmegaT reverts to default values (the
+ OmegaT folder in the user home folder, or if not available: the
+ current working directory).
+
+
+
+
+
+ --mode=console-translate
+ OmegaT launches in console mode and
+ translates the given project
+
+
+
+ --source-pattern={regexp} The files to be
+ translated can be specified this way. Here is an example of the
+ regular expression: test\.html
+
+
+
+ --tag-validation=[abort|warn] On abort,
+ the program is aborted when tag validation finds errors. On warn the
+ errors are printed but the program continues. In all other cases no
+ tag validation is done.
+
+
+
+
+
+ Quiet option
+
+ An extra command line parameter specific to console mode:
+ --quiet. In the quiet mode, less info is logged to
+ the screen. The messages you would usually find in the status bar are
+ not displayed.
+
+ Usage: java -jar OmegaT.jar
+ /path/to/project --mode=console-translate --quiet
+
+
+
+ Tag validation option
+
+ Another extra command line parameter specific to console mode:
+ --tag-validation=[abort|warn]. When this parameter is
+ added, tag validation is done prior to translation/aligning. If the
+ value is abort, then on tag errors the errors are
+ printed and the program stops. If the value is warn
+ then the errors are printed but OmegaT continues.
+
+ Usage: java -jar OmegaT.jar
+ /path/to/project --mode=console-translate
+ --tag-validation=abort
+
+
+
+
+ Automatic Java Properties Aligner<indexterm class="singular">
+ <primary>Miscellanea</primary>
+
+ <secondary>Automatic aligner for Java properties</secondary>
+
+ <seealso>Miscelanea</seealso>
+ </indexterm>
+
+ OmegaT can align Java .properties in console mode. If you have the
+ source and the target Properties files for one and the same contents in
+ your language pair, this procedure will create a corresponding tmx file
+ for these contents. Usage:
+
+ java -jar OmegaT.jar --mode=console-align /my-project-dir
+ --alignDir=/translatedFiles/
+
+ alignDir must contain a translation in the
+ target language of the project. E.g., if the project is EN->FR,
+ alignDir must contain a bundle ending with _fr. The resulting tmx is
+ stored in the omegat folder under the name
+ align.tmx.
+
+
+
+ Font settings<indexterm class="singular">
+ <primary>Miscellanea</primary>
+
+ <secondary>Font settings</secondary>
+ </indexterm>
+
+ In this dialog one can define the font used by
+ OmegaT in the following windows:
+
+
+
+ OmegaT main window (Editor, Match
+ viewer, Glossary viewer)
+
+
+
+
+
+ Search window
+
+
+
+
+
+ Tag validation window
+
+
+
+ The dialog can be accessed via the
+ Menu Options
+
+ Font...
+
+ Options
+
+ Font...
+ item in the Main menu. The dialog contains:
+
+
+
+ Font: drop-down to select one
+ of the fonts available on your machine
+
+
+
+
+
+ Size: edit to change font
+ size
+
+
+
+
+
+ Sample text: field for
+ immediate preview of the selected font
+
+
+
+ Note: In some cases it may take
+ quite some time for OmegaT to update the display after the font setting
+ has been changed. This is especially the case when a large file containing
+ many segments is open in the editor, and/or slow hardware is used. Note
+ also that some fonts behave better for some language pairs than for
+ others. In particular, if you are translating between two languages with
+ different alphabets/writing systems (such as Russian and Japanese), select
+ a font that can be used for both.
+
+
+
+ Preventing data loss<indexterm class="singular">
+ <primary>Miscellanea</primary>
+
+ <secondary>Preventing data Loss</secondary>
+ </indexterm>
+
+ OmegaT is a robust application. However,
+ you should take precautions against data loss when using
+ OmegaT, just as with any other application.
+ When you translate your files, OmegaT stores
+ all your progress in the translation memory
+ project_save.tmx that resides in the project's
+ /omegat subfolder.
+
+ OmegaT also backs up the translation memory to
+ project_save.tmx.YEARMMDDHHNN.bak in the same subfolder each time a
+ project is opened or reloaded. YEAR is the 4-digit year, MM is the month,
+ DD the day of the month, and HH and NN are the hours and minutes when the
+ previous translation memory was saved.
+
+ If you believe that you have lost translation data, you can use the
+ following procedure to restore the project to its most recently saved
+ state, usually not older than approximately 10 minutes or so:
+
+
+
+ close the project
+
+
+
+ rename the current project_save.tmx file
+ (e.g. to project_save.tmx.temporary)
+
+
+
+ select the backup translation memory that is the most likely to
+ contain the data you are looking for
+
+
+
+ rename it project_save.tmx
+
+
+
+ open the project
+
+
+
+ To avoid losing important data:
+
+
+
+ Make regular copies of the file /omegat/project_save.tmx to
+ backup media, such as CD or DVD.
+
+
+
+ Until you are familiar with OmegaT,
+ create translated files at regular intervals and check that the
+ translated file contains the latest version of your
+ translation.
+
+
+
+ Take particular care when making changes to the files in
+ /source while in the middle of a project. If the
+ source file is modified after you have begun translating,
+ OmegaT may be unable to find a segment that
+ you have already translated.
+
+
+
+
+
+ Use these Help texts to get started. Should you run into
+ problems, post a message in the OmegaT
+ user group. Do not hesitate to post in the language you feel
+ the most familiar with.
+
+
+
+
diff --git a/OmegaT/doc_src/en/OmegaT.css b/OmegaT/doc_src/en/OmegaT.css
new file mode 100644
index 0000000..1893c29
--- /dev/null
+++ b/OmegaT/doc_src/en/OmegaT.css
@@ -0,0 +1,78 @@
+body {
+ font-family: sans-serif;
+ margin: 1em;
+}
+
+h1, h2, table, dt {
+ color: navy;
+}
+
+h3, h4, ul a {
+ color: green;
+}
+
+code, .code {
+ color: black;
+ background: #ffffcc;
+ border-style: solid;
+ border-width: 1px;
+ border-color: #ffff66;
+ vertical-align: top;
+}
+
+.new {
+ font-size: x-small;
+ color: red;
+ background: yellow;
+}
+
+.updated {
+ font-size: x-small;
+ color: orange;
+}
+
+.note {
+ font-size: small;
+ color: black;
+ background: silver;
+}
+
+.warning {
+ color: red;
+ background: yellow;
+}
+
+.chapter {
+ color: black;
+}
+
+.navbar-top, .navbar-bottom {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.rel-p {
+ width: 9%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.rel-n {
+ width: 6%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.nav-link {
+ width: 39%;
+ align: left;
+ valign: center;
+}
+
+.toc-link {
+ width: 7%;
+ align: left;
+ valign: center;
+}
\ No newline at end of file
diff --git a/OmegaT/doc_src/en/OmegaTUsersManual_xinclude full.xml b/OmegaT/doc_src/en/OmegaTUsersManual_xinclude full.xml
new file mode 100644
index 0000000..e9d7a5d
--- /dev/null
+++ b/OmegaT/doc_src/en/OmegaTUsersManual_xinclude full.xml
@@ -0,0 +1,97 @@
+
+
+
+
+ OmegaT - User's Guide
+
+ vs
+ Vito
+Smolej
+
+
+
+
+
+ This document is the official user's guide to OmegaT, the free Computer Aided Translation tool. It also contains installation instructions.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/OmegaT/doc_src/en/PlainText.xml b/OmegaT/doc_src/en/PlainText.xml
new file mode 100644
index 0000000..44c0b60
--- /dev/null
+++ b/OmegaT/doc_src/en/PlainText.xml
@@ -0,0 +1,178 @@
+
+
+
+ Working with plain text<indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Plain text files</secondary>
+ </indexterm>
+
+
+ Default encoding<indexterm class="singular">
+ <primary>Default encoding</primary>
+
+ <secondary>Plain text files</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Default encoding</secondary>
+ </indexterm>
+
+ Plain text files - in most cases files with a txt extension -
+ contain just textual information and offer no clearly defined way to
+ inform the computer which language they contain. The most that OmegaT can
+ do in such a case, is to assume that the text is written in the same
+ language the computer itself uses. This is no problem for files encoded in
+ Unicode using a 16 bit character encoding set. If the text is encoded in 8
+ bits, however, one can be faced with the following awkward situation:
+ instead of displaying the text, for Japanese characters...
+
+
+
+
+
+
+
+
+
+
+
+ ...the system will display it like this for instance:
+
+
+
+
+
+
+
+
+
+
+
+ The computer, running OmegaT, has Russian as the default language,
+ and thus shows the characters in the Cyrillic alphabet and not in
+ Kanji.
+
+
+
+ The <application>OmegaT</application> solution<indexterm
+ class="singular">
+ <primary>Default encoding</primary>
+
+ <secondary>OmegaT solution</secondary>
+ </indexterm>
+
+ There are basically three ways to address this problem in
+ OmegaT. They all involve the application of
+ file filters in the Options menu.
+
+
+
+ Change the encoding of your files to Unicode
+
+
+ open your source file in a text editor that correctly
+ interprets its encoding and save the file in "UTF-8" encoding. Change the file extension
+ from .txt to
+ .utf8.OmegaT will
+ automatically interpret the file as a UTF-8 file. This is the most
+ common-sense alternative, sparing you problems in the long
+ run.
+
+
+
+
+
+
+ Specify the encoding for your plain text files
+
+
+ - i.e. files with a .txt extension - : in
+ the Text files section of the file
+ filters dialog, change the Source File
+ Encoding from <auto> to the encoding that
+ corresponds to your source .txt file, for
+ instance to .jp for the above example.
+
+
+
+
+
+
+ Change the extensions of your plain text source files
+
+
+ for instance from .txt to
+ .jp for Japanese plain texts: in the Text files section of the file filters
+ dialog, add new Source Filename
+ Pattern (*.jp for this example) and
+ select the appropriate parameters for the source and target
+ encoding
+
+
+
+
+ OmegaT has by default the following short
+ list available to make it easier for you to deal with some plain text
+ files:
+
+
+
+ .txt files are automatically (<auto>)
+ interpreted by OmegaT as being encoded in
+ the computer's default encoding.
+
+
+
+
+
+ .txt1 files are files in ISO-8859-1, covering
+ most Western Europe
+ languages.
+ Default encoding
+
+ Western
+
+
+
+
+
+
+ .txt2 files are files in ISO-8859-2, that
+ covers most Central and Eastern
+ Europe languages
+ Default encoding
+
+ Central and Eastern European
+
+
+
+
+
+
+ .utf8 files are interpreted by
+ OmegaT as being encoded in UTF-8 (an
+ encoding that covers almost all languages in the world).
+ Default encoding
+
+ Unicode
+
+
+
+
+ You can check that yourself by selecting the item File Filters in the menu Options. For example, when you have a Czech text
+ file (very probably written in the ISO-8859-2 code) you just need to change the
+ extension .txt to .txt2 and
+ OmegaT will interpret its contents correctly.
+ And of course, if you wish to be on the safe side, consider converting
+ this kind of file to Unicode, i.e. to the .utf8 file
+ format.
+
+
diff --git a/OmegaT/doc_src/en/ProjectProperties.xml b/OmegaT/doc_src/en/ProjectProperties.xml
new file mode 100644
index 0000000..7c3065d
--- /dev/null
+++ b/OmegaT/doc_src/en/ProjectProperties.xml
@@ -0,0 +1,173 @@
+
+
+
+ Project properties<indexterm class="singular">
+ <primary>Project</primary>
+
+ <secondary>Properties</secondary>
+ </indexterm>
+
+
+
+
+ Properties dialog
+
+ The
+
+
+ Ctrl
+
+ E
+
+
+
+ Project
+
+ Properties...
+ dialog is used to define and modify the project folders
+ and languages.
+
+ It is possible to modify the project properties during a translation
+ session. Note that changes to the project setup may have some
+ consequences, especially, when the project has already been started. Until
+ you have some experience with OmegaT, it is safest to consider all
+ settings final once the translation has started – unless of course you
+ realize a major mistake has been made. See the section Preventing data
+ loss for ways and means of protecting your work.
+
+
+ Project properties window
+
+
+
+
+
+
+
+
+
+
+
+
+ It contains:
+
+
+
+ An area for setting project source and target languages with
+ drop-down menus
+
+ You can either enter the source and target languages by hand or
+ use the drop down menu. Bear in mind that changing the languages may
+ render the currently used translation memories useless since their
+ language pair may not longer match the new languages.
+
+
+
+
+
+ the Enable Sentence-level segmentation
+ check box
+
+
+ Project
+
+ Enable Sentence-level segmentation
+
+
+ The segmentation settings only address the way the source files
+ are handled by OmegaT. The predominant way
+ of segmenting the sources is the sentence-level segmenting, so this
+ check box should in a normal case be left checked.
+
+ In some seldom cases the alternative, i.e. segmenting by
+ paragraphs, may be preferred. Changing this flag does not modify the
+ segmentation of already existing translation memories. If you decide
+ mid-translation to switch from sentence to paragraph translation, the
+ internal translation memory of the project will not be changed (OmegaT
+ may upgrade old translation memories that did not use sentence
+ segmentation, but not vice versa).
+
+ Changing segmentation settings may cause some already translated
+ segments to be split or merged. This will effectively return them to
+ the "untranslated" status, as they will no longer match segments
+ recorded in the project memory, even though their original translation
+ is still there.
+
+
+
+
+
+ Segmentation... button
+ Segmentation
+
+ global vs project rules
+
+
+ The segmentation rules are generally valid across all the
+ projects. The user, however, may need to generate a set of rules,
+ specific to the project in question. Use this button to open a
+ dialog,activate the check box Project specific
+ segmentation rules, then proceed to adjust the
+ segmentation rules as desired . The new set of rules will be stored
+ together with the project and will not interfere with the general set
+ of segmentation rules. To delete project specific Segmentation rules,
+ uncheck the check box. See chapter Source Segmentation for more
+ information on segmentation rules.
+
+ Hint: the set of segmentation rules for a
+ given project is stored as
+ project/omegat/segmentation.conf.
+
+
+
+ File Filters... button
+ File Filters
+
+ global vs project file filters
+
+
+ In a similar fashion as above the user can create
+ project-specific File filters, which will be stored together with the
+ project and will be valid for the current project only. To create a
+ project-specific set of file filters, click on the File
+ filter ... button, then activate Enable
+ project specific filters check box in the window, that
+ opens. A copy of the changed filters configuration will be stored with
+ the project. To delete project specific file filters, uncheck the
+ check box. Note that in the menu Options->File
+ Filters, the global user filters are changed, not the
+ project filters. See chapter File
+ filters for more on the subject.
+
+ Hint: the set of file filters for a given
+ project is stored as
+ project/omegat/filters.xml.
+
+
+
+
+
+ An area for setting project folders
+ Glossary
+
+ Location of the writable glossary file
+
+
+
+ Project
+
+ Changing the folder structure
+
+
+ if you enter names of folders that do not exist yet,
+ OmegaT creates them for you. In case you
+ decide to modify project folders, keep in mind that this will not move
+ the contained files from old folders to the new location.
+
+
+
+
diff --git a/OmegaT/doc_src/en/Regexp.xml b/OmegaT/doc_src/en/Regexp.xml
new file mode 100644
index 0000000..38a7f3b
--- /dev/null
+++ b/OmegaT/doc_src/en/Regexp.xml
@@ -0,0 +1,610 @@
+
+
+
+ Regular expressions<indexterm class="singular">
+ <primary>Regular expressions</primary>
+
+ <seealso>Segmentation</seealso>
+
+ <seealso>Searching</seealso>
+ </indexterm>
+
+ The regular expressions (or regex for short) used in searches and
+ segmentation rules are those supported by Java. Should you need more
+ specific information, consult the Java
+ Regex documentation. See additional references and examples
+ below.
+
+
+ This chapter is intended for advanced users, who need to define
+ their own variants of segmentation rules or devise more complex and
+ powerful key search items.
+
+
+
+ Regex - Flags
+
+
+
+
+
+
+ The construct
+
+ ... matches the following
+
+
+
+
+
+ (?i)
+
+ Enables case-insensitive matching (by default, the pattern is
+ case-sensitive).
+
+
+
+
+
+
+ Regex - Character
+
+
+
+
+
+
+ The construct
+
+ ... matches the following
+
+
+
+
+
+ x
+
+ The character x, except the following...
+
+
+
+ \uhhhh
+
+ The character with hexadecimal value 0xhhhh
+
+
+
+ \t
+
+ The tab character ('\u0009')
+
+
+
+ \n
+
+ The newline (line feed) character ('\u000A')
+
+
+
+ \r
+
+ The carriage-return character ('\u000D')
+
+
+
+ \f
+
+ The form-feed character ('\u000C')
+
+
+
+ \a
+
+ The alert (bell) character ('\u0007')
+
+
+
+ \e
+
+ The escape character ('\u001B')
+
+
+
+ \cx
+
+ The control character corresponding to x
+
+
+
+ \0n
+
+ The character with octal value 0n (0 <= n <= 7)
+
+
+
+ \0nn
+
+ The character with octal value 0nn (0 <= n <=
+ 7)
+
+
+
+ \0mnn
+
+ The character with octal value 0mnn (0 <= m <= 3, 0
+ <= n <= 7)
+
+
+
+ \xhh
+
+ The character with hexadecimal value 0xhh
+
+
+
+
+
+
+ Regex - Quotation
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ \
+
+ Nothing, but quotes the following character. This is required
+ if you would like to enter any of the meta characters
+ !$()*+.<>?[\]^{|} to match as themselves.
+
+
+
+ \\
+
+ For example, this is the backslash character
+
+
+
+ \Q
+
+ Nothing, but quotes all characters until \E
+
+
+
+ \E
+
+ Nothing, but ends quoting started by \Q
+
+
+
+
+
+
+ Regex - Classes for Unicode blocks and categories
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ \p{InGreek}
+
+ A character in the Greek block (simple
+ block)
+
+
+
+ \p{Lu}
+
+ An uppercase letter (simple
+ category)
+
+
+
+ \p{Sc}
+
+ A currency symbol
+
+
+
+ \P{InGreek}
+
+ Any character except one in the Greek block
+ (negation)
+
+
+
+ [\p{L}&&[^\p{Lu}]]
+
+ Any letter except an uppercase letter (subtraction)
+
+
+
+
+
+
+ Regex - Character classes
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ [abc]
+
+ a, b, or c (simple class)
+
+
+
+ [^abc]
+
+ Any character except a, b, or c (negation)
+
+
+
+ [a-zA-Z]
+
+ a through z or A through Z, inclusive (range)
+
+
+
+
+
+
+ Regex - Predefined character classes
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ .
+
+ Any character (except for line terminators)
+
+
+
+ \d
+
+ A digit: [0-9]
+
+
+
+ \D
+
+ A non-digit: [^0-9]
+
+
+
+ \s
+
+ A whitespace character: [ \t\n\x0B\f\r]
+
+
+
+ \S
+
+ A non-whitespace character: [^\s]
+
+
+
+ \w
+
+ A word character: [a-zA-Z_0-9]
+
+
+
+ \W
+
+ A non-word character: [^\w]
+
+
+
+
+
+
+ Regex - Boundary matchers
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ ^
+
+ The beginning of a line
+
+
+
+ $
+
+ The end of a line
+
+
+
+ \b
+
+ A word boundary
+
+
+
+ \B
+
+ A non-word boundary
+
+
+
+
+
+
+ Regex - Greedy quantifiers
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ X?
+
+ X, once or not at all
+
+
+
+ X*
+
+ X, zero or more times
+
+
+
+ X+
+
+ X, one or more times
+
+
+
+
+
+
+ greedy quantifiers will match as much as they can. For example,
+ a+? will match the aaa in
+ aaabbb
+
+
+
+ Regex - Reluctant (non-greedy) quantifiers
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ X??
+
+ X, once or not at all
+
+
+
+ X*?
+
+ X, zero or more times
+
+
+
+ X+?
+
+ X, one or more times
+
+
+
+
+
+
+ non-greedy quantifiers will match as little as they can. For
+ example, a+? will match the first
+ a in aaabbb
+
+
+
+ Regex - Logical operators
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ XY
+
+ X followed by Y
+
+
+
+ X|Y
+
+ Either X or Y
+
+
+
+ (XY)
+
+ XY as a single group
+
+
+
+
+
+
+ <indexterm class="singular">
+ <primary>Regular expressions</primary>
+
+ <secondary>Tools</secondary>
+ </indexterm>Regex tools and examples of use<indexterm class="singular">
+ <primary>Regular expressions</primary>
+
+ <secondary>Examples of use</secondary>
+ </indexterm>
+
+ A number of interactive tools are available to develop and test
+ regular expressions. They generally follow much the same pattern (for an
+ example from the Regular Expression Tester see below): the regular
+ expression (top entry) analyzes the search text (Text box in the middle) ,
+ yielding the hits, shown in the result Text box.
+
+
+ Regex Tester
+
+
+
+
+
+
+
+
+
+
+
+
+ See The Regex
+ Coach for Windows,Linux, FreeBSD versions of a stand-alone tool.
+ This is much the same as the above example.
+
+ A nice collection of useful regex cases can be found in
+ OmegaT itself (see Options > Segmentation).
+ The following list includes expressions you may find useful when searching
+ through the translation memory:
+
+
+ Regex - Examples of regular expressions in translations
+
+
+
+
+
+
+ Regular expression
+
+ Finds the following:
+
+
+
+
+
+ (\b\w+\b)\s\1\b
+
+ double words
+
+
+
+ [\.,]\s*[\.,]+
+
+ comma or a period, followed by spaces and yet another comma
+ or period
+
+
+
+ \. \s+$
+
+ extra spaces after the period at the end of the
+ line
+
+
+
+ \s+a\s+[aeiou]
+
+ English: words, beginning with vowels, should generally be
+ preceded by "an", not "a"
+
+
+
+ \s+an\s+[^aeiou]
+
+ English: the same check as above, but concerning consonants
+ ("a", not "an")
+
+
+
+ \s\s+
+
+ more than one space
+
+
+
+ \.[A-Z]
+
+ Period, followed by an upper-case letter - possibly a space
+ is missing between the period and the start of a new
+ sentence?
+
+
+
+
+
+
diff --git a/OmegaT/doc_src/en/Searches.xml b/OmegaT/doc_src/en/Searches.xml
new file mode 100644
index 0000000..89c78ab
--- /dev/null
+++ b/OmegaT/doc_src/en/Searches.xml
@@ -0,0 +1,226 @@
+
+
+
+ Searches<indexterm class="singular">
+ <primary>Searches</primary>
+ </indexterm>
+
+
+ Search window
+
+
+ Text search Window<indexterm class="singular">
+ <primary>Search window</primary>
+
+ <secondary>Example</secondary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The above search finds all target segments where two or more white
+ spaces - \s\s+ - occur.
+
+
+
+ Searching<indexterm class="singular">
+ <primary>Shortcuts</primary>
+
+ <secondary>Ctrl+F - Search</secondary>
+ </indexterm>
+
+ OmegaT provides a powerful range of
+ search functions. Open the Search window with
+ Ctrl
+
+ F
+ and enter the word or phrase you wish to search for in the
+ Search for box. Alternatively, in the Editor window, select a word or
+ phrase in the editing field (target text of the current segment) and hit
+
+ Ctrl
+
+ F
+ . The word or phrase is entered in the Search for box
+ automatically. You can have several Search windows open at the same
+ time, but close them when they are no longer needed so that they do not
+ clutter your desktop.
+
+
+
+ Search location
+
+ Searches are performed by default in both the source and target
+ sections of the project, but you can limit your search to just the
+ source or the target text. You may search in
+
+
+
+ the project only (default setting)
+
+
+
+
+
+ both the project and the reference translation memories in
+ /tm/ (check Search TMs)
+
+
+
+
+
+ a single file or a folder containing a set of files (check
+ Search files)
+
+
+
+ When searching through files (as opposed to translation memories),
+ OmegaT restricts the search to files in
+ source file formats. Consequently, although OmegaT is quite able to
+ handle tmx files, it does not include them in the
+ Search files search. If you turn on
+ Searches
+
+ Advanced Options
+ Advanced Options, you can combine the search
+ with the name of the author of the translation and time of the last
+ change made.
+
+
+
+
+ Using wild cards<indexterm class="singular">
+ <primary>Searches</primary>
+
+ <secondary>Using wild cards</secondary>
+ </indexterm>
+
+ In both exact and keyword searches, the wild card search characters
+ '*' and '?' can be used. To use wild cards, the regular expressions option
+ should not be selected, as '*' and '?' have special meaning in regular
+ expressions.
+
+
+
+ '*' matches zero or more characters, from the current position
+ in a given word to its end. The search term'run*'
+ for example would match words 'run',
+ 'runs' and 'running'.
+
+
+
+
+
+ '?' matches any single character. For instance, 'run?'
+ would match the word 'runs' and
+ 'runn' in the word
+ 'running'.
+
+
+
+ The matches will be displayed in bold blue.
+
+
+
+ Search methods<indexterm class="singular">
+ <primary>Searches</primary>
+
+ <secondary>Methods</secondary>
+ </indexterm>
+
+ Select the method using the radio buttons. You can choose between
+ two methods to search:
+
+
+
+ exact search
+
+
+ Search for segments containing the exact string you specified.
+ An exact search looks for a phrase, i.e. if several words are
+ entered, they are found only if they occur in exactly that sequence.
+ Searching for open file will thus find all
+ occurrences of the string open
+ file, but not file
+ opened or open input
+ file.
+
+
+
+
+ keyword search
+
+
+ Search for segments containing all keywords you specified, in
+ any order. Select keyword search to search for any number of
+ individual full words, in any order. OmegaT displays a list of all
+ segments containing all of the words specified. Keyword searches are
+ similar to a search "with all of the words" in an Internet search
+ engine such as Google (AND logic). Using keyword search with
+ open file will thus find all
+ occurrences of the string open
+ file, as well as file
+ opened, open input file, file
+ may not be safe to open, etc.
+
+
+
+
+ For either of these two methods you can select the following three
+ options:
+
+
+
+ case sensitive: the search will
+ be performed for the exact string specified; i.e. capitalization is
+ observed.
+
+
+
+ regular expressions: The search
+ string will be treated as a regular expression. A regular expression
+ search is a powerful way to look for instances of a string. It is
+ similar to a wild card search, but allows far more flexibility. The
+ regular expressions used in searches are those supported by Java. See
+ more in the chapter on regular Expressions.
+
+
+
+ search TMs: translation
+ memories in the tm folder are included in the
+ search.
+
+
+
+
+
+ Search results display
+
+ Pressing the search button after entering a string in the search
+ field displays all the segments in the project that include the entered
+ string. As OmegaT handles identical segments as
+ one single entity, only the first unique segment is shown. The segments
+ are displayed in order of appearance in the project. Translated segments
+ are displayed with the original text at the top and the translated text at
+ the bottom, untranslated segments are displayed as the source only.
+
+ Clicking on a segment opens it in the Editor for modifications. You
+ can then switch back to the Search window for the next segment found, for
+ instance to check and, if necessary, correct the terminology.
+
+ You may have several Search windows open at the same time. You can
+ quickly see their contents by looking at their title: it will contain the
+ search term used.
+
+
diff --git a/OmegaT/doc_src/en/Segmentation.xml b/OmegaT/doc_src/en/Segmentation.xml
new file mode 100644
index 0000000..283af90
--- /dev/null
+++ b/OmegaT/doc_src/en/Segmentation.xml
@@ -0,0 +1,286 @@
+
+
+
+ Source segmentation
+
+ Translation memory tools work with textual units called segments.
+ OmegaT has two ways to segment a text: by
+ paragraph or by sentence segmentation (also referred to as “rule-based
+ segmentation”). In order to select the type of segmentation, select
+
+
+ Project
+
+ Properties
+ Project
+
+ Properties...
+ from the main menu and tick or untick the check box
+ provided. Paragraph segmentation is advantageous in certain cases, such as
+ highly creative or stylistic translations in which the translator may wish
+ to change the order of entire sentences; for the majority of projects,
+ however, sentence segmentation is a choice to be preferred, since it
+ delivers better matches from previous translations. If sentence segmentation
+ has been selected, you can setup the rules by selecting
+
+ Project
+
+ Options
+ Options
+
+ Segmentation...
+ from the main menu.
+
+ Dependable segmentation rules are already available for many
+ languages, so it is likely that you will not need to get involved with
+ writing your own segmentation rules. On the other hand this functionality
+ can be very useful in special cases, where you can increase your
+ productivity by tuning the segmentation rules to the text to be
+ translated.
+
+ Warning: because the text will
+ segment differently after filter options have been changed, so you may have
+ to start translating from scratch. At the same time the previous valid
+ segments in the project translation memory will turn into orphan segments.
+ If you change segmentation options when a project is open, you must reload
+ the project in order for the changes to take effect.
+
+ OmegaT uses the following sequence of
+ steps:
+
+
+
+
+ Segmentation
+
+ Source level segmentation
+ Structure level segmentation
+
+
+ OmegaT first parses the text for
+ structure-level segmentation. During this process it is only the
+ structure of the source file that is used to produce segments.
+
+ For example, text files may be segmented on line breaks, empty
+ lines, or not be segmented at all. Files containing formatting
+ (OpenOffice.org documents, HTML documents, etc.) are segmented on the
+ block-level (paragraph) tags. Translatable object attributes in XHTML
+ or HTML files can be extracted as separate segments.
+
+
+
+
+
+ Segmentation
+
+ Sentence level segmentation
+ Sentence level segmentation
+
+
+ After segmenting the source file into structural units,
+ OmegaT will segment these blocks further
+ into sentences.
+
+
+
+
+
+ Segmentation rules<indexterm class="singular">
+ <primary>Segmentation</primary>
+
+ <secondary>Rules</secondary>
+ </indexterm>
+
+ The process of segmenting can be pictured as follows: the cursor
+ moves along the text, one character at a time. At each cursor position
+ rules, consisting of a Before and
+ After pattern, are applied in their given
+ order to see if any of the Before
+ patterns are valid for the text on the left and the corresponding
+ After pattern for the text on the right
+ of the cursor. If the rule matches, either the cursor moves on without
+ inserting a segment break (for an exception rule) or a new segment break
+ is created at the current cursor position (for the break rule).
+
+ The two types of rules behave as follows:
+
+
+
+
+ Segmentation
+
+ Rules
+
+ Break rule
+ Break rule
+
+
+ Separates the source text into segments. For example,
+ "Did it make sense? I was not sure." should be
+ split into two segments. For this to happen, there should be a break
+ rule for "?", when followed by spaces and a capitalized word. To
+ define a rule as a break rule, tick the Break/Exception check
+ box.
+
+
+
+
+
+
+
+ Segmentation
+
+ Rules
+
+ Exception rule
+ Exception rule
+
+
+ specify what parts of text should NOT be separated. In spite
+ of the period, "Mrs. Dalloway " should not be
+ split in two segments, so an exception rule should be established
+ for Mrs (and for Mr, for Dr, for prof etc), followed by a period. To
+ define a rule as an exception rule, leave the Break/Exception check
+ box unticked.
+
+
+
+
+ The predefined break rules should be sufficient for most European
+ languages and Japanese. In view of the flexibility, you may consider
+ defining more exception rules for your source language in order to provide
+ more meaningful and coherent segments.
+
+
+
+ Rule priority<indexterm class="singular">
+ <primary>Segmentation</primary>
+
+ <secondary>Rules priority</secondary>
+ </indexterm>
+
+ All segmentation rule sets for a matching language pattern are
+ active and are applied in the given order of priority, so rules for
+ specific language should be higher than default ones. For example, rules
+ for Canadian French (FR-CA) should be set higher than rules for French
+ (FR.*), and higher than Default (.*) ones. Thus, when translating from
+ Canadian French the rules for Canadian French - if any - will be applied
+ first, followed by the rules for French and lastly, by the Default
+ rules.
+
+
+
+ Creating a new rule<indexterm class="singular">
+ <primary>Segmentation</primary>
+
+ <secondary>Creating a new rule</secondary>
+
+ <seealso>Regular expressions</seealso>
+ </indexterm>
+
+ Major changes to the segmentation rules should be generally avoided,
+ especially after completion of the first draft, but minor changes, such as
+ the addition of a recognized abbreviation, can be advantageous.
+
+ In order to edit or expand an existing set of rules, simply click on
+ it in the top table. The rules for that set will appear in the bottom half
+ of the window.
+
+ In order to create an empty set of rules for a new language pattern
+ click Add in the upper half of the
+ dialog. An empty line will appear at the bottom of the upper table (you
+ may have to scroll down to see it). Change the name of the rule set and
+ the language pattern to the language concerned and its code (see for a list of language codes).
+ The syntax of the language pattern conforms to regular expression syntax.
+ If your set of rules handles a language-country pair, we advise you to
+ move it to the top using the Move Up
+ button.
+
+ Add the Before and After patterns. To check their syntax and their
+ applicability, it is advisable to use tools which allow you to see their
+ effect directly. See the chapter on Regular
+ expressions. A good starting point will always be the existing
+ rules.
+
+
+
+ <indexterm class="singular">
+ <primary>Segmentation</primary>
+
+ <secondary>Examples</secondary>
+ </indexterm>A few simple examples
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Intention
+
+ Before
+
+ After
+
+ Note
+
+
+
+
+
+ Set a segment after a period ('.') and before a
+ space
+
+ \.
+
+ \s
+
+ "\." means the character "." "\s" means any white space
+ character ((space, tab, new page etc.)
+
+
+
+ Do not segment after Mr.
+
+ Mr\.
+
+ \s
+
+ This an exception rule, so the rule check box must not be
+ ticked
+
+
+
+ Set a segment after "。" (Japanese period)
+
+ 。
+
+
+
+ Note that after is empty
+
+
+
+ Do not segment after M. Mr. Mrs. and Ms.
+
+ Mr??s??\.
+
+ \s
+
+ Exception rule - see the use of ? in regular
+ expressions
+
+
+
+
+
+
diff --git a/OmegaT/doc_src/en/Spellchecker.xml b/OmegaT/doc_src/en/Spellchecker.xml
new file mode 100644
index 0000000..d09265f
--- /dev/null
+++ b/OmegaT/doc_src/en/Spellchecker.xml
@@ -0,0 +1,165 @@
+
+
+
+ Spell checker<indexterm class="singular">
+ <primary>Spell checker</primary>
+ </indexterm>
+
+ OmegaT has a built-in spell checker based on the spelling checker used
+ in OpenOffice.org, Firefox and Thunderbird. It is consequently able to use
+ the huge range of free spelling dictionaries available for these
+ applications.
+
+
+ Installing spelling dictionaries
+
+ Before the spell check function can be used, a suitable dictionary
+ or dictionaries (i.e. for your target language) must be installed. To
+ install spelling dictionaries, follow this procedure:
+
+
+
+ In your file manager, create a new folder in a suitable location
+ in which to store spelling dictionaries (D:\Translations\spellcheckers
+ in the example below).
+
+
+
+
+
+ In OmegaT, select
+ Menu Options
+
+ Spell checking..
+ Options > Spell
+ Checking, then click Choose
+ beside the Dictionary file folder field. Navigate to and
+ select the folder you created for dictionaries.
+
+
+
+
+
+ Place the dictionary files you wish to use in this folder. There
+ are essentially two ways in which you can do this. You can either copy
+ files manually, i.e. from elsewhere on your system, using your file
+ manager; or you can use OmegaT's "Install new
+ dictionary" function to provide a list of available
+ dictionaries to select from. Note that the "Install" function requires
+ an Internet connection. The selected languages will then be installed
+ and will eventually appear in your spell checker setup window (this
+ may take a while).
+
+
+
+ Copying the files manually makes sense if you already have suitable
+ dictionary files on your system, for instance as part of your
+ OpenOffice.org or Thunderbird installation. It is simpler, however, to
+ look foir dictionaries online, using the URL of
+ online dictionaries field:
+
+
+ <indexterm class="singular">
+ <primary>Spell checker setup</primary>
+
+ <secondary>Spell checker setup - figure</secondary>
+ </indexterm>Spellchecker setup
+
+
+
+
+
+
+
+
+
+
+
+
+ Clicking on Install new dictionary button
+ will open the Dictionary installer window, where you can select the
+ dictionaries zou want to install.Make sure the language code of your
+ target files corresponds to the dictionary's language code: an FR-FR
+ dictionary will not work with an FR target setting. You need to change the
+ setting to FR-FR to have the spell checker recognize the correct
+ dictionary for your target. Look for files with the name, indicating the
+ language used and having extensions aff and
+ dic.
+
+
+
+ Using spelling dictionaries
+
+ There is no need to instruct OmegaT to use a particular spelling
+ dictionary; OmegaT will use the correct language dictionary based upon the
+ language codes of your project. Check however that the language codes are
+ exactly the same: an FR-FR dictionary will not work with an FR target
+ setting, for example. If necessary, edit the file names of the dictionary
+ or change your project's language settings.
+
+ To enable the spell checker, select Options > Spell
+ Checking and tick the Automatically check the
+ spelling of text checkbox (see above).
+
+
+ <indexterm class="singular">
+ <primary>Spell checker</primary>
+
+ <secondary>Spell checker - figure</secondary>
+ </indexterm>Spellchecker in action
+
+
+
+
+
+
+
+
+
+
+
+
+ Right-clicking on an underlined word (Artund in the figure above)
+ opens a drop-down menu listing suggestions for the correction (Art und).
+ You can also instruct the spell checker to ignore all the occurrences of
+ the mis-spelled word, or add it to the dictionary.
+
+
+
+ Hints<indexterm class="singular">
+ <primary>Spell checker</primary>
+
+ <secondary>Hints</secondary>
+ </indexterm>
+
+ If the spell checker is not working, then make sure first that the
+ check box "Automatically check the spelling of text"
+ in the spell checker dialog (Options > Spell
+ checking...) is checked.
+
+ Also check that the target language code of your project against the
+ available vocabularies in the setup window. The spell checker uses the
+ target language code to determine the language to be used : if the target
+ language is Brazilian Portuguese (PT_BR), the subfolder with vocabularies
+ must contain the two vocabulary files, called
+ pt_br.aff and pt_br.dic.
+
+ If you have already translated a large body of text, and then
+ realize the target language code of the project does not match the spell
+ checker's language code (you specified pt_BR as the language, but there
+ are no pt_BR vocabularies, for instance) you can simply copy the two
+ corresponding files and rename them (e.g. from
+ pt_PT.arr and pt_PT.dic to
+ pt._BR.arr and pt_BR.dic). Of
+ course it is much wiser, to take a short break and download the correct
+ versions of the spell checker.
+
+ Note that Remove physically removes the
+ selected vocabularies. If they are used bz some other application on your
+ system, they will disappear from that application, too. If, for whatever
+ reason, you need to do this from time to time, it may make sense to copy
+ the files involved to a different folder, reserved just for use by
+ OmegaT.
+
+
diff --git a/OmegaT/doc_src/en/TranslationMemories.xml b/OmegaT/doc_src/en/TranslationMemories.xml
new file mode 100644
index 0000000..851d2a0
--- /dev/null
+++ b/OmegaT/doc_src/en/TranslationMemories.xml
@@ -0,0 +1,492 @@
+
+
+
+ Translation memories<indexterm class="singular">
+ <primary>Translation memories</primary>
+ </indexterm>
+
+
+ Translation memories in OmegaT
+
+
+ tmx folders - location and purpose
+
+ OmegaT projects can have translation
+ memory files - i.e. files with the extension tmx - in four different
+ places:
+
+
+
+
+ Translation memories
+
+ Subfolder omegat
+
+ Project files
+ omegat folder
+
+
+ The omegat folder contains the
+ project_save.tmx and possibly a number of
+ backup TMX files. The project_save.tmx file
+ contains all the segments that have been recorded in memory since
+ you started the project. This file always exists in the project.
+ Its contents will always be sorted alphabetically by the source
+ segment.
+
+
+
+
+
+ Translation memories
+
+ Project main folder
+ main project folder
+
+
+ The main project folder contains 3 tmx files,
+ project_name-omegat.tmx,
+ project_name-level1.tmx and
+ project_name-level2.tmx (project_name being
+ the name of your project).
+
+
+
+ The level1 file contains only textual
+ information.
+
+
+
+ The level2 file encapsulates
+ OmegaT specific tags in correct tmx
+ tags so that the file can be used with its formatting
+ information in a translation tool that supports tmx level 2
+ memories, or OmegaT itself.
+
+
+
+ The OmegaT file includes
+ OmegaT specific formatting tags so
+ that the file can be used in other
+ OmegaT projects
+
+
+
+ These files are copies of the file
+ project_save.tmx, i.e. of the project's main
+ translation memory, excluding the so-called orphan segments. They
+ carry appropriately changed names, so that its contents still
+ remain identifiable, when used elsewhere, for instance in
+ the tm subfolder of some other project (see
+ below).
+
+
+
+
+
+ Translation memories
+
+ Subfolder tm
+
+ Project files
+ tm folder
+
+
+ The /tm/ folder can contain any number of ancillary
+ translation memories - i.e. tmx files. Such files can be created
+ in any of the three varieties indicated above. Note that other CAT
+ tools can export (and import as well) tmx files, usually in all
+ three forms. The best thing of course is to use OmegaT-specific
+ TMX files (see above), so that the in-line formatting within the
+ segment is retained.
+
+ The contents of translation memories in the tm subfolder
+ serve to generate suggestions for the text(s) to be translated.
+ Any text, already translated and stored in those files, will
+ appear among the fuzzy matches, if it is sufficiently similar to
+ the text currently being translated.
+
+ If the source segment in one of the ancillary TMs is
+ identical to the text being translated, OmegaT acts as defined in
+ the
+ Options
+
+ Editing Behavior...
+ dialogue window. For instance (if the default is
+ accepted), the translation from the ancillary TM is accepted and
+ prefixed with [fuzzy], so that the translator
+ can review the translations at a later stage and check whether the
+ segments tagged this way, have been translated correctly (see the
+ Editing
+ behavior chapter)
+ .
+
+
+
+
+
+
+ Translation memories
+
+ Subfolder tm/auto
+
+ Project files
+ tm/auto folder
+ Project
+
+ Pretranslation
+
+
+
+ If it is clear from the very start, that translations in a
+ given TM (or TMs) are all correct, one can put them into
+ the tm/auto folder and avoid
+ confirming a lot of [fuzzy] cases. This will
+ effectively pre-translate the
+ source text: all the segments in the source text, for which
+ translations can be found in those "auto" TMs, will land in the
+ main TM of the project without any user intervention.
+
+
+
+
+ Optionally, you can let OmegaT have an
+ additional tmx file (OmegaT-style) anywhere
+ you specify, containing all translatable segments of the project. See
+ pseudo-translated memory below.
+
+ Note that all the translation memories are loaded into memory when
+ the project is opened. Back-ups are produced regularly of the project
+ translation memory (see next chapter), and
+ project_save.tmx is also saved/updated when the
+ project is closed or loaded again. This means for instance that you do
+ not need to exit a project you are currently working on if you decide to
+ add another ancillary TM to it: you simply reload the project, and the
+ changes you have made will be included.
+
+ The locations of the various different translation memories for a
+ given project are user-defined (see Project dialog window in Instant start guide)
+
+ Depending on the situation, different strategies are thus
+ possible, for instance:
+
+ several projects on the same subject:
+ keep the project structure, and change source and target
+ directories (Source = source/order1, target = target/order1 etc). Note
+ that you segments from order1, that are not present in order2 and other
+ subsequent jobs, will be tagged as orphan segments; however, they will
+ still be useful for getting fuzzy matches.
+
+ several translators working on the same
+ project: split the source files into source/Alice,
+ source/Bob... and allocate them to team members (Alice, Bob ...). They
+ can then create their own projects and, deliver their own
+ project_save.tmx, when finished or when a given
+ milestone has been reached. The project_save.tmx
+ files are then collected and possible conflicts as regards terminology
+ for instance get resolved. A new version of the master TM is then
+ created, either to be put in team members'
+ tm/autosubdirectories or to replace their
+ project_save.tmx files. The team can also use the
+ same subfolder structure for the target files. This allows them for
+ instance to check at any moment, whether the target version for the
+ complete project is still OK
+
+
+
+ tmx backup<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Backup</secondary>
+ </indexterm>
+
+ As you translate your files, OmegaT
+ stores your work continually in project_save.tmx in
+ the project's /omegat subdirectory.
+
+ OmegaT also backups translation memory
+ to project_save.tmx.YEARMMDDHHNN.bak in the same
+ subfolder whenever a project is opened or reloaded. YEAR is 4-digit
+ year, MM is a month, DD day of the month, HH and NN are hours and
+ minutes when the previous translation memory was saved.
+
+ If you believe you have lost translation data, follow the
+ following procedure:
+
+
+
+ Close the project
+
+
+
+ Rename the current project_save.tmx file
+ ( e.g. to project_save.tmx.temporary)
+
+
+
+ Select the backup translation memory that is most likely -
+ e.g. the most recent one, or the last version from the day before)
+ to contain the data you are looking for
+
+
+
+ Copy it to project_save.tmx
+
+
+
+ Open the project
+
+
+
+
+
+ tmx files and language<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Language</secondary>
+ </indexterm>
+
+ tmx files contain translation units, made of a number of
+ equivalent segments in several languages. A translation unit comprises
+ at least two translation unit variations (TUV). Either can be used as
+ the source or target.
+
+ The settings in your project indicate which is the source and
+ which the target language. OmegaT thus takes the TUV segments
+ corresponding to the project's source and target language codes and uses
+ them as the source and target segments respectively. OmegaT recognizes
+ the language codes using the following two standard conventions :
+
+
+
+ 2 letters (e.g. JA for Japanese), or
+
+
+
+ 2- or 3-letter language code followed by the 2-letter country
+ code (e.g. EN-US - See for a
+ partial list of language and country codes).
+
+
+
+ If the project language codes and the tmx language codes fully
+ match, the segments are loaded in memory. If languages match but not the
+ country, the segments still get loaded. If neither the language code not
+ the country code match, the segments will be ignored.
+
+
+ Translation memories
+
+ multilingual, handling of
+ TMX files can generally contain translation units with
+ several candidate languages. If for a given source segment there is no
+ entry for the selected target language, all other target segments are
+ loaded, regardless of the language. This avoids loading unwanted
+ non-project languages from multilingual TMXs, while still allowing the
+ use of monolingual TMXs with other target languages than the project
+ target language selected. For instance if the language pair of the
+ project is DE-FR, it can be still be of some help to have access to a
+ DE-EN translation, if there's no match in the DE-FR pair.
+
+
+
+ Orphan segments<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Orphan segments</secondary>
+ </indexterm>
+
+ The file project_save.tmx contains all the
+ segments that have been translated since you started the project. If you
+ modify the project segmentation or delete files from the source, some
+ matches may appear as orphan strings in
+ the Match Viewer: such matches refer to segments that do not exist any
+ more in the source documents, as they correspond to segments translated
+ and recorded before the modifications took place.
+
+
+
+
+ Reusing translation memories<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Import and export</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Reusing translation memories</secondary>
+ </indexterm>
+
+ Initially, that is when the project is created, the main TM of the
+ project, project_save.tmx is empty. This TM gradually
+ becomes filled during the translation. To speed up this process, existing
+ translations can be reused. If a given sentence has already been
+ translated once, and translated correctly, there is no need for it to be
+ retranslated. Translation memories may also contain reference
+ translations: multinational legislation, such as that of the European
+ Community, is a typical example.
+
+ When you create the target documents in an
+ OmegaT project, the translation memory of the
+ project is outputted in the form of three files in the root folder of your
+ OmegaT project (see the above description). You
+ can regard these three tmx files (-omegat.tmx,
+ -level1.tmx and -level2.tmx) as
+ an "export translation memory", i.e. as an export of your current
+ project's content in bilingual form.
+
+ Should you wish to reuse a translation memory from a previous
+ project (for example because the new project is similar to the previous
+ project, or uses terminology which might have been used before), you can
+ use these translation memories as "input translation memories", i.e. for
+ import into your new project. In this case, place the translation memories
+ you wish to use in the \tm or
+ \tm\auto folder of your new project: in the former
+ case you will get hits from these translation memories in the fuzzy
+ matches viewer, and in the latter case these TMs will be used to
+ pre-translate your source text.
+
+ By default, the \tm folder is below the project's root folder (e.g.
+ ...\MyProject\tm), but you can choose a different
+ folder in the project properties dialog if you wish. This is useful if you
+ frequently use translation memories produced in the past, for example
+ because they are on the same subject or for the same customer. In this
+ case, a useful procedure would be:
+
+
+
+ Create a folder (a "repository folder") in a convenient location
+ on your hard drive for the translation memories for a particular
+ customer or subject.
+
+
+
+
+
+ Whenever you finish a project, copy one of the three "export"
+ translation memory files from the root folder of the project to the
+ repository folder.
+
+
+
+
+
+ When you begin a new project on the same subject or for the same
+ customer, navigate to the repository folder in the
+ Project > Properties > Edit Project
+ dialog and select it as the translation memory
+ folder.
+
+
+
+ Note that all the tmx files in the /tm repository are parsed when
+ the project is opened, so putting all different TMs you may have on hand
+ into this folder may unnecessarily slow OmegaT down. You may even consider
+ removing those that are not required any more, once you have used their
+ contents to fill up the project-save.tmx file.
+
+
+ Importing and exporting translation memories
+
+ OmegaT supports imported tmx versions 1.1-1.4b (both level 1 and
+ level 2). This enables the translation memories produced by other tools
+ to be read by OmegaT. However, OmegaT does not fully support imported
+ level 2 tmx files (these store not only the translation, but also the
+ formatting). Level 2 tmx files will still be imported and their textual
+ content can be seen in OmegaT, but the quality of fuzzy matches will be
+ somewhat lower.
+
+ OmegaT follows very strict procedures when loading translation
+ memory (tmx) files. If an error is found in such a file, OmegaT will
+ indicate the position within the defective file at which the error is
+ located.
+
+ Some tools are known to produce invalid tmx files under certain
+ conditions. If you wish to use such files as reference translations in
+ OmegaT, they must be repaired, or OmegaT will report an error and fail
+ to load them. Fixes are trivial operations and OmegaT assists
+ troubleshooting with the related error message. You can ask the user
+ group for advice if you have problems.
+
+ OmegaT exports version 1.4 TMX files (both level 1
+ and level 2). The level 2 export is not fully compliant with the level 2
+ standard, but is sufficiently close and will generate correct matches in
+ other translation memory tools supporting TMX Level 2. If you only need
+ textual information (and not formatting information), use the level 1
+ file that OmegaT has created.
+
+
+
+
+ Pseudo-translated memory<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Pseudotranslation</secondary>
+ </indexterm>
+
+
+ Of interest for advanced users only!
+
+
+ Before segments get translated, you may wish to pre-process them or
+ address them in some other way than is possible with OmegaT. For example,
+ if you wish to create a pseudo-translation for testing purposes, OmegaT
+ enables you to create an additional tmx file that contains all segments of
+ the project. The translation in this tmx can be either
+
+
+
+ translation equals source (default)
+
+
+
+
+
+ translation segment is empty
+
+
+
+ The tmx file can be given any name you specify. A pseudo-translated
+ memory can be generated with the following command line parameters:
+
+ java -jar omegat.jar --pseudotranslatetmx=<filename>
+ [pseudotranslatetype=[equal|empty]]
+
+ Replace <filename> with the name of the
+ file you wish to create, either absolute or relative to the working
+ directory (the directory you start OmegaT
+ from). The second argument --pseudotranslatetype is
+ optional. Its value is either equal (default value, for
+ source=target) or empty (target segment is empty). You
+ can process the generated tmx with any tool you want. To reuse it in
+ OmegaT rename it to project_save.tmx
+ and place it in the omegat-folder of your
+ project.
+
+
+
+ Upgrading translation memories<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Upgrading to sentence segmentation</secondary>
+ </indexterm>
+
+ Very early versions of OmegaT were
+ capable of segmenting source files into paragraphs only and were
+ inconsistent when numbering formatting tags in HTML and Open Document
+ files. OmegaT 2.5 can detect and upgrade such
+ tmx files on the fly to increase fuzzy matching quality and leverage your
+ existing translation better, saving you the work of doing this
+ manually.
+
+ A project's tmx will be upgraded only once, and will be written in
+ upgraded form into the project-save.tmx; legacy tmx
+ files will be upgraded on the fly each time the project is loaded. Note
+ that in some cases changes in file filters in
+ OmegaT 2.5 may lead to totally different
+ segmentation; as a result, you will have to upgrade your translation
+ manually in such rare cases.
+
+
diff --git a/OmegaT/doc_src/en/UserInterface.xml b/OmegaT/doc_src/en/UserInterface.xml
new file mode 100644
index 0000000..e7c7eb2
--- /dev/null
+++ b/OmegaT/doc_src/en/UserInterface.xml
@@ -0,0 +1,1089 @@
+
+
+
+ The user interface
+
+
+ User interface items
+
+
+ Frequently used windows<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+ </indexterm>
+
+
+
+ OmegaT main window
+
+
+ contains the main menu, status bar and several panes:
+
+
+
+ Editor - where you type and edit the translation
+
+
+
+ Match Viewer - displays the most similar segments from
+ translation memories
+
+
+
+ Glossary Viewer - displays terminology
+
+
+
+ Dictionary Viewer - displays information provided by
+ dictionaries
+
+
+
+ Machine Translation - displays the translation, provided
+ by MT services, like Google Translate
+
+
+
+ Multiple Translations - shows translation alternatives -
+ if any entered - for the current segment
+
+
+
+ Notes viewer - notes by the translator, regarding the
+ current segment
+
+
+
+ Comments - comments by the translator, regarding the
+ current segment
+
+
+
+
+
+
+
+ Shortcuts
+
+ Ctrl+L - Project files window
+ Project Files window
+
+
+ The list of your translatable files (open with
+ Ctrl
+
+ L
+ , close with Esc)
+
+
+
+
+
+ Shortcuts
+
+ Ctrl+F - Search window
+ Search window
+
+
+ Used to search for specific segments in the project (open
+ with
+ Ctrl
+
+ F
+ , close with Esc)
+
+
+
+
+
+
+ Less frequently used
+
+
+
+
+ Shortcuts
+
+ Ctrl+T - Tag validation window
+ Tag Validation window
+
+
+ Used to check for tag mistakes in translations (open with
+
+ Ctrl
+
+ T
+ close with Esc)
+
+
+
+
+
+ Shortcuts
+
+ F1 - Help
+ Help browser
+
+
+ Used to read the user manual (open with F1,
+ close with Esc)
+
+
+
+
+ Statistics window
+
+
+ Used to open the window with the statistics of the project,
+ display it, using
+
+ Menu Tools
+
+ statistics
+ Tools
+
+ Statistics.
+
+
+
+
+
+ Match statistics window
+
+
+ Used to display the match statistics of the project, select
+
+
+ Menu Tools
+
+ Match statistics
+ Tools
+
+ Match statistics
+ to open it.
+
+
+
+
+
+
+ Project settings dialogs <indexterm class="singular">
+ <primary>Project</primary>
+
+ <secondary>Project Settings</secondary>
+ </indexterm>
+
+ The dialogs below are used to change OmegaT project settings. Each
+ is described in detail in a separate section; the information below
+ summarizes their use and how they are invoked:
+
+
+
+
+ Shortcuts
+
+ Ctrl+E - Project properties
+
+ Menu Project
+
+ Properties
+ Project Properties
+
+
+ Used to modify the project folders and languages, (access
+ via
+
+
+ Ctrl
+
+ E
+
+
+
+ Project
+
+ properties...
+ , close via Esc)
+
+
+
+
+
+ Project Settings
+
+ Font
+ Font
+ Menu Options
+
+ Font
+
+
+
+ Used to modify the font used by
+ OmegaT to display source, translation, matches and
+ glossary terms, (access via
+ Options
+
+ Font...
+ , close via
+ Esc)
+
+
+
+
+
+ Project Settings
+
+ File filters
+ File filters
+ Menu Options
+
+ File filters
+
+
+
+ Used to adjust the handling of supported file formats
+ (access via
+ Options
+
+ File Filters...
+ , close via Esc)
+
+
+
+
+
+ Project Settings
+
+ Segmentation
+ Segmentation
+ Menu Options
+
+ Segmentation
+
+
+
+ Used to change the way your text is segmented into sentences
+ (access via
+ Options
+
+ Segmentation
+ , close via Esc)
+
+
+
+
+
+ Project Settings
+
+ Editing Behavior
+ Editing Behavior
+ Menu Options
+
+ Editing Behavior
+
+
+
+ Used to change how OmegaT behaves
+ when you iterate between the segments (access via
+ Options
+
+ Behavior...
+ , close via Esc)
+
+
+
+
+
+
+
+ <application>OmegaT</application> main window<indexterm
+ class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Main window</secondary>
+
+ <tertiary>- figure</tertiary>
+ </indexterm><indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Main window</secondary>
+ </indexterm>
+
+
+ OmegaT panes
+
+
+
+
+
+
+
+
+
+
+
+
+ The main window consists of several panes, the main menu and a
+ status bar. You can change the position of any pane or even undock it to a
+ separate window by clicking and dragging the pane by its name. Depending
+ on the pane status, different signs can appear at its top right
+ corner:
+
+
+ Pane widgets<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Pane widgets</secondary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ minimizes the pane, so that only its name is shown at the
+ bottom of the window.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ maximizes the pane
+
+
+
+
+
+
+
+
+
+
+
+
+
+ undocks the pane from the main window.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ puts the pane back within the main window.
+
+
+
+
+
+ You can overlap panes if desired. When this is done the panes
+ display a tab at the top. The separators between the panes can be dragged
+ to resize panes. Should you lose track of your changes to the user
+ interface, you can use
+ OmegaT windows
+
+ Windows and panes in OmegaT
+
+ OmegaT windows
+
+ Restoring to factory setup
+ Options → Restore the main window any time to
+ return to the original layout.
+
+ The counters in the lower right corner keep track of the progress of
+ the translation (numbers in the left hand column refer to the figure
+ above):
+
+
+ Main Window - counters<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Counters</secondary>
+ </indexterm>
+
+
+
+
+
+
+ 33/33
+
+ number of segments - translated vs total for the current
+ file
+
+
+
+ 2780/2780
+
+ number of unique segments - translated vs total in the
+ project
+
+
+
+ 3760
+
+ total number of segments (including repeats) in the
+ project
+
+
+
+ 126/127
+
+ number of source and target characters in the current
+ segment
+
+
+
+
+
+ From a practical point of view, the most important pair of numbers
+ is the second pair: it tells, how much you have done so far, in relation
+ to the total or second number. The project in the example is evidently
+ finished, as all the unique segments have been translated.
+
+
+ Editor pane<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Editor pane</secondary>
+ </indexterm>
+
+ This is where you type and edit your translation. The Editor pane
+ displays the text of the partially translated document: the text already
+ translated is displayed in translation while the untranslated text is
+ displayed in the original language. The displayed text is split into
+ segments and you may scroll through the document and double-click on any
+ segment to open and edit it. In the above case, the segments already
+ translated are shown in yellow, but this may be changed to suit your
+ preferences (see ).
+
+ One of the above segments is the current segment. It is the
+ segment that is displayed in two parts. The upper part is in the source
+ language, in bold characters with a green background color, the lower
+ part is the editing field, ended by a marker:
+ Segment marker
+ the marker is <segment nnnn>
+ where nnnn is a number of the segment in the project. Use the upper part
+ as a reference and replace or modify the contents of the editing field
+ with your translation.
+
+ Depending upon the preferred editing behavior, the editing field
+ for the untranslated segment may be empty, contain the source text, or
+ contain the translation of the string most similar to the one to be
+ translated. When you move to another segment, the translation is
+ validated and stored. If you want the translation to be the same as the
+ source, simply make the editing field empty by removing all the text
+ (select all with Ctrl+A and delete with
+ Del). OmegaT is able to store translations that are
+ identical to the source. This is useful for documents that contain trade
+ marks, names or other proper nouns, or parts in a third language that do
+ not require translation. See Translation editing
+ for more details.
+
+ If you right click on the Editor pane, a pop-up menu opens,
+ offering Cut, Copy, Paste (i.e. same
+ functions as
+ Ctrl
+
+ X
+ ,
+ Ctrl
+
+ C
+ and
+ Ctrl
+
+ V
+ ) and the GoTo segment
+ functions.
+
+
+
+ Fuzzy matches pane<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Fuzzy matches pane</secondary>
+ </indexterm>
+
+
+ <indexterm class="singular">
+ <primary>Matches</primary>
+
+ <secondary>Matches pane - figure</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Matches pane - figure</secondary>
+ </indexterm>Matches pane
+
+
+
+
+
+
+
+
+
+
+
+
+ The match viewer shows the most similar segments from translation
+ memories, both from internal project translation memory created in real
+ time as you translate your project and from ancillary translation
+ memories you have imported from your earlier jobs, or received from your
+ client or translation agency.
+
+ When you move to the next segment, the first fuzzy match (the one
+ with the best matching percentage) is automatically selected. You may
+ select a different match by pressing Ctrl+2, 3, 4, or
+ 5.
+ Shortcuts
+
+ Ctrl+N - Selecting the match
+ Of course, pressing
+ Ctrl
+
+ 5
+ will have no effect, if there is no match #5. To use the
+ selected match in your translation, use
+ Ctrl+R
+ Shortcuts
+
+ Ctrl+R - Replace text
+ to replace the target field with the match or use
+ Ctrl+I
+ Shortcuts
+
+ Ctrl+I - Insert text
+ to insert it at the cursor position.
+
+ The matching percentage is roughly equivalent to taking the number
+ of common words in the matched and the matching segment and dividing by
+ the number of words in the longer of the two. The selected fuzzy match
+ is highlighted in bold, words that are missing in the segment you are
+ translating are colored blue and words adjacent to the missing parts
+ green. In the above example the source segment is Context menu command. The top match is 100%,
+ because all words match. So do the next two matches, and the match #4 is
+ similar, but different. The line with the matching percentage also
+ includes the name of the translation memory
+ Translation memories
+
+ Matches
+ containing the match. If there's no file name displayed,
+ the source is the internal project translation memory. Orphan
+ segments
+ Translation memories
+
+ Orphan segments
+ (the match #2) describe segments in the default project
+ translation memory that have no corresponding source segment.
+
+ There are actually three match estimates available (66/66/30 in
+ the case of the match #4 above). They are defined as follows:
+
+
+
+ match percentage when the tokenizer plugin is used
+
+
+
+
+
+ default OmegaT match - number of matched words - with numerals
+ and tags ignored - divided by the total word count
+
+
+
+
+
+ OmegaT match, including numbers, tags
+
+
+
+
+
+ Glossary pane<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Glossary pane</secondary>
+ </indexterm>
+
+ The Glossary pane allows you to access your own collection of
+ expressions and specialist terminology which you have built up in your
+ glossary files. It shows translation of terms found in the current
+ segment. The source segment in the example below was “Context
+ menu command”, as in the Fuzzy Matches example above, and the
+ terms shown were found in the glossaries, available (Microsoft's Term
+ collection and Slovenian Linux User group Glossary).
+
+
+ <indexterm class="singular">
+ <primary>Glossaries</primary>
+
+ <secondary>multi-word entry in the glossary - figure</secondary>
+ </indexterm>multi-word entry in the glossary
+
+
+
+
+
+
+
+
+
+
+
+
+ If you have TransTip option activated Options →
+ Transtip), you can right click on the highlighted word in
+ the source segment to open a drop-down menu with suggested translation,
+ as offered by your glossary. Selecting one of them will insert it at the
+ current position into the target segment. You can also highlight your
+ preferred alternative in the glossary pane and insert it into the target
+ by right clicking on the selection.
+
+
+
+ Dictionary pane<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Dictionary pane</secondary>
+ </indexterm>
+
+ Dictionaries are the electronic equivalents of printed
+ dictionaries like Merriam Webster, Duden, Larousse etc., that you may
+ have on your desk. See more about them in the chapter on Dictionaries
+
+
+
+ Multiple Translations pane<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Multiple Translations pane</secondary>
+ </indexterm>
+
+ A given source segment may require several different translations,
+ depending on the context. If the current translation of the segment does
+ not fit, the user can select Edit → Create Alternative
+ Translation . The target text entered after that will be
+ treated as an alternative translation of the source segment. You can
+ define one of the alternative - for instance the most probable among
+ them - as default translation by selecting Edit → Use as
+ Default Translation
+
+
+
+ Notes pane
+
+ The translator can add notes to the opened segment, for instance
+ to come back later to the segment and redo the translation, check that
+ alternative translations are correct or to ask colleagues for their
+ opinion. You can browse through notes using GoTo → Next
+ Note and GoTo → Previous
+ Note.
+
+
+
+ Comments pane
+
+ Some of the file formats, specialized for translation work, for
+ instance PO, allow the inclusion of comments. This way the translator
+ can be provided the context about the segment to be translated. In the
+ example below, the author of the PO file included a warning for the
+ translator to check the length of the translation:
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Machine Translation pane<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Machine Translation pane</secondary>
+ </indexterm>
+
+ The machine translation pane, when opened, contains the
+ suggestions by machine translation tools for the current segment. Press
+ Ctrl+M to replace the translation of the current
+ segment with the suggested translation. More in the chapter Machine translation
+
+
+
+ Main menu
+
+ The main menu provides access to all
+ OmegaT functions. See the Main
+ Menu appendix for a full description of all menus and menu
+ items. The most frequently used functions are accessible with keyboard
+ shortcuts, so once you become accustomed to them, you will no longer
+ need to browse through the menus while translating. See chapter Menu and Keyboard shortcuts for
+ details.
+
+
+
+ Status bar
+
+ The status bar displays work-flow related messages at the bottom
+ of the main window. This bar gives the user feedback on specific
+ operations that are in progress. It also displays the number of fuzzy
+ and glossary matches for the current segment.
+
+
+
+
+ Other windows
+
+
+ Project files<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Project files</secondary>
+ </indexterm>
+
+ The Project Files window lists the project files and displays
+ other project information. It is displayed automatically when OmegaT
+ loads a project. Use Ctrl+L
+ Shortcuts
+
+ Ctrl+L - Project files list
+ to open and Esc to close
+ it. The Project Files Window displays the following information:
+
+
+
+ the list of all translatable files in the project. These are
+ the files present in the Source files folder in a format that OmegaT
+ is able to recognize. Clicking on any file will open it for
+ translation
+
+
+
+
+
+ the file currently available in the Editor pane is highlighted
+ with a blue background. Pressing Enter will move
+ the Editor pane to the top of the file selected
+
+
+
+
+
+ the number of segments in each file is shown next to the file
+ name
+
+
+
+
+
+ the total number of segments, the number of unique segments in
+ the whole project, and the number of unique segments already
+ translated are shown at the bottom
+
+
+
+ The set of Unique segments is
+ computed by taking all the segments and removing all duplicate segments.
+ (The definition of “unique” is case-sensitive: "Run" and "run" are
+ treated as being different)
+
+ The difference between "Number of segments" and "Number of unique
+ segments" provides an approximate idea of the number of repetitions in
+ the text. Note however that the numbers do not indicate how relevant the
+ repetitions are: they could mean relatively long sentences repeated a
+ number of times (in which case you are fortunate) or it could describe a
+ table of keywords (not so fortunate). The
+ project_stats.txt located in the omegat folder of
+ your project contains more detailed segment information, broken down by
+ file.
+
+ Modifying the segmentation rules may have the effect of modifying
+ the number of segments/unique segments. This, however, should generally
+ be avoided once you have started translating the project. See the
+ chapter Segmentation rules for more
+ information.
+
+
+ Source files
+
+ Adding files to the project
+ Adding files to the project: You can add source
+ files to the project by clicking on the "Import Source
+ Files..." button. This copies the selected files to the
+ source folder and reloads the project to import the
+ new files. You can also add source files from Internet pages, written in
+ MediaWiki, by clicking on "Import from
+ MediaWiki" button and providing the corresponding
+ URL.
+
+
+
+ Search window<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Search pane</secondary>
+ </indexterm>
+
+ You can use the search window to find specific segments in a
+ project. You can also have several search windows open simultaneously.
+ To open a new search window, use
+ Ctrl
+
+ F
+ in the Main window. The search window consists of a text
+ field for search strings or keywords, flags and radio buttons for
+ setting up the search and a display area containing the results of the
+ search. See the chapter Searches for more
+ information about the search window.
+
+
+
+ Tag validation<indexterm class="singular">
+ <primary>Tag validation</primary>
+
+ <seealso>Shortcuts, Tags</seealso>
+ </indexterm><indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Tag validation</secondary>
+
+ <seealso>Tags</seealso>
+ </indexterm>
+
+ The tag validation window detects and lists any tag errors and
+ inconsistencies in the translation. Open the window with
+ Ctrl+T. The window features a 3 column table
+ with a link to the segment and its source and target contents:
+
+
+ <indexterm class="singular">
+ <primary>Tag validation</primary>
+
+ <secondary>Window - figure</secondary>
+
+ <seealso>Tags</seealso>
+ </indexterm>Tag validation window
+
+
+
+
+
+
+
+
+
+
+
+
+ Tags are highlighted in bold blue for easy comparison between the
+ original and the translated contents. Click on the link to jump to the
+ segment in the Editor pane. Correct the error if necessary and press
+ Ctrl+T to return to the tag validation window
+ to correct other errors. In the first and third case above tags are
+ paired incorrectly, and in the second case the < sign is missing from
+ the starting tag.
+
+ Tag errors are cases in which the tags in the translation do not
+ correspond in order and number to the original segment. Some tag
+ scenarios flagged in the tag validation window are necessary and are
+ benign, others will cause problems when the translated document is
+ created. Tags generally represent some kind of formatting in the
+ original text. Simplifying the original text formatting in the source
+ file before commencing translation greatly contributes to reducing the
+ number of tags.
+
+
+
+ Statistics<indexterm class="singular">
+ <primary>Statistics</primary>
+
+ <seealso>Menu Tools</seealso>
+ </indexterm>
+
+ The statistics window - accessed via Tools>Statistics - shows the statistics of the
+ current OmegaT project, both in the summary form as well as in detail
+ for every file to be translated. The statistics shown is available as a
+ tab-separated project_stats.txt file (subfolder
+ omegat), ready to be loaded into a spreadsheet
+ program for the user's convenience. You can use Ctrl+A
+
+ Shortcuts
+
+ Ctrl+A - Select All
+ , Ctrl+C
+ Shortcuts
+
+ Ctrl+C - copy text
+ , Ctrl+V
+ Shortcuts
+
+ Ctrl+V - Paste text
+ to copy/paste the contents.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Match statistics<indexterm class="singular">
+ <primary>Match Statistics</primary>
+
+ <seealso>Menu Tools</seealso>
+ </indexterm>
+
+ The match statistics are accessed viaTools>Match
+ Statistics. The evaluation is rather CPU intensive and can
+ be time-consuming, so a progress bar is shown during the calculation. As
+ far as categories are concerned, the de facto industry standard of
+ classifying matches into the following groups is used: Exact match,
+ 95%-100%, 85%-94%, 75%-84%, 50%-74% and No match. The word counts,
+ identical to counts in the Project Files window, are based strictly on
+ OmegaT's method of counting, with a few differences in terminology to
+ account for concept differences. This information is computed for
+ segments as well as for words and for characters (without and including
+ spaces).
+
+ Note that these totals are a good (or as-good-as-it-can-be)
+ approximation of the work involved in the project and thus can serve as
+ a basis for your cost and price calculations.
+
+
+ match statistics
+
+
+
+
+
+
+
+
+
+
+
+
+ Spaces between segments are not taken into account in the last
+ column. Repetitions stand for identical segments present several times
+ in the text. The first segment and its contents will be classified as
+ "no match", and the rest of them as a repetition of the first. If the
+ translation for several identical source segments already exists in the
+ translation memory of the project, these segments, together with other,
+ already translated unique segments, will be classified as an "Exact
+ match". The number of unique segments, if needed, is provided in the
+ standard statistics window, regardless of whether they have been
+ translated or not.
+
+ The rest of the categories (50-100%) involves untranslated
+ segments with a fuzzy match. Fuzzy matches can come from the
+ /tm folder as well - and not just from the internal
+ translation memory in /omegaT, as is the case for
+ repetitions and exact matches. The only difference with matches from the
+ project_save translation memory is that external
+ TMs cannot give exact matches, only 100%. If one does not wish to use
+ external TMs for counting, one will either have to empty the /tm folder
+ or change the project setup (temporarily) so that the value for /tm
+ points to a different location.
+
+ The Match Statistics are tab-separated and you can use
+ Ctrl+A
+ Shortcuts
+
+ Ctrl+A - Select All
+ , Ctrl+C
+ Shortcuts
+
+ Ctrl+C - copy text
+ , Ctrl+V
+ Shortcuts
+
+ Ctrl+V - Paste text
+ to copy/paste them, for instance into a
+ spreadsheet or into your cost-accounting application. Once computed, the
+ data also available in
+ omegat/project_stats_match.txt. Note that the file
+ is time-stamped, as the calculation (contrary to the standard
+ statistics) is not instantaneous and can thus quickly become
+ obsolete.
+
+
+
+ Help browser<indexterm class="singular">
+ <primary>Menu Help</primary>
+
+ <secondary>Help browser</secondary>
+ </indexterm>
+
+ The help browser (which displays this manual) can be opened by
+ pressing
+ Shortcuts
+
+ F1 - Help
+ F1 or navigating to
+ Menu Help
+
+ User Manual...
+ Help → User Manual... in the main menu. In
+ the window, the manual and two buttons are displayed: Back and Contents.
+ The user manual is an HTML document with links to different chapters.
+ Clicking on a link as you would do in a web browser brings the desired
+ page to the front.
+
+ The user manual is located in the docs subfolder under the OmegaT
+ installation folder, so you may can, for instance, view the English
+ documentation by opening the docs/en/index.html
+ file in your browser. Opening the user manual in this way
+ also enables you to follow external links, as the built-in help browser
+ does not accept external Internet links.
+
+
+
diff --git a/OmegaT/doc_src/en/images/AppleKey.gif b/OmegaT/doc_src/en/images/AppleKey.gif
new file mode 100644
index 0000000..dabdac4
Binary files /dev/null and b/OmegaT/doc_src/en/images/AppleKey.gif differ
diff --git a/OmegaT/doc_src/en/images/Comments_25.png b/OmegaT/doc_src/en/images/Comments_25.png
new file mode 100644
index 0000000..2040603
Binary files /dev/null and b/OmegaT/doc_src/en/images/Comments_25.png differ
diff --git a/OmegaT/doc_src/en/images/DictMerriamWebster.png b/OmegaT/doc_src/en/images/DictMerriamWebster.png
new file mode 100644
index 0000000..08bc241
Binary files /dev/null and b/OmegaT/doc_src/en/images/DictMerriamWebster.png differ
diff --git a/OmegaT/doc_src/en/images/Dock.gif b/OmegaT/doc_src/en/images/Dock.gif
new file mode 100644
index 0000000..4a6487c
Binary files /dev/null and b/OmegaT/doc_src/en/images/Dock.gif differ
diff --git a/OmegaT/doc_src/en/images/EditingBehaviourOptions.png b/OmegaT/doc_src/en/images/EditingBehaviourOptions.png
new file mode 100644
index 0000000..e4328f9
Binary files /dev/null and b/OmegaT/doc_src/en/images/EditingBehaviourOptions.png differ
diff --git a/OmegaT/doc_src/en/images/GlossaryEntry_25.png b/OmegaT/doc_src/en/images/GlossaryEntry_25.png
new file mode 100644
index 0000000..6c614b7
Binary files /dev/null and b/OmegaT/doc_src/en/images/GlossaryEntry_25.png differ
diff --git a/OmegaT/doc_src/en/images/GlossaryPane_25.png b/OmegaT/doc_src/en/images/GlossaryPane_25.png
new file mode 100644
index 0000000..1c02dc9
Binary files /dev/null and b/OmegaT/doc_src/en/images/GlossaryPane_25.png differ
diff --git a/OmegaT/doc_src/en/images/InstantGuide_1.png b/OmegaT/doc_src/en/images/InstantGuide_1.png
new file mode 100644
index 0000000..700879e
Binary files /dev/null and b/OmegaT/doc_src/en/images/InstantGuide_1.png differ
diff --git a/OmegaT/doc_src/en/images/InstantGuide_2.png b/OmegaT/doc_src/en/images/InstantGuide_2.png
new file mode 100644
index 0000000..006ce2c
Binary files /dev/null and b/OmegaT/doc_src/en/images/InstantGuide_2.png differ
diff --git a/OmegaT/doc_src/en/images/MatchStatistics.png b/OmegaT/doc_src/en/images/MatchStatistics.png
new file mode 100644
index 0000000..7297bf5
Binary files /dev/null and b/OmegaT/doc_src/en/images/MatchStatistics.png differ
diff --git a/OmegaT/doc_src/en/images/MatchesPane_25.png b/OmegaT/doc_src/en/images/MatchesPane_25.png
new file mode 100644
index 0000000..ea6409d
Binary files /dev/null and b/OmegaT/doc_src/en/images/MatchesPane_25.png differ
diff --git a/OmegaT/doc_src/en/images/Maximize.gif b/OmegaT/doc_src/en/images/Maximize.gif
new file mode 100644
index 0000000..24e1b0a
Binary files /dev/null and b/OmegaT/doc_src/en/images/Maximize.gif differ
diff --git a/OmegaT/doc_src/en/images/Minimize.gif b/OmegaT/doc_src/en/images/Minimize.gif
new file mode 100644
index 0000000..f41fac5
Binary files /dev/null and b/OmegaT/doc_src/en/images/Minimize.gif differ
diff --git a/OmegaT/doc_src/en/images/MobyDick.png b/OmegaT/doc_src/en/images/MobyDick.png
new file mode 100644
index 0000000..b6de59a
Binary files /dev/null and b/OmegaT/doc_src/en/images/MobyDick.png differ
diff --git a/OmegaT/doc_src/en/images/MultiTerm_Glossary_25.png b/OmegaT/doc_src/en/images/MultiTerm_Glossary_25.png
new file mode 100644
index 0000000..fa5c256
Binary files /dev/null and b/OmegaT/doc_src/en/images/MultiTerm_Glossary_25.png differ
diff --git a/OmegaT/doc_src/en/images/NewProject_25.png b/OmegaT/doc_src/en/images/NewProject_25.png
new file mode 100644
index 0000000..8d33951
Binary files /dev/null and b/OmegaT/doc_src/en/images/NewProject_25.png differ
diff --git a/OmegaT/doc_src/en/images/OmT_Cyrillic.png b/OmegaT/doc_src/en/images/OmT_Cyrillic.png
new file mode 100644
index 0000000..fd74105
Binary files /dev/null and b/OmegaT/doc_src/en/images/OmT_Cyrillic.png differ
diff --git a/OmegaT/doc_src/en/images/OmT_Japanese.png b/OmegaT/doc_src/en/images/OmT_Japanese.png
new file mode 100644
index 0000000..b760d89
Binary files /dev/null and b/OmegaT/doc_src/en/images/OmT_Japanese.png differ
diff --git a/OmegaT/doc_src/en/images/OmegaT_icon.png b/OmegaT/doc_src/en/images/OmegaT_icon.png
new file mode 100644
index 0000000..5e8762b
Binary files /dev/null and b/OmegaT/doc_src/en/images/OmegaT_icon.png differ
diff --git a/OmegaT/doc_src/en/images/OmegaT_panes_25.png b/OmegaT/doc_src/en/images/OmegaT_panes_25.png
new file mode 100644
index 0000000..bfd04ce
Binary files /dev/null and b/OmegaT/doc_src/en/images/OmegaT_panes_25.png differ
diff --git a/OmegaT/doc_src/en/images/OmegaT_projects_and_subdirectories.png b/OmegaT/doc_src/en/images/OmegaT_projects_and_subdirectories.png
new file mode 100644
index 0000000..e277b5c
Binary files /dev/null and b/OmegaT/doc_src/en/images/OmegaT_projects_and_subdirectories.png differ
diff --git a/OmegaT/doc_src/en/images/Omegatproject.png b/OmegaT/doc_src/en/images/Omegatproject.png
new file mode 100644
index 0000000..2736898
Binary files /dev/null and b/OmegaT/doc_src/en/images/Omegatproject.png differ
diff --git a/OmegaT/doc_src/en/images/OptionsTabValidation_25.png b/OmegaT/doc_src/en/images/OptionsTabValidation_25.png
new file mode 100644
index 0000000..40c1429
Binary files /dev/null and b/OmegaT/doc_src/en/images/OptionsTabValidation_25.png differ
diff --git a/OmegaT/doc_src/en/images/RegexTester.png b/OmegaT/doc_src/en/images/RegexTester.png
new file mode 100644
index 0000000..bb44bdf
Binary files /dev/null and b/OmegaT/doc_src/en/images/RegexTester.png differ
diff --git a/OmegaT/doc_src/en/images/Restore.gif b/OmegaT/doc_src/en/images/Restore.gif
new file mode 100644
index 0000000..4099595
Binary files /dev/null and b/OmegaT/doc_src/en/images/Restore.gif differ
diff --git a/OmegaT/doc_src/en/images/SpellcheckerSetup_25.png b/OmegaT/doc_src/en/images/SpellcheckerSetup_25.png
new file mode 100644
index 0000000..355b613
Binary files /dev/null and b/OmegaT/doc_src/en/images/SpellcheckerSetup_25.png differ
diff --git a/OmegaT/doc_src/en/images/SpellcheckingText.png b/OmegaT/doc_src/en/images/SpellcheckingText.png
new file mode 100644
index 0000000..44f1648
Binary files /dev/null and b/OmegaT/doc_src/en/images/SpellcheckingText.png differ
diff --git a/OmegaT/doc_src/en/images/StatisticsWindow_25.png b/OmegaT/doc_src/en/images/StatisticsWindow_25.png
new file mode 100644
index 0000000..3012eca
Binary files /dev/null and b/OmegaT/doc_src/en/images/StatisticsWindow_25.png differ
diff --git a/OmegaT/doc_src/en/images/TagValidation.png b/OmegaT/doc_src/en/images/TagValidation.png
new file mode 100644
index 0000000..e109554
Binary files /dev/null and b/OmegaT/doc_src/en/images/TagValidation.png differ
diff --git a/OmegaT/doc_src/en/images/TagValidator.png b/OmegaT/doc_src/en/images/TagValidator.png
new file mode 100644
index 0000000..44f994e
Binary files /dev/null and b/OmegaT/doc_src/en/images/TagValidator.png differ
diff --git a/OmegaT/doc_src/en/images/TextSearch.png b/OmegaT/doc_src/en/images/TextSearch.png
new file mode 100644
index 0000000..428a4e9
Binary files /dev/null and b/OmegaT/doc_src/en/images/TextSearch.png differ
diff --git a/OmegaT/doc_src/en/images/Undock.gif b/OmegaT/doc_src/en/images/Undock.gif
new file mode 100644
index 0000000..6680e9c
Binary files /dev/null and b/OmegaT/doc_src/en/images/Undock.gif differ
diff --git a/OmegaT/doc_src/en/images/saveglossary.png b/OmegaT/doc_src/en/images/saveglossary.png
new file mode 100644
index 0000000..9923673
Binary files /dev/null and b/OmegaT/doc_src/en/images/saveglossary.png differ
diff --git a/OmegaT/doc_src/en/index.xml b/OmegaT/doc_src/en/index.xml
new file mode 100644
index 0000000..76ed4dc
--- /dev/null
+++ b/OmegaT/doc_src/en/index.xml
@@ -0,0 +1,11379 @@
+
+
+
+
+ OmegaT - User's Guide
+
+ vs
+ Vito
+Smolej
+
+
+
+
+
+ This document is the official user's guide to OmegaT, the free Computer Aided Translation tool. It also contains installation instructions.
+
+
+
+
+
+ About <application>OmegaT</application> - introduction
+
+
+ OmegaT highlights
+
+ OmegaT is a free multi platform Computer
+ Aided Translation tool, with the following highlights:
+
+
+
+ Translation
+ memory:OmegaT stores your
+ translations in a translation memory file. At the same time, it can
+ use memories files from previous translations for reference.
+ Translation memories can be very useful in a translation where there
+ are numerous repetitions or reasonably similar segments of text.
+ OmegaT uses translation memories to store your previous translations
+ and then suggest likely translations for the text you are currently
+ working on.
+
+ These translation memories can be very useful when a document
+ that has already been translated needs to be updated. Unchanged
+ sentences are automatically translated, while updated sentences are
+ shown with the translation of the most similar, older sentence.
+ Modifications to the original document are thus handled with greater
+ ease. If you are supplied with previously created translation memories
+ , for example by your translation agency or your client, OmegaT is
+ able to use these as reference memories.
+
+ OmegaT uses the standard tmx file format to store and access
+ translation memories, which guarantees that you can exchange your
+ translation material with other CAT applications supporting this file
+ format.
+
+
+
+
+
+ Terminology management:
+ Terminology management is important for translation consistency.
+ OmegaT uses glossaries containing translations of single words or
+ small phrases: a simplified bilingual dictionary for a specific
+ domain. For your reference, OmegaT displays the translation of any
+ words that happen to be present in the segment that currently has
+ focus.
+
+
+
+
+
+ Translation process: Imagine
+ having to translate something; from a single file to a folder
+ containing subfolders each with a number of files in a variety of
+ formats. When you let OmegaT know the files that you need to
+ translate, it looks for the files it understands based on file
+ filtering rules, recognizes the textual parts within them, splits up
+ the text groups according to the segmentation rules, and displays the
+ segments one by one so that you can proceed with the translation.
+ OmegaT stores your translations and proposes possible translations
+ from similar segments in previous memory files. When you are ready to
+ view the final product, you can export the translated files, open them
+ in the appropriate application and view the translation in the final
+ format...
+
+
+
+
+
+ Summary of chapters
+
+ This documentation is intended both as a tutorial and as a reference
+ guide. Here is a short summary of the chapters and their contents.
+
+
+
+ Instant start guide: this
+ chapter is intended as an Instant Start Guide for beginners and “tyre
+ kickers”, showing the complete procedure from opening a new
+ translation project through to completing the translation.
+
+
+
+
+
+ Installing and running OmegaT:
+ this chapter is useful when you first begin using OmegaT.
+ It contains the specific instructions on how to install OmegaT and run
+ it on Windows, Mac OS X and Linux. For advanced users, the chapter
+ describes the command line mode and its possibilities.
+
+
+
+
+
+ The user interface,Main Menu and Keyboard Shortcuts: these two
+ chapters are likely to be heavily consulted, since they explain the
+ user interface of OmegaT and the functions available via the main menu
+ and the keyboard shortcuts.
+
+
+
+
+
+ Project properties, OmegaT Files and
+ Directories: a project in the context of OmegaT is the
+ piece of work that OmegaT as a CAT tool is able to handle. This
+ chapter describes the project properties, such as the source and
+ target languages. The second of these chapters describes the various
+ subfolders and files in a translation project and their role as well
+ as other user and application files associated with OmegaT.
+
+
+
+
+
+ Editing field behavior: a short
+ chapter describing how to set up the editing behavior of the segment
+ being translated.
+
+
+
+
+
+ Working with plain text and
+ Working with formatted text: these
+ two chapters explain certain important points concerning texts to be
+ translated, such as the encoding set (in the case of plain text files)
+ and tag handling (in the case of formatted text).
+
+
+
+
+
+ Translation memories: explains
+ the role of the various subdirectories containing translation
+ memories, and provides information on other important aspects relating
+ to translation memories.
+
+
+
+ Segmentation:translation memory
+ tools work with textual units called segments. In OmegaT, segments can
+ be based on paragraphs or on segmentation rules. Paragraph
+ segmentation is less frequently used, but can be useful in cases of
+ so-called "creative" texts, The rule-based segmentation is usually
+ synonymous with sentence-based segmentation. A number of rule sets are
+ provided while additional rules can be defined by the user, as
+ described in this chapter.
+
+
+
+ Searches andRegular
+ expressions: Searches in OmegaT can be as simple as
+ "list segments with the word 'kangaroo'
+ ". They can also be complex, allowing for instance to
+ search for segments with two or more consecutive spaces. In this case
+ the regular expression ^s^s+ would be used to find and list the
+ offending segments. Regular expressions are also used extensively in
+ the segmentation rules.
+
+
+
+ Dictionaries, Glossaries,
+ Machine translation and Spellchecker: OmegaT enables the extensive of
+ dictionaries and glossaries. If an Internet connection is available,
+ various MT services such as Google Translate can be utilized from
+ within OmegaT. If spell checking is activated, spelling mistakes and
+ typos are recognized and can be corrected during translation.
+
+
+
+ Miscellanea: deals with other
+ issues of interest, such as how to avoid losing data.
+
+
+
+ Appendices contain the
+ following information
+
+
+
+ OmegaT on the web:
+ information regarding on-line OmegaT resources
+
+
+
+
+
+ Languages: contains the ISO
+ list of languages and language codes
+
+
+
+
+
+ Keyboard shortcuts in the
+ editor: the list of shortcuts used in the editor
+
+
+
+ Shortcuts
+ customization:shortcuts can be customized to suit your
+ personal preferences
+
+
+
+
+
+ Legal notices
+
+
+
+
+
+ Keyword index: an extensive
+ keyword index is provided to help the reader find the relevant
+ information.
+
+
+
+
+
+
+ Learn to use OmegaT in 5 minutes!
+
+
+ Set up a new project<indexterm class="singular">
+ <primary>Project</primary>
+
+ <secondary>Create / open new</secondary>
+ </indexterm>
+
+ Note:On an Apple Mac, use the Cmd
+ or Apple key instead of the Ctrl
+ key
+
+ To start using OmegaT, first create a project that will hold all
+ your files, such as your source file, translation memories, glossaries,
+ and eventually your translated file. In the Project
+ menu, select
+
+
+ New...
+
+ Menu Project
+
+ New...
+ type a name for your project. Remember where you create the
+ project, because you will later need to return to it.
+
+ After you give your project a name, the Create New Project dialog
+ will open. At the top of that dialog, select your source file's language
+ and the language that your translated file will be, and click
+ OK to continue
+
+ If you are interested in other settings of this dialog,
+ you can return to it any time by pressing
+ Ctrl+E.
+
+ Next, the Project Files dialog opens. Click the Import source
+ files... to select your source file. OmegaT will then copy the selected
+ file to the /source/subfolder of your newly created
+ project. After the source file has loaded in the Editor pane, you can
+ close the Project files dialog.
+
+
+
+ Translate the file
+
+ OmegaT will present one segment at a time for you to translate.
+ After you have translated each segment, press Ctrl+U to
+ move to the next untranslated segment. Whenever you want to see what your
+ translation will look like in its final format, press
+ Ctrl+D to generate the translated document, which will be
+ created in the /target/ subfolder of your project folder. During
+ translation, use the Edit and Go To
+ menus to perform various useful functions..
+
+
+
+ Validate your tags
+
+ If your source file is a formatted file, e.g. Microsoft Word,
+ LibreOffice Writer or HTML, OmegaT will convert the formatting into tags
+ that surround the text that you translate. Often documents will also have
+ tags that have nothing to do with formatting, but which are also
+ important.In the source file (and in the translated file), A source
+ sentence might look like
+
+
+
+
+
+
+
+
+
+
+
+ OmegaT, however, will present this sentence in the following
+ fashion:
+
+
+
+
+
+
+
+
+
+
+
+ The tags in OmegaT are greyed, so they are easy to recognise. They
+ are not protected, so that you can delete them, enter them by hand or move
+ them around in the target sentence. However, if you made mistakes when you
+ typed the formatting tags, your translated file might fail to open.
+ Therefore, press Ctrl+T before you generate your
+ translated file, to validate that your tags are correct.
+
+
+
+ Generate the translated file
+
+ Once you have made certain that there are no tag errors in your
+ translation, press Ctrl+D to generate the target file,
+ which will be created in the /target/subfolder of
+ your project folder.
+
+
+
+ Few more things to remember
+
+
+
+ If a file does not loads into the Editor pane, then it could be
+ that your source file is in a format that doesn't work in OmegaT. See
+ Chapter 7: File Filters in the User Manual for a list of file formats
+ that OmegaT can handle. If a file does not loads into the Editor pane,
+ then it could be that your source file is in a format that doesn't
+ work in OmegaT. See Chapter 7: File Filters in the User Manual for a
+ list of file formats that OmegaT can handle.
+
+
+
+
+
+ You can create a new project for each new job, and you can add
+ several source files to a project at a time.
+
+
+
+
+
+ To remind yourself of the project's initial settings, open the
+ Project Settings dialog by pressing Ctrl+E. To see a
+ list of files in the project, open the Project Files dialog by
+ pressing Ctrl+L..
+
+
+
+
+
+ At the end of your translation, OmegaT exports three translation
+ memories called "level1", "level2" and "omegat" to your project
+ folder. The "level1" and "level2" memories can be shared with users of
+ other translation programs. The memory named "omegat" can be used in
+ OmegaT itself, in future projects that you create. If you place
+ translation memory files in the /tm/ subfolder of your project folder,
+ OmegaT will automatically search them for similar segments, called
+ "fuzzy matches". .
+
+
+
+
+
+ You can create a glossary by pressing
+ Ctrl+Shift+G, or copy existing glossaries to
+ the/glossary/subfolder of your project folder,
+ and OmegaT will automatically look up words in them.
+
+
+
+
+
+ It is often useful to search for words and phrases in the source
+ text and in your translation, so press Ctrl+F for the
+ "Text Search" dialog at any time.
+
+
+
+
+
+ For a more comprehensive introduction see OmegaT
+ for beginners on the OmegaT web site. If you need assistance
+ with any aspect of OmegaT, feel free to join the OmegaT users
+ group.
+
+
+
+
+
+
+ Installing and running <application>OmegaT</application>
+
+
+ Windows Users<indexterm class="singular">
+ <primary>Installing OmegaT</primary>
+
+ <secondary>Windows</secondary>
+ </indexterm>
+
+
+ Downloading the
+ package
+
+ Do you have a Java implementation compatible with Oracle's Java
+ 1.5 JRE?
+
+
+
+ Yes: download
+ OmegaT_2.5.x_Windows_without_JRE.exe.
+
+
+
+ No / I don't know:
+ download OmegaT_2.5.x_Windows.exe.
+
+ This package is bundled with Oracle's Java Runtime
+ Environment. This JRE will not interfere with other Java
+ implementations that may already be installed on your system.
+
+
+
+
+
+ <application>Installing OmegaT</application>
+
+ To install OmegaT, double-click on the
+ program you have downloaded, and follow the instructions
+
+
+
+ Adding <application>OmegaT</application> to the start menu or
+ desktop<indexterm class="singular">
+ <primary>Customizing OmegaT</primary>
+
+ <secondary>Windows</secondary>
+ </indexterm>
+
+ During the installation, the setup program asks you whether you
+ wish to create a folder in the start menu, and
+ whether you wish to create a shortcut on the desktop and in the quick
+ launch bar.
+
+ You can still create a shortcut later by dragging
+ OmegaT.exe to the
+ desktop or start menu to link it from there.
+
+
+
+ Running <application>OmegaT<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Windows</secondary>
+ </indexterm></application>
+
+ Once OmegaT is installed, you can click
+ on OmegaT.jar to launch
+ it directly or you can launch it directly from the command line.
+
+ The simplest way to launch OmegaT, however, is to execute
+ theOmegaT.exe program.
+
+ Running OmegaT
+
+ Windows
+
+ INI file
+ The options for the program start-up in this case will be
+ read from the OmegaT.l4J.ini
+ file, which resides in the same folder as the exe file and
+ which you can edit to reflect your setup. The following example for the
+ INI file reserves 1GB of memory, requests French as the user language
+ and Canada as the country:
+
+ # OmegaT.exe runtime configuration
+# To use a parameter, remove the '#' before the '-'
+# Memory
+-Xmx1024M
+# Language
+-Duser.language=FR
+# Country
+-Duser.country=CA
+
+
+
+ Upgrading OmegaT <indexterm class="singular">
+ <primary>Upgrading OmegaT</primary>
+
+ <secondary>Windows</secondary>
+ </indexterm>
+
+ This information applies only to the "Traditional"
+ Windows versions of OmegaT. It does not apply to the Web Start versions,
+ which are upgraded automatically, nor to cross-platform versions
+ installed on Windows.
+
+ If you already have a version of OmegaT installed on your PC and
+ wish to upgrade to a more recent version, you have two options:
+
+
+
+ Install over the existing installation.
+ To do this, simply select the same installation folder as
+ the existing installation when installing the new version. The "old"
+ version of OmegaT will be overwritten, but any settings from it will
+ be retained. This includes preferences set from within OmegaT, any
+ changes you have made to your OmegaT.l4J.ini
+ file, and also your launch script (.bat file), if you are using
+ one.
+
+
+
+ With this method, you may also download the "Windows without JRE"
+ version, since the new installation will use your existing JRE.
+
+
+
+ Install to a new folder. This
+ will enable you to keep both versions side-by-side, which you may
+ wish to do until you feel comfortable with the new version. This
+ method will also use preferences and settings you have made from
+ within OmegaT. In this case, however:
+
+
+
+ If you have made changes to your OmegaT.l4J.ini
+ file and/or are using a .bat file, you must copy
+ these over.
+
+
+
+
+
+ If your existing OmegaT installation is a "Windows with
+ JRE" version, the new version must also be a "Windows with JRE"
+ version.
+
+
+
+
+
+
+
+
+ Linux (Intel) Users<indexterm class="singular">
+ <primary>Installing OmegaT</primary>
+
+ <secondary>Linux</secondary>
+ </indexterm>
+
+
+ Downloading the right package
+
+ Do you have a Java implementation compatible with Oracle's Java
+ 1.5 JRE?
+
+
+
+ Yes: download
+ OmegaT_2.5.x_Without_JRE.zip.
+
+
+
+ No / I don't know: download
+ OmegaT_2.5.x_Linux.tar.bz2.
+
+ This package is bundled with Oracle's Java Runtime
+ Environment. This JRE will not interfere with other Java
+ implementations that may already be installed on your system.
+
+
+
+
+
+ <application>Installing OmegaT</application>
+
+ Unpack/untar the downloaded file. This will create an omegat/
+ folder in the working folder in which you will find all the files needed
+ to run OmegaT. To untar the
+ .tar.gz file:
+
+ $ tar xf downloaded_file.tar.gz
+
+
+
+ Adding <application>OmegaT</application> to your menus (KDE) or
+ panels (Gnome)
+
+
+ KDE 4 Users<indexterm class="singular">
+ <primary>Customizing OmegaT</primary>
+
+ <secondary>KDE 4</secondary>
+ </indexterm>
+
+ You can add OmegaT to your menus as
+ follows:
+
+
+
+ Press Alt+F2
+ to show KRunner. Type
+ kmenuedit+enter to run the command. The
+ KMenuEditor appears. In KMenuEditor select File ->
+ New Item.
+
+
+
+ Then, after selecting a suitable menu, add a submenu/item
+ with File - New Submenu and File -
+ New Item. Enter OmegaT as
+ the name of the new item.
+
+
+
+ In the "Command" field, use the navigation button to find
+ your OmegaT launch script (the file
+ named OmegaT in the unpacked folder),
+ and select it.
+
+
+
+ Click on the icon button (to the right of the
+ Name/Description/Comment fields)
+
+
+
+ Other Icons - Browse, and navigate to the /images subfolder
+ in the OmegaT application folder.
+ Select the OmegaT.png icon.
+
+
+
+ Finally, save the changes with File -
+ Save.
+
+
+
+
+
+ GNOME Users<indexterm class="singular">
+ <primary>Customizing OmegaT</primary>
+
+ <secondary>GNOME</secondary>
+ </indexterm>
+
+ You can add OmegaT to your menus as
+ follows:
+
+
+
+ Right-click on the panel - Add New
+ Launcher.
+
+
+
+ Enter "OmegaT" in the "Name"
+ field; in the "Command" field, use the navigation button to find
+ your OmegaT launch script (the file
+ named OmegaT in the unpacked folder).
+ Select it and confirm with OK.
+
+
+
+ Click on the icon button, then hit
+ Browse... and navigate to the /images
+ subfolder in the OmegaT application
+ folder. Select the
+ OmegaT.png icon.
+ GNOME may fail to display the icon files in the available formats
+ and initially appear to expect an SVG file, but if the folder is
+ selected, the files should appear and
+ OmegaT.png can be selected.
+
+
+
+
+
+
+ Running <application>OmegaT<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Linux</secondary>
+ </indexterm></application>
+
+ You can launch OmegaT from the command line with a script that
+ includes start-up options or you can click on
+ OmegaT.jar to launch it
+ directly. Methods differ depending on the distribution. Make sure that
+ your PATH settings are correct and that
+ .jar files are properly associated with a Java
+ launcher. Check "Command line launching" below for more
+ information.
+
+
+
+
+ Mac OS X Users<indexterm class="singular">
+ <primary>OS X</primary>
+
+ <secondary>Installing OmegaT</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Installing OmegaT</primary>
+
+ <secondary>OS X</secondary>
+ </indexterm>
+
+
+ Downloading the package
+
+ OmegaT 2.5 requires Java 1.5 to run.
+ Use "Software Update..." from the Apple menu to update your Java
+ version.
+
+ Download OmegaT_2.5.x_Mac.zip.
+
+
+
+ <application>Installing OmegaT </application>
+
+ Double click on OmegaT_2.5.x_Mac.zip to
+ unpack it. This creates a folder called
+ OmegaT. The folder contains 2
+ files: index.html and
+ OmegaT.app. Copy the
+ folder to a suitable folder (e.g. Applications). Once you have done
+ this, you can delete the OmegaT_2.5.x_Mac.zip file,
+ it is no longer needed.
+
+
+
+ Adding <application>OmegaT</application> to the Dock<indexterm class="singular">
+ <primary>OS X</primary>
+
+ <secondary>Adding OmegaT to the Dock</secondary>
+
+ <seealso>Customizing OmegaT</seealso>
+ </indexterm>
+
+ Drag and drop
+ OmegaT.app onto the
+ Dock.
+
+
+
+ Running <application>OmegaT<indexterm class="singular">
+ <primary>OS X</primary>
+
+ <secondary>Running OmegaT</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>OS X</secondary>
+ </indexterm></application>
+
+ Double-click on
+ OmegaT.app or click on its
+ location in the Dock.
+
+ To access
+ Info.plist, right-click
+ on OmegaT.app and select
+ "Show Package Contents", then open the file by right-clicking on it and
+ selecting your text editor of choice. You can also "cd" there directly
+ from the command line and open
+ Info.plist in a command line editor
+ like emacs or vi.
+ OS X
+
+ Customizing OmegaT
+
+ Launch parameters
+
+ OS X
+
+ Customizing OmegaT
+
+
+ You can modify the Properties as well as the
+ VMOptions part.
+
+ If you wish to add values to VMOptions, put a
+ space between them. For example, -Xmx1024M
+ -Duser.language=ja will launch
+ OmegaT with 1024MB of memory and with the
+ user interface in Japanese.
+
+ To launch multiple instances of
+ OmegaT.app, double-click
+ the file JavaApplicationStub located in
+ OmegaT.app/
+ Contents/MacOS/.
+
+ Use
+ OmegaT.jar file located
+ in
+ OmegaT.app/Contents/Resources/Java/
+ to launch OmegaT from the command line. Check
+ "Command line launching" below for more information.
+
+
+
+ Mac OS X goodies
+
+ OmegaT.app can be
+ accessed from the Mac OS X Services. You can thus select a word anywhere
+ in OmegaT and use Services to check this
+ word, for instance in Spotlight or in Google. You can also use
+ AppleScript or Automator to create Services or scripts that will
+ automate frequent actions
+
+
+
+
+ Other Systems<indexterm class="singular">
+ <primary>Installing OmegaT</primary>
+
+ <secondary>Other systems</secondary>
+ </indexterm>
+
+ This information applies to systems such as Solaris SPARC/x86/x64,
+ Linux x64/PowerPC, Windows x64
+
+
+ Downloading the right
+ package
+
+ OmegaT is available bundled with a
+ Oracle Java JRE for Linux (Intel x86) and Windows platforms. Users of
+ other platforms (Linux PowerPC, Linux x64, Solaris SPARC/x86/x64,
+ Windows x64 etc) must have a running compatible Java JRE on their system
+ to be able to use OmegaT.
+
+ Do you have a Java implementation compatible with Oracle's Java
+ 1.5 JRE?
+
+
+
+ Yes: download
+ OmegaT_2.5.x_Windows_without_JRE.zip. This
+ package can be used on any platform where a Java 1.5 JRE compatible
+ JRE is installed.
+
+
+
+ I don't know: open a terminal
+ and type "java -version". If a "command not found" or similar
+ message is returned, it is likely that Java is not installed on your
+ system
+
+
+
+ No: obtain a Java JRE for
+ your system (see below) and download
+ OmegaT_2.5.x_Without_JRE.zip.
+
+ Oracle provides JREs for Solaris SPARC/x86 (Java 1.5) and for
+ Linux x64, Solaris x64, Windows x64 (Java 1.5) at http://www.oracle.com/technetwork/java/archive-139210.html
+
+ IBM provides JREs for Linux PowerPC at http://www.ibm.com/developerworks/java/jdk/linux/download.htm
+
+ Follow the installation instructions of the package you
+ need.
+
+
+
+
+
+ <application>Installing OmegaT</application><indexterm class="singular">
+ <primary>Installing OmegaT</primary>
+
+ <secondary>Other systems</secondary>
+ </indexterm>
+
+ To install OmegaT, simply unpack the
+ OmegaT_2.5.x_Without_JRE.zip file. This
+ creates an ./OmegaT_2.5.x_Without_JRE/ directory in
+ the working folder with all the files necessary to run
+ OmegaT.
+
+
+
+ Installing convenient shortcuts
+
+ Follow your system's instructions to install
+ OmegaT shortcuts in convenient places of your
+ choosing.
+
+
+
+ Running <application>OmegaT<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Other systems</secondary>
+ </indexterm></application>
+
+ Once OmegaT is installed, you can
+ launch it directly from the command line, you can create a script that
+ includes launch parameters for the command line or you can click on
+ OmegaT.jar to launch it
+ directly. Methods differ depending on the distribution. Make sure that
+ your PATH settings are correct and that
+ .jar files are properly associated with a Java
+ launcher. Check "Command line launching" below for more
+ information.
+
+
+
+
+ Using Java Web Start<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Using Java Web Start</secondary>
+ </indexterm>
+
+ Java Web Start technology (part of Java 1.5 and above) can be used
+ to deploy standalone Java software applications with a single click over
+ the network. Java Web Start ensures that the latest version of the
+ application will be deployed, as well as the correct version of the Java
+ Runtime Environment (JRE) used. To start OmegaT for the first time with
+ Java Web Start, load the following URL in your browser:
+
+ http://omegat.sourceforge.net/webstart/OmegaT.jnlp
+
+ Download the file
+ OmegaT.jnlp and then click on it.
+ During the installation, depending on your operating system, you may
+ receive several security warnings. The permissions you give to this
+ version (which may appear as "unrestricted access to the computer") are
+ identical to the permissions you give to the local version, i.e., they
+ allow access to the hard drive of the computer. Subsequent clicks on
+ OmegaT.jnlp will check for
+ any upgrades, install them, if there are any, and then start
+ OmegaT. After the initial installation you can,
+ of course, also use
+ OmegaT.jnlp also when you
+ are offline.
+
+ Privacy:
+ OmegaT Java Web Start does not save any of your
+ information beyond the computer on which you are running it. The
+ application runs on your machine only. Your documents and translation
+ memories remain on your computer, and the
+ OmegaT project will have no access to your work
+ or information.
+
+ Note that if you need or wish to use any of the launch command
+ arguments (see above), you must use the normal installation.
+
+
+
+ Starting OmegaT from the command line<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Command line launching</secondary>
+ </indexterm>
+
+ Normally, it is not necessary to start
+ OmegaT from the command line. However, the
+ command-line alternative allows the user to control and modify the
+ program's behavior. There are two ways of launching
+ OmegaT using the command line.
+
+
+ Opening a command line window
+
+ A command line window is also referred to as a "terminal window".
+ On Windows it is called an "MS-DOS window" and is available from the
+ Start Menu, inside Programs, through the "MS-DOS" item. The Mac OS X
+ equivalent is the application Terminal located in Applications →
+ Utilities.
+
+ To launch OmegaT, you must normally
+ type two commands. The first of these is:
+
+ cd {folder}
+
+ where {folder} is the name of the folder,
+ with complete path, in which your OmegaT
+ program - specifically, the file
+ OmegaT.jar - is located.
+ In practice, this command will therefore be something like this:
+
+ On Windows
+
+ cd C:\Program
+ Files\OmegaT
+
+ On Mac OS X
+
+ cd <OmegaT.app
+ location>/OmegaT.app/Contents/Resources/Java/
+
+
+ On Linux
+
+ cd /usr/local/omegat
+
+ This command changes the folder to the folder containing the
+ executable OmegaT file. The second command is
+ the command which actually launches OmegaT.
+ In its most basic form, this command is:
+
+ java -jar
+ OmegaT.jar
+
+ Pay attention to the capitalization - the program will not start,
+ if you enter omegat instead of OmegaT
+ !
+
+ This method has a particular benefit of being suitable for finding
+ causes of problems: if an error occurs during use of the program, an
+ error message is output in the terminal window which may contain useful
+ information on the cause of the error.
+
+ The above method somewhat impractical way of launching a program
+ routinely. For this reason, the two commands described above are
+ contained in a file (a "script", also called a ".bat file" on Windows
+ systems).
+
+ When this file is executed, the commands within it are
+ automatically carried out. Consequently, to make changes to the launch
+ command, it is sufficient to modify the file.
+
+
+
+ Launch command arguments<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Launch script arguments</secondary>
+ </indexterm>
+
+ The basic command has already been mentioned above. Changes to
+ this command involve the addition of "arguments" to it. Arguments are
+ added after the initial "java", and before the
+ "-jar OmegaT.jar". Note
+ that in Windows you can change the
+ OmegaT.l4J.ini file to
+ reflect your preferences. On Mac OS X, you can change the
+ Info.plist located in
+ OmegaT.app/Contents/ to
+ do the same.
+
+ A list of possible arguments is given below. Advanced users can
+ obtain more information on the arguments by typing man
+ java in the terminal window.
+
+
+
+ User interface language
+
+
+ -Duser.language=XX
+ Running OmegaT
+
+ Launch script arguments
+
+ User.language
+ Normally, i.e. when OmegaT
+ is launched without any arguments, the program first detects the
+ language of the user's operating system. If a user interface in this
+ language is available, OmegaT uses it.
+ So, if the user's operating system is Russian and
+ OmegaT has been localized in Russian,
+ OmegaT is displayed with a Russian user
+ interface, Russian menus, etc. If the language of the user's system
+ is not available, OmegaT defaults to
+ English. This is the standard behavior.
+
+ The "-Duser.language=XX" argument causes
+ OmegaT to use the language specified
+ rather than the language of the user's operating system. "XX" in the
+ command stands for the two-digit code of the desired language. To
+ launch OmegaT with a French interface
+ (for example on a Russian operating system), the command would
+ therefore be:
+
+ java -Duser.language=fr -jar
+ OmegaT.jar
+
+
+
+
+
+ User country setup
+
+ -Duser.country=XX
+ Running OmegaT
+
+ Launch script arguments
+
+ User.country
+ Besides the language, you can also specify the
+ country, for example CN or TW in case of the Chinese language. To
+ display the instant start guide in the desired language, you need to
+ specify both the language and the country. This is necessary even if
+ there's only one combination available, like pt_BR in case of
+ Portuguese / Brazil.
+
+
+
+
+
+ Font antialiasing - (Java 1.5
+ only)
+
+ -Dswing.aatext=true
+ Running OmegaT
+
+ Launch script arguments
+
+ Font antialiasing
+ This argument effects anti-aliasing of the
+ fonts, thereby improving their appearance.
+
+
+
+ Memory assignment
+
+ -XmxZZM
+ Running OmegaT
+
+ Launch script arguments
+
+ Memory assignment
+ This command assigns more memory to
+ OmegaT. By default, 512 MB are assigned,
+ so there is no advantage in assigning less than this figure. "ZZ"
+ stands for the amount of memory assigned, in megabytes. The command
+ to launch OmegaT with assignment of 1024
+ MB (1 gigabyte) of memory is therefore:
+
+ java -Xmx1024M -jar
+ OmegaT.jar
+
+
+
+ Proxy host IP address
+
+ -Dhttp.proxyHost=nnn.nnn.nnn.nnn
+ Running OmegaT
+
+ Launch script arguments
+
+ Proxy server IP address
+ The IP address of your proxy server, if
+ your system uses a proxy.
+
+
+
+ Proxy Server Port
+ Number
+
+ -Dhttp.proxyPort=NNNN
+
+ Running OmegaT
+
+ Launch script arguments
+
+ Proxy server - Port Number
+ The port number your system uses to access the proxy
+ server.
+
+
+
+ Google Translate V2
+
+ -Dgoogle.api.key=A123456789B123456789C123456789D12345678
+
+ Running OmegaT
+
+ Launch script arguments
+
+ Google Translate V2
+ If you have signed up for the Google
+ Translate services, enter your private Google API key here. Note
+ that the key is 38 characters long.
+
+
+
+ Arguments can be combined: to launch
+ OmegaT with all the examples described above,
+ the command would be:
+
+ java -Dswing.aatext=true -Duser.language=pt
+ -Duser.country=BR -Xmx1024M -DDhttp.proxyHost=192.168.1.1
+ -Dhttp.proxyport=3128 -jar
+ -OmegaT.jar
+
+
+
+ OmegaT in the command line mode<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Command line mode</secondary>
+ </indexterm>
+
+ The purpose of the console mode is to use OmegaT as a translation
+ tool in a scripting environment. When started in console mode, no GUI is
+ loaded (so it will work on any console) and the given project is
+ automatically processed as requested.
+
+
+ Prerequisites
+
+ To run OmegaT in the command line
+ mode, a valid OmegaT project must be
+ present. The location does not matter, since you have to add it to the
+ command line at the start-up anyway.
+
+ If you need altered settings, the configuration files must be
+ available. This can be achieved in two ways:
+
+
+
+ Run OmegaT normally (with the
+ GUI) and specify the settings. If you start
+ OmegaT in console mode, it will use the
+ same settings.
+
+
+
+ If you can't run OmegaT normally
+ (no graphical environment available): copy the settings files from
+ some other OmegaT installation on
+ another machine to a specific directory. The location does not
+ matter, since you can add it to the command line at startup. The
+ relevant files are filters.conf and
+ segmentation.conf and can be found in the user
+ home directory (e.g. C:\Documents and
+ Settings\%User%\OmegaT under
+ Windows, %user%/.omegat/ under Linux)
+
+
+
+
+
+ Starting in console mode
+
+ To start OmegaT in console mode, some
+ extra parameters have to be passed to it on startup. The most
+ important is <project-dir>, and
+ optionally --config-dir=<config-dir>.
+ Example:
+
+ java -jar OmegaT.jar
+ /path/to/project \
+
+ --config-dir=/path/to/config-files/ \
+
+
+ --mode=console-translate|console-createpseudotranslatetmx|console-align
+
+ --source-pattern={regexp}
+
+ Note that all parameters start with a double - character.
+
+ Explanation:
+
+
+
+ <project-dir> tells
+ OmegaT where to find the project to
+ translate. If given, OmegaT starts in
+ console mode and will translate the given project.
+
+
+
+
+
+ --config-dir=<config-dir> tells
+ OmegaT in which directory the
+ configuration files are stored. If not given,
+ OmegaT reverts to default values
+ (OmegaT dir under user home, or if not
+ available, the current working directory). Note double -
+ character
+
+
+
+
+
+ --mode=...-
+ OmegaT starts in console mode to
+ perform one of the following services automatically
+
+
+
+ --mode=console-translate
+
+ In this mode, OmegaT will attempt to translate the files
+ in /source/ with the available translation memories. This is
+ useful to run OmegaT on a server with TMX files automatically
+ fed to a project.
+
+
+
+ --mode=console-createpseudotranslatetmx
+
+ In this mode OmegaT will create a TMX for the whole
+ project, based on the source files only. You specify the TMX
+ file to be created with
+
+ --pseudotranslatetmx=allsegments.tmx
+ --pseudotranslatetype=[equal|empty]
+
+ The argument pseudotranslatetype
+ specifies, whether the target segments are to be equal to the
+ source, or left empty.
+
+
+
+ --mode=console-align
+
+ In this mode, OmegaT will align the Java properties
+ files found in the /source/ folder of the
+ project to the contents found at the specified location. The
+ resulting TMX is stored in the /omegat/
+ folder under the name align.tmx.
+
+ Additional parameter is required in this case,
+ specifying the location of the target data:
+
+ --alignDir={location of translated
+ files}
+
+ alignDir must contain a translation
+ in the target language of the project. For instance, if the
+ project is EN->FR, alignDir must contain a bundle ending
+ with _fr. The resulting tmx is stored in the
+ omegat folder under the name
+ align.tmx.
+
+
+
+
+
+ --source-pattern={regexp}
+
+ When mode has been used, this option will specify the files
+ to be processed automatically.. If the parameter is not specified,
+ all files will be processed. Here's few typical examples to limit
+ your choice:
+
+
+
+ .*\.html
+
+ All HTML files will be translated - note that the period
+ in the usual *.html has to be escaped (\.) as specified by the
+ rules for regular expressions
+
+
+
+ test\.html
+
+ Only the file test.html at the root of the source
+ directory will be translated. If there are other files named
+ test.html in other directories, they will be ignored.
+
+
+
+ dir-10\\test\.html
+
+ Only the file test.html in the directory dir-10 will be
+ processed. Again note that the backslash is escaped as
+ well.
+
+
+
+
+
+ --output-tag-validation-={regexp}
+
+ When mode has been used, this option will specify the files
+ to be processed automatically.. If the parameter is not specified,
+ all files will be processed. Here's few typical examples to limit
+ your choice:
+
+
+
+ .*\.html
+
+ All HTML files will be translated - note that the period
+ in the usual *.html has to be escaped (\.) as specified by the
+ rules for regular expressions
+
+
+
+ test\.html
+
+ Only the file test.html at the root of the source
+ directory will be translated. If there are other files named
+ test.html in other directories, they will be ignored.
+
+
+
+ dir-10\\test\.html
+
+ Only the file test.html in the directory dir-10 will be
+ processed. Again note that the backslash is escaped as
+ well.
+
+
+
+
+
+
+
+ Quiet option
+
+ An extra command line parameter specific to console mode:
+ --quiet. In the quiet mode, less info is logged to
+ the screen. The messages you would usually find in the status bar are
+ not displayed.
+
+ Usage: java -jar OmegaT.jar
+ /path/to/project --mode=console-translate --quiet
+
+
+
+ Tag validation option
+
+ Another extra command line parameter specific to console mode:
+ --tag-validation=[abort|warn]. When this parameter
+ is added, tag validation is done prior to translation/aligning. If the
+ value is abort, then on tag errors the errors are
+ printed and the program stops. If the value is warn
+ then the errors are printed but OmegaT continues.
+
+ Usage: java -jar OmegaT.jar
+ /path/to/project --mode=console-translate
+ --tag-validation=abort
+
+
+
+
+
+ Building <application>OmegaT</application> From Source<indexterm class="singular">
+ <primary>Running OmegaT</primary>
+
+ <secondary>Building OmegaT from source</secondary>
+ </indexterm>
+
+ Note that you will need the ant program
+ (http://ant.apache.org/bindownload.cgi) to build your
+ own version of OmegaT. Unpack the
+ OmegaT_2.5.x_Source.zip file and enter the
+ OmegaT_2.5.x_Source directory or enter the ./omegat/
+ directory of the SVN checked out code. Please make sure that a build.xml
+ file is present in that folder. Then, on the command line, type:
+
+ $ ant jar release
+
+ This will create a full distribution of
+ OmegaT in the ./dist/ folder, where you will
+ find all the files necessary to run
+ OmegaT.
+
+
+
+
+ The user interface
+
+
+ User interface items
+
+
+ Frequently used windows<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+ </indexterm>
+
+
+
+ OmegaT main window
+
+
+ contains the main menu, status bar and several panes:
+
+
+
+ Editor - where you type and edit the translation
+
+
+
+ Match Viewer - displays the most similar segments from
+ translation memories
+
+
+
+ Glossary Viewer - displays terminology
+
+
+
+ Dictionary Viewer - displays information provided by
+ dictionaries
+
+
+
+ Machine Translation - displays the translation, provided
+ by MT services, like Google Translate
+
+
+
+ Multiple Translations - shows translation alternatives -
+ if any entered - for the current segment
+
+
+
+ Notes viewer - notes by the translator, regarding the
+ current segment
+
+
+
+ Comments - comments by the translator, regarding the
+ current segment
+
+
+
+
+
+
+
+ Shortcuts
+
+ Ctrl+L - Project files window
+ Project Files window
+
+
+ The list of your translatable files (open with
+ Ctrl
+
+ L
+ , close with Esc)
+
+
+
+
+
+ Shortcuts
+
+ Ctrl+F - Search window
+ Search window
+
+
+ Used to search for specific segments in the project (open
+ with
+ Ctrl
+
+ F
+ , close with Esc)
+
+
+
+
+
+
+ Less frequently used
+
+
+
+
+ Shortcuts
+
+ Ctrl+T - Tag validation window
+ Tag Validation window
+
+
+ Used to check for tag mistakes in translations (open with
+
+ Ctrl
+
+ T
+ close with Esc)
+
+
+
+
+
+ Shortcuts
+
+ F1 - Help
+ Help browser
+
+
+ Used to read the user manual (open with F1,
+ close with Esc)
+
+
+
+
+ Statistics window
+
+
+ Used to open the window with the statistics of the project,
+ display it, using
+
+ Menu Tools
+
+ statistics
+ Tools
+
+ Statistics.
+
+
+
+
+
+ Match statistics window
+
+
+ Used to display the match statistics of the project, select
+
+
+ Menu Tools
+
+ Match statistics
+ Tools
+
+ Match statistics
+ to open it.
+
+
+
+
+
+
+ Project settings dialogs <indexterm class="singular">
+ <primary>Project</primary>
+
+ <secondary>Project Settings</secondary>
+ </indexterm>
+
+ The dialogs below are used to change OmegaT project settings. Each
+ is described in detail in a separate section; the information below
+ summarizes their use and how they are invoked:
+
+
+
+
+ Shortcuts
+
+ Ctrl+E - Project properties
+
+ Menu Project
+
+ Properties
+ Project Properties
+
+
+ Used to modify the project folders and languages, (access
+ via
+
+
+ Ctrl
+
+ E
+
+
+
+ Project
+
+ properties...
+ , close via Esc)
+
+
+
+
+
+ Project Settings
+
+ Font
+ Font
+ Menu Options
+
+ Font
+
+
+
+ Used to modify the font used by
+ OmegaT to display source, translation, matches and
+ glossary terms, (access via
+ Options
+
+ Font...
+ , close via
+ Esc)
+
+
+
+
+
+ Project Settings
+
+ File filters
+ File filters
+ Menu Options
+
+ File filters
+
+
+
+ Used to adjust the handling of supported file formats
+ (access via
+ Options
+
+ File Filters...
+ , close via Esc)
+
+
+
+
+
+ Project Settings
+
+ Segmentation
+ Segmentation
+ Menu Options
+
+ Segmentation
+
+
+
+ Used to change the way your text is segmented into sentences
+ (access via
+ Options
+
+ Segmentation
+ , close via Esc)
+
+
+
+
+
+ Project Settings
+
+ Editing Behavior
+ Editing Behavior
+ Menu Options
+
+ Editing Behavior
+
+
+
+ Used to change how OmegaT behaves
+ when you iterate between the segments (access via
+ Options
+
+ Behavior...
+ , close via Esc)
+
+
+
+
+
+
+
+ <application>OmegaT</application> main window<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Main window</secondary>
+
+ <tertiary>- figure</tertiary>
+ </indexterm><indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Main window</secondary>
+ </indexterm>
+
+
+ OmegaT panes
+
+
+
+
+
+
+
+
+
+
+
+
+ The main window consists of several panes, the main menu and a
+ status bar. You can change the position of any pane or even undock it to a
+ separate window by clicking and dragging the pane by its name. Depending
+ on the pane status, different signs can appear at its top right
+ corner:
+
+
+ Pane widgets<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Pane widgets</secondary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ minimizes the pane, so that only its name is shown at the
+ bottom of the window.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ maximizes the pane
+
+
+
+
+
+
+
+
+
+
+
+
+
+ undocks the pane from the main window.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ puts the pane back within the main window.
+
+
+
+
+
+ You can overlap panes if desired. When this is done the panes
+ display a tab at the top. The separators between the panes can be dragged
+ to resize panes. Should you lose track of your changes to the user
+ interface, you can use
+ OmegaT windows
+
+ Windows and panes in OmegaT
+
+ OmegaT windows
+
+ Restoring to factory setup
+ Options → Restore the main window any time to
+ return to the original layout.
+
+ The counters in the lower right corner keep track of the progress of
+ the translation (numbers in the left hand column refer to the figure
+ above):
+
+
+ Main Window - counters<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Counters</secondary>
+ </indexterm>
+
+
+
+
+
+
+ 33/33
+
+ number of segments - translated vs total for the current
+ file
+
+
+
+ 2780/2780
+
+ number of unique segments - translated vs total in the
+ project
+
+
+
+ 3760
+
+ total number of segments (including repeats) in the
+ project
+
+
+
+ 126/127
+
+ number of source and target characters in the current
+ segment
+
+
+
+
+
+ From a practical point of view, the most important pair of numbers
+ is the second pair: it tells, how much you have done so far, in relation
+ to the total or second number. The project in the example is evidently
+ finished, as all the unique segments have been translated.
+
+
+ Editor pane<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Editor pane</secondary>
+ </indexterm>
+
+ This is where you type and edit your translation. The Editor pane
+ displays the text of the partially translated document: the text already
+ translated is displayed in translation while the untranslated text is
+ displayed in the original language. The displayed text is split into
+ segments and you may scroll through the document and double-click on any
+ segment to open and edit it. In the above case, the segments already
+ translated are shown in yellow, but this may be changed to suit your
+ preferences (see ).
+
+ One of the above segments is the current segment. It is the
+ segment that is displayed in two parts. The upper part is in the source
+ language, in bold characters with a green background color, the lower
+ part is the editing field, ended by a marker:
+ Segment marker
+ the marker is <segment nnnn>
+ where nnnn is a number of the segment in the project. Use the upper part
+ as a reference and replace or modify the contents of the editing field
+ with your translation.
+
+ Depending upon the preferred editing behavior, the editing field
+ for the untranslated segment may be empty, contain the source text, or
+ contain the translation of the string most similar to the one to be
+ translated. When you move to another segment, the translation is
+ validated and stored. If you want the translation to be the same as the
+ source, simply make the editing field empty by removing all the text
+ (select all with Ctrl+A and delete with
+ Del). OmegaT is able to store translations that are
+ identical to the source. This is useful for documents that contain trade
+ marks, names or other proper nouns, or parts in a third language that do
+ not require translation. See Translation editing
+ for more details.
+
+ If you right click on the Editor pane, a pop-up menu opens,
+ offering Cut, Copy, Paste (i.e. same
+ functions as
+ Ctrl
+
+ X
+ ,
+ Ctrl
+
+ C
+ and
+ Ctrl
+
+ V
+ ) and the GoTo segment
+ functions.
+
+
+
+ Fuzzy matches pane<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Fuzzy matches pane</secondary>
+ </indexterm>
+
+
+ <indexterm class="singular">
+ <primary>Matches</primary>
+
+ <secondary>Matches pane - figure</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Matches pane - figure</secondary>
+ </indexterm>Matches pane
+
+
+
+
+
+
+
+
+
+
+
+
+ The match viewer shows the most similar segments from translation
+ memories, both from internal project translation memory created in real
+ time as you translate your project and from ancillary translation
+ memories you have imported from your earlier jobs, or received from your
+ client or translation agency.
+
+ When you move to the next segment, the first fuzzy match (the one
+ with the best matching percentage) is automatically selected. You may
+ select a different match by pressing Ctrl+2, 3, 4, or
+ 5.
+ Shortcuts
+
+ Ctrl+N - Selecting the match
+ Of course, pressing
+ Ctrl
+
+ 5
+ will have no effect, if there is no match #5. To use the
+ selected match in your translation, use
+ Ctrl+R
+ Shortcuts
+
+ Ctrl+R - Replace text
+ to replace the target field with the match or use
+ Ctrl+I
+ Shortcuts
+
+ Ctrl+I - Insert text
+ to insert it at the cursor position.
+
+ The matching percentage is roughly equivalent to taking the number
+ of common words in the matched and the matching segment and dividing by
+ the number of words in the longer of the two. The selected fuzzy match
+ is highlighted in bold, words that are missing in the segment you are
+ translating are colored blue and words adjacent to the missing parts
+ green. In the above example the source segment is Context menu command. The top match is 100%,
+ because all words match. So do the next two matches, and the match #4 is
+ similar, but different. The line with the matching percentage also
+ includes the name of the translation memory
+ Translation memories
+
+ Matches
+ containing the match. If there's no file name displayed,
+ the source is the internal project translation memory. Orphan
+ segments
+ Translation memories
+
+ Orphan segments
+ (the match #2) describe segments in the default project
+ translation memory that have no corresponding source segment.
+
+ There are actually three match estimates available (66/66/30 in
+ the case of the match #4 above). They are defined as follows:
+
+
+
+ match percentage when the tokenizer plugin is used
+
+
+
+
+
+ default OmegaT match - number of matched words - with numerals
+ and tags ignored - divided by the total word count
+
+
+
+
+
+ OmegaT match, including numbers, tags
+
+
+
+
+
+ Glossary pane<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Glossary pane</secondary>
+ </indexterm>
+
+ The Glossary pane allows you to access your own collection of
+ expressions and specialist terminology which you have built up in your
+ glossary files. It shows translation of terms found in the current
+ segment. The source segment in the example below was “Context
+ menu command”, as in the Fuzzy Matches example above, and the
+ terms shown were found in the glossaries, available (Microsoft's Term
+ collection and Slovenian Linux User group Glossary).
+
+
+ <indexterm class="singular">
+ <primary>Glossaries</primary>
+
+ <secondary>multi-word entry in the glossary - figure</secondary>
+ </indexterm>multi-word entry in the glossary
+
+
+
+
+
+
+
+
+
+
+
+
+ If you have TransTip option activated Options →
+ Transtip), you can right click on the highlighted word in
+ the source segment to open a drop-down menu with suggested translation,
+ as offered by your glossary. Selecting one of them will insert it at the
+ current position into the target segment. You can also highlight your
+ preferred alternative in the glossary pane and insert it into the target
+ by right clicking on the selection.
+
+
+
+ Dictionary pane<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Dictionary pane</secondary>
+ </indexterm>
+
+ Dictionaries are the electronic equivalents of printed
+ dictionaries like Merriam Webster, Duden, Larousse etc., that you may
+ have on your desk. See more about them in the chapter on Dictionaries
+
+
+
+ Multiple Translations pane<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Multiple Translations pane</secondary>
+ </indexterm>
+
+ A given source segment may require several different translations,
+ depending on the context. If the current translation of the segment does
+ not fit, the user can select Edit → Create Alternative
+ Translation . The target text entered after that will be
+ treated as an alternative translation of the source segment. You can
+ define one of the alternative - for instance the most probable among
+ them - as default translation by selecting Edit → Use as
+ Default Translation
+
+
+
+ Notes pane
+
+ The translator can add notes to the opened segment, for instance
+ to come back later to the segment and redo the translation, check that
+ alternative translations are correct or to ask colleagues for their
+ opinion. You can browse through notes using GoTo → Next
+ Note and GoTo → Previous
+ Note.
+
+
+
+ Comments pane
+
+ Some of the file formats, specialized for translation work, for
+ instance PO, allow the inclusion of comments. This way the translator
+ can be provided the context about the segment to be translated. In the
+ example below, the author of the PO file included a warning for the
+ translator to check the length of the translation:
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Machine Translation pane<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Machine Translation pane</secondary>
+ </indexterm>
+
+ The machine translation pane, when opened, contains the
+ suggestions by machine translation tools for the current segment. Press
+ Ctrl+M to replace the translation of the current
+ segment with the suggested translation. More in the chapter Machine translation
+
+
+
+ Main menu
+
+ The main menu provides access to all
+ OmegaT functions. See the Main
+ Menu appendix for a full description of all menus and menu
+ items. The most frequently used functions are accessible with keyboard
+ shortcuts, so once you become accustomed to them, you will no longer
+ need to browse through the menus while translating. See chapter Menu and Keyboard shortcuts for
+ details.
+
+
+
+ Status bar
+
+ The status bar displays work-flow related messages at the bottom
+ of the main window. This bar gives the user feedback on specific
+ operations that are in progress. It also displays the number of fuzzy
+ and glossary matches for the current segment.
+
+
+
+
+ Other windows
+
+
+ Project files<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Project files</secondary>
+ </indexterm>
+
+ The Project Files window lists the project files and displays
+ other project information. It is displayed automatically when OmegaT
+ loads a project. Use Ctrl+L
+ Shortcuts
+
+ Ctrl+L - Project files list
+ to open and Esc to close
+ it. The Project Files Window displays the following information:
+
+
+
+ the list of all translatable files in the project. These are
+ the files present in the Source files folder in a format that OmegaT
+ is able to recognize. Clicking on any file will open it for
+ translation
+
+
+
+
+
+ the file currently available in the Editor pane is highlighted
+ with a blue background. Pressing Enter will move
+ the Editor pane to the top of the file selected
+
+
+
+
+
+ the number of segments in each file is shown next to the file
+ name
+
+
+
+
+
+ the total number of segments, the number of unique segments in
+ the whole project, and the number of unique segments already
+ translated are shown at the bottom
+
+
+
+ The set of Unique segments is
+ computed by taking all the segments and removing all duplicate segments.
+ (The definition of “unique” is case-sensitive: "Run" and "run" are
+ treated as being different)
+
+ The difference between "Number of segments" and "Number of unique
+ segments" provides an approximate idea of the number of repetitions in
+ the text. Note however that the numbers do not indicate how relevant the
+ repetitions are: they could mean relatively long sentences repeated a
+ number of times (in which case you are fortunate) or it could describe a
+ table of keywords (not so fortunate). The
+ project_stats.txt located in the omegat folder of
+ your project contains more detailed segment information, broken down by
+ file.
+
+ Modifying the segmentation rules may have the effect of modifying
+ the number of segments/unique segments. This, however, should generally
+ be avoided once you have started translating the project. See the
+ chapter Segmentation rules for more
+ information.
+
+
+ Source files
+
+ Adding files to the project
+ Adding files to the project: You can add source
+ files to the project by clicking on the "Import Source
+ Files..." button. This copies the selected files to the
+ source folder and reloads the project to import the
+ new files. You can also add source files from Internet pages, written in
+ MediaWiki, by clicking on "Import from
+ MediaWiki" button and providing the corresponding
+ URL.
+
+
+
+ Search window<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Search pane</secondary>
+ </indexterm>
+
+ You can use the search window to find specific segments in a
+ project. You can also have several search windows open simultaneously.
+ To open a new search window, use
+ Ctrl
+
+ F
+ in the Main window. The search window consists of a text
+ field for search strings or keywords, flags and radio buttons for
+ setting up the search and a display area containing the results of the
+ search. See the chapter Searches for more
+ information about the search window.
+
+
+
+ Tag validation<indexterm class="singular">
+ <primary>Tag validation</primary>
+
+ <seealso>Shortcuts, Tags</seealso>
+ </indexterm><indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Tag validation</secondary>
+
+ <seealso>Tags</seealso>
+ </indexterm>
+
+ The tag validation window detects and lists any tag errors and
+ inconsistencies in the translation. Open the window with
+ Ctrl+T. The window features a 3 column table
+ with a link to the segment and its source and target contents:
+
+
+ <indexterm class="singular">
+ <primary>Tag validation</primary>
+
+ <secondary>Window - figure</secondary>
+
+ <seealso>Tags</seealso>
+ </indexterm>Tag validation window
+
+
+
+
+
+
+
+
+
+
+
+
+ Tags are highlighted in bold blue for easy comparison between the
+ original and the translated contents. Click on the link to jump to the
+ segment in the Editor pane. Correct the error if necessary and press
+ Ctrl+T to return to the tag validation window
+ to correct other errors. In the first and third case above tags are
+ paired incorrectly, and in the second case the < sign is missing from
+ the starting tag.
+
+ Tag errors are cases in which the tags in the translation do not
+ correspond in order and number to the original segment. Some tag
+ scenarios flagged in the tag validation window are necessary and are
+ benign, others will cause problems when the translated document is
+ created. Tags generally represent some kind of formatting in the
+ original text. Simplifying the original text formatting in the source
+ file before commencing translation greatly contributes to reducing the
+ number of tags.
+
+
+
+ Statistics<indexterm class="singular">
+ <primary>Statistics</primary>
+
+ <seealso>Menu Tools</seealso>
+ </indexterm>
+
+ The statistics window - accessed via Tools>Statistics - shows the statistics of the
+ current OmegaT project, both in the summary form as well as in detail
+ for every file to be translated. The statistics shown is available as a
+ tab-separated project_stats.txt file (subfolder
+ omegat), ready to be loaded into a spreadsheet
+ program for the user's convenience. You can use Ctrl+A
+
+ Shortcuts
+
+ Ctrl+A - Select All
+ , Ctrl+C
+ Shortcuts
+
+ Ctrl+C - copy text
+ , Ctrl+V
+ Shortcuts
+
+ Ctrl+V - Paste text
+ to copy/paste the contents.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Match statistics<indexterm class="singular">
+ <primary>Match Statistics</primary>
+
+ <seealso>Menu Tools</seealso>
+ </indexterm>
+
+ The match statistics are accessed viaTools>Match
+ Statistics. The evaluation is rather CPU intensive and can
+ be time-consuming, so a progress bar is shown during the calculation. As
+ far as categories are concerned, the de facto industry standard of
+ classifying matches into the following groups is used: Exact match,
+ 95%-100%, 85%-94%, 75%-84%, 50%-74% and No match. The word counts,
+ identical to counts in the Project Files window, are based strictly on
+ OmegaT's method of counting, with a few differences in terminology to
+ account for concept differences. This information is computed for
+ segments as well as for words and for characters (without and including
+ spaces).
+
+ Note that these totals are a good (or as-good-as-it-can-be)
+ approximation of the work involved in the project and thus can serve as
+ a basis for your cost and price calculations.
+
+
+ match statistics
+
+
+
+
+
+
+
+
+
+
+
+
+ Spaces between segments are not taken into account in the last
+ column. Repetitions stand for identical segments present several times
+ in the text. The first segment and its contents will be classified as
+ "no match", and the rest of them as a repetition of the first. If the
+ translation for several identical source segments already exists in the
+ translation memory of the project, these segments, together with other,
+ already translated unique segments, will be classified as an "Exact
+ match". The number of unique segments, if needed, is provided in the
+ standard statistics window, regardless of whether they have been
+ translated or not.
+
+ The rest of the categories (50-100%) involves untranslated
+ segments with a fuzzy match. Fuzzy matches can come from the
+ /tm folder as well - and not just from the internal
+ translation memory in /omegaT, as is the case for
+ repetitions and exact matches. The only difference with matches from the
+ project_save translation memory is that external
+ TMs cannot give exact matches, only 100%. If one does not wish to use
+ external TMs for counting, one will either have to empty the /tm folder
+ or change the project setup (temporarily) so that the value for /tm
+ points to a different location.
+
+ The Match Statistics are tab-separated and you can use
+ Ctrl+A
+ Shortcuts
+
+ Ctrl+A - Select All
+ , Ctrl+C
+ Shortcuts
+
+ Ctrl+C - copy text
+ , Ctrl+V
+ Shortcuts
+
+ Ctrl+V - Paste text
+ to copy/paste them, for instance into a
+ spreadsheet or into your cost-accounting application. Once computed, the
+ data also available in
+ omegat/project_stats_match.txt. Note that the file
+ is time-stamped, as the calculation (contrary to the standard
+ statistics) is not instantaneous and can thus quickly become
+ obsolete.
+
+
+
+ Help browser<indexterm class="singular">
+ <primary>Menu Help</primary>
+
+ <secondary>Help browser</secondary>
+ </indexterm>
+
+ The help browser (which displays this manual) can be opened by
+ pressing
+ Shortcuts
+
+ F1 - Help
+ F1 or navigating to
+ Menu Help
+
+ User Manual...
+ Help → User Manual... in the main menu. In
+ the window, the manual and two buttons are displayed: Back and Contents.
+ The user manual is an HTML document with links to different chapters.
+ Clicking on a link as you would do in a web browser brings the desired
+ page to the front.
+
+ The user manual is located in the docs subfolder under the OmegaT
+ installation folder, so you may can, for instance, view the English
+ documentation by opening the docs/en/index.html
+ file in your browser. Opening the user manual in this way
+ also enables you to follow external links, as the built-in help browser
+ does not accept external Internet links.
+
+
+
+
+
+ Menu and Keyboard shortcuts
+
+
+ <indexterm class="singular">
+ <primary>Main menu</primary>
+ </indexterm>Main Menu
+
+
+ Shortcuts
+
+ Main menu
+
+
+ All of OmegaT's functions are available through the menu bar at the
+ top of the Editor window. Most functions are also available via keyboard
+ shortcuts. Shortcuts are activated by pressing Ctrl and a
+ letter. Some shortcuts involve other keys. For readability purposes,
+ letters are written in uppercase here. Ctrl is used on
+ Windows, UNIX and UNIX-like operating systems with keyboards featuring a
+ Ctrl or Control key. Mac users should
+ instead use
+ Cmd
+
+ key
+ instead. The "Cmd" key either has a "command" label or an
+ apple symbol on Apple keyboards.
+
+ You can customize existing shortcuts or add new ones according to
+ your needs. See Appendix -
+ Shortcuts Customization
+
+
+ Main Menu
+
+
+
+
+ Project
+
+ Edit
+
+ Go to
+
+ View
+
+ Tools
+
+ Options
+
+ Help
+
+
+
+
+ Project menu
+
+
+
+
+
+
+
+
+ New
+
+
+
+ Creates and opens a new project. The dialog to create a
+ project is the same as to edit the project. See
+
+
+
+ Open
+
+
+ Ctrl
+
+ O
+
+
+ Opens a previously created project.
+
+
+
+ Import Source Files...
+
+
+
+ Copies the selected files to the
+ source folder and reloads the project to
+ load the new files.
+
+
+
+ Import From
+ MediaWiki...
+
+
+
+ Imports units from MediaWiki pages, based on the URL
+ entered.
+
+
+
+ Reload
+
+ F5
+
+ Reloads the project to take external changes in source
+ files, legacy translation memories, glossaries and project
+ settings into account.
+
+
+
+ Close
+
+
+ Ctrl
+
+ Shift
+
+ W
+
+
+ Saves the translation and closes the project.
+
+
+
+ Save
+
+
+ Ctrl
+
+ S
+
+
+ Saves the internal translation memory to the hard disk.
+ OmegaT automatically saves translations every 10 minutes as well
+ as when you close the project or quit OmegaT.
+
+
+
+ Create translated
+ documents
+
+
+ Ctrl
+
+ D
+
+
+ Creates the target documents based on your translation of
+ the documents' text. The created target documents are located in
+ the target folder.
+
+
+
+ Properties...
+
+
+ Ctrl
+
+ E
+
+
+ Displays Project properties
+ dialog to edit project languages and folder locations.
+
+
+
+ Project Files...
+
+
+ Ctrl
+
+ L
+
+
+ Closes or opens the Project files window
+ (depending on whether it is open or closed).
+
+
+
+ Quit
+
+
+ Ctrl
+
+ Q
+
+
+ Saves the project and quits
+ OmegaT. If you haven't yet saved the
+ project, this manually confirms whether you really wish to
+ quit.
+
+
+
+
+
+
+
+ Edit<indexterm class="singular">
+ <primary>Main menu</primary>
+
+ <secondary>Edit</secondary>
+ </indexterm>
+
+ Note: Items that are found in most applications (copy/cut/paste)
+ are not displayed in this menu, but are available using your system
+ shortcuts. For example:
+
+
+ Copy/cut/paste shortcuts
+
+
+
+
+
+
+
+
+ Copy
+
+
+ Ctrl
+
+ C
+
+
+ Copies the selected text to the clipboard.
+
+
+
+ Cut
+
+
+ Ctrl
+
+ X
+
+
+ Copies the selected text to the clipboard and deletes the
+ selected text.
+
+
+
+ Paste
+
+
+ Ctrl
+
+ V
+
+
+ Pastes the text from the clipboard at the cursor
+ position.
+
+
+
+
+
+ The Edit menu itself contains the following items:
+
+
+ Edit menu
+
+
+
+
+
+
+
+
+ Undo Last Action
+
+
+ Ctrl
+
+ Z
+
+
+ Restores the status before the last editing action was
+ taken. This command does not work once the modified segment has
+ been validated.
+
+
+
+ Redo Last Action
+
+
+ Ctrl
+
+ Y
+
+
+ Restores the status before the last editing action was
+ cancelled. This command does not work once the modified segment
+ has been validated.
+
+
+
+ Replace With Match
+
+
+ Ctrl
+
+ R
+
+
+ Replaces the whole target segment with the currently
+ selected fuzzy match (by default the first match is
+ selected).
+
+
+
+ Insert Match
+
+
+ Ctrl
+
+ I
+
+
+ Inserts the currently selected fuzzy match at the cursor
+ position. If part of the target segment has been selected, this
+ function overwrites the selected portion.
+
+
+
+ Replace with Machine
+ Translation
+
+
+ Ctrl
+
+ M
+
+
+ Replaces the target segment with the translation,
+ provided by the selected Machine Translation service. No action
+ is taken, if no Machine Translation service has been activated
+ (see Menu > Options below).
+
+
+
+ Replace With Source
+
+
+ Shift
+
+ Ctrl
+
+ R
+
+
+ Replaces the whole target segment with the
+ source.
+
+
+
+ Insert Source
+
+
+ Shift
+
+ Ctrl
+
+ I
+
+
+ Inserts the source at the cursor position.
+
+
+
+ Insert Source Tags
+
+
+ Shift
+
+ Ctrl
+
+ T
+
+
+
+ Tags
+
+ Inserting source tags
+ Inserts the source tags at the cursor position.
+ All the relevant tags in the source - i.e. OmegaT as well as
+ custom, Java, printf etc tags - will be inserted into the
+ current target, regardless of whether they are already there or
+ not. Texts, bracketed by tags, are replaced by spaces:.
+ <f0><f1>This is
+ text</f0></f1> thus will be copied as
+ <f0><f1>one_space</f0></f1>
+
+
+
+ Export Selection
+
+
+ Shift
+
+ Ctrl
+
+ C
+
+
+ Exports the current selection to a text file for
+ processing. If no text has been selected, the current source
+ segment is written to this file. When the user exits
+ OmegaT, this file is not emptied, in
+ order to be consistent with usual clipboard behavior. The
+ exported contents are copied to the file
+ selection.txt located in the User's
+ preference files folder (see ).
+
+
+
+ Create Glossary Entry
+
+
+ Shift
+
+ Ctrl
+
+ G
+
+
+ Allows the user create an entry in the default glossary
+ file.
+
+
+
+ Search Project...
+
+
+ Ctrl
+
+ F
+
+
+ Opens a new Search
+ window.
+
+
+
+ Switch case to...
+
+
+ Shift
+
+ F3
+ (see text)
+
+ Changes the case of the highlighted text in the target
+ segment to the selected option (Lower case, Upper case or Title
+ case). Use Shift+F3
+ Shortcuts
+
+ Shift+F3 - Case selection
+ to cycle through the three alternatives. If no
+ text is selected, OmegaT selects the
+ word that contains the letter immediately to the right of the
+ cursor.
+
+
+
+ Select Fuzzy Match #N
+
+
+ Ctrl
+
+ #N
+
+
+ (#N is a digit from 1 to 5) - Selects the Nth fuzzy match
+ displayed in the match viewer to replace or insert it to the
+ segment. The describes the color
+ coding in detail.
+
+
+
+ Use as Default
+ Translation
+
+
+
+ If there's several alternative translations available
+ active segment, you can label the alternative selected as the
+ default translation. The entry will be greyed, if there's just
+ one translation available.
+
+
+
+ Create Alternative
+ Translation
+
+
+
+ The one and the same segment may, depending on the
+ context, require different translations. Select this menu item,
+ if the current translation does not apply and enter the
+ alternative translation.
+
+
+
+
+ Go To menu
+
+
+
+
+
+
+
+
+ Next Untranslated
+ Segment
+
+
+ Ctrl
+
+ U
+
+
+ Moves to the next segment that has no equivalent in the
+ translation memory.
+
+
+
+ Next Segment
+
+
+ Ctrl
+
+ N
+ or Enter or
+ Tab
+
+ Moves to the next segment. If the current segment is the
+ last segment in a file, it moves to the first segment of the
+ next file.
+
+
+
+ Previous Segment
+
+
+ Ctrl
+
+ P
+ or
+ Ctrl
+
+ Enter
+ or
+ Ctrl
+
+ Tab
+
+
+ Moves to the previous segment. If the current segment is
+ the first one in a file, it moves to the last segment of the
+ previous file.
+
+
+
+ Segment number...
+
+
+ Ctrl
+
+ J
+
+
+ The segment is opened when its segment number is
+ entered..
+
+
+
+ Next Note
+
+
+
+ The next segment with a note attached to it, will
+ open.
+
+
+
+ Previous Note
+
+
+
+ The previous segment with a note will open.
+
+
+
+ Forward in history...
+
+
+ Ctrl
+
+ Shift
+
+ N
+
+
+ OmegaT remembers the segments
+ executed. With this command you can step forward to the segment,
+ you have previously left by the Back in
+ history...command.
+
+
+
+ Back in history...
+
+
+ Ctrl
+
+ Shift
+
+ P
+
+
+ With this command you can move backward one segment at a
+ time, to return later to the current segment using
+ Forward in history... command
+ below.
+
+
+
+
+ View menu
+
+
+
+
+
+
+ Mark Translated
+ Segments
+
+ If checked, the translated segments will be marked in
+ yellow.
+
+
+
+ Mark Untranslated
+ Segments
+
+ If checked, the untranslated segments will be marked in
+ violet.
+
+
+
+ Display Source
+ Segments
+
+ If checked, source segments will be shown and marked in
+ green. If not checked, source segments will not be
+ shown.
+
+
+
+ Mark Non-Unique
+ Segments
+
+ If checked, non-unique segments will be marked in pale
+ grey.
+
+
+
+ Mark Segments with
+ Notes
+
+ If checked, segments with notes will be marked in cyan.
+ This marking has priority over Mark Translated Segments and Mark
+ Untranslated Segments.
+
+
+
+ Mark Non-breakable
+ Spaces
+
+ If checked, non-breakable spaces in the segment will be
+ displayed with a grey background.
+
+
+
+ Modification Info
+
+ Setting the Display Modification option to
+ Selected will display the time and the
+ author of the last change in the current segment. Setting it
+ to All shows this information for all
+ segments and None turns this option
+ off.
+
+
+
+
+ Tools menu
+
+
+ Matches
+
+ Matches statistics
+
+
+
+ Project
+
+ Match statistics
+
+
+
+ Project
+
+ Statistics
+
+
+
+
+
+
+
+ Validate Tags
+
+ Ctrl+T: Checks for missing or
+ displaced tags in formatted files. Will display a list of
+ segments with tag errors and possible inconsistencies. See Tag Validation and .
+
+
+
+ Remove Tags
+
+ When enabled, all the formatting tags are removed from
+ source segments. This is useful when dealing with texts where
+ inline formatting has no real use (e.g., OCRed PDF, bad
+ converted .odt or .docx, etc.) Only inline tags are removed, so
+ normally there should be no problem with opening the target
+ documents. Non-visible formatting (i.e., which doesn't appear as
+ tags in the OmegaT editor) is kept in the target
+ document.
+
+
+
+ Statistics
+
+ Opens a new window and displays the project statistics,
+ i.e. the project totals and totals for every file in the
+ project.
+
+
+
+ Match Statistics
+
+ Displays the Match Statistics for the project: the number
+ of repetitions, exact matches, fuzzy matches and no-matches, for
+ segments, words and in characters.
+
+
+
+
+ Options menu
+
+
+
+
+
+
+ Use TAB To Advance
+
+ Sets segment validation key to
+ Tab instead of the default
+ Enter. This option is useful for some
+ Chinese, Japanese or Korean character input systems.
+
+
+
+ Always Confirm Quit
+
+ The program will see confirmation before closing
+ down.
+
+
+
+ Machine Translate
+
+ Allows you to activate/deactivate the Machine Translation
+ tools offered. When active,
+ Ctrl
+
+ M
+ will insert the suggestion into the target part of
+ the current segment.
+
+
+
+ Glossary
+
+ reserved for future use by plugins
+
+
+
+ TransTips
+
+ Allows you to activate/deactivate TransTips
+ feature and set its option Exact
+ Match. With TransTips activated
+ a right click on a highlighted word in the source will open a
+ popup menu with the glossary entries for the word you clicked.
+ You can then click on the preferred translation to insert it
+ into the target segment at the current position. With
+ TransTips/Exact Match checked, only
+ complete words will be checked, otherwise parts of words will be
+ matched as well.
+
+
+
+ Font...
+
+ Shows the dialogue to modify the text display font. Users
+ of old computers who feel window resizing is very slow can try
+ changing the font. See font settings in Miscellanea
+
+
+
+ File Filters...
+
+ Displays the File
+ filters dialogue to configure file handling and
+ parsing.
+
+
+
+ Segmentation...
+
+ Opens the Source
+ segmentation dialogue to configure text
+ segmentation.
+
+
+
+ Spell checking...
+
+ Displays the Spell
+ checker setup window to install, configure and activate
+ the spell checker.
+
+
+
+ Editing Behavior...
+
+ Displays the Translation editing
+ dialog to configure.
+
+
+
+ Tag Validation...
+
+ For programmers: Allows you to configure the Tag
+ Validator options to also check programming (%...)
+ variables.
+
+
+
+ Team...
+
+ Enter your name here and it will be attached to all
+ segments translated by you.
+
+
+
+ External TMXs...
+
+ Allows the user decide, how tags in foreign TMX files
+ (i.e. not generated by OmegaT) are to be treated.
+
+
+
+ View...
+
+ Contains the option to have all source segments in bold
+ and to mark the first non-unique segment.
+
+
+
+ Proxy login...
+
+ Enter your user name and your password, if you use a
+ proxy to access your projects.
+
+
+
+ Restore Main Window
+
+ Restores the components of the main OmegaT window to
+ their default state. Use this feature when you have undocked,
+ moved, or hidden one or more components and you are unable to
+ restore the desired arrangement. It can also be used when panes
+ do not appear as expected following an OmegaT upgrade.
+
+
+
+
+ Help menu
+
+
+
+
+
+
+ User Manual...
+
+ F1: Opens Help browser displaying this
+ manual in a separate window.
+
+
+
+ About...
+
+ Displays copyright, credits and license
+ information.
+
+
+
+
+
+
+
+
+ Keyboard shortcuts<indexterm class="singular">
+ <primary>Keyboard shortcuts</primary>
+ </indexterm>
+
+ The following shortcuts are available from the main window. When
+ another window is on the foreground, click on the main window to bring it
+ to the foreground or press Esc to close the other
+ window.
+
+ Shortcuts are activated by pressing Ctrl and a
+ letter. Some shortcuts involve other keys. For readability purposes,
+ letters are written in uppercase here.
+
+ Ctrl is used on Windows, UNIX and UNIX-like operating systems with
+ keyboards featuring a Ctrl / Control
+ key. Mac users should instead use the
+ cmd+key. On Apple keyboards the
+ cmd key either has a command label or an Apple
+ icon on it.
+
+
+
+ Project management
+
+
+
+
+
+ Editing
+
+
+
+
+
+ Moving around
+
+
+
+
+
+ Reference windows
+
+
+
+
+
+ Other
+
+
+
+
+ <indexterm class="singular">
+ <primary>Keyboard shortcuts</primary>
+
+ <secondary>Project</secondary>
+ </indexterm>Project management<indexterm class="singular">
+ <primary>Project</primary>
+
+ <secondary>Project management shortcuts</secondary>
+ </indexterm>
+
+
+ Project management shortcuts
+
+
+
+
+
+
+
+
+ Open project
+
+
+ Ctrl
+
+ O
+
+
+ Displays a dialogue to locate an existing
+ project.
+
+
+
+ Save
+
+
+ Ctrl
+
+ S
+
+
+ Saves the current work to the internal translation memory
+ (file project_save.tmx located in the project's
+ omegat folder).
+
+
+
+ Close Project
+
+
+ Shift
+
+ Ctrl
+
+ W
+
+
+ Closes the current project.
+
+
+
+ Create Translated Documents
+
+
+ Ctrl
+
+ D
+
+
+ Creates the translated documents in the project's Target
+ folder and creates translation memory files (level1, level2 and
+ omegat tmx files) in the project's root folder.
+
+
+
+ Project properties
+
+
+ Ctrl
+
+ E
+
+
+ Displays the project's settings for modification, if
+ required.
+
+
+
+
+ Editing shortcuts
+
+
+
+
+
+
+
+
+ Undo last action
+
+
+ Ctrl
+
+ Z
+
+
+ Undoes the last editing actions in the current target
+ segment
+
+
+
+ Redo last action
+
+
+ Ctrl
+
+ Y
+
+
+ Redoes the last editing actions in the current target
+ segment
+
+
+
+ Select match #N
+
+
+ Ctrl
+
+ #N
+
+
+ #N is a digit from 1 to 5. The shortcut selects the Nth
+ match displayed in the match window (the first match is selected
+ by default)
+
+
+
+ Replace with match
+
+
+ Ctrl
+
+ R
+
+
+ Replaces the current target segment contents with the
+ selected match (the first match is selected by default)
+
+
+
+ Insert match
+
+
+ Ctrl
+
+ I
+
+
+ Inserts the selected match at the cursor position in the
+ current target segment (the first match is inserted by
+ default)
+
+
+
+ Replace with source
+
+
+ Ctrl
+
+ Shift+R
+
+
+ Replaces the current target segment contents with the
+ source text contents
+
+
+
+ Insert source
+
+
+ Ctrl
+
+ Shift+I
+
+
+ Inserts the source text contents into the target segment
+ at the cursor position
+
+
+
+ Insert Source Tags
+
+
+ Ctrl
+
+ Shift+T
+
+
+ Inserts the source tags into the target segment at the
+ cursor position
+
+
+
+ Search project
+
+
+ Ctrl
+
+ F
+
+
+ Displays a dialogue to conduct searches in the
+ project
+
+
+
+ Replace with Machine Translation
+
+
+ Ctrl
+
+ M
+
+
+ Replaces the target segment with the machine translation
+ of the source. No action, if machine tools are deactivated (see
+ Menu > Options > Machine Translate)
+
+
+
+ Export Selection
+
+
+ Shift
+
+ Ctrl
+
+ C
+
+
+ Exports the current selection to a text file for
+ processing.
+
+
+
+ Create Glossary Entry
+
+
+ Shift
+
+ Ctrl
+
+ G
+
+
+ Allows the user create an entry in the default glossary
+ file.
+
+
+
+
+ Moving around shortcuts
+
+
+
+
+
+
+
+
+ Next Untranslated Segment
+
+
+ Ctrl
+
+ U
+
+
+ Moves the editing field to the next segment that is not
+ registered in the project's translation memory
+
+
+
+ Next Segment
+
+
+ Ctrl
+
+ N
+ , Enter or
+ Return
+
+ Moves the editing field to the next segment.
+
+
+
+ Previous Segment
+
+
+ Ctrl
+
+ P
+
+
+ Moves the editing field to the previous segment
+
+
+
+ Segment number...
+
+
+ Ctrl
+
+ J
+
+
+ Moves to the segment number entered
+
+
+
+ Back in history...
+
+
+ Ctrl
+
+ Shift+P
+
+
+ Moves one segment back in history
+
+
+
+ Forward in history...
+
+
+ Ctrl
+
+ Shift+N
+
+
+ Moves one segment forward in history
+
+
+
+
+ Various shortcuts
+
+
+
+
+
+
+
+
+ Project files listing
+
+
+ Ctrl
+
+ L
+
+
+ Displays the Project files listing
+
+
+
+ Validate Tags
+
+
+ Ctrl
+
+ T
+
+
+ Opens the Tag validation window.
+
+
+
+ Export Selection
+
+
+ Shift
+
+ Ctrl+C
+
+
+ Exports the current selection or the current source, if
+ no text has been selected. The text is exported to a plain text
+ file.
+
+
+
+ Search Project
+
+
+ Ctrl
+
+ F
+
+
+ Opens a new Search window.
+
+
+
+ Help files
+
+ F1
+
+ Displays the OmegaT help files
+ in a separate window
+
+
+
+
+
+
+
+
+
+ Project properties<indexterm class="singular">
+ <primary>Project</primary>
+
+ <secondary>Properties</secondary>
+ </indexterm>
+
+
+
+
+ Properties dialog
+
+ The
+
+
+ Ctrl
+
+ E
+
+
+
+ Project
+
+ Properties...
+ dialog is used to define and modify the project folders
+ and languages.
+
+ It is possible to modify the project properties during a translation
+ session. Note that changes to the project setup may have some
+ consequences, especially, when the project has already been started. Until
+ you have some experience with OmegaT, it is safest to consider all
+ settings final once the translation has started – unless of course you
+ realize a major mistake has been made. See the section Preventing data
+ loss for ways and means of protecting your work.
+
+
+ Project properties window
+
+
+
+
+
+
+
+
+
+
+
+
+ It contains:
+
+
+
+ An area for setting project source and target languages with
+ drop-down menus
+
+ You can either enter the source and target languages by hand or
+ use the drop down menu. Bear in mind that changing the languages may
+ render the currently used translation memories useless since their
+ language pair may not longer match the new languages.
+
+
+
+
+
+ the Enable Sentence-level segmentation
+ check box
+
+
+ Project
+
+ Enable Sentence-level segmentation
+
+
+ The segmentation settings only address the way the source files
+ are handled by OmegaT. The predominant way
+ of segmenting the sources is the sentence-level segmenting, so this
+ check box should in a normal case be left checked.
+
+ In some seldom cases the alternative, i.e. segmenting by
+ paragraphs, may be preferred. Changing this flag does not modify the
+ segmentation of already existing translation memories. If you decide
+ mid-translation to switch from sentence to paragraph translation, the
+ internal translation memory of the project will not be changed (OmegaT
+ may upgrade old translation memories that did not use sentence
+ segmentation, but not vice versa).
+
+ Changing segmentation settings may cause some already translated
+ segments to be split or merged. This will effectively return them to
+ the "untranslated" status, as they will no longer match segments
+ recorded in the project memory, even though their original translation
+ is still there.
+
+
+
+
+
+ Segmentation... button
+ Segmentation
+
+ global vs project rules
+
+
+ The segmentation rules are generally valid across all the
+ projects. The user, however, may need to generate a set of rules,
+ specific to the project in question. Use this button to open a
+ dialog,activate the check box Project specific
+ segmentation rules, then proceed to adjust the
+ segmentation rules as desired . The new set of rules will be stored
+ together with the project and will not interfere with the general set
+ of segmentation rules. To delete project specific Segmentation rules,
+ uncheck the check box. See chapter Source Segmentation for more
+ information on segmentation rules.
+
+ Hint: the set of segmentation rules for a
+ given project is stored as
+ project/omegat/segmentation.conf.
+
+
+
+ File Filters... button
+ File Filters
+
+ global vs project file filters
+
+
+ In a similar fashion as above the user can create
+ project-specific File filters, which will be stored together with the
+ project and will be valid for the current project only. To create a
+ project-specific set of file filters, click on the File
+ filter ... button, then activate Enable
+ project specific filters check box in the window, that
+ opens. A copy of the changed filters configuration will be stored with
+ the project. To delete project specific file filters, uncheck the
+ check box. Note that in the menu Options->File
+ Filters, the global user filters are changed, not the
+ project filters. See chapter File
+ filters for more on the subject.
+
+ Hint: the set of file filters for a given
+ project is stored as
+ project/omegat/filters.xml.
+
+
+
+
+
+ An area for setting project folders
+ Glossary
+
+ Location of the writable glossary file
+
+
+
+ Project
+
+ Changing the folder structure
+
+
+ if you enter names of folders that do not exist yet,
+ OmegaT creates them for you. In case you
+ decide to modify project folders, keep in mind that this will not move
+ the contained files from old folders to the new location.
+
+
+
+
+
+
+ File Filters
+
+ OmegaT features highly customizable filters, enabling you to configure
+ numerous aspects. File filters are pieces of code capable of:
+
+
+
+ Reading the document in some specific file format. For instance,
+ plain text files.
+
+
+
+
+
+ Extracting the translatable content out of the file.
+
+
+
+
+
+ Automating modifications of the translated document file names by
+ replacing translatable contents with its translation.
+
+
+
+ To see which file formats can be handled by OmegaT, see the menu
+ Options > File Filters ...
+
+ Most users will find the default file filter options sufficient. If
+ this is not the case, open the main dialog by selecting Options → File Filters... from the main menu. You
+ can also enable project-specific file filters, which will only be used on
+ the current project, by selecting the File
+ Filters... option in Project Properties.
+
+ You can enable project specific filters via the Options → Properties... . Klick on File
+ Filters button and activate the check box Enable
+ project specific filters
+ File filters
+
+ project specific file filters
+ . A copy of the filters configuration will be stored with the
+ project in this case. If you later change filters, only the project filters
+ will be updated, while the user filters stay unchanged.
+
+ Warning! Should you change filter
+ options whilst a project is open, you must reload the project in order for
+ the changes to take effect.
+
+
+ File filters dialog<indexterm class="singular">
+ <primary>File filters</primary>
+
+ <secondary>Dialog</secondary>
+ </indexterm>
+
+ This dialog lists available file filters. Should you wish not to use
+ OmegaT to translate files of a certain type, you can turn off the
+ corresponding filter by deactivating the check box beside its name. OmegaT
+ will then omit the appropriate files while loading projects, and will copy
+ them unmodified when creating target documents. When you wish to use the
+ filter again, just tick the check box. Click Defaults to reset the file filters to the default
+ settings. To edit which files in which encodings the filter is to process,
+ select the filter from the list and click Edit.
+
+
+
+ Filter options<indexterm class="singular">
+ <primary>File filters</primary>
+
+ <secondary>Options</secondary>
+ </indexterm>
+
+ Five filters (Text files, XHTML files, HTML and XHTML files,
+ OpenDocument/OpenOffice.org files and Microsoft Open XML files) have one
+ or more specific options. To modify the options select the filter from the
+ list and click on Options. The available
+ options are:
+
+ Text files
+
+
+
+ Paragraph segmentation on line breaks, empty lines or
+ never:
+
+ if sentence segmentation rules are active, the text will further
+ be segmented according to the option selected here.
+
+
+
+ PO files
+
+
+
+ Allow blank translations in the target
+ file:
+
+ If on, when a PO segment (which may be a whole paragraph) is not
+ translated, the translation will be empty in the target file.
+ Technically speaking, the msgstr segment in the PO target
+ file, if created, will be left empty. As this is the standard behavior
+ for PO files, it is on by default. If the option is off, the source
+ text will be copied to the target segment.
+
+
+
+ XHTML Files
+
+
+
+ Translate the following attributes - the
+ selected attributes will appear as segments in the Editor
+ window.
+
+
+
+
+
+ Start a new paragraph on: the <br>
+ HTML tag will constitute a paragraph for segmentation purposes.
+
+
+
+
+
+ Skip text matching regular expression: the
+ text matching the regular expression gets skipped. It is shown
+ rendered red in the tag validator. Text in source segment that matches
+ is shown in italic.
+
+
+
+
+
+ Do not translate the content attribute of meta-tags
+ ... :
+
+ It is sometimes useful to be able make some tags untranslatable
+ based on the value of attributes. E.g., <div
+ class="hide"> <span translate="no"> You can define
+ key-value pairs for tags to be left untranslated. For the example
+ above, the field would contain: class=hide, translate=no
+
+
+
+
+ Microsoft Office Open XML
+ files
+
+ You can select which elements are to be translated. They will appear
+ as separate segments in the translation.
+
+
+
+ Word: non-visible instruction
+ text, comments, footnotes, endnotes, footers
+
+
+
+
+
+ Excel: comments, sheet
+ names
+
+
+
+
+
+ Power Point: slide comments,
+ slide masters, slide layouts
+
+
+
+
+
+ Global: charts, diagrams,
+ drawings, WordArt
+
+
+
+
+
+ Other Options:
+
+
+
+ Aggregate tags: if checked, tags
+ without translatable text between them will be aggregated into
+ single tags.
+
+
+
+ Preserve spaces for all tags: if
+ checked, "white space" (i.e., spaces and newlines) will be
+ preserved, even if not set technically in the document
+
+
+
+
+
+ HTML and XHTML files
+
+
+
+ Add or rewrite encoding declaration in HTML and XHTML
+ files: Always (default), Only if (X)HTML file has a header,
+ Only if (X)HTML file has an encoding declaration, Never
+
+
+
+
+
+ Translate the following attributes: the
+ selected attributes will appear as segments in the Editor
+ window.
+
+
+
+
+
+ Start a new paragraph on: the <br>
+ HTML tag will constitute a paragraph for segmentation purposes.
+
+
+
+
+
+ Skip text matching regular expression: The
+ text, matching the regular expression, will be skipped.
+
+
+
+
+
+ Do not translate the content attribute of
+ meta-tags ... : the attribute key-value pairs, separated by
+ commas, will be left untranslated
+
+
+
+ Text files
+
+
+
+ Paragraph segmentation on line breaks, empty lines or
+ never:
+
+ if sentence segmentation rules are active, the text will further
+ be segmented according to the option selected here.
+
+
+
+ OpenDocument/OpenOffice.org
+ files
+
+
+
+ You can select which of the following items are to be
+ translated:
+
+ index entries, bookmarks, bookmark references, notes, comments,
+ presentation notes, links (URL), sheet names
+
+
+
+
+
+ Edit filter dialog<indexterm class="singular">
+ <primary>File filters</primary>
+
+ <secondary>Editing</secondary>
+ </indexterm>
+
+ This dialog enables you to set up the source filename patterns of
+ files to be processed by the filter, customize the filenames of translated
+ files, and select which encodings should be used for loading the file and
+ saving its translated counterpart. To modify a file filter pattern, either
+ modify the fields directly or click Edit.
+ To add a new file filter pattern, click Add. The same dialog is used to add a pattern or to
+ edit a particular pattern. The dialog is useful because it includes a
+ special target filename pattern editor with which you can customize the
+ names of output files.
+
+
+ <indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>File type, filename pattern</secondary>
+ </indexterm>Source file type, filename pattern<indexterm class="singular">
+ <primary>File filters</primary>
+
+ <secondary>Source file type, filename</secondary>
+ </indexterm>
+
+ When OmegaT encounters a file in its source folder, it attempts to
+ select the filter based upon the file's extension. More precisely,
+ OmegaT attempts to match each filter's source filename patterns against
+ the filename. For example, the pattern *.xhtml
+ matches any file with the .xhtml extension.
+ If the appropriate filter is found, the file is assigned to it for
+ processing. For example, by default, XHTML filters are used for
+ processing files with the .xhtml extension. You can change or add
+ filename patterns for files to be handled by each file. Source filename
+ patterns use wild card characters similar to those used in Searches. The '*' character matches zero or more
+ characters. The '?' character matches exactly one character. All other
+ characters represent themselves. For example, if you wish the text
+ filter to handle readme files (readme, read.me, and
+ readme.txt) you should use the pattern
+ read*.
+
+
+
+ Source and Target file encoding
+
+
+ Source files
+
+ Encoding
+
+
+
+ Target files
+
+ Encoding
+
+
+
+ File filters
+
+ Source, target encoding
+
+
+ Only a limited number of file formats specify a mandatory
+ encoding. File formats that do not specify their encoding will use the
+ encoding you set up for the extension that matches their name. For
+ example, by default .txt files will be loaded using
+ the default encoding of your operating system. You may change the source
+ encoding for each different source filename pattern. Such files may also
+ be written out in any encoding. By default, the translated file encoding
+ is the same as the source file encoding. Source and target encoding
+ fields use combo boxes with all supported encodings included.
+ <auto> leaves the encoding choice to
+ OmegaT. This is how it works:
+
+
+
+ OmegaT identifies the source file encoding by using its
+ encoding declaration, if present (HTML files, XML based
+ files)
+
+
+
+
+
+ OmegaT is instructed to use a mandatory encoding for certain
+ file formats (Java properties etc)
+
+
+
+
+
+ OmegaT uses the default encoding of
+ the operating system for text files.
+
+
+
+
+
+ Target filename<indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Filenames</secondary>
+ </indexterm>
+
+ Sometimes you may wish to rename the files you translate
+ automatically, for example adding a language code after the file name.
+ The target filename pattern uses a special syntax, so if you wish to
+ edit this field, you must click Edit...and use the
+ File filters
+
+ Dialog
+ Edit Pattern Dialog. If you wish to revert to default
+ configuration of the filter, click Defaults. You may also modify the name directly
+ in the target filename pattern field of the file filters dialog. The
+ Edit Pattern Dialog offers among others the following options:
+
+
+
+ Default is ${filename}– full filename of
+ the source file with extension: in this case the name of the
+ translated file is the same as that of the source file.
+
+
+
+
+
+ ${nameOnly}– allows you to insert only the
+ name of the source file without the extension.
+
+
+
+ ${extension} - the original file
+ extension
+
+
+
+
+
+ ${targetLocale}– target locale code (of a
+ form "xx_YY").
+
+
+
+
+
+ ${targetLanguage}– the target language and
+ country code together (of a form "XX-YY").
+
+
+
+
+
+ ${targetLanguageCode} – the target language
+ - only "XX"
+
+
+
+
+
+ ${targetCountryCode}– the target country -
+ only "YY"
+
+
+
+ $(timestamp-????) - system date time at
+ generation time in various patterns
+
+ See Oracle
+ documentation for examples of the "SimpleDateFormat"
+ patterns
+
+
+
+ ${system-os-name} - operating system of the computer
+ used
+
+
+
+ ${system-user-name) - system user name
+
+
+
+ ${system-host-name} - system host name
+
+
+
+ ${file-source-encoding} - source file encoding
+
+
+
+ ${file-target-encoding} - target file encoding
+
+
+
+ ${targetLocaleLCID) - Microsoft target locale
+
+
+
+ Additional variants are available for variables ${nameOnly} and
+ ${Extension}. In case the file name has ambivalent name, one can apply
+ variables of the form $(name only-number of
+ extensions) and
+ ${extension-number of extensions}
+ . If for example the original file is named Document.xx.docx,
+ the following variables will give the following results:
+
+
+
+ ${nameOnly-0} Document
+
+
+
+ ${nameOnly-1} Document.xx
+
+
+
+ ${nameOnly-2} Document.xx.docx
+
+
+
+ ${extension-0} docx
+
+
+
+ ${extension-1} xx.docx
+
+
+
+ ${extension-2} Document.xx.docx
+
+
+
+
+
+
+
+ <application>OmegaT</application> Files and Directories
+
+ OmegaT works with three types of
+ files.
+
+
+
+ Translation project files: These constitute a translation project.
+ Losing them may affect the project's integrity and your ability to
+ complete a job. Project files are the most important files in
+ OmegaT. They are the files you deal with on a
+ daily basis while translating.
+
+
+
+
+
+ User settings files: These are created when OmegaT's behavior is
+ modified by user preference settings. Losing them usually results in
+ OmegaT reverting to its "factory settings". This can sometimes cause a
+ little trouble when you are in the middle of a translation.
+
+
+
+
+
+ Application files: These are included in the package you download.
+ Most of them are required in order for OmegaT to function properly. If
+ for some reason these files are lost or corrupted, simply download
+ and/or reinstall OmegaT to restore them all.
+
+
+
+
+ Translation project files
+
+
+ Project files
+
+ Translation project files
+
+
+ An OmegaT translation project consists of
+ a number of files and directories.
+
+ When you create a translation project, OmegaT automatically creates
+ a folder with the specified name, and a list of folders:
+
+
+ OmegaT project
+
+
+
+
+
+
+
+
+ Alternate locations for some of the folders can be chosen at project
+ creation or during the translation. It is therefore possible to select
+ existing folders or create folders in locations that reflect your work
+ flow and project management habits. To change the location of folders
+ after a project has been created, open Project >
+ Properties... in the menu or with
+ Ctrl+E and make the necessary changes.
+
+ In a file manager a translation project looks and acts just like any
+ other folder. In the foillowing example the folder my
+ projects contains three OmegaT projects:
+
+
+ OmegaT projects and subdirectories
+
+
+
+
+
+
+
+
+ Double clicking the item with the OmegaT icon is sufficient to open
+ the project. A translation project Example_Project created with the default settings
+ will be created as a new subfolder with the following structure:
+
+
+ Top folder<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>File omegat.project</secondary>
+ </indexterm>
+
+ Top folder of a project always contains the file
+ OmegaT.Project, containing project parameters as defined in
+ the Project properties window (File >
+ Properties). While the translation is progressing,
+ additional files
+ (project_name-omegat.tmx,
+ project_name-level1.tmx and project_name-level2.tmx) are
+ created (and updated during the process of translation) in thes folder.
+ They contain the one and the same translation memory contents in
+ different forms, to be sued in future projects.
+
+
+
+ Subfolder dictionary
+
+ Initially empty, this folder with contain dictionaries you have
+ added to the project. See chapter
+ Dictionaries for more on this subject.
+
+
+
+ Subfolder glossary
+
+ This folder is nitially empty. It will contain glossaries you will
+ be using in the project. See chapter
+ Glossaries for more on this subject.
+
+
+
+ Subfolder omegat<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>Subfolder omegat</secondary>
+ </indexterm>
+
+ The omegat subfolder contains at
+ least one and possibly several other files. The most important file here
+ is the project_save.tmx, that is the working
+ translation memory for the project. Backups of this file (with extension
+ bak) are added progressively to this subfolder, first at the beginning
+ of the translation session, at its end, and while the translation
+ progresses. This way an inadvertent loss of is averted - see Preventing
+ Data Loss in chapter Miscellanea.
+
+ During translation additional files may get created in this
+ subdirectory as follows
+
+
+
+
+
+
+
+ stats.txt
+
+
+ Project files
+
+ statistics file
+ contains the current statistics of the current
+ project. You can view it by selecting Tools >
+ Statistics
+
+
+
+ ignored_words.txt. learned_words.txt
+
+
+ Project files
+
+ ignored_words and learned_words
+ are created and used by the spell checker. If
+ you already have collected words you wish the spell checker to
+ ignore / accept, you just need to copy the corresponding two
+ files into the omegatsubfolder of your
+ current project.
+
+
+
+ project_stats_match.txt
+
+ contains the latest project match statistics, generated
+ by Tools > Match
+ Statistics
+
+
+
+ segmentation.conf
+
+ if existing, it contains project-specific segmentation
+ rules, if requested in Project > Properties
+ ... See Chapter Project
+ properties
+
+
+
+ filters.xml
+
+ if existing, it contains project-specific file filters,
+ if requested in Project > Properties ...
+ See Chapter Project
+ properties
+
+
+
+
+
+
+
+ Subfolder source<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>Source subfolder</secondary>
+ </indexterm>
+
+ The source subfolder contains files to be translated. You can add
+ the files to it later. Note that the structure of the source subfolder
+ may take any form you like. If the files to be translated are parts of a
+ tree structure (as in a website), you need only specify the top-level
+ subfolder and OmegaT will maintain the entire contents, while keeping
+ the tree structure intact.
+
+
+
+ Subfolder target<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>Target subfolder</secondary>
+ </indexterm>
+
+ This subfolder is initially empty. To add contents to it, select
+
+
+
+ Ctrl
+
+ D
+
+
+
+ Project
+
+ Create Translated Documents
+ . Files within the source directory,
+ whether translated or not, are then generated here, with the same
+ hierarchy as present in the source subfolder. The contents of the target
+ subfolder will reflect the current state of the translation, as present
+ in the project translation memory, saved in the current /omegat/project_save.tmx. Untranslated segments
+ will hereby remain in the source language.
+
+
+
+
+ User settings files<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>User settings files</secondary>
+ </indexterm>
+
+ User files contain the information, applicable to all the projects
+ for a given user;
+
+
+
+
+
+
+
+ logs/OmegaT.log
+
+ This file records Java error messages while
+ OmegaT is running. Should OmegaT appear
+ to be behaving erratically, it is important to include this file
+ or the relevant part in any bug report
+
+
+
+ script/
+
+ folder, containing script files for the script plugin, if
+ installed
+
+
+
+ filters.xml
+
+ user's default file filters
+
+
+
+ omegat.prefs
+
+ OmegaT preferences
+
+
+
+ segmentation.conf
+
+ user's default segmentation rules
+
+
+
+ uiLayout.xml
+
+ An xml file with all the GUI accessible option
+ settings
+
+
+
+
+
+ Note that default segmentation rules and file filters can be
+ overridden by project-specific setup (see above).The location of user
+ files depends upon the platform you use:
+
+
+
+
+
+
+
+ Windows 2000 and XP
+
+ Documents and Settings\<User
+ Name>\Application
+ Data\OmegaT
+
+
+
+ Windows Vista and 7
+
+ Users\<User
+ Name>\AppData\Roaming\OmegaT
+
+
+
+ Windows other
+
+ <Something>\OmegaT
+ (<Something> corresponds to the location of the "home"
+ folder as determined by Java)
+
+
+
+ Linux/Solaris/FreeBSD
+
+ <User Home>/.omegat (.omegat is a
+ directory, the dot preceding its name makes it invisible unless
+ you type ls -a or an equivalent command)
+
+
+
+ MAC OSX
+
+ <User
+ Home>/Library/Preferences/OmegaT
+
+
+
+ Other
+
+ <User Home>
+
+
+
+
+
+
+
+ Application files<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>Application files</secondary>
+ </indexterm>
+
+ OmegaT is supplied as a package that can be downloaded from
+ SourceForge. Here a platform-independent package in a standard Java form
+ is considered. Alternatives include include a Linux .tar package, a
+ Windows installer – with or without a Java Runtime Environment –, a MacOSX
+ installer, and a source code package for developers.
+
+ The platform-independent package can be used on any platform with a
+ working Java 1.5 runtime environment, including the platforms for which a
+ specific package also exists. It is provided as a compressed file (zip or
+ tar archive) that you must extract to the folder of your choice for
+ installation. The file can usually be extracted by double-clicking on the
+ downloaded package. Once the archive has been extracted, a folder
+ containing the following contents is created:
+
+
+
+
+
+
+
+ File/ subfolder
+
+ Contents
+
+
+
+ /docs/
+
+ All the user manual files can be found in this folder. You
+ can open them in An Internet browser to obtain access to external
+ links.
+
+
+
+ /images/
+
+ Icons and logo graphics
+
+
+
+ /lib/
+
+ Contains Java files, necessary to the operation of
+ OmegaT.
+
+
+
+ join.html
+
+ This is an ordinary html file that, when opened in your
+ Internet browser, directs you to the OmegaT user group hosted on
+ Yahoo Groups. Joining is not necessary, but will provide you with
+ access to additional services, such as files, questionnaires, and
+ the opportunity to take part in OmegaT-related discussions. The
+ group archives are public and can be viewed without subscription
+ to the group.
+
+
+
+ changes.txt
+
+ A relatively detailed list of modifications between this
+ version and the preceding versions.
+
+
+
+ license.txt
+
+ The GNU GENERAL PUBLIC LICENSE. This license allows you to
+ do certain things with OmegaT,
+ including modifying and distributing it. If you are interested in
+ modifying or distributing OmegaT, read
+ this document carefully and ensure you understand its implications
+ before doing anything. If in doubt, don't hesitate to ask project
+ members directly either by sending them an e-mail from the
+ SourceForge page or by sending a public mail to the user
+ group.
+
+
+
+ doc-license.txt
+
+ The GNU GENERAL PUBLIC LICENSE. This license covers the
+ documentation. See above.
+
+
+
+ readme.txt
+
+ This file is very important and you should make sure you
+ read it before launching OmegaT. It includes general information
+ on OmegaT, where to find more information, how to contribute, etc.
+ It has been translated into a number of languages.
+
+
+
+ OmegaT
+
+ A text file containing two lines:
+
+
+
+
+
+ #!/bin/bash java
+
+
+
+
+
+ java -jar
+ OmegaT.jar $*
+
+
+
+
+
+ Linux and OSX users may find this file useful. Make it
+ executable (chmod +x OmegaT) from the command line after making
+ sure you are in the /OmegaT_2.5/ directory. You will then be able
+ to launch OmegaT by executing this file from the command
+ line
+
+
+
+ OmegaT.bat
+
+ A batch file, used to launch
+ OmegaT from the Windows command line.
+ It contains just the following line:
+
+
+
+
+
+ java -jar OmegaT.jar
+ %*
+
+
+
+ OmegaT.jar
+
+ The main OmegaT application. To launch OmegaT, you must
+ launch this file either from the command line or from your file
+ manager, usually by double-clicking it.
+
+
+
+
+
+
+
+
+ Files to translate
+
+
+ File formats<indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>File formats</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>File formats</secondary>
+ </indexterm>
+
+ You can use OmegaT to translate files in
+ a number of file formats. There are basically two types of file formats,
+ plain text and formatted text.
+
+
+ Plain text files<indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Plain text files</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Plain text files</secondary>
+ </indexterm>
+
+ Plain text files contain text only, so their translation is as
+ simple as typing the translation. There are several methods to specify
+ the file's encoding so that its contents are not garbled when opened in
+ OmegaT. Such files do not contain any
+ formatting information beyond the "white space" used to align text,
+ indicate paragraphs or insert page breaks. They are not able to contain
+ or retain information regarding the color, font etc of the text.
+ Currently, OmegaT supports the following
+ plain text formats:
+ File formats
+
+ Unformatted
+
+ Source files
+
+
+
+
+ ASCII text (.txt, etc.)
+
+
+
+
+
+ Encoded text (*.UTF8)
+
+
+
+
+
+ Java resource bundles (*.properties)
+
+
+
+
+
+ PO files (*.po)
+
+
+
+
+
+ INI (key=value) files (*.ini)
+
+
+
+
+
+ DTD files (*.DTD)
+
+
+
+ DocuWiki files (*.txt)
+
+
+
+
+
+ SubRip title files (*.srt)
+
+
+
+
+
+ Magento CE Locale CSV files (*.csv)
+
+
+
+ Other plain text file types can be handled by
+ OmegaT by associating their file extension to
+ a supported file type (for example, .pod files can be associated to the
+ ASCII text filter) and by pre-processing them with specific segmentation
+ rules.
+
+
+
+ Formatted text files<indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Formatted text files</secondary>
+
+ <seealso>Tagged text</seealso>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Formatted text files</secondary>
+ </indexterm>
+
+ Formatted text files contain information such as font type, size,
+ color etc. as well as text. They are commonly created in word processors
+ or HTML editors. Such file formats are designed to hold formatting
+ information. The formatting information can be as simple as “this is
+ bold”, or as complex as table data with different font sizes, colors,
+ positions, etc. In most translation jobs, it is considered important for
+ the formatting of the original text to be retained in the translation.
+ OmegaT allows you to do this by marking the characters/words that have a
+ special formatting with easy-to-handle tags. Simplifying the original
+ text formatting greatly contributes to reducing the number of tags.
+ Where possible, unifying the fonts, font sizes, colors, etc. used in the
+ document simplifies the task of translation and reduces the possible
+ number of tag errors. Each file type is handled differently in OmegaT.
+ Specific behavior can be set up in the file filters. At the time of
+ writing, OmegaT supports the following formatted text formats:
+
+ File formats
+
+ formatted
+
+ Source files
+
+
+
+
+ OpenOffice.org / OpenDocument (*.ods, *.ots, *.odt, *.ott,
+ *.odp, *.otp)
+
+
+
+ Microsoft Office Open XML (*.docx, *.dotx, *.xlsx, *.xltx,
+ *.pptx)
+
+
+
+ (X)HTML (*.html, *.xhtml,*.xht)
+
+
+
+ HTML Help Compiler (*.hhc, *.hhk)
+
+
+
+ DocBook (*.xml)
+
+
+
+ XLIFF (*.xlf, *.xliff, *.sdlxliff) - monolingual, i.e. one
+ language combination possible for a given project
+
+
+
+ QuarkXPress CopyFlowGold (*.tag, *.xtg)
+
+
+
+ ResX files (*.resx)
+
+
+
+ Android resource (*.xml)
+
+
+
+ LaTex (*.tex, *.latex)
+
+
+
+ Help (*.xml) and Manual (*.hmxp) files
+
+
+
+ Typo3 LocManager (*.xml)
+
+
+
+ WiX Localization (*.wxl)
+
+
+
+ Iceni Infix (*.xml)
+
+
+
+ Flash XML export (*.xml)
+
+
+ Wordfast TXML (*.txml)
+
+
+ Camtasia for Windows (*.camproj)
+
+
+
+
+ Other formatted text file types may also be handled by OmegaT by
+ associating their file extensions to a supported file type, assuming
+ that the corresponding segmentation rules will segment them
+ correctly.
+
+
+
+
+ Other file formats<indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Other file formats</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Other file formats</secondary>
+ </indexterm>
+
+ Other plain text or formatted text file formats suitable for
+ processing in OmegaT may also exist.
+
+
+ Target files
+
+ File conversion tools
+ External tools can be used to convert files to supported
+ formats. The translated files will then need to be converted back to the
+ original format. For example, if you have an outdated Microsoft Word
+ version, that does not handle the ODT format, here's a round trip for Word
+ files with the DOC extension:
+
+
+
+ import the file into OpenOffice.org writer
+
+
+
+
+
+ save the file in ODT format
+
+
+
+
+
+ translate it into the target ODT file
+
+
+
+
+
+ load the target file in OpenOffice.org writer
+
+
+
+
+
+ save the file as a DOC file
+
+
+
+ The quality of formatting of the translated file will depend on the
+ quality of the round-trip conversion. Before proceeding with such
+ conversions, be sure to test all options. Check the OmegaT home page for an up-to-date
+ listing of auxiliary translation tools.
+
+
+
+ Right to left languages<indexterm class="singular">
+ <primary>Right to left languages</primary>
+ </indexterm><indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Right to left languages</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Right to left languages</secondary>
+ </indexterm>
+
+ Justification of source and target segments depends upon the project
+ languages. By default, left justification is used for Left-To-Right (LTR)
+ languages and right justification for Right-To-Left (RTL) languages. You
+ can toggle between different display modes by pressing
+ Shift
+
+ Ctrl
+
+ O
+ (this is the letter O and not the numeral 0). The
+ Shift
+
+ Ctrl
+
+ O
+ toggle has three states:
+
+
+
+ default justification, that is as defined by the language
+
+
+
+
+
+ left justification
+
+
+
+
+
+ right justification
+
+
+
+ Using the RTL mode in OmegaT has no
+ influence whatsoever on the display mode of the translated documents
+ created in OmegaT. The display mode of the
+ translated documents must be modified within the application (such as
+ Microsoft Word) commonly used to display or modify them (check the
+ relevant manuals for details). Using
+ Shift
+
+ Ctrl
+
+ O
+ causes both text input and display in
+ OmegaT to change. It can be used separately for
+ all three panes (Editor, Fuzzy Matches and Glossary) by clicking on the
+ pane and toggling the display mode. It can also be used in all the input
+ fields found in OmegaT - in the search window,
+ for segmentation rules etc.
+
+ Mac OS X users, note: use
+ Shift
+
+ Ctrl
+
+ O
+ shortcut and not
+ cmd+Ctrl+O.
+
+
+ Mixing RTL and LTR strings in segments<indexterm class="singular">
+ <primary>Right to left languages</primary>
+
+ <secondary>Mixing RTL and LTR strings</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Mixing RTL and LTR strings</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Mixing RTL and LTR strings</secondary>
+ </indexterm>
+
+ When writing purely RTL text, the default (LTR) view may be used.
+ In many cases, however, it is necessary to embed LTR text in RTL text.
+ For example, in OmegaT tags, product names that must be left in the LTR
+ source language, place holders in localization files, and numbers in
+ text. In cases like these it becomes necessary to switch to RTL mode, so
+ that the RTL (in fact bidirectional) text is displayed correctly. It
+ should be noted that when OmegaT is in RTL
+ mode, both source and target are displayed in RTL mode. This means that
+ if the source language is LTR and the target language is RTL, or vice
+ versa, it may be necessary to toggle back and forth between RTL and LTR
+ modes to view the source and enter the target easily in their respective
+ modes.
+
+
+
+ <application>OmegaT</application> tags in RTL segments<indexterm class="singular">
+ <primary>Right to left languages</primary>
+
+ <secondary>OmegaT tags in RTL languages</secondary>
+ </indexterm>
+
+ As stated above, OmegaT tags are LTR strings. When translating
+ between RTL and LTR languages, correctly reading the tags from the
+ source and entering them properly in the target may require the
+ translator to toggle between LTR and RTL modes numerous times.
+
+ If the document allows, the translator is strongly encouraged to
+ remove style information from the original document so that as few tags
+ as possible appear in the OmegaT interface. Follow the indications given
+ in Hints for tags management. Frequently validate tags (see Tag
+ validation) and produce translated documents (see below and Menu) at
+ regular intervals to make it easier to catch any problems that arise. A
+ hint: translating a plain text version of the text and adding the
+ necessary style in the relevant application at a later stage may turn
+ out to be less hassle.
+
+
+
+ Creating translated RTL documents<indexterm class="singular">
+ <primary>Right to left languages</primary>
+
+ <secondary>Creating RTL target files</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Right to left languages</primary>
+
+ <secondary>Target files</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Right to left languages</primary>
+
+ <secondary>Creating RTL target text</secondary>
+ </indexterm>
+
+ When the translated document is created, its display direction
+ will be the same as that of the original document. If the original
+ document was LTR, the display direction of the target document must be
+ changed manually to RTL in its viewing application. Each output format
+ has specific ways of dealing with RTL display; check the relevant
+ application manuals for details.
+
+ To avoid changing the target files display parameters each time
+ the files are opened, it may be possible to change the source file
+ display parameters such that such parameters are inherited by the target
+ files. Such modifications are possible in OpenOffice.org files for
+ example.
+
+
+
+
+
+ Editing behavior<indexterm class="singular">
+ <primary>Menu options</primary>
+
+ <secondary>Editing behavior...</secondary>
+ </indexterm>
+
+ The dialog in
+ Options
+
+ Editing Behavior...
+ enables the user to select, how the current segment in the
+ editing field is to be initialized and handled:
+
+
+ Editing behavior options
+
+
+
+
+
+
+
+
+
+ Editing behaviour - options<indexterm class="singular">
+ <primary>Editing behaviour</primary>
+
+ <secondary>Options</secondary>
+ </indexterm>
+
+ You translate your files by moving from segment to segment, editing
+ each current segment in turn. When moving between segments, you may wish
+ to populate the editing field with an existing translation in the fuzzy
+ match pane or with the source text. In
+ Options
+
+ Editing Behavior...
+ OmegaT offers you the following
+ alternatives:
+
+
+
+ The source text
+
+
+ You can have the source text inserted automatically into the
+ editing field. This is useful for texts containing many trade marks
+ or other proper nouns you which must be left unchanged.
+
+
+
+
+ Leave the segment empty
+ Editing behaviour
+
+ Empty translation
+
+
+
+ OmegaT leaves the editing field blank. This option allows you
+ to enter the translation without the need to remove the source text,
+ thus saving you two keystrokes (Ctrl+A
+ and Del). Empty
+ translations are now allowed. They are displayed as <EMPTY> in
+ the Editor. To create one, right-click in a segment, and select
+ "Set empty translation". The entry
+ Remove translation in the same
+ popup menu also allows to delete the existing translation of the
+ current segment. You achieve the same by clearing the target segment
+ and pressing Enter.
+
+
+
+
+ Insert the best fuzzy match
+ Editing behaviour
+
+ Inserting fuzzy matches
+
+
+
+ OmegaT inserts the translation of the string most similar to
+ the current source, if it is above the similarity threshold that you
+ have selected in this dialog. The prefix (per default empty) can be
+ used to tag translations, done via fuzzy matches. If you add a
+ prefix (for instance [fuzzy]), you can trace those translations
+ later to see they are correct.
+
+
+
+
+
+
+ Allow the translation to be equal to source<indexterm class="singular">
+ <primary>Editing behaviour</primary>
+
+ <secondary>Translation equal to source</secondary>
+ </indexterm>
+
+ Documents for translation may contain trade marks, names or other
+ proper nouns that will be the same in translated documents. There are two
+ strategies for segments that contain only such invariable text.
+
+ You can decide not to translate such segments at all. OmegaT will
+ then report these segments as not translated. This is the default. The
+ alternative is to enter a translation that is identical to the source
+ text. OmegaT is able to recognize that you have done this. To make this
+ possible, go to
+ Options
+
+ Editing Behavior...
+ and check the box Allow translation
+ to be equal to source.
+
+
+
+ Export the segment to text files<indexterm class="singular">
+ <primary>Editing behaviour</primary>
+
+ <secondary>Exporting the current segment</secondary>
+ </indexterm>
+
+ The text export function exports data from within the current
+ OmegaT project to plain text files. The data
+ are exported when the segment is opened. The files appear in the /script
+ subfolder in the OmegaT user files folder, and include:
+
+
+
+ The content of the segment source text
+ (source.txt).
+
+
+
+ The content of the segment target text
+ (target.txt).
+
+
+
+ The text highlighted by the user, when
+ Ctrl-Shift-C is pressed or Edit >
+ Export Selection is selected
+ (selection.txt).
+
+
+
+ The content of the files is overwritten either when a new segment is
+ opened (source.txt and target.txt) or when a new selection is exported
+ (selection.txt). The files are unformatted plain text files. The whole
+ process can be steered and controlled via Tck/Tcl-based scripting. See
+ Using the
+ OmegaT text export function for specifics, examples and
+ suggestions.
+
+
+
+
+ Working with formatted text<indexterm class="singular">
+ <primary>Target files</primary>
+
+ <secondary>Formatted text</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Formatted text</secondary>
+ </indexterm>
+
+ Formatting information present in the source file usually needs to be
+ reproduced in the target file. The in-line formatting information made
+ possible by the supported formats (in particular DocBook, HTML, XHTML, Open
+ Document (OpenOffice.org) and Office Open XML (MS Office 2007 and later) at
+ the time of writing) is presented as tags in OmegaT. Normally tags are
+ ignored when considering the similarity between different texts for matching
+ purposes. Tags reproduced in the translated segment will be present in the
+ translated document.
+
+
+ Formatting tags<indexterm class="singular">
+ <primary>Tags</primary>
+ </indexterm>
+
+
+ Tags
+
+ Naming
+ Tag naming:
+
+ The tags consist of one to three characters and a number. Unique
+ numbering allows tags, corresponding to each other to be grouped together
+ and differentiates between tags, that have the same shortcut character,
+ but are in fact different. The shortcut characters used try to reflect the
+ underlying meaning of the tag (e.g. b for bold, i for italics,
+ etc.)
+
+
+ Tags
+
+ Numbering
+ Tag numbering:
+
+ Tags are numbered incrementally by tag group. "Tag groups" in this
+ context are a single tag (such as <i0> and </i0>). Within a
+ segment, the first group (pair or single) receives the number 0, the
+ second the number 1 etc. The first example below has 3 tag groups (a pair,
+ a single, and then another pair), the second example has one group only (a
+ pair).
+
+
+ Tags
+
+ Pairs and singles
+ Pairs and singles:
+
+ Tags are always either singles or paired. Single tags indicate
+ formatting information that does not affect the surrounding text (an extra
+ space or line break for example).
+
+ <b0><Ctr+N></b0>,
+ <br1><b2><Enter></b2><segment 2132>
+
+
+ <br1> is a single tag and does not affect any surrounding
+ text. Paired tags usually indicate style information that applies to the
+ text between the opening tag and the closing tag of a pair. <b0> and
+ </b0> below are paired and affect the text log.txt. Note that the
+ opening tag must always come before the corresponding closing tag:
+
+ <Log file (<b0>log.txt</b0>) for tracking
+ operations and errors.<segment 3167>
+
+ OmegaT creates its tags before the
+ process of sentence segmenting. Depending upon the segmenting rules, the
+ pair of tags may get separated into two consecutive segments and the tag
+ validation will err on the side of caution and mark the two
+ segments.
+
+
+
+ Tag operations<indexterm class="singular">
+ <primary>Tags</primary>
+
+ <secondary>Operations</secondary>
+ </indexterm>
+
+ Care must be exercised with tags. If they are accidentally changed,
+ the formatting of the final file may be corrupted. The basic rule is that
+ the sequence of tags must be preserved in the same order. However, it is
+ possible, if certain rules are strictly followed, to deviate from this
+ basic rule.
+
+
+ Tags
+
+ Duplication
+ Tag duplication:
+
+ To duplicate tag groups, just copy them in the position of your
+ choice. Keep in mind that in a pair group, the opening tag must come
+ before the closing tag. The formatting represented by the group you have
+ duplicated will be applied to both sections.
+
+ Example:
+
+ <b0>This formatting</b0> is going to be
+ duplicated here.<segment 0001>
+
+ After duplication:
+
+ <b0>This formatting</b0> has been
+ <b0>duplicated here</b0>.<segment 0001>
+
+
+
+ Tags
+
+ Group deletion
+ Tag group deletion:
+
+ To delete tag groups, just remove them from the segment. Keep in
+ mind that a pair group must have both its opening and its closing tag
+ deleted to ensure that all traces of the formatting are properly erased,
+ otherwise the translated file may become corrupted. By deleting a tag
+ group you will remove the related formatting from the translated
+ file.
+
+ Example:
+
+ <b0>This formatting</b0> is going to be
+ deleted.<segment 0001>
+
+ After deletion:
+
+ This formatting has been deleted.<segment 0001>
+
+
+
+
+ Tag group nesting<indexterm class="singular">
+ <primary>Tags</primary>
+
+ <secondary>Group nesting</secondary>
+ </indexterm>
+
+ Modifying tag group order may result in the nesting of a tag group
+ within another tag group. This is acceptable, provided the enclosing group
+ totally encloses the enclosed group. In other words, when moving paired
+ tags, ensure that both the opening and the closing tag are both either
+ inside or outside other tag pairs, or the translated file may be corrupted
+ and fail to open.
+
+ Example:
+
+ <b0>Formatting</b0> <b1>one</b1> is
+ going to be nested inside formatting zero.<segment 0001>
+
+
+ After nesting:
+
+ <b0>Formatting <b1>one</b1></b0>
+ has been nested inside formatting zero.<segment
+ 0001>
+
+
+
+ Tag group overlapping<indexterm class="singular">
+ <primary>Tags</primary>
+
+ <secondary>Group overlapping</secondary>
+ </indexterm>
+
+ Overlapping is the result of bad manipulations of tag pairs and is
+ guaranteed to result in formatting corruption and sometimes in the
+ translated file not opening at all.
+
+ Example:
+
+ <b0>Formatting</b0> <b1>one</b1> is
+ going to be messed up.<segment 0001>
+
+ After a bad manipulation:
+
+ <b0>Formatting <b1>one</b0> </b1>is
+ very messed up now.<end segment 0001>
+
+
+
+ Tag validation options
+
+ To customize the work with tags, one can set down some of the rules
+ in the Options > Tag validation...
+ window:
+
+
+
+
+
+
+
+ The behaviour, stated here, applies to all the source files and not
+ just to some of the file types, like formatted text.
+
+
+
+ Printf variables
+
+ OmegaT can check that programming variables (like %s for
+ instance) in the source exist in the translation. You can decide not
+ to check at all, check for simple printf variables (like %s %d etc) or
+ for print variables of all types. .
+
+
+
+
+
+ check simple java MessageFormat patterns
+
+ Activating this check box will cause OmegaT to check if simple
+ java MessageFormat tags (like {0}) are processed correctly.
+
+
+
+
+
+ Text field Custom tags
+
+ Entering a regular expression here will cause OmegaT treat the
+ detected instances as a customer tag. It is checked if the number of
+ tags and their order is identical, just like it is the case for
+ omegat-tags.
+
+
+
+
+
+ Fragments that should be removed from the translation
+
+ One can enter a regular expression which will remove any of its
+ instances from the source segment - after it has been extracted from
+ the file and before it is shown in the editor window.
+
+
+
+
+
+ Tag group validation<indexterm class="singular">
+ <primary>Tags</primary>
+
+ <secondary>Group validation</secondary>
+ </indexterm>
+
+ The validate tags function detects changes to tag sequences (whether
+ deliberate or accidental), and shows the affected segments. Launching this
+ function – Ctrl+T
+ Shortcuts
+
+ Ctrl+T - Tag validation
+ - opens a window containing all segments in
+ the file containing suspected broken or bad tags in the translation.
+ Repairing the tags and recreating the target documents is easy with the
+ validate tags function. The window that opens when
+ Ctrl+T is pressed features a 3-column table
+ with a link to the segment, the original segment and the target
+ segment
+
+
+ Tag validation entry
+
+
+
+
+
+
+
+
+
+
+
+
+ The tags are highlighted in bold blue for easy comparison between
+ the original and the translated contents. Click on the link to activate
+ the segment in the Editor. Correct the error if necessary (in the case
+ above it is the missing <i2></i2> pair) and press
+ Ctrl+T to return to the tag validation window
+ to correct other errors. Tag errors are tag sequences in the translation
+ in which the same tag order and number as in the original segment is not
+ reproduced. Some tag manipulations are necessary and are benign, others
+ will cause problems when the translated document is created.
+
+
+
+ Hints for tags management<indexterm class="singular">
+ <primary>Tags</primary>
+
+ <secondary>Hints</secondary>
+ </indexterm>
+
+ Simplify the original text
+
+ Tags generally represent formatting in some form of the original
+ text. Simplifying the original formatting greatly contributes to reducing
+ the number of tags. Where circumstances permit, unifying used fonts, font
+ sizes, colors, etc. should be considered, as it could simplify the
+ translation and reduce the potential for tag errors. Read the tag
+ operations section to see what can be done with tags. Remember that if you
+ find tags a problem in OmegaT and formatting is not extremely relevant for
+ the current translation, removing tags may be the easiest way out of
+ problems.
+
+ Pay extra attention to tag
+ pairs
+
+ If you need to see tags in OmegaT but do not need to retain most of
+ the formatting in the translated document you are free not to include tags
+ in the translation. In this case pay extra attention to tag pairs since
+ deleting one side of the pair but forgetting to delete the other is
+ guaranteed to corrupt your document's formatting. Since tags are included
+ in the text itself, it is possible to use segmentation rules to create
+ segments with fewer tags. This is an advanced feature and some experience
+ is required in order for it to be applied properly.
+
+ OmegaT is not yet able to detect mistakes in formatting fully
+ automatically, so it will not prompt you if you make an error or change
+ formatting to fit your target language better. Sometimes, however, your
+ translated file may look strange, and – in the worst case – may even
+ refuse to open.
+
+
+
+
+ Working with plain text<indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Plain text files</secondary>
+ </indexterm>
+
+
+ Default encoding<indexterm class="singular">
+ <primary>Default encoding</primary>
+
+ <secondary>Plain text files</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Source files</primary>
+
+ <secondary>Default encoding</secondary>
+ </indexterm>
+
+ Plain text files - in most cases files with a txt extension -
+ contain just textual information and offer no clearly defined way to
+ inform the computer which language they contain. The most that OmegaT can
+ do in such a case, is to assume that the text is written in the same
+ language the computer itself uses. This is no problem for files encoded in
+ Unicode using a 16 bit character encoding set. If the text is encoded in 8
+ bits, however, one can be faced with the following awkward situation:
+ instead of displaying the text, for Japanese characters...
+
+
+
+
+
+
+
+
+
+
+
+ ...the system will display it like this for instance:
+
+
+
+
+
+
+
+
+
+
+
+ The computer, running OmegaT, has Russian as the default language,
+ and thus shows the characters in the Cyrillic alphabet and not in
+ Kanji.
+
+
+
+ The <application>OmegaT</application> solution<indexterm class="singular">
+ <primary>Default encoding</primary>
+
+ <secondary>OmegaT solution</secondary>
+ </indexterm>
+
+ There are basically three ways to address this problem in
+ OmegaT. They all involve the application of
+ file filters in the Options menu.
+
+
+
+ Change the encoding of your files to Unicode
+
+
+ open your source file in a text editor that correctly
+ interprets its encoding and save the file in "UTF-8" encoding. Change the file extension
+ from .txt to
+ .utf8.OmegaT will
+ automatically interpret the file as a UTF-8 file. This is the most
+ common-sense alternative, sparing you problems in the long
+ run.
+
+
+
+
+
+
+ Specify the encoding for your plain text files
+
+
+ - i.e. files with a .txt extension - : in
+ the Text files section of the file
+ filters dialog, change the Source File
+ Encoding from <auto> to the encoding that
+ corresponds to your source .txt file, for
+ instance to .jp for the above example.
+
+
+
+
+
+
+ Change the extensions of your plain text source files
+
+
+ for instance from .txt to
+ .jp for Japanese plain texts: in the Text files section of the file filters
+ dialog, add new Source Filename
+ Pattern (*.jp for this example) and
+ select the appropriate parameters for the source and target
+ encoding
+
+
+
+
+ OmegaT has by default the following short
+ list available to make it easier for you to deal with some plain text
+ files:
+
+
+
+ .txt files are automatically (<auto>)
+ interpreted by OmegaT as being encoded in
+ the computer's default encoding.
+
+
+
+
+
+ .txt1 files are files in ISO-8859-1, covering
+ most Western Europe
+ languages.
+ Default encoding
+
+ Western
+
+
+
+
+
+
+ .txt2 files are files in ISO-8859-2, that
+ covers most Central and Eastern
+ Europe languages
+ Default encoding
+
+ Central and Eastern European
+
+
+
+
+
+
+ .utf8 files are interpreted by
+ OmegaT as being encoded in UTF-8 (an
+ encoding that covers almost all languages in the world).
+ Default encoding
+
+ Unicode
+
+
+
+
+ You can check that yourself by selecting the item File Filters in the menu Options. For example, when you have a Czech text
+ file (very probably written in the ISO-8859-2 code) you just need to change the
+ extension .txt to .txt2 and
+ OmegaT will interpret its contents correctly.
+ And of course, if you wish to be on the safe side, consider converting
+ this kind of file to Unicode, i.e. to the .utf8 file
+ format.
+
+
+
+
+ Translation memories<indexterm class="singular">
+ <primary>Translation memories</primary>
+ </indexterm>
+
+
+ Translation memories in OmegaT
+
+
+ tmx folders - location and purpose
+
+ OmegaT projects can have translation
+ memory files - i.e. files with the extension tmx - in four different
+ places:
+
+
+
+
+ Translation memories
+
+ Subfolder omegat
+
+ Project files
+ omegat folder
+
+
+ The omegat folder contains the
+ project_save.tmx and possibly a number of
+ backup TMX files. The project_save.tmx file
+ contains all the segments that have been recorded in memory since
+ you started the project. This file always exists in the project.
+ Its contents will always be sorted alphabetically by the source
+ segment.
+
+
+
+
+
+ Translation memories
+
+ Project main folder
+ main project folder
+
+
+ The main project folder contains 3 tmx files,
+ project_name-omegat.tmx,
+ project_name-level1.tmx and
+ project_name-level2.tmx (project_name being
+ the name of your project).
+
+
+
+ The level1 file contains only textual
+ information.
+
+
+
+ The level2 file encapsulates
+ OmegaT specific tags in correct tmx
+ tags so that the file can be used with its formatting
+ information in a translation tool that supports tmx level 2
+ memories, or OmegaT itself.
+
+
+
+ The OmegaT file includes
+ OmegaT specific formatting tags so
+ that the file can be used in other
+ OmegaT projects
+
+
+
+ These files are copies of the file
+ project_save.tmx, i.e. of the project's main
+ translation memory, excluding the so-called orphan segments. They
+ carry appropriately changed names, so that its contents still
+ remain identifiable, when used elsewhere, for instance in
+ the tm subfolder of some other project (see
+ below).
+
+
+
+
+
+ Translation memories
+
+ Subfolder tm
+
+ Project files
+ tm folder
+
+
+ The /tm/ folder can contain any number of ancillary
+ translation memories - i.e. tmx files. Such files can be created
+ in any of the three varieties indicated above. Note that other CAT
+ tools can export (and import as well) tmx files, usually in all
+ three forms. The best thing of course is to use OmegaT-specific
+ TMX files (see above), so that the in-line formatting within the
+ segment is retained.
+
+ The contents of translation memories in the tm subfolder
+ serve to generate suggestions for the text(s) to be translated.
+ Any text, already translated and stored in those files, will
+ appear among the fuzzy matches, if it is sufficiently similar to
+ the text currently being translated.
+
+ If the source segment in one of the ancillary TMs is
+ identical to the text being translated, OmegaT acts as defined in
+ the
+ Options
+
+ Editing Behavior...
+ dialogue window. For instance (if the default is
+ accepted), the translation from the ancillary TM is accepted and
+ prefixed with [fuzzy], so that the translator
+ can review the translations at a later stage and check whether the
+ segments tagged this way, have been translated correctly (see the
+ Editing
+ behavior chapter)
+ .
+
+
+
+
+
+
+ Translation memories
+
+ Subfolder tm/auto
+
+ Project files
+ tm/auto folder
+ Project
+
+ Pretranslation
+
+
+
+ If it is clear from the very start, that translations in a
+ given TM (or TMs) are all correct, one can put them into
+ the tm/auto folder and avoid
+ confirming a lot of [fuzzy] cases. This will
+ effectively pre-translate the
+ source text: all the segments in the source text, for which
+ translations can be found in those "auto" TMs, will land in the
+ main TM of the project without any user intervention.
+
+
+
+
+ Optionally, you can let OmegaT have an
+ additional tmx file (OmegaT-style) anywhere
+ you specify, containing all translatable segments of the project. See
+ pseudo-translated memory below.
+
+ Note that all the translation memories are loaded into memory when
+ the project is opened. Back-ups are produced regularly of the project
+ translation memory (see next chapter), and
+ project_save.tmx is also saved/updated when the
+ project is closed or loaded again. This means for instance that you do
+ not need to exit a project you are currently working on if you decide to
+ add another ancillary TM to it: you simply reload the project, and the
+ changes you have made will be included.
+
+ The locations of the various different translation memories for a
+ given project are user-defined (see Project dialog window in Instant start guide)
+
+ Depending on the situation, different strategies are thus
+ possible, for instance:
+
+ several projects on the same subject:
+ keep the project structure, and change source and target
+ directories (Source = source/order1, target = target/order1 etc). Note
+ that you segments from order1, that are not present in order2 and other
+ subsequent jobs, will be tagged as orphan segments; however, they will
+ still be useful for getting fuzzy matches.
+
+ several translators working on the same
+ project: split the source files into source/Alice,
+ source/Bob... and allocate them to team members (Alice, Bob ...). They
+ can then create their own projects and, deliver their own
+ project_save.tmx, when finished or when a given
+ milestone has been reached. The project_save.tmx
+ files are then collected and possible conflicts as regards terminology
+ for instance get resolved. A new version of the master TM is then
+ created, either to be put in team members'
+ tm/autosubdirectories or to replace their
+ project_save.tmx files. The team can also use the
+ same subfolder structure for the target files. This allows them for
+ instance to check at any moment, whether the target version for the
+ complete project is still OK
+
+
+
+ tmx backup<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Backup</secondary>
+ </indexterm>
+
+ As you translate your files, OmegaT
+ stores your work continually in project_save.tmx in
+ the project's /omegat subdirectory.
+
+ OmegaT also backups translation memory
+ to project_save.tmx.YEARMMDDHHNN.bak in the same
+ subfolder whenever a project is opened or reloaded. YEAR is 4-digit
+ year, MM is a month, DD day of the month, HH and NN are hours and
+ minutes when the previous translation memory was saved.
+
+ If you believe you have lost translation data, follow the
+ following procedure:
+
+
+
+ Close the project
+
+
+
+ Rename the current project_save.tmx file
+ ( e.g. to project_save.tmx.temporary)
+
+
+
+ Select the backup translation memory that is most likely -
+ e.g. the most recent one, or the last version from the day before)
+ to contain the data you are looking for
+
+
+
+ Copy it to project_save.tmx
+
+
+
+ Open the project
+
+
+
+
+
+ tmx files and language<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Language</secondary>
+ </indexterm>
+
+ tmx files contain translation units, made of a number of
+ equivalent segments in several languages. A translation unit comprises
+ at least two translation unit variations (TUV). Either can be used as
+ the source or target.
+
+ The settings in your project indicate which is the source and
+ which the target language. OmegaT thus takes the TUV segments
+ corresponding to the project's source and target language codes and uses
+ them as the source and target segments respectively. OmegaT recognizes
+ the language codes using the following two standard conventions :
+
+
+
+ 2 letters (e.g. JA for Japanese), or
+
+
+
+ 2- or 3-letter language code followed by the 2-letter country
+ code (e.g. EN-US - See for a
+ partial list of language and country codes).
+
+
+
+ If the project language codes and the tmx language codes fully
+ match, the segments are loaded in memory. If languages match but not the
+ country, the segments still get loaded. If neither the language code not
+ the country code match, the segments will be ignored.
+
+
+ Translation memories
+
+ multilingual, handling of
+ TMX files can generally contain translation units with
+ several candidate languages. If for a given source segment there is no
+ entry for the selected target language, all other target segments are
+ loaded, regardless of the language. This avoids loading unwanted
+ non-project languages from multilingual TMXs, while still allowing the
+ use of monolingual TMXs with other target languages than the project
+ target language selected. For instance if the language pair of the
+ project is DE-FR, it can be still be of some help to have access to a
+ DE-EN translation, if there's no match in the DE-FR pair.
+
+
+
+ Orphan segments<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Orphan segments</secondary>
+ </indexterm>
+
+ The file project_save.tmx contains all the
+ segments that have been translated since you started the project. If you
+ modify the project segmentation or delete files from the source, some
+ matches may appear as orphan strings in
+ the Match Viewer: such matches refer to segments that do not exist any
+ more in the source documents, as they correspond to segments translated
+ and recorded before the modifications took place.
+
+
+
+
+ Reusing translation memories<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Import and export</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Reusing translation memories</secondary>
+ </indexterm>
+
+ Initially, that is when the project is created, the main TM of the
+ project, project_save.tmx is empty. This TM gradually
+ becomes filled during the translation. To speed up this process, existing
+ translations can be reused. If a given sentence has already been
+ translated once, and translated correctly, there is no need for it to be
+ retranslated. Translation memories may also contain reference
+ translations: multinational legislation, such as that of the European
+ Community, is a typical example.
+
+ When you create the target documents in an
+ OmegaT project, the translation memory of the
+ project is outputted in the form of three files in the root folder of your
+ OmegaT project (see the above description). You
+ can regard these three tmx files (-omegat.tmx,
+ -level1.tmx and -level2.tmx) as
+ an "export translation memory", i.e. as an export of your current
+ project's content in bilingual form.
+
+ Should you wish to reuse a translation memory from a previous
+ project (for example because the new project is similar to the previous
+ project, or uses terminology which might have been used before), you can
+ use these translation memories as "input translation memories", i.e. for
+ import into your new project. In this case, place the translation memories
+ you wish to use in the \tm or
+ \tm\auto folder of your new project: in the former
+ case you will get hits from these translation memories in the fuzzy
+ matches viewer, and in the latter case these TMs will be used to
+ pre-translate your source text.
+
+ By default, the \tm folder is below the project's root folder (e.g.
+ ...\MyProject\tm), but you can choose a different
+ folder in the project properties dialog if you wish. This is useful if you
+ frequently use translation memories produced in the past, for example
+ because they are on the same subject or for the same customer. In this
+ case, a useful procedure would be:
+
+
+
+ Create a folder (a "repository folder") in a convenient location
+ on your hard drive for the translation memories for a particular
+ customer or subject.
+
+
+
+
+
+ Whenever you finish a project, copy one of the three "export"
+ translation memory files from the root folder of the project to the
+ repository folder.
+
+
+
+
+
+ When you begin a new project on the same subject or for the same
+ customer, navigate to the repository folder in the
+ Project > Properties > Edit Project
+ dialog and select it as the translation memory
+ folder.
+
+
+
+ Note that all the tmx files in the /tm repository are parsed when
+ the project is opened, so putting all different TMs you may have on hand
+ into this folder may unnecessarily slow OmegaT down. You may even consider
+ removing those that are not required any more, once you have used their
+ contents to fill up the project-save.tmx file.
+
+
+ Importing and exporting translation memories
+
+ OmegaT supports imported tmx versions 1.1-1.4b (both level 1 and
+ level 2). This enables the translation memories produced by other tools
+ to be read by OmegaT. However, OmegaT does not fully support imported
+ level 2 tmx files (these store not only the translation, but also the
+ formatting). Level 2 tmx files will still be imported and their textual
+ content can be seen in OmegaT, but the quality of fuzzy matches will be
+ somewhat lower.
+
+ OmegaT follows very strict procedures when loading translation
+ memory (tmx) files. If an error is found in such a file, OmegaT will
+ indicate the position within the defective file at which the error is
+ located.
+
+ Some tools are known to produce invalid tmx files under certain
+ conditions. If you wish to use such files as reference translations in
+ OmegaT, they must be repaired, or OmegaT will report an error and fail
+ to load them. Fixes are trivial operations and OmegaT assists
+ troubleshooting with the related error message. You can ask the user
+ group for advice if you have problems.
+
+ OmegaT exports version 1.4 TMX files (both level 1
+ and level 2). The level 2 export is not fully compliant with the level 2
+ standard, but is sufficiently close and will generate correct matches in
+ other translation memory tools supporting TMX Level 2. If you only need
+ textual information (and not formatting information), use the level 1
+ file that OmegaT has created.
+
+
+
+
+ Pseudo-translated memory<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Pseudotranslation</secondary>
+ </indexterm>
+
+
+ Of interest for advanced users only!
+
+
+ Before segments get translated, you may wish to pre-process them or
+ address them in some other way than is possible with OmegaT. For example,
+ if you wish to create a pseudo-translation for testing purposes, OmegaT
+ enables you to create an additional tmx file that contains all segments of
+ the project. The translation in this tmx can be either
+
+
+
+ translation equals source (default)
+
+
+
+
+
+ translation segment is empty
+
+
+
+ The tmx file can be given any name you specify. A pseudo-translated
+ memory can be generated with the following command line parameters:
+
+ java -jar omegat.jar --pseudotranslatetmx=<filename>
+ [pseudotranslatetype=[equal|empty]]
+
+ Replace <filename> with the name of the
+ file you wish to create, either absolute or relative to the working
+ directory (the directory you start OmegaT
+ from). The second argument --pseudotranslatetype is
+ optional. Its value is either equal (default value, for
+ source=target) or empty (target segment is empty). You
+ can process the generated tmx with any tool you want. To reuse it in
+ OmegaT rename it to project_save.tmx
+ and place it in the omegat-folder of your
+ project.
+
+
+
+ Upgrading translation memories<indexterm class="singular">
+ <primary>Translation memories</primary>
+
+ <secondary>Upgrading to sentence segmentation</secondary>
+ </indexterm>
+
+ Very early versions of OmegaT were
+ capable of segmenting source files into paragraphs only and were
+ inconsistent when numbering formatting tags in HTML and Open Document
+ files. OmegaT 2.5 can detect and upgrade such
+ tmx files on the fly to increase fuzzy matching quality and leverage your
+ existing translation better, saving you the work of doing this
+ manually.
+
+ A project's tmx will be upgraded only once, and will be written in
+ upgraded form into the project-save.tmx; legacy tmx
+ files will be upgraded on the fly each time the project is loaded. Note
+ that in some cases changes in file filters in
+ OmegaT 2.5 may lead to totally different
+ segmentation; as a result, you will have to upgrade your translation
+ manually in such rare cases.
+
+
+
+
+ Source segmentation
+
+ Translation memory tools work with textual units called segments.
+ OmegaT has two ways to segment a text: by
+ paragraph or by sentence segmentation (also referred to as “rule-based
+ segmentation”). In order to select the type of segmentation, select
+
+
+ Project
+
+ Properties
+ Project
+
+ Properties...
+ from the main menu and tick or untick the check box
+ provided. Paragraph segmentation is advantageous in certain cases, such as
+ highly creative or stylistic translations in which the translator may wish
+ to change the order of entire sentences; for the majority of projects,
+ however, sentence segmentation is a choice to be preferred, since it
+ delivers better matches from previous translations. If sentence segmentation
+ has been selected, you can setup the rules by selecting
+
+ Project
+
+ Options
+ Options
+
+ Segmentation...
+ from the main menu.
+
+ Dependable segmentation rules are already available for many
+ languages, so it is likely that you will not need to get involved with
+ writing your own segmentation rules. On the other hand this functionality
+ can be very useful in special cases, where you can increase your
+ productivity by tuning the segmentation rules to the text to be
+ translated.
+
+ Warning: because the text will
+ segment differently after filter options have been changed, so you may have
+ to start translating from scratch. At the same time the previous valid
+ segments in the project translation memory will turn into orphan segments.
+ If you change segmentation options when a project is open, you must reload
+ the project in order for the changes to take effect.
+
+ OmegaT uses the following sequence of
+ steps:
+
+
+
+
+ Segmentation
+
+ Source level segmentation
+ Structure level segmentation
+
+
+ OmegaT first parses the text for
+ structure-level segmentation. During this process it is only the
+ structure of the source file that is used to produce segments.
+
+ For example, text files may be segmented on line breaks, empty
+ lines, or not be segmented at all. Files containing formatting
+ (OpenOffice.org documents, HTML documents, etc.) are segmented on the
+ block-level (paragraph) tags. Translatable object attributes in XHTML
+ or HTML files can be extracted as separate segments.
+
+
+
+
+
+ Segmentation
+
+ Sentence level segmentation
+ Sentence level segmentation
+
+
+ After segmenting the source file into structural units,
+ OmegaT will segment these blocks further
+ into sentences.
+
+
+
+
+
+ Segmentation rules<indexterm class="singular">
+ <primary>Segmentation</primary>
+
+ <secondary>Rules</secondary>
+ </indexterm>
+
+ The process of segmenting can be pictured as follows: the cursor
+ moves along the text, one character at a time. At each cursor position
+ rules, consisting of a Before and
+ After pattern, are applied in their given
+ order to see if any of the Before
+ patterns are valid for the text on the left and the corresponding
+ After pattern for the text on the right
+ of the cursor. If the rule matches, either the cursor moves on without
+ inserting a segment break (for an exception rule) or a new segment break
+ is created at the current cursor position (for the break rule).
+
+ The two types of rules behave as follows:
+
+
+
+
+ Segmentation
+
+ Rules
+
+ Break rule
+ Break rule
+
+
+ Separates the source text into segments. For example,
+ "Did it make sense? I was not sure." should be
+ split into two segments. For this to happen, there should be a break
+ rule for "?", when followed by spaces and a capitalized word. To
+ define a rule as a break rule, tick the Break/Exception check
+ box.
+
+
+
+
+
+
+
+ Segmentation
+
+ Rules
+
+ Exception rule
+ Exception rule
+
+
+ specify what parts of text should NOT be separated. In spite
+ of the period, "Mrs. Dalloway " should not be
+ split in two segments, so an exception rule should be established
+ for Mrs (and for Mr, for Dr, for prof etc), followed by a period. To
+ define a rule as an exception rule, leave the Break/Exception check
+ box unticked.
+
+
+
+
+ The predefined break rules should be sufficient for most European
+ languages and Japanese. In view of the flexibility, you may consider
+ defining more exception rules for your source language in order to provide
+ more meaningful and coherent segments.
+
+
+
+ Rule priority<indexterm class="singular">
+ <primary>Segmentation</primary>
+
+ <secondary>Rules priority</secondary>
+ </indexterm>
+
+ All segmentation rule sets for a matching language pattern are
+ active and are applied in the given order of priority, so rules for
+ specific language should be higher than default ones. For example, rules
+ for Canadian French (FR-CA) should be set higher than rules for French
+ (FR.*), and higher than Default (.*) ones. Thus, when translating from
+ Canadian French the rules for Canadian French - if any - will be applied
+ first, followed by the rules for French and lastly, by the Default
+ rules.
+
+
+
+ Creating a new rule<indexterm class="singular">
+ <primary>Segmentation</primary>
+
+ <secondary>Creating a new rule</secondary>
+
+ <seealso>Regular expressions</seealso>
+ </indexterm>
+
+ Major changes to the segmentation rules should be generally avoided,
+ especially after completion of the first draft, but minor changes, such as
+ the addition of a recognized abbreviation, can be advantageous.
+
+ In order to edit or expand an existing set of rules, simply click on
+ it in the top table. The rules for that set will appear in the bottom half
+ of the window.
+
+ In order to create an empty set of rules for a new language pattern
+ click Add in the upper half of the
+ dialog. An empty line will appear at the bottom of the upper table (you
+ may have to scroll down to see it). Change the name of the rule set and
+ the language pattern to the language concerned and its code (see for a list of language codes).
+ The syntax of the language pattern conforms to regular expression syntax.
+ If your set of rules handles a language-country pair, we advise you to
+ move it to the top using the Move Up
+ button.
+
+ Add the Before and After patterns. To check their syntax and their
+ applicability, it is advisable to use tools which allow you to see their
+ effect directly. See the chapter on Regular
+ expressions. A good starting point will always be the existing
+ rules.
+
+
+
+ <indexterm class="singular">
+ <primary>Segmentation</primary>
+
+ <secondary>Examples</secondary>
+ </indexterm>A few simple examples
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Intention
+
+ Before
+
+ After
+
+ Note
+
+
+
+
+
+ Set a segment after a period ('.') and before a
+ space
+
+ \.
+
+ \s
+
+ "\." means the character "." "\s" means any white space
+ character ((space, tab, new page etc.)
+
+
+
+ Do not segment after Mr.
+
+ Mr\.
+
+ \s
+
+ This an exception rule, so the rule check box must not be
+ ticked
+
+
+
+ Set a segment after "。" (Japanese period)
+
+ 。
+
+
+
+ Note that after is empty
+
+
+
+ Do not segment after M. Mr. Mrs. and Ms.
+
+ Mr??s??\.
+
+ \s
+
+ Exception rule - see the use of ? in regular
+ expressions
+
+
+
+
+
+
+
+
+ Regular expressions<indexterm class="singular">
+ <primary>Regular expressions</primary>
+
+ <seealso>Segmentation</seealso>
+
+ <seealso>Searching</seealso>
+ </indexterm>
+
+ The regular expressions (or regex for short) used in searches and
+ segmentation rules are those supported by Java. Should you need more
+ specific information, consult the Java
+ Regex documentation. See additional references and examples
+ below.
+
+
+ This chapter is intended for advanced users, who need to define
+ their own variants of segmentation rules or devise more complex and
+ powerful key search items.
+
+
+
+ Regex - Flags
+
+
+
+
+
+
+ The construct
+
+ ... matches the following
+
+
+
+
+
+ (?i)
+
+ Enables case-insensitive matching (by default, the pattern is
+ case-sensitive).
+
+
+
+
+
+
+ Regex - Character
+
+
+
+
+
+
+ The construct
+
+ ... matches the following
+
+
+
+
+
+ x
+
+ The character x, except the following...
+
+
+
+ \uhhhh
+
+ The character with hexadecimal value 0xhhhh
+
+
+
+ \t
+
+ The tab character ('\u0009')
+
+
+
+ \n
+
+ The newline (line feed) character ('\u000A')
+
+
+
+ \r
+
+ The carriage-return character ('\u000D')
+
+
+
+ \f
+
+ The form-feed character ('\u000C')
+
+
+
+ \a
+
+ The alert (bell) character ('\u0007')
+
+
+
+ \e
+
+ The escape character ('\u001B')
+
+
+
+ \cx
+
+ The control character corresponding to x
+
+
+
+ \0n
+
+ The character with octal value 0n (0 <= n <= 7)
+
+
+
+ \0nn
+
+ The character with octal value 0nn (0 <= n <=
+ 7)
+
+
+
+ \0mnn
+
+ The character with octal value 0mnn (0 <= m <= 3, 0
+ <= n <= 7)
+
+
+
+ \xhh
+
+ The character with hexadecimal value 0xhh
+
+
+
+
+
+
+ Regex - Quotation
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ \
+
+ Nothing, but quotes the following character. This is required
+ if you would like to enter any of the meta characters
+ !$()*+.<>?[\]^{|} to match as themselves.
+
+
+
+ \\
+
+ For example, this is the backslash character
+
+
+
+ \Q
+
+ Nothing, but quotes all characters until \E
+
+
+
+ \E
+
+ Nothing, but ends quoting started by \Q
+
+
+
+
+
+
+ Regex - Classes for Unicode blocks and categories
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ \p{InGreek}
+
+ A character in the Greek block (simple
+ block)
+
+
+
+ \p{Lu}
+
+ An uppercase letter (simple
+ category)
+
+
+
+ \p{Sc}
+
+ A currency symbol
+
+
+
+ \P{InGreek}
+
+ Any character except one in the Greek block
+ (negation)
+
+
+
+ [\p{L}&&[^\p{Lu}]]
+
+ Any letter except an uppercase letter (subtraction)
+
+
+
+
+
+
+ Regex - Character classes
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ [abc]
+
+ a, b, or c (simple class)
+
+
+
+ [^abc]
+
+ Any character except a, b, or c (negation)
+
+
+
+ [a-zA-Z]
+
+ a through z or A through Z, inclusive (range)
+
+
+
+
+
+
+ Regex - Predefined character classes
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ .
+
+ Any character (except for line terminators)
+
+
+
+ \d
+
+ A digit: [0-9]
+
+
+
+ \D
+
+ A non-digit: [^0-9]
+
+
+
+ \s
+
+ A whitespace character: [ \t\n\x0B\f\r]
+
+
+
+ \S
+
+ A non-whitespace character: [^\s]
+
+
+
+ \w
+
+ A word character: [a-zA-Z_0-9]
+
+
+
+ \W
+
+ A non-word character: [^\w]
+
+
+
+
+
+
+ Regex - Boundary matchers
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ ^
+
+ The beginning of a line
+
+
+
+ $
+
+ The end of a line
+
+
+
+ \b
+
+ A word boundary
+
+
+
+ \B
+
+ A non-word boundary
+
+
+
+
+
+
+ Regex - Greedy quantifiers
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ X?
+
+ X, once or not at all
+
+
+
+ X*
+
+ X, zero or more times
+
+
+
+ X+
+
+ X, one or more times
+
+
+
+
+
+
+ greedy quantifiers will match as much as they can. For example,
+ a+? will match the aaa in
+ aaabbb
+
+
+
+ Regex - Reluctant (non-greedy) quantifiers
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ X??
+
+ X, once or not at all
+
+
+
+ X*?
+
+ X, zero or more times
+
+
+
+ X+?
+
+ X, one or more times
+
+
+
+
+
+
+ non-greedy quantifiers will match as little as they can. For
+ example, a+? will match the first
+ a in aaabbb
+
+
+
+ Regex - Logical operators
+
+
+
+
+
+
+ The construct
+
+ ...matches the following
+
+
+
+
+
+ XY
+
+ X followed by Y
+
+
+
+ X|Y
+
+ Either X or Y
+
+
+
+ (XY)
+
+ XY as a single group
+
+
+
+
+
+
+ <indexterm class="singular">
+ <primary>Regular expressions</primary>
+
+ <secondary>Tools</secondary>
+ </indexterm>Regex tools and examples of use<indexterm class="singular">
+ <primary>Regular expressions</primary>
+
+ <secondary>Examples of use</secondary>
+ </indexterm>
+
+ A number of interactive tools are available to develop and test
+ regular expressions. They generally follow much the same pattern (for an
+ example from the Regular Expression Tester see below): the regular
+ expression (top entry) analyzes the search text (Text box in the middle) ,
+ yielding the hits, shown in the result Text box.
+
+
+ Regex Tester
+
+
+
+
+
+
+
+
+
+
+
+
+ See The Regex
+ Coach for Windows,Linux, FreeBSD versions of a stand-alone tool.
+ This is much the same as the above example.
+
+ A nice collection of useful regex cases can be found in
+ OmegaT itself (see Options > Segmentation).
+ The following list includes expressions you may find useful when searching
+ through the translation memory:
+
+
+ Regex - Examples of regular expressions in translations
+
+
+
+
+
+
+ Regular expression
+
+ Finds the following:
+
+
+
+
+
+ (\b\w+\b)\s\1\b
+
+ double words
+
+
+
+ [\.,]\s*[\.,]+
+
+ comma or a period, followed by spaces and yet another comma
+ or period
+
+
+
+ \. \s+$
+
+ extra spaces after the period at the end of the
+ line
+
+
+
+ \s+a\s+[aeiou]
+
+ English: words, beginning with vowels, should generally be
+ preceded by "an", not "a"
+
+
+
+ \s+an\s+[^aeiou]
+
+ English: the same check as above, but concerning consonants
+ ("a", not "an")
+
+
+
+ \s\s+
+
+ more than one space
+
+
+
+ \.[A-Z]
+
+ Period, followed by an upper-case letter - possibly a space
+ is missing between the period and the start of a new
+ sentence?
+
+
+
+
+
+
+
+
+ Searches<indexterm class="singular">
+ <primary>Searches</primary>
+ </indexterm>
+
+
+ Search window
+
+
+ Text search Window<indexterm class="singular">
+ <primary>Search window</primary>
+
+ <secondary>Example</secondary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The above search finds all target segments where two or more white
+ spaces - \s\s+ - occur.
+
+
+
+ Searching<indexterm class="singular">
+ <primary>Shortcuts</primary>
+
+ <secondary>Ctrl+F - Search</secondary>
+ </indexterm>
+
+ OmegaT provides a powerful range of
+ search functions. Open the Search window with
+ Ctrl
+
+ F
+ and enter the word or phrase you wish to search for in the
+ Search for box. Alternatively, in the Editor window, select a word or
+ phrase in the editing field (target text of the current segment) and hit
+
+ Ctrl
+
+ F
+ . The word or phrase is entered in the Search for box
+ automatically. You can have several Search windows open at the same
+ time, but close them when they are no longer needed so that they do not
+ clutter your desktop.
+
+
+
+ Search location
+
+ Searches are performed by default in both the source and target
+ sections of the project, but you can limit your search to just the
+ source or the target text. You may search in
+
+
+
+ the project only (default setting)
+
+
+
+
+
+ both the project and the reference translation memories in
+ /tm/ (check Search TMs)
+
+
+
+
+
+ a single file or a folder containing a set of files (check
+ Search files)
+
+
+
+ When searching through files (as opposed to translation memories),
+ OmegaT restricts the search to files in
+ source file formats. Consequently, although OmegaT is quite able to
+ handle tmx files, it does not include them in the
+ Search files search. If you turn on
+ Searches
+
+ Advanced Options
+ Advanced Options, you can combine the search
+ with the name of the author of the translation and time of the last
+ change made.
+
+
+
+
+ Using wild cards<indexterm class="singular">
+ <primary>Searches</primary>
+
+ <secondary>Using wild cards</secondary>
+ </indexterm>
+
+ In both exact and keyword searches, the wild card search characters
+ '*' and '?' can be used. To use wild cards, the regular expressions option
+ should not be selected, as '*' and '?' have special meaning in regular
+ expressions.
+
+
+
+ '*' matches zero or more characters, from the current position
+ in a given word to its end. The search term'run*'
+ for example would match words 'run',
+ 'runs' and 'running'.
+
+
+
+
+
+ '?' matches any single character. For instance, 'run?'
+ would match the word 'runs' and
+ 'runn' in the word
+ 'running'.
+
+
+
+ The matches will be displayed in bold blue.
+
+
+
+ Search methods<indexterm class="singular">
+ <primary>Searches</primary>
+
+ <secondary>Methods</secondary>
+ </indexterm>
+
+ Select the method using the radio buttons. You can choose between
+ two methods to search:
+
+
+
+ exact search
+
+
+ Search for segments containing the exact string you specified.
+ An exact search looks for a phrase, i.e. if several words are
+ entered, they are found only if they occur in exactly that sequence.
+ Searching for open file will thus find all
+ occurrences of the string open
+ file, but not file
+ opened or open input
+ file.
+
+
+
+
+ keyword search
+
+
+ Search for segments containing all keywords you specified, in
+ any order. Select keyword search to search for any number of
+ individual full words, in any order. OmegaT displays a list of all
+ segments containing all of the words specified. Keyword searches are
+ similar to a search "with all of the words" in an Internet search
+ engine such as Google (AND logic). Using keyword search with
+ open file will thus find all
+ occurrences of the string open
+ file, as well as file
+ opened, open input file, file
+ may not be safe to open, etc.
+
+
+
+
+ For either of these two methods you can select the following three
+ options:
+
+
+
+ case sensitive: the search will
+ be performed for the exact string specified; i.e. capitalization is
+ observed.
+
+
+
+ regular expressions: The search
+ string will be treated as a regular expression. A regular expression
+ search is a powerful way to look for instances of a string. It is
+ similar to a wild card search, but allows far more flexibility. The
+ regular expressions used in searches are those supported by Java. See
+ more in the chapter on regular Expressions.
+
+
+
+ search TMs: translation
+ memories in the tm folder are included in the
+ search.
+
+
+
+
+
+ Search results display
+
+ Pressing the search button after entering a string in the search
+ field displays all the segments in the project that include the entered
+ string. As OmegaT handles identical segments as
+ one single entity, only the first unique segment is shown. The segments
+ are displayed in order of appearance in the project. Translated segments
+ are displayed with the original text at the top and the translated text at
+ the bottom, untranslated segments are displayed as the source only.
+
+ Clicking on a segment opens it in the Editor for modifications. You
+ can then switch back to the Search window for the next segment found, for
+ instance to check and, if necessary, correct the terminology.
+
+ You may have several Search windows open at the same time. You can
+ quickly see their contents by looking at their title: it will contain the
+ search term used.
+
+
+
+
+ <indexterm class="singular">
+ <primary>Dictionaries</primary>
+ </indexterm>Dictionaries
+
+
+
+
+ How to download and install dictionaries<indexterm class="singular">
+ <primary>Dictionaries</primary>
+
+ <secondary>Downloading and installing</secondary>
+ </indexterm>
+
+ Dictionaries in OmegaT are based on the
+ StartDict Platform. To install the necessary files, proceed as
+ follows:
+
+
+
+ Search for the required language combination - for instance on
+ the
+ FreeDict
+
+ Dictionaries
+ StartDict Platform above or on FreeDict
+ Stardict
+
+ Dictionaries
+
+
+
+
+
+
+ Download the file - it should be a tarball
+ archive (extension tar.bz or
+ tar.bz2).
+
+
+
+
+
+ Use untar utility (or its equivalent, for instance
+ winrar in Windows) to extract its contents into the project
+ folder "Dictionary". There should be three files, with extensions
+ dz, idx and ifo.
+
+
+
+ Note that in addition to "source-target" dictionaries you can, using
+ the Dictionary feature, obtain access to information such as:
+
+
+
+
+ Webster
+
+ Dictionaries
+ Webster's Revised Unabridged Dictionary (1913)
+
+
+
+
+
+
+ Longman
+
+ Dictionaries
+ Longman Dictionary of Contemporary English
+
+
+
+
+
+
+ Britannica
+
+ Dictionaries
+ The Britannica Concise Encyclopedia
+
+
+
+
+
+ etc...
+
+
+
+ Some of the dictionaries have no strings attached - i.e. are "Free
+ to use", and others, like the selection above, are under the GPL license.
+ The following example shows Merriam Webster 10th dictionary "in
+ action":
+
+
+ <indexterm class="singular">
+ <primary>Dictionary</primary>
+
+ <secondary>Merriam Webster - figure</secondary>
+
+ <seealso>Dictionaries</seealso>
+ </indexterm>Merriam Webster dictionary - use
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ <indexterm class="singular">
+ <primary>Dictionaries</primary>
+
+ <secondary>Problems with</secondary>
+ </indexterm>Problems with dictionaries
+
+
+
+ Check that your dict files are in the correct folder (or in a subfolder
+ below it). Check in
+
+
+
+ Shortcuts
+
+ Ctrl+E - Project properties
+ Ctrl
+
+ E
+
+
+
+ Project
+
+ Properties
+ .
+
+
+
+
+
+ Does the folder contain three files of the same name, with
+ extensions ? If only one file is present, check its extension. If it
+ is tar.bz, you have forgotten to unpack (untar)
+ it.
+
+
+
+
+
+
+ Glossaries<indexterm class="singular">
+ <primary>Windows and panes in OmegaT</primary>
+
+ <secondary>Glossary pane</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Glossaries</primary>
+ </indexterm>
+
+ Glossaries are files created and updated manually for use in
+ OmegaT.
+
+ If an OmegaT project contains one or more
+ glossaries, any terms in the glossary which are also found in the current
+ segment will be automatically displayed in the Glossary viewer.
+
+ You define its location and name in the project properties dialog. The
+ extension must be .txt (if not, it will be added). The
+ location of the file must be within the /glossary
+ folder, but it can be in a deeper directory (e.g.,
+ glossary/sub/glossary.txt). The file does not need to
+ exist when setting it, it will be created (if necessary) when adding a
+ glossary entry. If the file already exists, not attempt is done to verify
+ the format or the character set of the file: the new entries will always be
+ in tab-separated format and UTF-8. As the existing content will not be
+ touched, damaged to an existing file would be limited.
+
+
+ Usage
+
+ To use an existing glossary, simply place it in the
+ Project files
+
+ Glossary subfolder
+ /glossary folder after creating the
+ project. OmegaT automatically detects glossary
+ files in this folder when a project is opened. Terms in the current
+ segment which OmegaT finds in the glossary
+ file(s) are displayed in the Glossary pane:
+
+
+ Glossary pane
+
+
+
+ Glossary pane
+
+
+
+
+
+
+
+
+
+
+
+
+ The word before the = sign is the source term, and its translation
+ is (or are) the words after =. The vocabulary entry can have a comment
+ added (see "transitive verb" for the second item). The glossary function
+ only finds exact matches with the glossary entry (e.g. does not find
+ inflected forms etc.). New terms can be added manually to the glossary
+ file(s) during translation (for example in a text editor), but newly added
+ terms will not be recognized until the project is reloaded.
+
+ The source term does not have to be a single-word item, as the next
+ example shows:
+
+
+ multiple words entries in glossaries - example<indexterm class="singular">
+ <primary>Glossary pane - multiple-words entries</primary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+ The underlined item "pop-up menu" can be found in the glossary pane
+ as "pojavni menu". Highlighting it in the Glossary pane and then
+ rightclicking insets at the cursor position in the target
+ segment.
+ Note that in the above case, this is just half (or even less) of
+ the story, as the target language (Slovenian) uses declension. So the
+ inserted "pojavni meni" has to be changed to "pojavnem meniju". In
+ other words, typing the term correctly without bothering with
+ highlighting and rightclicking is probably faster.
+
+
+
+
+ <indexterm class="singular">
+ <primary>Glossaries</primary>
+
+ <secondary>File format</secondary>
+ </indexterm>File format<indexterm class="singular">
+ <primary>Project files</primary>
+
+ <secondary>User files</secondary>
+
+ <seealso>Glossaries</seealso>
+ </indexterm>
+
+ Glossary files are simple plain text files containing three-column,
+ tab-delimited lists with the source and target terms in the first and
+ second columns respectively. The third column can be used for additional
+ information. You can have entries with the target column missing, i.e.
+ just containing the source term and the comment.
+
+ Glossary files can be either in system default encoding (and
+ indicated by the extension .tab) or in UTF-8 (the extension .utf8). The
+ Unicode encoding (UTF8) is preferred for obvious reasons. Also supported
+ is the CSV format. This format is the same as the tab separated one:
+ source term, target term. Comment fields are separated by a comma ','.
+ Strings can be enclosed by quotes ", which allows having a comma inside a
+ string:
+
+ "This is a source term, which contains a comma","c'est un
+ terme, qui contient une virgule"
+
+ In addition to the plain text format, TBX format
+ Glossaries
+
+ TBX format
+ is also supported. TBX - Term Base eXchange - is the open,
+ XML-based standard for exchanging structured terminological data, TBX has
+ been approved as an international standard by LISA
+ LISA -
+
+ File format
+ and ISO. If you have an existing terminology handling
+ system - MultiTerm for example - it is quite possible it offers the export
+ of terminology data via TBX format. Microsoft
+ Terminology Collection
+ Glossaries
+
+ Microsoft Terminology collection
+ can be downloaded in nearly 100 languages and can serve as
+ a cornerstone IT glossary.
+
+
+
+ How to create glossaries<indexterm class="singular">
+ <primary>Glossaries</primary>
+
+ <secondary>Creating a glossary</secondary>
+ </indexterm>
+
+ The project setting allows one can enter a name for a writable
+ glossary file (see beginning of this chapter). Adding new entries is done
+ by using the keyboard shortcut Ctrl+Shift+G . A dialog
+ opens, allowing you to enter the source term, target term and any comments
+ you may have:
+
+
+
+
+
+
+
+
+
+
+
+ The contents of glossary files are kept in memory and are loaded
+ when the project is opened or reloaded. Updating a glossary file is thus
+ rather simple: press Ctrl+Shift+G and enter the new
+ term, its translation and any comments you may have (ensuring you press
+ tab between the fields) and save the file. The contents of the glossary
+ pane will be updated accordingly.
+
+
+ Glossaries
+
+ Location of the writable glossary file
+ The location of the writable glossary file can be set in the
+ Project > Properties ... dialog. The recognized extensions are
+ TXT and UTF8
+
+ Note: Of course there are other
+ ways and means to create a simple file with tab delimited entries. Nothing
+ speaks against using Notepad++ on Windows, GEdit on Linux for instance or
+ some spreadsheet program for this purpose: any application, that can
+ handle UTF8 and that can show white space (so that you do not miss the
+ required TAB characters) can be used.
+
+
+
+ <indexterm class="singular">
+ <primary>Glossaries</primary>
+
+ <secondary>Trados MultiTerm</secondary>
+ </indexterm>Using Trados MultiTerm
+
+ Data exported from Trados MultiTerm can be used as
+ OmegaT glossaries without further modification,
+ provided they are given the file extension .tab and
+ the source and target term fields are the first two fields respectively.
+ If you export using the system option "Tab-delimited export", you will
+ need to delete the first 5 columns (Seq. Nr, Date created etc). The newer
+ versions of MultiTerm support exporting to TBX format.
+
+
+
+ <indexterm class="singular">
+ <primary>Glossaries</primary>
+
+ <secondary>Problems with glossaries</secondary>
+ </indexterm>Common glossary problems
+
+ Problem: No glossary terms are displayed -
+ possible causes:
+
+
+
+ No glossary file found in the "glossary" folder.
+
+
+
+
+
+ The glossary file is empty.
+
+
+
+
+
+ The items are not separated with a TAB character.
+
+
+
+
+
+ The glossary file does not have the correct extension (.tab or
+ .utf8).
+
+
+
+
+
+ There is no EXACT match between the glossary entry and the
+ source text in your document - for instance plurals.
+
+
+
+
+
+ The glossary file does not have the correct encoding.
+
+
+
+
+
+ There are no terms in the current segment which match any terms
+ in the glossary.
+
+
+
+
+
+ One or more of the above problems may have been fixed, but the
+ project has not been reloaded.
+
+
+
+ Problem: In the glossary pane, some characters
+ are not displayed properly
+
+
+
+ ...but the same characters are displayed properly in the Editing
+ pane: the extension and the file encoding do not match.
+
+
+
+
+
+
+ Machine Translation<indexterm class="singular">
+ <primary>Machine Translation</primary>
+ </indexterm>
+
+
+ Introduction<indexterm class="singular">
+ <primary>Machine Translation</primary>
+
+ <secondary>Introduction</secondary>
+ </indexterm>
+
+ As opposed to user-generated translation memories (as in the case of
+ OmegaT) Machine translation (MT) tools use
+ rule-based linguistic tools to create a translation of the source segment
+ without the need for a translation memory. Statistical learning
+ techniques, based on source and target texts, are used to build a
+ translation model. Machine translation services have been achieving good
+ and steadfastly improving results in research evaluations.
+
+ To activate any of the Machine Translation services, go to
+ Options > Machine Translate ... and activate
+ the service desired. Note that they are all web-based: you will have to be
+ on-line if you want to use them.
+
+
+
+ Google Translate<indexterm class="singular">
+ <primary>Machine Translation</primary>
+
+ <secondary>Google Translate</secondary>
+ </indexterm>
+
+ Google Translate is a payable service offered by Google, for
+ translating sentences, web sites and complete texts between an
+ ever-growing number of languages. At the time of writing the list includes
+ more than 50 languages, from Albanian to Yiddish, including of course all
+ the major languages. The current version of the service is based on usage,
+ with the price of 20 USD per million characters at the time of writing.
+
+
+ Important: Google Translate API v2
+ requires billing information for all accounts before you can start using
+ the service (see Pricing
+ and Terms of Service for more). To identify yourself as a valid
+ user for the Google services, you use your private unique key sent to you
+ by Google, when you have registered for the service. See chapter Installing and Running,
+ section Launch command arguments, for details on how to add this key to
+ the OmegaT environment.
+
+ The quality of the Google Translate translation depends on one side
+ on the reservoir of target-language texts and the availability of their
+ bilingual versions, on the other hand on the quality of the models built.
+ It is pretty much certain that while the quality may be insufficient in
+ some cases, it will definitely get better with time and not worse.
+
+
+
+ <application>OmegaT</application> users and Google
+ Translate
+
+ The OmegaT user is not forced to use
+ Google Translate. If used, neither the user's decision to accept the
+ translation nor the final translation are made available to Google. The
+ following window shows an example of a) the English source b) Spanish and
+ c) Slovenian Google Translate translation.
+
+
+ Google Translate - example
+
+
+
+
+
+
+
+
+
+
+
+
+ The Spanish translation is better than the Slovenian. Note
+ interesar and navegar in
+ Spanish, are correctly translated as the verbs interest and sail
+ respectively. In the Slovenian version both words have been translated as
+ nouns. It is actually quite probable that the Spanish translation is based
+ at least partially on the actual translation of the book.
+
+ Once you have activated the service, a suggestion for the
+ translation will appear in the Machine Translate pane every time a new
+ source segment is opened. If you find the suggestion acceptable, press
+
+
+ Shortcuts
+
+ Ctrl+M - Machine Translate
+ Ctrl
+
+ M
+ to replace the target part of the opened segment with the
+ suggestion. In the above segment, for instance,
+ Ctrl
+
+ M
+ would replace the Spanish version with the Slovenian
+ suggestion.
+
+ If you do not wish OmegaT to send your
+ source segments to Google to get translated, untick the Google Translate
+ menu entry in Options.
+
+ Note that nothing but your source segment is sent to the MT service.
+ The online version of Google Translate allows the user to correct the
+ suggestion and send the corrected segment in. This feature, however, is
+ not implemented in OmegaT.
+
+
+
+ Belazar<indexterm class="singular">
+ <primary>Machine Translation</primary>
+
+ <secondary>Belazar</secondary>
+ </indexterm>
+
+ Belazar is a
+ Machine language translation tool for the Russian-Belarusian language
+ pair.
+
+
+
+ Apertium<indexterm class="singular">
+ <primary>Machine Translation</primary>
+
+ <secondary>Apertium</secondary>
+ </indexterm>
+
+ Apertium is a
+ free/open-source machine translation platform, initially aimed at
+ related-language pairs, like CA, ES, GA, PT, OC and FR but recently
+ expanded to deal with more divergent language pairs (such as
+ English-Catalan). Check the web site for the latest list of implemented
+ language pairs.
+
+ The platform provides
+
+
+
+ a language-independent machine translation engine
+
+
+
+ tools to manage the linguistic data necessary to build a machine
+ translation system for a given language pair and
+
+
+
+
+
+ linguistic data for a growing number of language pairs
+
+
+
+ Apertium uses a shallow-transfer machine translation engine which
+ processes the input text in stages, as in an assembly line: de-formatting,
+ morphological analysis, part-of-speech disambiguation, shallow structural
+ transfer, lexical transfer, morphological generation, and
+ re-formatting.
+
+ It is possible to use Apertium to build machine translation systems
+ for a variety of language pairs; to that end, Apertium uses simple
+ XML-based standard formats to encode the linguistic data needed (either by
+ hand or by converting existing data), which are compiled using the
+ provided tools into the high-speed formats used by the engine.
+
+
+
+ Machine translation - trouble shooting<indexterm class="singular">
+ <primary>Machine Translation</primary>
+
+ <secondary>Troubleshooting</secondary>
+ </indexterm>
+
+ If there's nothing appearing in the Machine Translate pane, then
+ check the following:
+
+
+
+ Are you online? You need to be online to be able to use an MT
+ tool.
+
+
+
+
+
+ What is the language pair you need? Check if the selected
+ service offers it.
+
+
+
+ Google Translate does not work: check Options > Machine
+ Translate: the Google Translate service is labelled Google Translate
+ V2. The older version of the service, labelled "Google Translate" and
+ available in outdated OmegaT versions, is deprecated and does not work
+ anymore.
+
+
+
+ "Google Translate returned HTTP response code: 403 ...": check
+ that the 38-characters key, entered in the pinfo.list file, is
+ correct. Check that Translate API
+ service has been activated.
+
+
+
+
+
+
+ Spell checker<indexterm class="singular">
+ <primary>Spell checker</primary>
+ </indexterm>
+
+ OmegaT has a built-in spell checker based on the spelling checker used
+ in OpenOffice.org, Firefox and Thunderbird. It is consequently able to use
+ the huge range of free spelling dictionaries available for these
+ applications.
+
+
+ Installing spelling dictionaries
+
+ Before the spell check function can be used, a suitable dictionary
+ or dictionaries (i.e. for your target language) must be installed. To
+ install spelling dictionaries, follow this procedure:
+
+
+
+ In your file manager, create a new folder in a suitable location
+ in which to store spelling dictionaries (D:\Translations\spellcheckers
+ in the example below).
+
+
+
+
+
+ In OmegaT, select
+ Menu Options
+
+ Spell checking..
+ Options > Spell
+ Checking, then click Choose
+ beside the Dictionary file folder field. Navigate to and
+ select the folder you created for dictionaries.
+
+
+
+
+
+ Place the dictionary files you wish to use in this folder. There
+ are essentially two ways in which you can do this. You can either copy
+ files manually, i.e. from elsewhere on your system, using your file
+ manager; or you can use OmegaT's "Install new
+ dictionary" function to provide a list of available
+ dictionaries to select from. Note that the "Install" function requires
+ an Internet connection. The selected languages will then be installed
+ and will eventually appear in your spell checker setup window (this
+ may take a while).
+
+
+
+ Copying the files manually makes sense if you already have suitable
+ dictionary files on your system, for instance as part of your
+ OpenOffice.org or Thunderbird installation. It is simpler, however, to
+ look foir dictionaries online, using the URL of
+ online dictionaries field:
+
+
+ <indexterm class="singular">
+ <primary>Spell checker setup</primary>
+
+ <secondary>Spell checker setup - figure</secondary>
+ </indexterm>Spellchecker setup
+
+
+
+
+
+
+
+
+
+
+
+
+ Clicking on Install new dictionary button
+ will open the Dictionary installer window, where you can select the
+ dictionaries zou want to install.Make sure the language code of your
+ target files corresponds to the dictionary's language code: an FR-FR
+ dictionary will not work with an FR target setting. You need to change the
+ setting to FR-FR to have the spell checker recognize the correct
+ dictionary for your target. Look for files with the name, indicating the
+ language used and having extensions aff and
+ dic.
+
+
+
+ Using spelling dictionaries
+
+ There is no need to instruct OmegaT to use a particular spelling
+ dictionary; OmegaT will use the correct language dictionary based upon the
+ language codes of your project. Check however that the language codes are
+ exactly the same: an FR-FR dictionary will not work with an FR target
+ setting, for example. If necessary, edit the file names of the dictionary
+ or change your project's language settings.
+
+ To enable the spell checker, select Options > Spell
+ Checking and tick the Automatically check the
+ spelling of text checkbox (see above).
+
+
+ <indexterm class="singular">
+ <primary>Spell checker</primary>
+
+ <secondary>Spell checker - figure</secondary>
+ </indexterm>Spellchecker in action
+
+
+
+
+
+
+
+
+
+
+
+
+ Right-clicking on an underlined word (Artund in the figure above)
+ opens a drop-down menu listing suggestions for the correction (Art und).
+ You can also instruct the spell checker to ignore all the occurrences of
+ the mis-spelled word, or add it to the dictionary.
+
+
+
+ Hints<indexterm class="singular">
+ <primary>Spell checker</primary>
+
+ <secondary>Hints</secondary>
+ </indexterm>
+
+ If the spell checker is not working, then make sure first that the
+ check box "Automatically check the spelling of text"
+ in the spell checker dialog (Options > Spell
+ checking...) is checked.
+
+ Also check that the target language code of your project against the
+ available vocabularies in the setup window. The spell checker uses the
+ target language code to determine the language to be used : if the target
+ language is Brazilian Portuguese (PT_BR), the subfolder with vocabularies
+ must contain the two vocabulary files, called
+ pt_br.aff and pt_br.dic.
+
+ If you have already translated a large body of text, and then
+ realize the target language code of the project does not match the spell
+ checker's language code (you specified pt_BR as the language, but there
+ are no pt_BR vocabularies, for instance) you can simply copy the two
+ corresponding files and rename them (e.g. from
+ pt_PT.arr and pt_PT.dic to
+ pt._BR.arr and pt_BR.dic). Of
+ course it is much wiser, to take a short break and download the correct
+ versions of the spell checker.
+
+ Note that Remove physically removes the
+ selected vocabularies. If they are used bz some other application on your
+ system, they will disappear from that application, too. If, for whatever
+ reason, you need to do this from time to time, it may make sense to copy
+ the files involved to a different folder, reserved just for use by
+ OmegaT.
+
+
+
+
+ Miscellaneous subjects<indexterm class="singular">
+ <primary>Miscellanea</primary>
+ </indexterm>
+
+
+ <application><indexterm class="singular">
+ <primary>OmegaT console mode</primary>
+
+ <seealso>Miscellanea</seealso>
+ </indexterm>OmegaT</application> Console Mode<indexterm class="singular">
+ <primary>Miscellanea</primary>
+
+ <secondary>OmegaT console mode</secondary>
+ </indexterm>
+
+
+ Of interest for advanced users only!
+
+
+ The purpose of the console (i.e. command line) mode is to permit the
+ use of OmegaT as translation tool in a
+ scripting environment. When launched in console mode, no GUI is loaded (
+ it will work therefore on any console) and the given project is
+ automatically translated. An example would be a software project, with GUI
+ localized in a number of languages. Using the console mode, one can make
+ generating a localized interface a part of the build process.
+
+
+ Prerequisites
+
+ To run OmegaT, a valid OmegaT project must be available. The
+ location is irrelevant, since it must be specified explicitly on the
+ command-line at launch..
+
+ If you need non-standard settings, the corresponding configuration
+ files (filters.conf and
+ segmentation.conf) must be present. This can be
+ achieved in two ways:
+
+
+
+ Run OmegaT normally (with the GUI)
+ and set the settings. If you start OmegaT
+ in console mode, it will use the settings you configured.
+
+
+
+ If you are unable to run OmegaT
+ normally (no graphical environment available): copy the settings
+ files from some other OmegaT installation
+ on another machine to a specific directory. The location does not
+ matter, since you can add it to the command line at launch (see
+ below). The relevant files filters.conf and
+ segmentation.conf can be found in the user home
+ directory (E.g. C:\Documents and
+ Settings\%User%\OmegaT under
+ Windows, %user%/.omegat/ under Linux)
+
+
+
+
+
+ Launching OmegaT in console mode
+
+ To launch OmegaT in console mode, additional parameters must be
+ specified at launch. The most important of these is
+ <project-dir>, and
+ optionally--config-dir=<config-dir>.
+ Example:
+
+ $> java -jar OmegaT.jar
+ /path/to/project \
+
+ --config-dir=/path/to/config-files/ \
+
+ --mode=console-translate \
+
+ --source-pattern={regexp} \
+
+ --tag-validation=[block|warn]
+
+ Explanation:
+
+
+
+ <project-dir> tells
+ OmegaT where to find the project to be
+ translated. If given, OmegaT launches in
+ console mode and translates the given project.
+
+
+
+
+
+ --config-dir=<config-dir> enables
+ OmegaT to be instructed in which folder the configuration files are
+ stored. If not specified, OmegaT reverts to default values (the
+ OmegaT folder in the user home folder, or if not available: the
+ current working directory).
+
+
+
+
+
+ --mode=console-translate
+ OmegaT launches in console mode and
+ translates the given project
+
+
+
+ --source-pattern={regexp} The files to be
+ translated can be specified this way. Here is an example of the
+ regular expression: test\.html
+
+
+
+ --tag-validation=[abort|warn] On abort,
+ the program is aborted when tag validation finds errors. On warn the
+ errors are printed but the program continues. In all other cases no
+ tag validation is done.
+
+
+
+
+
+ Quiet option
+
+ An extra command line parameter specific to console mode:
+ --quiet. In the quiet mode, less info is logged to
+ the screen. The messages you would usually find in the status bar are
+ not displayed.
+
+ Usage: java -jar OmegaT.jar
+ /path/to/project --mode=console-translate --quiet
+
+
+
+ Tag validation option
+
+ Another extra command line parameter specific to console mode:
+ --tag-validation=[abort|warn]. When this parameter is
+ added, tag validation is done prior to translation/aligning. If the
+ value is abort, then on tag errors the errors are
+ printed and the program stops. If the value is warn
+ then the errors are printed but OmegaT continues.
+
+ Usage: java -jar OmegaT.jar
+ /path/to/project --mode=console-translate
+ --tag-validation=abort
+
+
+
+
+ Automatic Java Properties Aligner<indexterm class="singular">
+ <primary>Miscellanea</primary>
+
+ <secondary>Automatic aligner for Java properties</secondary>
+
+ <seealso>Miscelanea</seealso>
+ </indexterm>
+
+ OmegaT can align Java .properties in console mode. If you have the
+ source and the target Properties files for one and the same contents in
+ your language pair, this procedure will create a corresponding tmx file
+ for these contents. Usage:
+
+ java -jar OmegaT.jar --mode=console-align /my-project-dir
+ --alignDir=/translatedFiles/
+
+ alignDir must contain a translation in the
+ target language of the project. E.g., if the project is EN->FR,
+ alignDir must contain a bundle ending with _fr. The resulting tmx is
+ stored in the omegat folder under the name
+ align.tmx.
+
+
+
+ Font settings<indexterm class="singular">
+ <primary>Miscellanea</primary>
+
+ <secondary>Font settings</secondary>
+ </indexterm>
+
+ In this dialog one can define the font used by
+ OmegaT in the following windows:
+
+
+
+ OmegaT main window (Editor, Match
+ viewer, Glossary viewer)
+
+
+
+
+
+ Search window
+
+
+
+
+
+ Tag validation window
+
+
+
+ The dialog can be accessed via the
+ Menu Options
+
+ Font...
+
+ Options
+
+ Font...
+ item in the Main menu. The dialog contains:
+
+
+
+ Font: drop-down to select one
+ of the fonts available on your machine
+
+
+
+
+
+ Size: edit to change font
+ size
+
+
+
+
+
+ Sample text: field for
+ immediate preview of the selected font
+
+
+
+ Note: In some cases it may take
+ quite some time for OmegaT to update the display after the font setting
+ has been changed. This is especially the case when a large file containing
+ many segments is open in the editor, and/or slow hardware is used. Note
+ also that some fonts behave better for some language pairs than for
+ others. In particular, if you are translating between two languages with
+ different alphabets/writing systems (such as Russian and Japanese), select
+ a font that can be used for both.
+
+
+
+ Preventing data loss<indexterm class="singular">
+ <primary>Miscellanea</primary>
+
+ <secondary>Preventing data Loss</secondary>
+ </indexterm>
+
+ OmegaT is a robust application. However,
+ you should take precautions against data loss when using
+ OmegaT, just as with any other application.
+ When you translate your files, OmegaT stores
+ all your progress in the translation memory
+ project_save.tmx that resides in the project's
+ /omegat subfolder.
+
+ OmegaT also backs up the translation memory to
+ project_save.tmx.YEARMMDDHHNN.bak in the same subfolder each time a
+ project is opened or reloaded. YEAR is the 4-digit year, MM is the month,
+ DD the day of the month, and HH and NN are the hours and minutes when the
+ previous translation memory was saved.
+
+ If you believe that you have lost translation data, you can use the
+ following procedure to restore the project to its most recently saved
+ state, usually not older than approximately 10 minutes or so:
+
+
+
+ close the project
+
+
+
+ rename the current project_save.tmx file
+ (e.g. to project_save.tmx.temporary)
+
+
+
+ select the backup translation memory that is the most likely to
+ contain the data you are looking for
+
+
+
+ rename it project_save.tmx
+
+
+
+ open the project
+
+
+
+ To avoid losing important data:
+
+
+
+ Make regular copies of the file /omegat/project_save.tmx to
+ backup media, such as CD or DVD.
+
+
+
+ Until you are familiar with OmegaT,
+ create translated files at regular intervals and check that the
+ translated file contains the latest version of your
+ translation.
+
+
+
+ Take particular care when making changes to the files in
+ /source while in the middle of a project. If the
+ source file is modified after you have begun translating,
+ OmegaT may be unable to find a segment that
+ you have already translated.
+
+
+
+
+
+ Use these Help texts to get started. Should you run into
+ problems, post a message in the OmegaT
+ user group. Do not hesitate to post in the language you feel
+ the most familiar with.
+
+
+
+
+
+
+ <application><indexterm class="singular">
+ <primary>OmegaT on the web</primary>
+ </indexterm>OmegaT</application> on the web
+
+
+ <application>OmegaT</application> sites and
+ <application>OmegaT</application> SourceForge project<indexterm class="singular">
+ <primary>OmegaT on the web</primary>
+
+ <secondary>SourceForge Project</secondary>
+ </indexterm>
+
+ The
+ OmegaT web site contains links to
+ numerous OmegaT resources. User support is
+ provided on a volunteer basis at the OmegaT
+ Yahoo User Group. The FAQ
+ is a good starting point for finding answers to questions you may
+ have. For the latest version of OmegaT, refer to the downloads page at
+ www.omegat.org. You can also file bug
+ reports and requests
+ for enhancements.
+
+
+
+ Bug reports<indexterm class="singular">
+ <primary>OmegaT on the web</primary>
+
+ <secondary>Reporting bugs</secondary>
+ </indexterm>
+
+ Remember that every good bug report needs just three things:
+
+
+
+ Steps to reproduce
+
+
+
+ What you expected to see
+
+
+
+ What you saw instead
+
+
+
+ More can be found in the Painless
+ Bug Tracking article by Joel Spolsky.
+
+ You should add copies of files, portions of the log, screenshots, and
+ anything else that you think will help the developers to find and fix your
+ bug. Note that bug reports and requests for enhancements are publicly
+ visible, so you should not add any sensitive files. If you wish to keep
+ track of what is happening to the report, register as a SourceForge user,
+ login and file a bug report or simply click Monitor at the top of the
+ report.
+
+
+
+ Contributing to <application>OmegaT</application> project<indexterm class="singular">
+ <primary>OmegaT on the web</primary>
+
+ <secondary>Contributing to OmegaT</secondary>
+ </indexterm>
+
+ To contribute to
+ OmegaT:
+
+ first join the user group (via web or
+ by sending an email to OmegaT-subscribe@yahoogroups.com).
+ To get involved in the OmegaT development
+ effort you can join the developer group, via the web or by sending an
+ email to omegat-development-request@lists.sourceforge.net
+ with "subscribe" as the subject line.
+
+ To translate
+ OmegaT's user interface, user manual or other
+ related documents:
+
+ first read the Localizing
+ and Customizing OmegaT guide, and join
+ the OmegaT translators' group via web or by
+ sending an email to omegat-l10n-request@lists.sourceforge.net
+ with subject "subscribe".
+
+
+ OmegaT on the web
+
+ Development, Localizing
+
+
+ To support the OmegaT project financially
+ OmegaT on the web
+
+ Financial support
+
+
+ If you would like to help support the continued development of
+ OmegaT, it would be very much appreciated - click on this link to go to
+ the
+ OmegaT PayPal account.
+
+
+ OmegaT on the web
+
+ Donating to OmegaT
+
+
+
+
+
+ Languages - ISO 639 code list
+ <indexterm class="singular">
+ <primary>Languages</primary>
+ </indexterm>
+ <indexterm class="singular">
+ <primary>ISO language codes</primary>
+ </indexterm>
+ <indexterm class="singular">
+ <primary>Project</primary>
+ <secondary>Properties</secondary>
+ <seealso>Languages</seealso>
+ </indexterm>
+
+
+ Please check the
+ ISO 639 Code Tables for further and up-to-date information about
+ language codes.
+
+
+ ISO 639-1/639-2 Language code list
+
+
+
+
+
+
+ Language name
+ ISO 639-1
+ ISO 639-2
+
+
+
+
+ Abkhaz
+ ab
+ abk
+
+
+ Afar
+ aa
+ aar
+
+
+ Afrikaans
+ af
+ afr
+
+
+ Akan
+ ak
+ aka
+
+
+ Albanian
+ sq
+ sqi
+
+
+ Amharic
+ am
+ amh
+
+
+ Arabic
+ ar
+ ara
+
+
+ Aragonese
+ an
+ arg
+
+
+ Armenian
+ hy
+ hye
+
+
+ Assamese
+ as
+ asm
+
+
+ Avaric
+ av
+ ava
+
+
+ Avestan
+ ae
+ ave
+
+
+ Aymara
+ ay
+ aym
+
+
+ Azerbaijani
+ az
+ aze
+
+
+ Bambara
+ bm
+ bam
+
+
+ Bashkir
+ ba
+ bak
+
+
+ Basque
+ eu
+ eus
+
+
+ Belarusian
+ be
+ bel
+
+
+ Bengali
+ bn
+ ben
+
+
+ Bihari
+ bh
+ bih
+
+
+ Bislama
+ bi
+ bis
+
+
+ Bosnian
+ bs
+ bos
+
+
+ Breton
+ br
+ bre
+
+
+ Bulgarian
+ bg
+ bul
+
+
+ Burmese
+ my
+ mya
+
+
+ Catalan
+ ca
+ cat
+
+
+ Chamorro
+ ch
+ cha
+
+
+ Chechen
+ ce
+ che
+
+
+ Chichewa, Chewa, Nyanja
+ ny
+ nya
+
+
+ Chinese
+ zh
+ zho
+
+
+ Chuvash
+ cv
+ chv
+
+
+ Cornish
+ kw
+ cor
+
+
+ Corsican
+ co
+ cos
+
+
+ Cree
+ cr
+ cre
+
+
+ Croatian
+ hr
+ hrv
+
+
+ Czech
+ cs
+ ces
+
+
+ Danish
+ da
+ dan
+
+
+ Divehi, Dhivehi, Maldivian
+ dv
+ div
+
+
+ Dutch
+ nl
+ nld
+
+
+ Dzongkha
+ dz
+ dzo
+
+
+ English
+ en
+ eng
+
+
+ Esperanto
+ eo
+ epo
+
+
+ Estonian
+ et
+ est
+
+
+ Ewe
+ ee
+ ewe
+
+
+ Faroese
+ fo
+ fao
+
+
+ Fijian
+ fj
+ fij
+
+
+ Finnish
+ fi
+ fin
+
+
+ French
+ fr
+ fra
+
+
+ Fula, Fulah, Pulaar, Pular
+ ff
+ ful
+
+
+ Galician
+ gl
+ glg
+
+
+ Georgian
+ ka
+ kat
+
+
+ German
+ de
+ deu
+
+
+ Greek, Modern
+ el
+ ell
+
+
+ Guaraní
+ gn
+ grn
+
+
+ Gujarati
+ gu
+ guj
+
+
+ Haitian, Haitian Creole
+ ht
+ hat
+
+
+ Hausa
+ ha
+ hau
+
+
+ Hebrew (modern)
+ he
+ heb
+
+
+ Herero
+ hz
+ her
+
+
+ Hindi
+ hi
+ hin
+
+
+ Hiri Motu
+ ho
+ hmo
+
+
+ Hungarian
+ hu
+ hun
+
+
+ Interlingua
+ ia
+ ina
+
+
+ Indonesian
+ id
+ ind
+
+
+ Interlingue
+ ie
+ ile
+
+
+ Irish
+ ga
+ gle
+
+
+ Igbo
+ ig
+ ibo
+
+
+ Inupiaq
+ ik
+ ipk
+
+
+ Ido
+ io
+ ido
+
+
+ Icelandic
+ is
+ isl
+
+
+ Italian
+ it
+ ita
+
+
+ Inuktitut
+ iu
+ iku
+
+
+ Japanese
+ ja
+ jpn
+
+
+ Javanese
+ jv
+ jav
+
+
+ Kalaallisut, Greenlandic
+ kl
+ kal
+
+
+ Kannada
+ kn
+ kan
+
+
+ Kanuri
+ kr
+ kau
+
+
+ Kashmiri
+ ks
+ kas
+
+
+ Kazakh
+ kk
+ kaz
+
+
+ Khmer
+ km
+ khm
+
+
+ Kikuyu, Gikuyu
+ ki
+ kik
+
+
+ Kinyarwanda
+ rw
+ kin
+
+
+ Kirghiz, Kyrgyz
+ ky
+ kir
+
+
+ Komi
+ kv
+ kom
+
+
+ Kongo
+ kg
+ kon
+
+
+ Korean
+ ko
+ kor
+
+
+ Kurdish
+ ku
+ kur
+
+
+ Kwanyama, Kuanyama
+ kj
+ kua
+
+
+ Latin
+ la
+ lat
+
+
+ Luxembourgish, Letzeburgesch
+ lb
+ ltz
+
+
+ Luganda
+ lg
+ lug
+
+
+ Limburgish, Limburgan, Limburger
+ li
+ lim
+
+
+ Lingala
+ ln
+ lin
+
+
+ Lao
+ lo
+ lao
+
+
+ Lithuanian
+ lt
+ lit
+
+
+ Luba-Katanga
+ lu
+ lub
+
+
+ Latvian
+ lv
+ lav
+
+
+ Manx
+ gv
+ glv
+
+
+ Macedonian
+ mk
+ mkd
+
+
+ Malagasy
+ mg
+ mlg
+
+
+ Malay
+ ms
+ msa
+
+
+ Malayalam
+ ml
+ mal
+
+
+ Maltese
+ mt
+ mlt
+
+
+ Māori
+ mi
+ mri
+
+
+ Marathi (Marāṭhī)
+ mr
+ mar
+
+
+ Marshallese
+ mh
+ mah
+
+
+ Mongolian
+ mn
+ mon
+
+
+ Nauru
+ na
+ nau
+
+
+ Navajo, Navaho
+ nv
+ nav
+
+
+ Norwegian Bokmål
+ nb
+ nob
+
+
+ North Ndebele
+ nd
+ nde
+
+
+ Nepali
+ ne
+ nep
+
+
+ Ndonga
+ ng
+ ndo
+
+
+ Norwegian Nynorsk
+ nn
+ nno
+
+
+ Norwegian
+ no
+ nor
+
+
+ Nuosu
+ ii
+ iii
+
+
+ South Ndebele
+ nr
+ nbl
+
+
+ Occitan
+ oc
+ oci
+
+
+ Ojibwe, Ojibwa
+ oj
+ oji
+
+
+ Old Church Slavonic, Church Slavic, Church Slavonic, Old
+ Bulgarian, Old Slavonic
+ cu
+ chu
+
+
+ Oromo
+ om
+ orm
+
+
+ Oriya
+ or
+ ori
+
+
+ Ossetian, Ossetic
+ os
+ oss
+
+
+ Panjabi, Punjabi
+ pa
+ pan
+
+
+ Pāli
+ pi
+ pli
+
+
+ Persian
+ fa
+ fas
+
+
+ Polish
+ pl
+ pol
+
+
+ Pashto, Pushto
+ ps
+ pus
+
+
+ Portuguese
+ pt
+ por
+
+
+ Quechua
+ qu
+ que
+
+
+ Romansh
+ rm
+ roh
+
+
+ Kirundi
+ rn
+ run
+
+
+ Romanian, Moldavian, Moldovan
+ ro
+ ron
+
+
+ Russian
+ ru
+ rus
+
+
+ Sanskrit (Saṁskṛta)
+ sa
+ san
+
+
+ Sardinian
+ sc
+ srd
+
+
+ Sindhi
+ sd
+ snd
+
+
+ Northern Sami
+ se
+ sme
+
+
+ Samoan
+ sm
+ smo
+
+
+ Sango
+ sg
+ sag
+
+
+ Serbian
+ sr
+ srp
+
+
+ Scottish Gaelic, Gaelic
+ gd
+ gla
+
+
+ Shona
+ sn
+ sna
+
+
+ Sinhala, Sinhalese
+ si
+ sin
+
+
+ Slovak
+ sk
+ slk
+
+
+ Slovene
+ sl
+ slv
+
+
+ Somali
+ so
+ som
+
+
+ Southern Sotho
+ st
+ sot
+
+
+ Spanish, Castilian
+ es
+ spa
+
+
+ Sundanese
+ su
+ sun
+
+
+ Swahili
+ sw
+ swa
+
+
+ Swati
+ ss
+ ssw
+
+
+ Swedish
+ sv
+ swe
+
+
+ Tamil
+ ta
+ tam
+
+
+ Telugu
+ te
+ tel
+
+
+ Tajik
+ tg
+ tgk
+
+
+ Thai
+ th
+ tha
+
+
+ Tigrinya
+ ti
+ tir
+
+
+ Tibetan Standard, Tibetan, Central
+ bo
+ bod
+
+
+ Turkmen
+ tk
+ tuk
+
+
+ Tagalog
+ tl
+ tgl
+
+
+ Tswana
+ tn
+ tsn
+
+
+ Tonga (Tonga Islands)
+ to
+ ton
+
+
+ Turkish
+ tr
+ tur
+
+
+ Tsonga
+ ts
+ tso
+
+
+ Tatar
+ tt
+ tat
+
+
+ Twi
+ tw
+ twi
+
+
+ Tahitian
+ ty
+ tah
+
+
+ Uighur, Uyghur
+ ug
+ uig
+
+
+ Ukrainian
+ uk
+ ukr
+
+
+ Urdu
+ ur
+ urd
+
+
+ Uzbek
+ uz
+ uzb
+
+
+ Venda
+ ve
+ ven
+
+
+ Vietnamese
+ vi
+ vie
+
+
+ Volapük
+ vo
+ vol
+
+
+ Walloon
+ wa
+ wln
+
+
+ Welsh
+ cy
+ cym
+
+
+ Wolof
+ wo
+ wol
+
+
+ Western Frisian
+ fy
+ fry
+
+
+ Xhosa
+ xh
+ xho
+
+
+ Yiddish
+ yi
+ yid
+
+
+ Yoruba
+ yo
+ yor
+
+
+ Zhuang, Chuang
+ za
+ zha
+
+
+ Zulu
+ zu
+ zul
+
+
+
+
+
+
+
+ Keyboard shortcuts in the editor
+
+ This short text describes key behavior in the editor pane. The term
+ "Move to inside segment" means, that the cursor moves to the beginning of
+ the segment if it was previously before the segment, and to the end of the
+ segment if it was previously after it.
+
+
+ Key behavior in the editor
+
+
+
+
+
+
+
+
+ Key combination
+
+ Action
+
+
+
+
+
+ Left:
+
+ one char left, but not further than the beginning of
+ segment
+
+
+
+ Right:
+
+ one char right, but not further than the end of
+ segment
+
+
+
+ Ctrl+Left:
+
+ one word left, but not further than the beginning of
+ segment
+
+
+
+ Ctrl+Right:
+
+ one word right, but not further than the end of
+ segment
+
+
+
+ PgUp:
+
+ page up through the document
+
+
+
+ PgDn:
+
+ page down through the document
+
+
+
+ Home*
+
+ move to the beginning of the line in the segment
+
+
+
+ End*
+
+ move to the end of the line in the segment
+
+
+
+ Ctrl+Home
+
+ move to the start of the segment
+
+
+
+ Ctrl+End
+
+ move to the end of the segment
+
+
+
+ Ctrl+PgUp
+
+ move to the start of the document (Mac: Cmd+PgUp)
+
+
+
+ Ctrl+PgDn
+
+ move to the end of the document (Mac: Cmd+PgDn)
+
+
+
+ Backspace*
+
+ remove char before cursor
+
+
+
+ Delete*
+
+ remove char after cursor
+
+
+
+ Ctrl+Backspace
+
+ remove chars up to the start of the current word (Mac:
+ Alt+Backspace)
+
+
+
+ Ctrl+Delete
+
+ remove chars up to the start of next word (Mac: Alt+Delete)
+
+
+
+ Ctrl+Enter
+
+ open previous segment (Mac: Cmd+Enter)
+
+
+
+ Ctrl+A
+
+ select complete segment (Mac: Cmd+A)
+
+
+
+ Ctrl+Shift+O
+
+ RTL-LTR switch
+
+
+
+
+
+ * These keys behave differently when the cursor is outside the
+ editable segment:
+
+
+
+ Home: cursor to the beginning of
+ the active segment
+
+
+
+ End: cursor to the end of the
+ active segment
+
+
+
+ Backspace: nothing
+
+
+
+ Delete: nothing
+
+
+
+ Any char key, if clicked outside
+ editable segment, will be ignored.
+
+
+
+ The "Shift" key doesn't exhibit any special behavior per se: when the
+ "Shift" key is pressed, all keys move the cursor in their usual
+ manner.
+
+ System-wide commands: Paste (Ctrl+V
+ or Ctrl+Insert), Cut (Ctrl+X or Ctrl+C),
+ Insert match (Ctrl+I) and Insert source
+ (Ctrl+Shift+I) act in principle on any
+ selection, including those that extend beyond the current segment. In such a
+ case the selection will of course be pared down to segment
+ boundaries.
+
+
+
+ Shortcuts customization
+
+
+ <indexterm class="singular">
+ <primary>Shortcuts - customization</primary>
+
+ <secondary>Customization</secondary>
+ </indexterm>Shortcuts customization
+
+ Most of the items that appear in the main menu can have a new
+ shortcut assigned. Only the most commonly used menu items are assigned a
+ shortcut by default. You can change the already assigned shortcuts and add
+ new shortcuts by putting a shortcut definition file in your OmegaT
+ preferences folder (see User files
+ location).
+
+ The shortcut definition file must be named
+ MainMenuShortcuts.properties and must contain at most
+ one shortcut definition per line. Empty lines are accepted and comment
+ lines should start with "//". Anything after the "//" will be
+ ignored.
+
+ Once the MainMenuShortcuts.properties file is
+ modified, OmegaT must be relaunched to take the
+ new shortcuts into account.
+
+ The shortcut definition syntax is the following: <menu item
+ code>=<shortcut>, where <menu item
+ code> is a code taken from the tables below and
+ <shortcut> is a combination of pressed keys
+ specified by the user
+ The full syntax for keystrokes (shortcuts) is defined in the
+ following Java 1.6 documentation from Oracle (bottom of page): Java
+ 1.6 keystrokes shortcuts
+ .
+
+ <shortcut> must be of the following form:0 or more
+ <modifier> followed by 0 or 1
+ <event> followed by 1 <key>,
+ where:
+
+ <modifier> can be:
+ shift, control,
+ ctrl, meta
+ On the Mac, the modifier meta must be
+ used to specify the command key.
+ , alt,
+ altGraph
+
+
+
+ <event> can be: typed,
+ pressed, released
+
+
+
+ and <key> can be any key available on your
+ keyboard
+ The possible keyevents (keys) are listed in the following
+ Java 1.6 documentation from Oracle: Java
+ 1.6 keyEvents description
+ .
+
+
+
+ For example, in the default OmegaT shortcuts
+ The default OmegaT shortcuts are available from Sourceforge:
+ Default
+ OmegaT Shortcuts
+
+ The default OmegaT shortcuts for the Mac are also available from
+ Sourceforge, they all use "meta" instead of "ctrl": Default
+ OmegaT Shortcuts for the Mac
+ , one can find:
+
+
+
+ projectOpenMenuItem=ctrl O
+
+
+
+ editCreateGlossaryEntryMenuItem=ctrl shift G
+
+
+
+ The first is the shortcut for Open
+ Project, the second for Create Glossary
+ Entry.
+
+ If you want to use
+ Shift
+
+ Ctrl
+
+ O
+ to open a project, modify your
+ MainMenuShortcuts.properties as follows:
+
+
+ projectOpenMenuItem=shift ctrl O.
+
+ If you are on a Mac and you want to add a
+ Shift
+
+ Command
+
+ S
+ shortcut to
+ Tools
+
+ Statistics
+ , add the following line to your
+ MainMenuShortcuts.properties:
+
+ toolsShowStatisticsStandardMenuItem=shift meta
+ S
+
+ Save then the file and relaunch OmegaT.
+ Your new shortcuts should now appear next to the menu items you have
+ modified. If they do not conflict with system shortcuts, they should be
+ available from within OmegaT.
+
+
+
+ Project Menu
+
+
+ Comportamiento clave en el editor
+
+
+
+
+
+
+
+
+ Combinación de teclas
+
+ Acción
+
+
+
+
+
+ Izquierda:
+
+ un carácter a la izquierda, pero no más allá del principio del segmento
+
+
+
+ Derecha:
+
+ un carácter a la derecha, pero no más allá del final del segmento
+
+
+
+ Ctrl+Izquierda:
+
+ una palabra a la izquierda, pero no más allá del principio del segmento
+
+
+
+ Ctrl+Derecha:
+
+ una palabra a la derecha, pero no más allá del final del segmento
+
+
+
+ RePág:
+
+ una página hacia arriba en el documento
+
+
+
+ AvPág:
+
+ una página hacia abajo en el documento
+
+
+
+ Inicio*
+
+ va al principio de la línea en el segmento
+
+
+
+ Fin*
+
+ va al final de la línea en el segmento
+
+
+
+ Ctrl+Inicio
+
+ va al principio del segmento
+
+
+
+ Ctrl+Fin
+
+ va al final del segmento
+
+
+
+ Ctrl+RePág
+
+ va al principio del documento (Mac: Cmd+RePág)
+
+
+
+ Ctrl+AvPág
+
+ va a la final del documento (Mac: Cmd+AvPág)
+
+
+
+ Retroceso*
+
+ elimina caracteres antes del cursor
+
+
+
+ Supr*
+
+ elimina caracteres después del cursor
+
+
+
+ Ctrl+Retroceso
+
+ elimina caracteres hasta el comienzo de la palabra actual (Mac: Alt+Retroceso)
+
+
+
+ Ctrl+Supr
+
+ elimina caracteres hasta el comienzo de la siguiente palabra (Mac: Alt+Supr)
+
+
+
+ Ctrl+Intro
+
+ abre un segmento anterior (Mac: Cmd+Intro)
+
+
+
+ Ctrl+A
+
+ selecciona el segmento completo (Mac: Cmd+A)
+
+
+
+ Ctrl+Cambio+O
+
+ intercambia RTL-LTR
+
+
+
+
+
+ * Estas teclas se comportan de manera diferente cuando el cursor se encuentra fuera del segmento editable:
+
+
+
+ Inicio: nueve el cursor al comienzo del segmento activo
+
+
+
+ Fin: mueve el cursor hasta el final del segmento activo
+
+
+
+ Retroceso: nada
+
+
+
+ Supr: nada
+
+
+
+ Cualquier tecla de carácter, si haces clic fuera del segmento editable, se tendrá en cuenta.
+
+
+
+ La tecla "Cambio" no presenta ningún comportamiento especial en sí misma: cuando la tecla "Cambio" se pulsa todas las teclas mueven el cursor en su forma habitual.
+
+ Todo el sistema de ordenes: Pegar (Ctrl+V o Ctrl+Insertar), Cortar (Ctrl+X o Ctrl+C), insertar coincidencia (Ctrl+I) e insertar fuente (Ctrl+Mayúsculas+I) actúan, en principio, en cualquier selección, incluidas las que se extienden más allá del segmento actual. En tal caso, la selección, por supuesto, se reduce a los límites del segmento.
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/es/App_Languages.xml b/OmegaT/doc_src/es/App_Languages.xml
new file mode 100644
index 0000000..f60aa05
--- /dev/null
+++ b/OmegaT/doc_src/es/App_Languages.xml
@@ -0,0 +1,954 @@
+
+
+
+ Idiomas ― Lista de códigos ISO 639<indexterm class="singular">
+ <primary>Idiomas</primary>
+ </indexterm>
+ <indexterm class="singular">
+ <primary>Códigos de idioma ISO</primary>
+ </indexterm>
+ <indexterm class="singular">
+ <primary>Proyecto</primary> <secondary>Propiedades</secondary> <seealso>Idiomas</seealso>
+ </indexterm>
+
+
+ Por favor, verifica la Tabla de código ISO 639 para información adicional y actualizada sobre los códigos de idioma.
+
+
+ Lista de códigos de Idioma ISO 639
+
+
+
+
+
+
+ Nombre de idioma
+ ISO 639-1
+ ISO 639-2
+
+
+
+
+ Abkhaz
+ ab
+ abk
+
+
+ Afar
+ aa
+ aar
+
+
+ Africanos
+ af
+ afr
+
+
+ Akan
+ ak
+ aka
+
+
+ Albania
+ sq
+ sqi
+
+
+ Amárico
+ am
+ amh
+
+
+ Árabe
+ ar
+ ara
+
+
+ Aragonés
+ an
+ arg
+
+
+ Armenio
+ hy
+ hye
+
+
+ Assamese
+ as
+ asm
+
+
+ Avaric
+ av
+ ava
+
+
+ Avestan
+ ae
+ ave
+
+
+ Aymara
+ ay
+ aym
+
+
+ Azerbaiyán
+ az
+ aze
+
+
+ Bambara
+ bm
+ bam
+
+
+ Bashkir
+ ba
+ bak
+
+
+ Vasco
+ eu
+ eus
+
+
+ Belarús
+ be
+ bel
+
+
+ Bengalí
+ bn
+ ben
+
+
+ Bihari
+ bh
+ bih
+
+
+ Bislama
+ bi
+ bis
+
+
+ Bosnia
+ bs
+ bos
+
+
+ Breton
+ br
+ bre
+
+
+ Búlgaro
+ bg
+ bul
+
+
+ Burmese
+ my
+ mya
+
+
+ Catalán
+ ca
+ cat
+
+
+ Chamorro
+ ch
+ cha
+
+
+ Chechenio
+ ce
+ che
+
+
+ Chichewa, Chewa, Nyanja
+ ny
+ nya
+
+
+ Chino
+ zh
+ zho
+
+
+ Chuvashia
+ cv
+ chv
+
+
+ Cornualles
+ kw
+ cor
+
+
+ Corso
+ co
+ cos
+
+
+ Cree
+ cr
+ cre
+
+
+ Croacia
+ hr
+ hrv
+
+
+ Checo
+ cs
+ ces
+
+
+ Danés
+ da
+ dan
+
+
+ Divehi, Dhivehi, Maldivas
+ dv
+ div
+
+
+ Holandés
+ nl
+ nld
+
+
+ Dzongkha
+ dz
+ dzo
+
+
+ Inglés
+ en
+ eng
+
+
+ Esperanto
+ eo
+ epo
+
+
+ Estonia
+ et
+ est
+
+
+ Ewe
+ ee
+ ewe
+
+
+ Faroese
+ fo
+ fao
+
+
+ Fiji
+ fj
+ fij
+
+
+ Finlandés
+ fi
+ fin
+
+
+ Francés
+ fr
+ fra
+
+
+ Fula, Fulah, Pulaar, Pular
+ ff
+ ful
+
+
+ Galicia
+ gl
+ glg
+
+
+ Georgiano
+ ka
+ kat
+
+
+ Alemán
+ de
+ deu
+
+
+ Griego Moderno
+ el
+ ell
+
+
+ Guaraní
+ gn
+ grn
+
+
+ Gujarati
+ gu
+ guj
+
+
+ Haitiano, creole haitiano
+ ht
+ hat
+
+
+ Hausa
+ ha
+ hau
+
+
+ Hebreo (moderno)
+ he
+ heb
+
+
+ Herero
+ hz
+ her
+
+
+ Hindi
+ hi
+ hin
+
+
+ Hiri Motu
+ ho
+ hmo
+
+
+ Húngaro
+ hu
+ hun
+
+
+ Interlingua
+ ia
+ ina
+
+
+ Indonesio
+ id
+ ind
+
+
+ Interlingue
+ ie
+ ile
+
+
+ Irlanda
+ ga
+ gle
+
+
+ Igbo
+ ig
+ ibo
+
+
+ Inupiaq
+ ik
+ ipk
+
+
+ Ido
+ io
+ ido
+
+
+ Islandés
+ is
+ isl
+
+
+ Italiano
+ it
+ ita
+
+
+ Inuktitut
+ iu
+ iku
+
+
+ Japonés
+ ja
+ jpn
+
+
+ Javanés
+ jv
+ jav
+
+
+ Kalaallisut, Groenlandia
+ kl
+ kal
+
+
+ Canarés
+ kn
+ kan
+
+
+ Kanuri
+ kr
+ kau
+
+
+ Cachemira
+ ks
+ kas
+
+
+ Kazajstán
+ kk
+ kaz
+
+
+ Khmer
+ km
+ khm
+
+
+ Kikuyu, Gikuyu
+ ki
+ kik
+
+
+ Kinyarwanda
+ rw
+ kin
+
+
+ Kirguises, Kirguistán
+ ky
+ kir
+
+
+ Komi
+ kv
+ kom
+
+
+ Kongo
+ kg
+ kon
+
+
+ Corea
+ ko
+ kor
+
+
+ Kurdo
+ ku
+ kur
+
+
+ Kwanyama, Kuanyama
+ kj
+ kua
+
+
+ Latin
+ la
+ lat
+
+
+ Luxemburgués, Luxemburgués
+ lb
+ ltz
+
+
+ Luganda
+ lg
+ lug
+
+
+ Limburgués, Limburgan, Limburger
+ li
+ lim
+
+
+ Lingala
+ ln
+ lin
+
+
+ Lao
+ lo
+ lao
+
+
+ Lituano
+ lt
+ lit
+
+
+ Luba-Katanga
+ lu
+ lub
+
+
+ Letonia
+ lv
+ lav
+
+
+ Manx
+ gv
+ glv
+
+
+ Macedonia
+ mk
+ mkd
+
+
+ Madagascar
+ mg
+ mlg
+
+
+ Malayo
+ ms
+ msa
+
+
+ Malayalam
+ ml
+ mal
+
+
+ Maltés
+ mt
+ mlt
+
+
+ Māori
+ mi
+ mri
+
+
+ Maratí (Marathi)
+ mr
+ mar
+
+
+ De las Islas Marshall
+ mh
+ mah
+
+
+ Mongolia
+ mn
+ mon
+
+
+ Nauru
+ na
+ nau
+
+
+ Navajo, Navaho
+ nv
+ nav
+
+
+ Noruego Bokmål
+ nb
+ nob
+
+
+ Ndebele del Norte
+ nd
+ nde
+
+
+ Nepali
+ ne
+ nep
+
+
+ Ndonga
+ ng
+ ndo
+
+
+ Noruego Nynorsk
+ nn
+ nno
+
+
+ Noruego
+ no
+ nor
+
+
+ Nuosu
+ ii
+ iii
+
+
+ Ndebele del sur
+ nr
+ nbl
+
+
+ Occitano
+ oc
+ oci
+
+
+ Ojibwe, Ojibwa
+ oj
+ oji
+
+
+ Antiguo eslavo eclesiástico, Iglesia eslava, eslavo eclesiástico, antiguo Búlgaro, Esclavo viejo
+ cu
+ chu
+
+
+ Oromo
+ om
+ orm
+
+
+ Oriya
+ or
+ ori
+
+
+ Osetia del Sur, osetio
+ os
+ oss
+
+
+ Panjabi, Punjabi
+ pa
+ pan
+
+
+ Pāli
+ pi
+ pli
+
+
+ Persa
+ fa
+ fas
+
+
+ Polaco
+ pl
+ pol
+
+
+ Pashto, Pushto
+ ps
+ pus
+
+
+ Portugués
+ pt
+ por
+
+
+ Quechua
+ qu
+ que
+
+
+ Romanche
+ rm
+ roh
+
+
+ Kirundi
+ rn
+ run
+
+
+ Rumania, Moldavia, Moldavan
+ ro
+ ron
+
+
+ Ruso
+ ru
+ rus
+
+
+ Sánscrito (samskrta)
+ sa
+ san
+
+
+ Sardo
+ sc
+ srd
+
+
+ Sindhi
+ sd
+ snd
+
+
+ Sami del norte
+ se
+ sme
+
+
+ Samoa
+ sm
+ smo
+
+
+ Sango
+ sg
+ sag
+
+
+ Serbio
+ sr
+ srp
+
+
+ Gaélico escocés, gaélico
+ gd
+ gla
+
+
+ Shona
+ sn
+ sna
+
+
+ Cingalés, singalés
+ si
+ sin
+
+
+ Eslovaca
+ sk
+ slk
+
+
+ Esloveno
+ sl
+ slv
+
+
+ Somalí
+ so
+ som
+
+
+ Southern Sotho
+ st
+ sot
+
+
+ Español, castellano
+ es
+ spa
+
+
+ Sundanese
+ su
+ sun
+
+
+ Swahili
+ sw
+ swa
+
+
+ Swati
+ ss
+ ssw
+
+
+ Sueco
+ sv
+ swe
+
+
+ Tamil
+ ta
+ tam
+
+
+ Telugu
+ te
+ tel
+
+
+ Tayikistán
+ tg
+ tgk
+
+
+ Tailandia
+ th
+ tha
+
+
+ Tigrinya
+ ti
+ tir
+
+
+ Tibetano estándar, Tibetano, Central
+ bo
+ bod
+
+
+ Turkmenistán
+ tk
+ tuk
+
+
+ Tagalo
+ tl
+ tgl
+
+
+ Tswana
+ tn
+ tsn
+
+
+ Tonga (Islas Tonga)
+ to
+ ton
+
+
+ Turco
+ tr
+ tur
+
+
+ Tsonga
+ ts
+ tso
+
+
+ Tártara
+ tt
+ tat
+
+
+ Twi
+ tw
+ twi
+
+
+ Tahitian
+ ty
+ tah
+
+
+ Uighur, Uyghur
+ ug
+ uig
+
+
+ Ucrania
+ uk
+ ukr
+
+
+ Urdu
+ ur
+ urd
+
+
+ Uzbeko
+ uz
+ uzb
+
+
+ Venda
+ ve
+ ven
+
+
+ Vietnamita
+ vi
+ vie
+
+
+ Volapük
+ vo
+ vol
+
+
+ Valonia
+ wa
+ wln
+
+
+ Galés
+ cy
+ cym
+
+
+ Wolof
+ wo
+ wol
+
+
+ Oeste de Frisia
+ fy
+ fry
+
+
+ Xhosa
+ xh
+ xho
+
+
+ Yiddish
+ yi
+ yid
+
+
+ Yoruba
+ yo
+ yor
+
+
+ Zhuang, Chuang
+ za
+ zha
+
+
+ Zulu
+ zu
+ zul
+
+
+
+
+ Menú Proyecto
+
+
+
+
+
+
+
+
+ Nuevo
+
+
+
+ Crea y abre un nuevo proyecto. El cuadro de diálogo para crear un proyecto es el mismo que para modificar el proyecto. Ver
+
+
+
+ Abrir
+
+
+ Ctrl
+
+ O
+
+
+ Abre un proyecto previamente creado.
+
+
+
+ Importar archivos fuente...
+
+
+
+ Copia los archivos seleccionados al directorio fuente y vuelve a cargar el proyecto para cargar los nuevos archivos.
+
+
+
+ Importar archivos desde MediaWiki...
+
+
+
+ Importa unidades de páginas MediaWiki, basándose en la dirección URL especificada
+
+
+
+ Volver a cargar
+
+ F5
+
+ Vuelve a cargar el proyecto para tomar en consideración los cambios externos en los archivos fuente, memorias de traducción heredadas, glosarios y configuración del proyecto.
+
+
+
+ Cerrar
+
+
+ CtrlCambioW
+
+
+ Guarda la traducción y cierra el proyecto.
+
+
+
+ Guardar
+
+
+ Ctrl
+
+ S
+
+
+ Guarda la memoria de traducción interna en el disco duro. OmegaT automáticamente guarda cada 10 minutos, traducciones, así como cuando cierras el proyecto o dejas OmegaT.
+
+
+
+ Creando los documentos finales
+
+
+ Ctrl
+
+ D
+
+
+ Crea los documentos traducidos basándose en la traducción del texto de los documentos. Los documentos traducidos creados se encuentran en el directorio destino.
+
+
+
+ Propiedades...
+
+
+ Ctrl
+
+ E
+
+
+ Muestra el cuadro de diálogo Propiedades del proyecto para editar los idiomas de proyecto y la ubicación de los directorios.
+
+
+
+ Archivos del proyecto...
+
+
+ Ctrl
+
+ L
+
+
+ Cierra o abre la ventana de los archivos del proyecto (dependiendo de si está abierta o cerrada).
+
+
+
+ Salir
+
+
+ Ctrl
+
+ Q
+
+
+ Guarda el proyecto y cierra OmegaT. Si aún no haz guardado el proyecto, este confirma manualmente si realmente quieres salir.
+
+
+
+
+
+
+
+ Editar<indexterm class="singular">
+ <primary>Menú principal</primary> <secondary>Editar</secondary>
+ </indexterm>
+
+ Nota: Los elementos que se encuentran en la mayoría de las aplicaciones (copiar/cortar/pegar) no se muestran en este menú, pero están disponibles con los atajos de tu sistema. Por ejemplo:
+
+
+ Atajos copiar/cortar/pegar
+
+
+
+
+
+
+
+
+ Copiar
+
+
+ Ctrl
+
+ C
+
+
+ Copia el texto seleccionado al portapapeles.
+
+
+
+ Cortar
+
+
+ Ctrl
+
+ X
+
+
+ Copia el texto seleccionado al portapapeles y borra el texto seleccionado.
+
+
+
+ Pegar
+
+
+ Ctrl
+
+ V
+
+
+ Pega el texto del portapapeles en la posición del cursor.
+
+
+
+
+
+ El menú Edición en sí contiene los siguientes elementos:
+
+
+ Menú Edición
+
+
+
+
+
+
+
+
+ Deshacer la última acción
+
+
+ Ctrl
+
+ Z
+
+
+ Restaura el estado anterior a la última acción de edición tomada. Esta orden no funciona una vez que se ha validado el segmento modificado.
+
+
+
+ Rehacer última acción
+
+
+ Ctrl
+
+ Y
+
+
+ Restaura el estado anterior a la última acción de edición cancelada. Esta orden no funciona una vez que se ha validado el segmento modificado.
+
+
+
+ Reemplazar con la coincidencia
+
+
+ Ctrl
+
+ R
+
+
+ Sustituye el segmento destino en su conjunto con la coincidencia parcial seleccionada (por omisión, está seleccionada la primer coincidencia).
+
+
+
+ Insertar coincidencia
+
+
+ Ctrl
+
+ I
+
+
+ Inserta la coincidencia parcial seleccionada en la posición del cursor. Si haz seleccionado una parte del segmento destino, esta función sobrescribe la parte seleccionada.
+
+
+
+ Reemplazar con la traducción automática
+
+
+ Ctrl
+
+ M
+
+
+ Sustituye el segmento destino con la traducción, facilitada por el servicio de Traducción Automática seleccionado. No hace nada, si no haz activado un servicio de traducción automática (consulta el Menú → Opciones abajo).
+
+
+
+ Reemplazar con el original
+
+
+ CambioCtrlR
+
+
+ Sustituye el segmento destino en su conjunto con el original.
+
+
+
+ Insertar original
+
+
+ CambioCtrlI
+
+
+ Inserta el original en la posición del cursor.
+
+
+
+ Insertar etiquetas fuente
+
+
+ CambioCtrlT
+
+
+
+ EtiquetasInsertando etiquetas originales
+ Inserta las etiquetas originales en la posición del cursor. Todas las etiquetas en originales se insertan en el segmento actual, independientemente de que ya estén allí o no. Los textos, encerrados entre las etiquetas, se sustituyen por espacios:. <f0><f1>Este es el texto</f0></f1> que se debe copiar como <f0><f1>un_espacio</f0></f1>
+
+
+
+ Exportar selección
+
+
+ CambioCtrlC
+
+
+ Exporta la selección actual a un archivo de texto para su procesamiento. Si no se ha seleccionado texto, el segmento fuente actual se escribe en ese archivo. Cuando el usuario sale de OmegaT, este archivo no se descarga, a fin de ser coherente con el comportamiento acostumbrado del portapapeles. El contenido exportado se copia en el archivo selection.txt ubicado en el directorio de los archivos preferentes del usuario (consulta ).
+
+
+
+ Buscar en el proyecto...
+
+
+ Ctrl
+
+ F
+
+
+ Se abre una nueva Ventana de búsqueda.
+
+
+
+ Intercambiar mayús/minús...
+
+ CambioF3 (Ve el texto)
+
+ Cambia las mayúsculas/minúsculas del texto resaltado en el segmento destino a la opción seleccionada (minúsculas, mayúsculas o mayúsculas iniciales). Usa Cambio+F3
+ AtajosCambio+F3 - Selección de mayúsculas/minúsculas
+ para recorrer las tres alternativas. Si no hay texto seleccionado, OmegaT selecciona la primera letra de la palabra inmediata a la derecha del cursor.
+
+
+
+ Seleccionar coincidencia #N
+
+
+ Ctrl
+
+ #N
+
+
+ (#N es un dígito del 1 al 5) - Selecciona la enésima coincidencia parcial que aparece en el visor de coincidencias para sustituir o insertarla en el segmento. La describe la codificación de colores en detalle.
+
+
+
+
+ Menú Dirigirse a
+
+
+
+
+
+
+
+
+ Siguiente segmento por traducir
+
+
+ Ctrl
+
+ U
+
+
+ Te lleva al siguiente segmento que no tiene equivalente en la memoria de traducción.
+
+
+
+ Siguiente segmento
+
+ CtrlN o Entrar o Tab
+
+ Te lleva al siguiente segmento. Si el segmento actual es el último segmento de un archivo, se mueve al primer segmento del siguiente archivo.
+
+
+
+ Segmento previo
+
+ CtrlP o CtrlEntrar o CtrlTab
+
+ Te lleva al segmento previo. Si el segmento actual es el primero en un archivo, éste te lleva al último segmento del archivo anterior.
+
+
+
+ Segmento número...
+
+
+ Ctrl
+
+ J
+
+
+ Abre el segmento cuando se ingresa el número de segmento..
+
+
+
+ Regresar en la historia...
+
+
+ CtrlCambioP
+
+
+ Con esta orden puedes moverte hacia atrás un segmento a la vez, para volver más tarde al segmento actual con la orden Avanzar en la historia....
+
+
+
+ Avanzar en la historia...
+
+
+ CtrlCambioN
+
+
+ OmegaT recuerda los segmentos ejecutados. Con esta orden puedes dar un paso hacia adelante en el segmento, que previamente haz dejado con la orden Regresar en la historia....
+
+
+
+
+ Menú Ver
+
+
+
+
+
+
+ Marcar segmentos traducidos
+
+ Si está marcada, los segmentos traducidos tendrán un fondo amarillo.
+
+
+
+ Marcar segmentos no traducidos
+
+ Si está marcada, los segmentos no traducidos tendrán un fondo en color violeta.
+
+
+
+ Mostrar segmentos originales
+
+ Si está marcada, mostrará los segmentos fuente y estarán resaltados en verde. Si no está marcada, no se muestran los segmentos fuente.
+
+
+
+ Información de modificación
+
+ Establece la opción de información de modificación para Seleccionado mostrará la hora y autor del último cambio para el segmento actual. Si lo estableces en Mostrar todo muestra esta información para todos los segmentos y Ninguno revierte esta opción.
+
+
+
+
+ Menú herramientas
+
+
+ CoincidenciasEstadísticas de coincidencias
+
+
+
+ ProyectoEstadísticas de coincidencias
+
+
+
+ ProyectoEstadística
+
+
+
+
+
+
+
+ Validar etiquetas
+
+ Ctrl+T: Verifica las etiquetas, si es que faltan o se desplazaron en archivos con formato. Mostrará una lista de los segmentos con errores de etiqueta y posibles inconsistencias. Consulta Validación de etiquetas y .
+
+
+
+ Estadísticas
+
+ Abre una nueva ventana y muestra las estadísticas del proyecto, es decir, los totales del proyecto y los totales para cada archivo en el proyecto.
+
+
+
+ Estadísticas de coincidencias
+
+ Muestra las estadísticas de coincidencias para el proyecto: el número de repeticiones, coincidencias exactas, coincidencias parciales y sin coincidencia -, por segmentos, palabras y caracteres.
+
+
+
+
+ Menú Opciones
+
+
+
+
+
+
+ Usar TAB para avanzar
+
+ Establece que la tecla Tab sea la validación del segmento en lugar de la predeterminada Entrar. Esta opción es útil para algunos sistemas de entrada de carácter Chinos, Japoneses o Coreanos.
+
+
+
+ Confirmar antes de salir
+
+ El programa pedirá una confirmación antes de cerrarse.
+
+
+
+ Traducción automática
+
+ Le permite activar/desactivar las herramientas de traducción automática ofrecidas. Cuando se activa, CtrlM inserta la sugerencia en la parte destino del segmento actual.
+
+
+
+ Consejos de traducción
+
+ Te permite activar/desactivar la función Consejos de traducción y establecer su opción Coincidencia exacta. Con los Consejos de traducción activados el botón derecho sobre una palabra resaltada en fuente se abrirá un menú desplegable con las entradas del glosario de la palabra en que haz hecho clic. A continuación, puedes hacer clic en la traducción preferida para insertarla en la posición actual del segmento destino. Con Consejos de traducción/Coincidencia exacta marcada, sólo se revisarán palabras completas, de lo contrario también partes de las palabras serán emparejadas.
+
+
+
+ Tipo de letra...
+
+ Muestra el diálogo para modificar el tipo de letra para visualizar el texto. Los usuarios de computadoras antiguas cuando sientan que cambiar el tamaño de la ventana es muy lento, pueden tratar de cambiar el tipo de letra. Consulta .
+
+
+
+ Filtros de archivo...
+
+ Muestra el diálogo Filtros de archivo para configurar la gestión y análisis de archivos.
+
+
+
+ Segmentación...
+
+ Abre el diálogo Configuración de segmentación para configurar la segmentación del texto.
+
+
+
+ Corrector ortográfico...
+
+ Muestra la ventana Configuración del corrector ortográfico para instalar, configurar y activar el corrector ortográfico.
+
+
+
+ Comportamiento del campo de edición...
+
+ Muestra el diálogo Opciones de comportamiento del campo de edición.
+
+
+
+ Validación de etiquetas...
+
+ A los programadores: les permite configurar las opciones de la validación de etiquetas también para comprobar las variables de programación (%...).
+
+
+
+ Trabajo en grupo...
+
+ Ingresa tu nombre aquí y este se adjuntará a todos los segmentos que traduzcas.
+
+
+
+ Restaurar ventana principal
+
+ Restaura los componentes de la ventana principal de OmegaT a su estado predeterminado. Utiliza esta función cuando haz desacoplado, movido u ocultado uno o más componentes y no puedes restaurar la disposición deseada. También la puedes utilizar cuando los paneles no aparecen como se esperaba después de una actualización de OmegaT.
+
+
+
+
+ Menú Ayuda
+
+
+
+
+
+
+ Manual de usuario...
+
+ F1: Abre el navegador de Ayuda mostrando este manual en una ventana separada.
+
+
+
+ Acerca de...
+
+ Muestra información de los derechos de autor, créditos y licencia.
+
+
+
+
+
+
+
+ Atajos del teclado<indexterm class="singular">
+ <primary>Atajos del teclado</primary>
+ </indexterm>
+
+ Los siguientes atajos están disponibles desde la ventana principal. Cuando otra ventana en el primer plano, haz clic en la ventana principal para ponerla en primer plano o pulse Esc para cerrar la otra ventana.
+
+ Los atajos se activan presionando Ctrl y una letra. Algunos atajos incluyen otras teclas. Aquí, para efecto de legibilidad, las letras están escritas en mayúsculas.
+
+ Ctrl se utiliza en Windows, UNIX y sistemas operativos similares a UNIX con teclados con una tecla Ctrl/Control. Los usuarios de Mac deberían usar cmd+tecla. en los teclados de Apple la tecla cmd o bien tienen una etiqueta "comando" o un icono de Apple en ella.
+
+
+
+ Gestión de proyectos
+
+
+
+
+
+ Editando
+
+
+
+
+
+ Moviéndose
+
+
+
+
+
+ Ventana de referencias
+
+
+
+
+
+ Otro
+
+
+
+
+ <indexterm class="singular">
+ <primary>Atajos de teclado</primary> <secondary>Proyecto</secondary>
+ </indexterm>Gestión de proyectos<indexterm class="singular">
+ <primary>Proyecto</primary> <secondary>Atajos para gestionar proyectos</secondary>
+ </indexterm>
+
+
+ Atajos para gestionar proyectos
+
+
+
+
+
+
+
+
+ Abrir proyecto
+
+
+ Ctrl
+
+ O
+
+
+ Muestra un diálogo para ubicar un proyecto existente.
+
+
+
+ Guardar
+
+
+ Ctrl
+
+ S
+
+
+ Guarda el trabajo actual en la memoria de traducción interna (el archivo project_save.tmx que se encuentra en el directorio omegat del proyecto).
+
+
+
+ Cerrar proyecto
+
+
+ CambioCtrlW
+
+
+ Cierra el proyecto actual
+
+
+
+ Crear documentos finales
+
+
+ Ctrl
+
+ D
+
+
+ Crea los documentos traducidos en el directorio destino del proyecto y crea archivos de memoria de traducción (Nivel 1, Nivel 2 y los archivos TMX de omegat) en el directorio raíz del proyecto.
+
+
+
+ Propiedades del Proyecto
+
+
+ Ctrl
+
+ E
+
+
+ Muestra la configuración del proyecto para modificación, de ser necesario.
+
+
+
+
+ Atajos de edición
+
+
+
+
+
+
+
+
+ Deshacer la última acción
+
+
+ Ctrl
+
+ Z
+
+
+ Deshace las últimas acciones de edición en el segmento destino actual
+
+
+
+ Rehacer última acción
+
+
+ Ctrl
+
+ Y
+
+
+ Rehace la última acción de edición en el segmento destino actual
+
+
+
+ Selecciona coincidencia #N
+
+
+ Ctrl
+
+ #N
+
+
+ Donde #N es un dígito del 1 al 5. Selecciona el acceso directo a la enésima coincidencia mostrada en la ventana de coincidencias parciales (la primer coincidencia está seleccionada por omisión)
+
+
+
+ Reemplazar con la coincidencia
+
+
+ Ctrl
+
+ R
+
+
+ Reemplaza el contenido destino del segmento actual con la coincidencia seleccionada (la primer coincidencia está seleccionada por omisión)
+
+
+
+ Insertar coincidencia
+
+
+ Ctrl
+
+ I
+
+
+ Inserta la coincidencia seleccionada en la posición del cursor en el segmento destino actual ( de manera predeterminada se inserta la primer coincidencia)
+
+
+
+ Sustituir con el original
+
+
+ CtrlCambio+R
+
+
+ Reemplaza el contenido destino del segmento actual con el contenido del texto fuente
+
+
+
+ Insertar original
+
+
+ CtrlCambio+I
+
+
+ Inserta el contenido del texto fuente en la posición del cursor del segmento destino
+
+
+
+ Insertar etiquetas fuente
+
+
+ CtrlCambio+T
+
+
+ Inserta las etiquetas fuente en la posición del cursor del segmento destino
+
+
+
+ Buscar en el proyecto
+
+
+ Ctrl
+
+ F
+
+
+ Muestra un diálogo para realizar búsquedas en el proyecto
+
+
+
+ Reemplazar con la traducción automática
+
+
+ Ctrl
+
+ M
+
+
+ Sustituye el segmento destino con la traducción automática de la fuente. Ninguna acción, si las herramientas de traducción automática están desactivadas (consulta Menú → Opciones → Traducción automática)
+
+
+
+
+ Atajos de movimiento
+
+
+
+
+
+
+
+
+ Siguiente segmento por traducir
+
+
+ Ctrl
+
+ U
+
+
+ Desplaza el campo de edición al próximo segmento que no está registrado en la memoria de traducción del proyecto
+
+
+
+ Siguiente segmento
+
+ CtrlN, Entrar o Retorno
+
+ Mueve el campo de edición al siguiente segmento
+
+
+
+ Segmento previo
+
+
+ Ctrl
+
+ P
+
+
+ Desplaza el campo de edición al segmento anterior
+
+
+
+ Segmento número...
+
+
+ Ctrl
+
+ J
+
+
+ Se desplaza al número de segmento proporcionado
+
+
+
+ Regresar en la historia...
+
+
+ CtrlCambio+P
+
+
+ Se mueve un segmento hacia atrás en la historia
+
+
+
+ Avanzar en la historia...
+
+
+ CtrlCambio+N
+
+
+ Se mueve un segmento hacia adelante en la historia
+
+
+
+
+ Varios atajos
+
+
+
+
+
+
+
+
+ Archivos del proyecto
+
+
+ Ctrl
+
+ L
+
+
+ Muestra la lista de archivos del proyecto
+
+
+
+ Validar etiquetas
+
+
+ Ctrl
+
+ T
+
+
+ Abre la ventana de validación de etiquetas.
+
+
+
+ Exportar selección
+
+
+ CambioCtrl+C
+
+
+ Exporta el texto seleccionado o la fuente actual, si no hay texto seleccionado. El texto se exporta a un archivo de texto plano.
+
+
+
+ Búsqueda en el proyecto
+
+
+ Ctrl
+
+ F
+
+
+ Abre una nueva búsqueda
+
+
+
+ Archivos de ayuda
+
+ F1
+
+ Muestra los archivos de ayuda de OmegaT en una ventana separada
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/es/Miscelanea.xml b/OmegaT/doc_src/es/Miscelanea.xml
new file mode 100644
index 0000000..f7498db
--- /dev/null
+++ b/OmegaT/doc_src/es/Miscelanea.xml
@@ -0,0 +1,203 @@
+
+
+
+ Temas diversos<indexterm class="singular">
+ <primary>Miscelánea</primary>
+ </indexterm>
+
+
+ <application><indexterm class="singular">
+ <primary>OmegaT en modo consola</primary> <seealso>Miscelánea</seealso>
+ </indexterm>OmegaT</application> Modo consola<indexterm class="singular">
+ <primary>Miscelánea</primary> <secondary>OmegaT en modo consola</secondary>
+ </indexterm>
+
+
+ ¡De interés sólo para usuarios avanzados!
+
+
+ El propósito del modo consola (es decir, la línea de ordenes) es el de permitir el uso de OmegaT como herramienta de traducción en un entorno de programación. Cuando se lanza en modo de consola, no se carga la interfaz gráfica de usuario (funcionará por lo tanto, en cualquier consola) y automáticamente traduce el proyecto dado. Un ejemplo podría ser un proyecto de software, con interfaz gráfica de usuario localizada en varios idiomas. Usando el modo consola, puedes generar una interfaz localizada en una parte del proceso de construcción.
+
+
+ Requisitos previos
+
+ Para ejecutar OmegaT, debe estar disponible un proyecto OmegaT válido. La ubicación es irrelevante, puesto que se debe especificar explícitamente en la línea de ordenes en el lanzamiento..
+
+ Si necesitas configuraciones no estándar, los archivos de configuración correspondientes (filters.conf y segmentation.conf) deben estar presentes. Esto se puede conseguir de dos maneras:
+
+
+
+ Ejecuta OmegaT normalmente (con la interfaz gráfica de usuario) y establece la configuración. Si arrancas OmegaT en modo consola, este utilizará los ajustes que hayas configurado.
+
+
+
+ Si no puedes ejecutar OmegaT normalmente (si no está disponible un entorno gráfico): copia los archivos de configuración de alguna otra instalación de OmegaT en otra máquina a un directorio específico. La ubicación no importa, ya que la puedes añadir en la línea de ordenes en el lanzamiento (ve más abajo). Los archivos importantes filters.conf y segmentation.conf se pueden encontrar en el directorio hogar del usuario (Por ejemplo, C:\Documents and Settings\%usuario%\OmegaT bajo Windows, %usuario%/.Omegat/ en Linux)
+
+
+
+
+
+ Lanzando OmegaT en modo consola
+
+ Para iniciar OmegaT en modo consola, los parámetros adicionales se deben especificar en el lanzamiento. El más importante de ellos es <project-dir> y, opcionalmente, --config-dir=<directorio-de-configuración> . Ejemplo:
+
+ $> java -jar OmegaT.jar /ruta/al/proyecto \
+
+ --config-dir=/ruta/a/los/archivos-de-configuración/ \
+
+ --mode=console-translate \
+
+ --source-pattern={regexp}
+
+ Explicación:
+
+
+
+ <project-dir> le dice a OmegaT dónde se encuentra el proyecto a traducir. Si se da, OmegaT se inicia en modo consola y traduce el proyecto.
+
+
+
+
+
+ --config-dir=<directorio-de-configuración> instruye a OmegaT sobre en cual directorio están los archivos de configuración. Si no se especifica, OmegaT vuelve a los valores predeterminados (el directorio de OmegaT en el hogar del usuario, si o no están disponibles: el directorio de trabajo actual).
+
+
+
+
+
+ --mode=console-translate OmegaT se inicia en modo consola y traduce el proyecto.
+
+
+
+ --source-pattern={regexp} Puedes especificar de esta manera los archivos a traducir. He aquí un ejemplo de la expresión regular: prueba\.html
+
+
+
+
+
+ Opciones adicionales
+
+ Uno de los parámetros existes más específicos de la línea de ordenes en el modo de consola: --quiet. En el modo silencioso, se registra menos información en pantalla. Los mensajes que normalmente se encuentran en la barra de estado no se muestran.
+
+ Uso: java -jar OmegaT.jar /ruta/al/proyecto --quiet
+
+
+
+
+ Alineador automático de propiedades Java<indexterm class="singular">
+ <primary>Miscelánea</primary> <secondary>Alineador automático para las propiedades de Java</secondary> <seealso>Miscelánea</seealso>
+ </indexterm>
+
+ OmegaT puede alinear .propeties de Java en modo consola. Si tienes los archivos de propiedades fuente y destino para uno y el mismo contenido en su idioma par, este procedimiento creará un archivo TMX correspondiente a este contenido. Uso:
+
+ java -jar OmegaT.jar --mode=console-align /dir-de-mi-proyecto --alignDir=/archivosTraducidos/
+
+ alignDir debe contener una traducción en el idioma destino del proyecto. Por ejemplo, si el proyecto es EN→FR, alignDir debe contener un paquete que termina con _fr. El tmx resultante se almacena en el directorio omegat bajo el nombre align.tmx.
+
+
+
+ Configurando el tipo de letra<indexterm class="singular">
+ <primary>Miscelánea</primary> <secondary>Configuración del tipo de letra</secondary>
+ </indexterm>
+
+ En este diálogo puedes definir el tipo de letra utilizado por OmegaT en las siguientes ventanas:
+
+
+
+ Ventana principal de OmegaT (Editor, Visor de coincidencias, Visor de glosario)
+
+
+
+
+
+ Ventana de búsqueda
+
+
+
+
+
+ Ventana de validación de etiquetas
+
+
+
+ Puedes acceder al cuadro de diálogo a través de
+ Menú OpcionesTipo de letra...
+ Opciones → Tipo de letra... en el menú principal. El cuadro de diálogo contiene:
+
+
+
+ Tipo de letra: hay un desplegable para seleccionar uno de los tipos de letra disponibles en tu máquina
+
+
+
+
+
+ Tamaño: modifícalo para cambiar el tamaño de la letra
+
+
+
+
+
+ Texto de ejemplo: campo para visualizar inmediatamente el tipo de letra seleccionado
+
+
+
+ Nota: En algunos casos, puede tomar bastante tiempo para que OmegaT actualice la pantalla después de cambiar la configuración del tipo de letra. Este es especialmente el caso cuando un archivo grande que contiene muchos segmentos se abre en el editor, y/o el equipo utilizado es lento. También ten en cuenta que algunos tipos de letra se comportan mejor en algunos pares de idiomas que en otros. En particular, si estás traduciendo entre dos idiomas con alfabetos/sistemas de escritura distintos (como el Ruso y Japonés), selecciona un tipo de letra que se pueda utilizar en ambos.
+
+
+
+ Previniendo la pérdida de datos<indexterm class="singular">
+ <primary>Miscelánea</primary> <secondary>Previniendo la pérdida de datos</secondary>
+ </indexterm>
+
+ OmegaT es una aplicación robusta. Sin embargo, debes tomar precauciones para evitar la pérdida de datos cuando utilizas OmegaT, al igual que con cualquier otra aplicación. Al traducir tus archivos, OmegaT almacena todos los avances en la memoria de traducción project_save.tmx que reside en el directorio /omegat del proyecto.
+
+ OmegaT también respalda la memoria de traducción en project_save.tmx.AÑOMESDIAHHNN.bak en el mismo subdirectorio cada vez que se abre o recarga un proyecto. Año es el año de 4 dígitos, MES es el mes, DÍA el día del mes, y HH y NN son las horas y minutos en que se salvó la memoria de traducción anterior.
+
+ Si usted crees que haz perdido los datos de traducción, puedes utilizar el siguiente procedimiento para restaurar el proyecto a su estado grabado más reciente, por lo general no más de aproximadamente 10 minutos más o menos:
+
+
+
+ cierra el proyecto
+
+
+
+ cambiar el nombre del archivo project_save.tmx actual (por ejemplo, a project_save.tmx.temporal)
+
+
+
+ selecciona la copia de seguridad de la memoria de traducción que sea la más probable que contenga los datos que estás buscando
+
+
+
+ cámbiale el nombre a project_save.tmx
+
+
+
+ abre el proyecto
+
+
+
+ Para evitar perder datos importantes:
+
+
+
+ Haz copias regulares de los archivos /omegat/project_save.tmx a medios de copia de seguridad, tales como CD o DVD.
+
+
+
+ Hasta que te familiarices con OmegaT, crea archivos traducidos a intervalos regulares y comprueba que el archivo traducido contiene la última versión de tu traducción.
+
+
+
+ Ten especial cuidado cuando haces cambios a los archivos /fuente mientras que en el medio de un proyecto. Si se ha modificado el archivo después de haber empezado a traducir, OmegaT puede ser incapaz de encontrar un segmento que ya hayas traducido.
+
+
+
+
+
+ Utiliza estos textos de ayuda para empezar. En caso de que algún problema, envía un mensaje al grupos de usuarios de OmegaT. No dudes en publicar en el idioma con el que te sientas más familiarizado.
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/es/OmegaT.css b/OmegaT/doc_src/es/OmegaT.css
new file mode 100644
index 0000000..1893c29
--- /dev/null
+++ b/OmegaT/doc_src/es/OmegaT.css
@@ -0,0 +1,78 @@
+body {
+ font-family: sans-serif;
+ margin: 1em;
+}
+
+h1, h2, table, dt {
+ color: navy;
+}
+
+h3, h4, ul a {
+ color: green;
+}
+
+code, .code {
+ color: black;
+ background: #ffffcc;
+ border-style: solid;
+ border-width: 1px;
+ border-color: #ffff66;
+ vertical-align: top;
+}
+
+.new {
+ font-size: x-small;
+ color: red;
+ background: yellow;
+}
+
+.updated {
+ font-size: x-small;
+ color: orange;
+}
+
+.note {
+ font-size: small;
+ color: black;
+ background: silver;
+}
+
+.warning {
+ color: red;
+ background: yellow;
+}
+
+.chapter {
+ color: black;
+}
+
+.navbar-top, .navbar-bottom {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.rel-p {
+ width: 9%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.rel-n {
+ width: 6%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.nav-link {
+ width: 39%;
+ align: left;
+ valign: center;
+}
+
+.toc-link {
+ width: 7%;
+ align: left;
+ valign: center;
+}
\ No newline at end of file
diff --git a/OmegaT/doc_src/es/OmegaTUsersManual_xinclude full.xml b/OmegaT/doc_src/es/OmegaTUsersManual_xinclude full.xml
new file mode 100644
index 0000000..4a8337f
--- /dev/null
+++ b/OmegaT/doc_src/es/OmegaTUsersManual_xinclude full.xml
@@ -0,0 +1,75 @@
+
+
+
+
+ OmegaT - Guía de usuario
+
+ vs
+ Vito
+Smolej
+
+
+
+
+
+ Este documento es la guía oficial del usuario de OmegaT, la herramienta libre de traducción asistida por ordenador. También contiene instrucciones de instalación.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/es/PlainText.xml b/OmegaT/doc_src/es/PlainText.xml
new file mode 100644
index 0000000..2e9b4ca
--- /dev/null
+++ b/OmegaT/doc_src/es/PlainText.xml
@@ -0,0 +1,113 @@
+
+
+
+ Trabajando con Texto sin Formato<indexterm class="singular">
+ <primary>Archivos fuente</primary> <secondary>Archivos de texto plano</secondary>
+ </indexterm>
+
+
+ Codificación predeterminada<indexterm class="singular">
+ <primary>Codificación predeterminada</primary> <secondary>Archivos de texto plano</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Archivos fuente</primary> <secondary>Codificación predeterminada</secondary>
+ </indexterm>
+
+ Archivos de texto sin formato - en la mayoría de los casos los archivos con extensión txt - contienen información sólo de texto y no ofrecen una alternativa claramente definida para informar al ordenador el lenguaje que contienen. Lo más que OmegaT puede hacer en este caso, es asumir que el texto está escrito en el mismo idioma que utiliza el propio equipo. Esto no es problema para los archivos codificados en Unicode utilizando un conjunto de caracteres en codificación de 16 bits. Si el texto está codificado en 8 bits, sin embargo, puedes estar ante la siguiente situación incómoda: en lugar de mostrar el texto, para los caracteres Japoneses...
+
+
+
+
+
+
+
+
+
+
+
+ ...El sistema lo mostrará así por ejemplo:
+
+
+
+
+
+
+
+
+
+
+
+ El equipo, corriendo OmegaT, tiene el Ruso como idioma predeterminado, y por lo tanto muestra los caracteres en el alfabeto Cirílico, y no en Kanji.
+
+
+
+ La solución <application>OmegaT</application><indexterm class="singular">
+ <primary>Codificación predeterminada</primary> <secondary>Solución OmegaT</secondary>
+ </indexterm>
+
+ Básicamente, hay tres formas de abordar este problema en OmegaT. Todas ellas implican la aplicación de filtros de archivo en el menú Opciones.
+
+
+
+ Cambiar la codificación de tus archivos a Unicode
+
+
+ abre tu archivo fuente en un editor de texto que interprete correctamente su codificación y guarda el archivo en codificación "UTF-8". Cambia la extensión del archivo de .txt a .utf8.OmegaT automáticamente debe interpretar el archivo como UTF-8. Esta es la alternativa con más sentido común, puesto que nos evita problemas a largo plazo.
+
+
+
+
+
+
+ Especifica la codificación de tus archivos de texto plano
+
+
+ - es decir, archivos con extensión .txt - : en la sección Archivos de texto del cuadro de diálogo Filtros de archivo, cambia la Codificación de archivos fuente de <auto> a la codificación que corresponde a tu archivo fuente .txt, por ejemplo, a .jp para el caso anterior.
+
+
+
+
+
+
+ Cambia las extensiones de los archivos fuente de texto sin formato
+
+
+ por ejemplo, de .txt a .jp para los archivos de texto plano Japoneses: en la sección Archivos de texto del cuadro de diálogo Filtros de archivo, añade un nuevo Patrón de nombre de archivo (*.jp para este ejemplo) y selecciona los parámetros adecuados para la codificación de los archivos fuente y destino
+
+
+
+
+ OmegaT de manera predeterminada tiene la siguiente lista disponible para hacer facilitarte hacer frente a algunos archivos de texto plano:
+
+
+
+ archivos .txt automáticamente a ( <auto> ) interpretados por OmegaT como codificados en la codificación predeterminada del equipo.
+
+
+
+
+
+ .txt1 son archivos en ISO-8859-1, que cubren la mayoría de los idiomas de Europa Occidental.
+ Codificación predeterminadaOccidental
+
+
+
+
+
+
+ .txt2 son archivos en ISO-8859-2, que cubren la mayoría de los idiomas de Europa Central y Oriental
+ Codificación predeterminadaEuropa Central y Oriental
+
+
+
+
+
+
+ .utf8 estos archivos son interpretados por OmegaT como codificado en UTF-8 (una codificación que abarca casi todos los idiomas del mundo).
+ Codificación predeterminadaUnicode
+
+
+
+
+ Lo puedes comprobar tú mismo seleccionando el elemento Filtros de archivo en el menú Opciones. Por ejemplo, cuando tienes un archivo de texto en idioma Checo (muy probablemente escrito en el código ISO-8859-2) sólo tienes que cambiar la extensión.txt a .txt2 y OmegaT interpretará su contenido correctamente. Y, por supuesto, si deseas estar en el lado seguro, ten en cuenta la conversión de este tipo de archivo a Unicode, es decir, al formato de archivo .utf8.
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/es/ProjectProperties.xml b/OmegaT/doc_src/es/ProjectProperties.xml
new file mode 100644
index 0000000..b89af2e
--- /dev/null
+++ b/OmegaT/doc_src/es/ProjectProperties.xml
@@ -0,0 +1,94 @@
+
+
+
+ Propiedades del Proyecto<indexterm class="singular">
+ <primary>Proyecto</primary> <secondary>Propiedades</secondary>
+ </indexterm>
+
+
+
+
+ Cuadro de diálogo propiedades
+
+ El diálogo Ctrl+EProyectoPropiedades... se utiliza para definir y modificar los directorios del proyecto y los idiomas.
+
+
+ Ventana Propiedades del proyecto
+
+
+
+
+
+
+
+
+
+
+
+ Contiene:
+
+
+
+ Un área para configurar el idiomas de origen y destino del proyecto con menús desplegables
+
+
+
+
+
+ Un indicador para configurar la segmentación
+
+
+
+
+
+ Un área para configurar los directorios del proyecto
+
+
+
+ Todos los campos son editables. Puedes introducir los idiomas a mano o usar el menú desplegable. Si ingresas nombres de directorios inexistentes, OmegaT los creará por ti.
+
+
+
+ Modificando las propiedades del proyecto
+
+ Ten en cuenta que los cambios en la configuración de un proyecto pueden tener algunas consecuencias, sobre todo, cuando ya se ha iniciado el proyecto.
+
+
+
+ Cambiando el idioma fuente o destino:
+ ProyectoIdiomas fuente y destino
+
+
+ Ten en cuenta que al cambiar los idiomas puede inutilizar las memorias de traducción utilizadas actualmente, ya que su par de idiomas ya no pueden coincidir con los nuevos idiomas.
+
+
+
+ Modificaciones de segmentación:
+ ProyectoModificando la segmentación
+
+
+ La configuración de segmentación sólo se refiere a la forma en que los archivos fuente son manejados por OmegaT. Esto no modifica la segmentación de las memorias de traducción existentes.
+
+ Los cambios realizados en la configuración de segmentación pueden provocar la división o fusión de algunos segmentos ya traducidos. Esto efectivamente los regresa al estado "original", puesto que ya no coinciden con los segmentos grabados en la memoria del proyecto, a pesar de que tu traducción original todavía está allí.
+
+ OmegaT puede actualizar memorias de traducción antiguas que no usan la segmentación de frases, pero no al revés. Si decides en medio de la traducción cambiar la traducción de frase a párrafo, no se modificará la memoria de traducción interna del proyecto.
+
+
+
+ Cambiando la estructura de directorios:
+ ProyectoCambiando la estructura de directorios
+
+
+ En caso de que decidas modificar los directorios del proyecto, ten en cuenta que esto no va a mover los archivos contenidos en los directorios antiguos a la nueva ubicación.
+
+
+
+ Modificando las propiedades del proyecto durante la sesión:
+ ProyectoModificando durante la sesión
+
+
+ Es posible modificar las propiedades del proyecto durante una sesión de traducción. Sin embargo, hasta que tengas algo de experiencia con OmegaT, lo más seguro es tener en cuenta como definitivos todos los ajustes una vez que haz comenzado la traducción - a menos que, por supuesto, te des cuenta de haber cometido un grave error. Consulta la sección Previniendo la pérdida de datos para los medios de proteger tu trabajo.
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/es/Regexp.xml b/OmegaT/doc_src/es/Regexp.xml
new file mode 100644
index 0000000..cdaabeb
--- /dev/null
+++ b/OmegaT/doc_src/es/Regexp.xml
@@ -0,0 +1,565 @@
+
+
+
+ Expresiones regulares<indexterm class="singular">
+ <primary>Expresiones regulares</primary> <seealso>Segmentación</seealso> <seealso>Búsqueda</seealso>
+ </indexterm>
+
+ Las expresiones regulares (o regex para abreviar) utilizadas en las búsquedas y reglas de segmentación son compatibles con Java. Si necesitas información más específica, consulta la Documentación Regex de Java. Ve las referencias adicionales y los siguientes ejemplos.
+
+
+ Este capítulo está destinado a usuarios avanzados, que tienen que definir sus propias variantes de las reglas de segmentación o idear más complejas y potentes búsquedas de elementos clave.
+
+
+
+ Regex - Indicadores
+
+
+
+
+
+
+ La construcción
+
+ ... coincide con el siguiente
+
+
+
+
+
+ (?i)
+
+ Habilita la coincidencia de mayúsculas y minúsculas (de manera predeterminada, el patrón distingue entre mayúsculas y minúsculas).
+
+
+
+
+
+
+ Regex - Carácter
+
+
+
+
+
+
+ La construcción
+
+ ... coincide con el siguiente
+
+
+
+
+
+ x
+
+ El carácter x, excepto los siguientes...
+
+
+
+ \uhhhh
+
+ El carácter con valor hexadecimal 0xhhhh
+
+
+
+ \t
+
+ El carácter de tabulador ('\u0009')
+
+
+
+ \n
+
+ El carácter de nueva línea (salto de línea) ('\u000A')
+
+
+
+ \r
+
+ El carácter de retorno de carro ('\u000D')
+
+
+
+ \f
+
+ El carácter de alimentación de hoja ('\u000C')
+
+
+
+ \a
+
+ El carácter de alerta (campana) ('\u0007')
+
+
+
+ \e
+
+ El carácter de escape ('\u001B')
+
+
+
+ \cx
+
+ El carácter de control correspondiente a x
+
+
+
+ \0n
+
+ El carácter octal con valor 0n (0 <= n <= 7)
+
+
+
+ \0nn
+
+ El carácter octal con valor 0nn (0 <= n <= 7)
+
+
+
+ \0mnn
+
+ El carácter octal con valor de 0mnn (0 <= m <= 3, 0 <= n <= 7)
+
+
+
+ \xhh
+
+ El carácter hexadecimal con valor 0xhh
+
+
+
+
+
+
+ Regex - Citado
+
+
+
+
+
+
+ La construcción
+
+ ... coincide con el siguiente
+
+
+
+
+
+ \
+
+ Nada, pero cita el siguiente carácter. Esto es necesario si quieres ingresar cualquiera de los caracteres meta !$()*+.<>?[\]^{} para que coincidan con ellos mismos.
+
+
+
+ \\
+
+ Por ejemplo, este es el carácter de barra invertida
+
+
+
+ \Q
+
+ Nada, sino que cita todos los caracteres hasta \E
+
+
+
+ \E
+
+ Nada, pero termina el citando iniciado por \Q
+
+
+
+
+
+
+ Regex - Clases para bloques Unicode y categorías
+
+
+
+
+
+
+ La construcción
+
+ ... coincide con el siguiente
+
+
+
+
+
+ \p{InGreek}
+
+ Un carácter en el bloque griego (simple bloque)
+
+
+
+ \p{Lu}
+
+ Una letra mayúscula (simple categoría)
+
+
+
+ \p{Sc}
+
+ Un símbolo de moneda
+
+
+
+ \P{InGreek}
+
+ Cualquier carácter excepto uno en el bloque Griego (negación)
+
+
+
+ [\p{L}&&[^\p{Lu}]]
+
+ Cualquier letra excepto una letra en mayúscula (sustracción)
+
+
+
+
+
+
+ Regex - Clases de caracteres
+
+
+
+
+
+
+ La construcción
+
+ ... coincide con el siguiente
+
+
+
+
+
+ [abc]
+
+ a, b o c (clase simple)
+
+
+
+ [^abc]
+
+ Cualquier carácter excepto a, b o c (negación)
+
+
+
+ [a-zA-Z]
+
+ desde la a hasta la z o desde la A hasta la Z, ambas inclusive (rango)
+
+
+
+
+
+
+ Regex - Clases predefinidas de caracteres
+
+
+
+
+
+
+ La construcción
+
+ ... coincide con el siguiente
+
+
+
+
+
+ .
+
+ Cualquier carácter (excepto los terminadores de línea)
+
+
+
+ \d
+
+ Un dígito: [0-9]
+
+
+
+ \D
+
+ Un no dígito: [^0-9]
+
+
+
+ \s
+
+ Un espacio en blanco: [ \t\n\x0B\f\r]
+
+
+
+ \S
+
+ Un carácter distinto al espacio en blanco: [^\s]
+
+
+
+ \w
+
+ Un carácter constituyente de palabra: [a-zA-Z_0-9]
+
+
+
+ \W
+
+ Un carácter no constituyente de palabra: [^\w]
+
+
+
+
+
+
+ Regex - Límites de coincidencia
+
+
+
+
+
+
+ La construcción
+
+ ... coincide con el siguiente
+
+
+
+
+
+ ^
+
+ Al comienzo de una línea
+
+
+
+ $
+
+ Al final de una línea
+
+
+
+ \b
+
+ En los límites de una palabra
+
+
+
+ \B
+
+ En los límites de un carácter no constituyente de palabra
+
+
+
+
+
+
+ Regex - Cuantificadores codiciosos
+
+
+
+
+
+
+ La construcción
+
+ ... coincide con el siguiente
+
+
+
+
+
+ X?
+
+ X, una vez o ninguna en absoluto
+
+
+
+ X*
+
+ X, cero o más veces
+
+
+
+ X+
+
+ X, una o más veces
+
+
+
+
+
+
+ cuantificadores codiciosos coinciden tanto como les sea posible. Por ejemplo, a+? coincidirá con aaa en aaabbb
+
+
+
+ Regex - Cuantificadores reacios (tímidos)
+
+
+
+
+
+
+ La construcción
+
+ ... coincide con el siguiente
+
+
+
+
+
+ X??
+
+ X, una vez o ninguna en absoluto
+
+
+
+ X*?
+
+ X, cero o más veces
+
+
+
+ X+?
+
+ X, una o más veces
+
+
+
+
+
+
+ los cuantificadores tímidos coincide tan poco como les sea posible. Por ejemplo, a+? coincidirá con la primera a en aaabbb
+
+
+
+ Regex - Operadores lógicos
+
+
+
+
+
+
+ La construcción
+
+ ... coincide con el siguiente
+
+
+
+
+
+ XY
+
+ X seguida por Y
+
+
+
+ X|Y
+
+ O bien X o bien Y
+
+
+
+ (XY)
+
+ XY como un solo grupo
+
+
+
+
+
+
+ <indexterm class="singular">
+ <primary>Expresiones regulares</primary> <secondary>Herramientas</secondary>
+ </indexterm>Herramienta Regex y ejemplos de uso<indexterm class="singular">
+ <primary>Expresiones regulares</primary> <secondary>Ejemplos de uso</secondary>
+ </indexterm>
+
+ Una serie de herramientas interactivas disponibles para desarrollar y probar expresiones regulares. Por lo general, siguen el mismo patrón (por ejemplo desde el Probador de expresiones regulares ve más abajo): la expresión regular (entrada superior), analiza el texto de búsqueda (cuadro de texto en el centro), produciendo los elementos, mostrados en el cuadro de texto resultado.
+
+
+ Probador Regex
+
+
+
+
+
+
+
+
+
+
+
+
+ Ve El entrenador Regex en versiones para Windows, Linux, FreeBSD de una herramienta independiente. Esta es similar al ejemplo anterior.
+
+ Puedes encontrar una buena colección de útiles casos de expresiones regulares en OmegaT sí (ves Opciones → Segmentación). La siguiente lista incluye expresiones que te pueden ser útiles cuando buscas a través de la memoria de traducción:
+
+
+ Regex - Ejemplos de expresiones regulares en traducciones
+
+
+
+
+
+
+ Expresión regular
+
+ Busca lo siguiente:
+
+
+
+
+
+ (\b\w+\b)\s\1\b
+
+ palabras dobles
+
+
+
+ [\.,]\s*[\.,]+
+
+ coma o un punto, seguido por espacios y otra coma o punto
+
+
+
+ \. \s+$
+
+ espacios en blanco extra después del punto al final de la línea
+
+
+
+ \s+a\s+[aeiou]
+
+ Inglés: las palabras, que empiezan con vocales, generalmente deben estar precedidas por "an", no "a"
+
+
+
+ \s+an\s+[^aeiou]
+
+ Inglés: la misma comprobación que la anterior, pero sobre las consonantes ("a", no "an")
+
+
+
+ \s\s+
+
+ más de un espacio
+
+
+
+ \.[A-Z]
+
+ Un punto, seguido por una letra mayúscula, posiblemente, un espacio omitido entre el punto y el comienzo de una nueva frase.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/es/Searches.xml b/OmegaT/doc_src/es/Searches.xml
new file mode 100644
index 0000000..0150d20
--- /dev/null
+++ b/OmegaT/doc_src/es/Searches.xml
@@ -0,0 +1,141 @@
+
+
+
+ Búsquedas<indexterm class="singular">
+ <primary>Búsquedas</primary>
+ </indexterm>
+
+
+ Ventana de búsqueda
+
+
+ Ventana de búsqueda de texto<indexterm class="singular">
+ <primary>Ventana de búsqueda</primary> <secondary>Ejemplo</secondary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+
+ La búsqueda de arriba encuentra todos los segmentos destino en que ocurren dos o más espacios en blanco - \s\s+ -.
+
+
+
+ Búsqueda<indexterm class="singular">
+ <primary>Atajos</primary> <secondary>Ctrl+F - Buscar</secondary>
+ </indexterm>
+
+ OmegaT proporciona una potente gama de funciones de búsqueda. Abre la ventana de búsqueda con Ctrl+F y escribe la palabra o frase que deseas buscar en el cuadro Buscar. Alternativamente, en la ventana del editor, selecciona una palabra o frase en el campo de edición (texto destino del segmento actual) y pulsa Ctrl+F. La palabra o frase automáticamente se copia en el cuadro Buscar. Puedes tener varias ventanas de búsqueda abiertas al mismo tiempo, pero ciérralas cuando ya no son necesarias para no saturar tu escritorio.
+
+
+
+ Ubicación de búsqueda
+
+ Las búsquedas de manera predeterminada se realizan en las secciones fuente y destino del proyecto, pero puedes limitar tu búsqueda a sólo el texto fuente o destino. Puedes buscar en
+
+
+
+ El proyecto únicamente (configuración predeterminada)
+
+
+
+
+
+ Ambos el proyecto y las memorias de traducción de referencia en /tm/ (consulta Buscar en MT)
+
+
+
+
+
+ un único archivo o un directorio que contiene un conjunto de archivos (consulta Búsqueda en archivos)
+
+
+
+ Al buscar a través de archivos (a diferencia de las memorias de traducción), OmegaT restringe la búsqueda a los archivos en los formatos de archivo fuente (consulta Archivos a traducir → Formatos de archivo). En consecuencia, aunque OmegaT es muy capaz de manejar archivos tmx, no los incluye en la búsqueda en archivos. Si activas
+ BúsquedasOpciones avanzadas
+ Opciones avanzadas, puedes combinar la búsqueda con el nombre del autor de la traducción y la hora del último cambio realizado.
+
+
+
+
+ Usando comodines<indexterm class="singular">
+ <primary>Búsquedas</primary> <secondary>Usando comodines</secondary>
+ </indexterm>
+
+ En ambas búsquedas exactas y por palabra clave, puedes utilizar los caracteres comodín de búsqueda '*' y '?'. Para usar comodines, la opción de expresiones regulares no se debe elegir, debido a que el '*' y la '?' tienen un significado especial en las expresiones regulares.
+
+
+
+ '*' Coincide con cero o más caracteres, desde la posición actual de una palabra dada hasta su fin. El término de búsqueda 'corr*' por ejemplo, correspondería con las palabras "correr", 'corrector' y "corresponder".
+
+
+
+
+
+ '?' coincide con cualquier carácter. Por ejemplo, 'err?' coincidiría con la palabra 'erre' y 'erro' en la palabra "errónea".
+
+
+
+ Las coincidencias se muestran en negrita azul.
+
+
+
+ Métodos de búsqueda<indexterm class="singular">
+ <primary>Búsquedas</primary> <secondary>Métodos</secondary>
+ </indexterm>
+
+ Selecciona el método a utilizar en los botones de radio. Puedes elegir entre dos métodos de búsqueda:
+
+
+
+ Búsqueda exacta
+
+
+ busca segmentos que contienen la cadena exacta que hayas especificado. La búsqueda exacta busca una frase, es decir, si introduces varias palabras, sólo se encuentran si aparecen exactamente en ese orden. Buscar archivo abierto por lo tanto encontrará todas las ocurrencias de la cadena archivo abierto, pero no archivo de salida abierto o archivo de entrada abierto.
+
+
+
+
+ Búsqueda por palabras clave
+
+
+ Busca segmentos que contienen todas las palabras clave que hayas especificado, en cualquier orden. Selecciona la búsqueda por palabra clave para buscar cualquier número de palabras completas individuales, en cualquier orden. OmegaT muestra una lista de todos los segmentos que contienen todas las palabras especificadas. Las búsquedas por palabras clave son similares a una búsqueda "con todas las palabras" en un motor de búsqueda en Internet como Google (y logic). Por lo tanto, al usar la búsqueda de palabras clave con archivo abierto encontrará todas las ocurrencias de la cadena archivo abierto, así como archivo abierto, archivo de entrada abierto, el archivo que haz abierto puede no ser seguro, etc.
+
+
+
+
+ Para cualquiera de estos dos métodos, puedes elegir las siguientes tres opciones:
+
+
+
+ sensible entre mayúsculas y minúsculas: La búsqueda se realizará para la cadena exacta especificada, es decir, observará las mayúsculas y minúsculas.
+
+
+
+ expresiones regulares: La cadena de búsqueda será tratada como una expresión regular. Una expresión regular es una poderosa manera para buscar instancias de una cadena. Es similar a una búsqueda con comodines, pero permite mucha más flexibilidad. Las expresiones regulares utilizadas en las búsquedas son compatibles con Java. Ve más en el capítulo de Expresiones regulares.
+
+
+
+ búsqueda en memorias de traducción: Incluye en la búsqueda las memorias de traducción que están en el directorio tm.
+
+
+
+
+
+ Mostrando resultados de búsqueda
+
+ Al pulsar el botón de búsqueda después de ingresar una cadena en el campo de búsqueda muestra todos los segmentos en el proyecto que incluye la cadena introducida. Dado que OmegaT maneja los segmentos idénticos como una sola entidad, únicamente figura el primer segmento.
+
+ Los segmentos se muestran en el orden de aparición en el proyecto. Segmentos traducidos se muestran con el texto original en la parte superior y el texto traducido en la parte inferior, los segmentos no traducidos únicamente muestran la fuente.
+
+ Al hacer clic en un segmento se abre en el Editor listo para hacerle modificaciones. A continuación, puedes volver a la ventana de búsqueda para el siguiente segmento encontrado, por ejemplo, para comprobar y, si es necesario, corregir la terminología.
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/es/Segmentation.xml b/OmegaT/doc_src/es/Segmentation.xml
new file mode 100644
index 0000000..d4627db
--- /dev/null
+++ b/OmegaT/doc_src/es/Segmentation.xml
@@ -0,0 +1,171 @@
+
+
+
+ Segmentación del texto fuente
+
+ La herramienta de memoria de traducción trabaja con unidades textuales denominadas segmentos. OmegaT tiene dos maneras de segmentar un texto: en párrafos o segmentación de frases (también conocida como "segmentación basada en reglas"). Con el fin de seleccionar el tipo de segmentación, selecciona
+ ProyectoPropiedades
+ Proyecto → Propiedades... desde el menú principal y marca o desmarca la casilla de verificación prevista. La segmentación de párrafo es ventajosa en algunos casos, tal como en traducciones altamente creativas o de estilo en el que el traductor puede desear cambiar el orden de frases enteras, para la mayoría de los proyectos, sin embargo, la segmentación de frases es una opción preferible, ya que ofrece una mejor coincidencia con traducciones anteriores. Si elegiste la segmentación por frases, puedes configurar las reglas seleccionando
+ ProyectoOpciones
+ Opciones → Segmentación... desde el menú principal.
+
+ Las reglas de segmentación fiables ya están disponibles en muchos idiomas, por lo que probablemente no tendrás que involucrarte en la escritura de tus propias reglas de segmentación. Por otro lado esta funcionalidad puede ser muy útil en casos especiales, donde puedes aumentar tu productividad afinando las reglas de segmentación del texto a traducir.
+
+ Precaución: Debido a que el segmentado del texto es diferente después de cambiar las opciones de filtro, posiblemente tengas que empezar a traducir desde cero. Al mismo tiempo, los segmentos válidos anteriormente en la memoria de traducción del proyecto se volverán segmentos huérfanos. Si cambias las opciones de segmentación, cuando un proyecto está abierto, debes volver a cargar el proyecto a fin de que los cambios surtan efecto.
+
+ OmegaT utiliza la siguiente secuencia de pasos:
+
+
+
+
+ SegmentaciónSegmentación a nivel de fuente
+ Estructura del nivel de segmentación
+
+
+ OmegaT primero analiza el texto para estructurar la segmentación de nivel superior. Durante este proceso, sólo estructura el archivo fuente que se utiliza para producir segmentos.
+
+ Por ejemplo, los archivos de texto se pueden segmentar en los saltos de línea, líneas en blanco, o no segmentarse en absoluto. Los archivos que contienen formato (documentos de OpenOffice.org, documentos HTML, etc.) se segmentan a nivel de etiquetas de bloque (párrafo). Atributos de objeto traducibles en XHTML o HTML se pueden extraer como segmentos separados.
+
+
+
+
+
+ SegmentaciónSegmentación a nivel de frase
+ Segmentación a nivel de frase
+
+
+ Después de segmentar el archivo fuente en unidades estructurales, OmegaT segmentará más los bloques en frases.
+
+
+
+
+
+ Reglas de segmentación<indexterm class="singular">
+ <primary>Segmentación</primary> <secondary>Reglas</secondary>
+ </indexterm>
+
+ El proceso de segmentación se puede describir de la siguiente manera: el cursor se mueve a lo largo del texto, un carácter a la vez. En cada posición del cursor las reglas, que consisten en un patrón Antes y Después, se aplican en el orden dado para ver si alguno de los patrones Antes es válido para el texto a la izquierda y el patrón correspondiente Después para el texto a la derecha del cursor. Si las reglas coinciden, ya sea que el cursor se mueva sin insertar un salto de segmento (por una regla de excepción) o se cree un nuevo segmento en la posición actual del cursor (para romper la regla).
+
+ Los dos tipos de reglas se comportan de la siguiente manera:
+
+
+
+
+ SegmentaciónReglasRegla de ruptura
+ Regla de ruptura
+
+
+ Separa el texto fuente en segmentos. Por ejemplo, "Did it make sense? I was not sure." debería dividirse en dos segmentos. Para que esto ocurra, debe haber una regla para romper "?", cuando está seguida por espacios y una palabra que comienza con mayúscula. Para definir una regla como una regla de ruptura, marca la casilla de verificación Ruptura/Excepción.
+
+
+
+
+
+
+
+ SegmentaciónReglasRegla de excepción
+ Regla de excepción
+
+
+ especificar qué partes del texto no se deben separar. A pesar del punto, "Mrs. Dalloway" no se debe dividir en dos segmentos, por tanto debes establecer una regla de excepción para "Mrs" (y para "Mr", "Dr", "prof", etc.), seguida de un punto. Para definir una regla como una regla de excepción, desmarca la casilla de verificación Ruptura/Excepción.
+
+
+
+
+ Las reglas de ruptura predefinidas deberían ser suficientes para la mayoría de los idiomas Europeos y Japoneses. En vista de tal flexibilidad, podrías considerar definir más reglas de excepción para tu idioma fuente a fin de proporcionar segmentos más significativos y coherentes.
+
+
+
+ Prioridad de regla<indexterm class="singular">
+ <primary>Segmentación</primary> <secondary>Prioridad de reglas</secondary>
+ </indexterm>
+
+ Todas las reglas de segmentación se establecen a un patrón de idioma correspondiente se activan y se aplican en el orden de prioridad, por lo que las reglas para el lenguaje específico deben ser superiores a los valores predeterminados. Por ejemplo, las reglas para el Francés canadiense (FR-CA) deben ser mayores que las reglas para el Francés (FR.*), y superiores a la (.*) predeterminada. Por lo tanto, al traducir del Francés canadiense las reglas del Francés de Canadá - su las hay - se aplicarán en primer lugar, seguidas por las reglas para el Francés y, por último, las reglas predeterminadas.
+
+
+
+ Creando una nueva regla<indexterm class="singular">
+ <primary>Segmentación</primary> <secondary>Creando una nueva regla</secondary> <seealso>Expresiones regulares</seealso>
+ </indexterm>
+
+ Generalmente, debes evitar hacer cambios importantes en las reglas de segmentación, en especial después de finalizar el primer borrador, pero algún cambio de menor importancia, tal como la adición de una abreviatura reconocida, puede ser ventajoso.
+
+ A fin de modificar o ampliar un conjunto de reglas, simplemente haz clic sobre ella en la tabla. Las reglas para ese conjunto aparecerán en la mitad inferior de la ventana.
+
+ Con el fin de crear un conjunto de reglas vacío para un nuevo patrón, haz clic en idioma Añadir en la mitad superior del cuadro de diálogo. Aparecerá una línea en blanco en la parte inferior de la tabla superior (posiblemente tengas que desplazarte hacia abajo para verla). Cambia el nombre del conjunto de reglas y el patrón y código del idioma en cuestión (consulta para ver una lista de códigos de idioma). La sintaxis del patrón de idioma se ajusta a la sintaxis de expresión regular. Si el conjunto de reglas maneja un par de idioma - país, te aconsejamos que te muevas a la parte superior con el botón Subir.
+
+ Agrega los patrones Antes y Despuésde. Para comprobar tu sintaxis y su aplicación, te recomendamos usar herramientas que le permiten ver su efecto directamente. Consulta el capítulo sobre lsa Expresiones regulares. Un buen punto de partida siempre serán las reglas existentes.
+
+
+
+ <indexterm class="singular">
+ <primary>Segmentación</primary> <secondary>Ejemplos</secondary>
+ </indexterm>Algunos ejemplos sencillos
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Intención
+
+ Antes
+
+ Después
+
+ Nota
+
+
+
+
+
+ Establece un segmento después de un período ('.') y antes de un espacio
+
+ \.
+
+ \s
+
+ "\." significa el carácter "." "\s" significa cualquier espacio en blanco (espacio, tabulador, nueva página, etc.)
+
+
+
+ No segmenta después de "Mr."
+
+ Mr\.
+
+ \s
+
+ Esta es una regla de excepción, por lo tanto la casilla de verificación de la regla no debe estar marcada
+
+
+
+ Establece un segmento después de "." (Punto Japonés)
+
+ 。
+
+
+
+ Ten en cuenta que después está vacío
+
+
+
+ No segmenta después de "Sr." "M." "Mrs." y "Ms."
+
+ Mr??s??\.
+
+ \s
+
+ Regla de excepción - consulta el uso de ? en expresiones regulares
+
+
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/es/Spellchecker.xml b/OmegaT/doc_src/es/Spellchecker.xml
new file mode 100644
index 0000000..284f0c1
--- /dev/null
+++ b/OmegaT/doc_src/es/Spellchecker.xml
@@ -0,0 +1,94 @@
+
+
+
+ El Corrector Ortográfico<indexterm class="singular">
+ <primary>El Corrector Ortográfico</primary>
+ </indexterm>
+
+ OmegaT ha incorporado un corrector ortográfico basado en el corrector ortográfico utilizado en OpenOffice.org, Firefox y Thunderbird. En consecuencia, es capaz de utilizar la amplia gama de diccionarios ortográficos libres, disponibles para estas aplicaciones.
+
+
+ Instalando diccionarios ortográficos
+
+ Antes de poder utilizar la función de corrección ortográfica, un diccionario o diccionarios adecuados (es decir, de tu idioma destino) deben estar instalados. Para instalar diccionarios ortográficos, sigue este procedimiento:
+
+
+
+ En el administrador de archivos, crea un nuevo directorio en un lugar adecuado en el cual almacenar los diccionarios ortográficos.
+
+
+
+
+
+ En OmegaT, selecciona
+ Menú OpcionesCorrector ortográfico..
+ Opciones → Corrector ortográfico, a continuación, haz clic en Seleccionar junto al campo directorio de archivos de diccionario. Navega y selecciona el directorio creado para los diccionarios.
+
+
+
+
+
+ Coloca los archivos del diccionario que desees utilizar en ese directorio. Fundamentalmente, hay dos maneras en que lo puedes hacer. Puedes copiar los archivos manualmente, es decir, de otra parte del sistema, usando tu gestor de archivos, o puedes utilizar la función "Instalar" de OmegaT la cual te proporciona una lista de diccionarios disponibles para elegir. Ten en cuenta que la opción "Instalar" requiere una conexión a Internet. Los idiomas seleccionados serán instalados y, finalmente, aparecerán en la ventana de configuración del corrector ortográfico (esto puede tardar un rato).
+
+
+
+ Copiar los archivos manualmente es útil si ya tienes los archivos de diccionario adecuados en tu sistema, por ejemplo, como parte de tu instalación de OpenOffice.org o Thunderbird. Los archivos que necesitas tienen las extensiones .aff y .dic, y necesitas dos archivos para que trabaje el diccionario en cuestión. Puedes utilizar estas extensiones de archivo para buscar en tu escritorio los diccionarios adecuados. En el siguiente caso, no se ha ningún directorio adicional y no se han copiado los archivos necesarios, puesto que en su lugar utilizamos el directorio diccionario de OpenOffice:
+
+
+ Configurando el corrector ortográfico
+
+
+
+
+
+
+
+
+ Ten en cuenta que en el caso anterior, es posible que pierdas los diccionarios ortográficos, si remueves de tu sistema la instalación de OpenOffice. Crear tu propio directorio y copiar esos archivos puede ser un trabajo extra, pero, posiblemente, valga la pena.
+
+ Los diccionarios ortográficos más recientes de OpenOffice.org se suministran como "extensiones de OpenOffice.org", con la extensión .oxt. Estos, sin embargo son archivos .zip, si les cambias el nombre a los archivos con la extensión zip, puedes extraer el contenido con una utilidad de compresión, y debes encontrar los archivos .aff y .dic que necesitas, los cuales podrás colocar en el directorio que creaste para ellos.
+
+ Ten en cuenta que la aplicación detrás de "Instalar" depende de la lista de diccionarios de Internet. Si no están actualizados o si no incluye el idioma que deseas, tendrás que buscar vocabularios adecuados a tú mismo. OpenOffice.org contiene probablemente la mayor colección de vocabularios en el sitio de extensiones de OpenOffice.org. Tras descargar e instalar la extensión del diccionario, los aff y dic correspondientes estarán disponibles. Puedes lograr lo mismo descargando un corrector ortográfico para Firefox o Thunderbird, en este caso los archivos del corrector ortográfico se almacenarán en tu perfil (de Firefox o Thunderbird).
+
+ Asegúrate de que el código de idioma de los archivos destino corresponde al código de idioma del diccionario: un diccionario FR-FR no funcionará con un destino configurado cómo FR. Es necesario cambiar la configuración a FR-FR para que el corrector ortográfico reconozca el diccionario correcto para tu destino. Busca los archivos con el nombre, que indica el idioma utilizado y las extensiones aff y dic.
+
+
+
+ Usando diccionarios ortográficos
+
+ No hay necesidad de instruir a OmegaT para utilizar un diccionario ortográfico particular; OmegaT utilizará el diccionario del idioma correcto basándose en los códigos de idioma de tu proyecto. Sin embargo, comprueba que los códigos de idioma son exactamente los mismos: un diccionario FR-FR no funcionará con un destino configurado cómo FR, por ejemplo. Si es necesario, modifica los nombres de archivo de los diccionarios o cambia el idioma configurado en tu proyecto.
+
+ Para habilitar el corrector ortográfico, selecciona Opciones → Corrector ortográfico y marca la casilla de verificación Comprobar la ortografía automáticamente (ver arriba)
+
+
+ <indexterm class="singular">
+ <primary>Corrector ortográfico</primary> <secondary>Corrector ortográfico - figura</secondary>
+ </indexterm>Corrector ortográfico en acción
+
+
+
+
+
+
+
+
+
+
+
+ Haz clic con el botón derecho sobre una palabra subrayada (Artund en la figura anterior), esto abrirá una lista de sugerencias del menú desplegable para la corrección (Art und). También puedes indicar el corrector ortográfico que ignore todas las apariciones de la palabra mal escrita, o agregarla al diccionario.
+
+
+
+ Consejos<indexterm class="singular">
+ <primary>Corrector ortográfico</primary> <secondary>Consejos</secondary>
+ </indexterm>
+
+ Si el corrector ortográfico no funciona, entonces, primero asegúrate de que la casilla de verificación "Comprobar la ortografía automáticamente" en el diálogo del corrector ortográfico (Opciones → Corrector ortográfico...) está marcada.
+
+ También puedes ver el código de idioma destino de tu proyecto contra los vocabularios disponibles en la ventana de configuración. El corrector ortográfico utiliza el código de idioma destino para determinar el idioma que se utilizará: si el idioma de destino es Portugués de Brasil (pt_BR), buscará en el subdirectorio un vocabulario que contenga los dos archivos del vocabulario, llamados pt_br.aff y pt_br.dic.
+
+ Si ya haz traducido una gran cantidad de texto, y te das cuenta que el código de idioma destino del proyecto no coincide con el código de idioma del corrector ortográfico (especificaste pt_BR como el idioma, pero no hay vocabularios pt_BR, por ejemplo), sólo tienes que copiar los dos archivos correspondientes y cambiarles el nombre (por ejemplo, pt_PT.arr y pt_PT.dic a pt._BR.arr y pt_BR.dic). Por supuesto, es mucho más sensato, tomar un breve descanso y descargar la versión correcta del corrector ortográfico.
+
+ Ten en cuenta que Desinstalar elimina físicamente el vocabulario seleccionado. Si son parte de OpenOffice.org, como en el caso anterior, estos van a desaparecer de esta aplicación, también. Si, por cualquier razón, necesitas hacerlo de vez en cuando, posiblemente tenga sentido copiar los archivos que intervienen en un directorio distinto, reservada sólo para que lo use OmegaT.
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/es/TranslationMemories.xml b/OmegaT/doc_src/es/TranslationMemories.xml
new file mode 100644
index 0000000..f0ebf0c
--- /dev/null
+++ b/OmegaT/doc_src/es/TranslationMemories.xml
@@ -0,0 +1,245 @@
+
+
+
+ Memorias de Traducción<indexterm class="singular">
+ <primary>Memorias de Traducción</primary>
+ </indexterm>
+
+
+ Memorias de traducción en OmegaT
+
+
+ directorios tmx - ubicación y propósito
+
+ Los proyectos OmegaT pueden tener los archivos de memoria de traducción - es decir, archivos con la extensión tmx - en cuatro diferentes lugares:
+
+
+
+
+ Memorias de traducciónSubdirectorio omegatArchivos del proyecto
+ Directorio omegat
+
+
+ El directorio omegat contiene el project_save.tmx y, posiblemente, una serie de archivos de copias de seguridad TMX. El archivo project_save.tmx contiene todos los segmentos que se han grabado en la memoria desde que empezó el proyecto. Este archivo existe siempre en el proyecto. Su contenido siempre se ordenará alfabéticamente por el segmento fuente.
+
+
+
+
+
+ Memorias de traducciónDirectorio principal del proyecto
+ Directorio principal del proyecto
+
+
+ El directorio principal del proyecto contiene tres archivos TMX, nombre_proyecto-omegat.tmx, nombre_proyecto-level1.tmx y nombre_proyecto-level2.tmx (donde nombre_proyecto es el nombre del proyecto).
+
+
+
+ El archivo level1 sólo contiene información textual.
+
+
+
+ El archivo de nivel 2 encapsula etiquetas específicas de OmegaT en etiquetas tmx correctas para que el archivo se pueda utilizar con su información de formato en una herramienta de traducción compatible con memorias tmx nivel 2, u OmegaT en sí mismo.
+
+
+
+ El archivo OmegaT incluye etiquetas de formato específicas de OmegaT para que el archivo se pueda utilizar en otros proyectos OmegaT
+
+
+
+ Estos archivos son copias del archivo project_save.tmx. es decir, de la memoria de traducción principal del proyecto, excluyendo los así llamados segmentos huérfanos. Llevan el nombre cambiado correctamente, de modo que su contenido sigue siendo identificable, cuando se utiliza en otros lugares, por ejemplo en el subdirectorio tm de algún otro proyecto (ve más adelante).
+
+
+
+
+ Directorio
+ Memorias de traducciónSubdirectorio tmArchivos del proyecto
+ tm
+
+
+ El directorio /tm/ puede contener cualquier número de memorias de traducción auxiliares - es decir, archivos TMX. Tales archivos se pueden crear en cualquiera de las tres variedades indicadas anteriormente. Ten en cuenta que otras herramientas TAO pueden exportar (también y importar) archivos TMX, por lo general en las tres formas. Lo mejor, por supuesto, es usar archivos TMX específico de OmegaT (ve arriba), para que se mantenga el formato en línea en el segmento.
+
+ El contenido de las memorias de traducción en el subdirectorio tm sirve para generar sugerencias para el texto a traducir. Cualquier texto, ya traducido y almacenado en estos archivos, aparece entre las coincidencias parciales, si es lo suficientemente similar al texto que se está traduciendo.
+
+ Si el segmento fuente en una de las memorias auxiliares es idéntico al texto traducido, OmegaT actúa cómo se ha definido en la ventana del diálogo Opciones → Comportamiento del campo de edición.... Por ejemplo (si aceptas el predeterminado), la traducción de la MT auxiliar es aceptada y prefijada con [parcial], por lo tanto el traductor puede revisar las traducciones en una etapa posterior y comprobar si los segmentos marcados de esta manera, se han traducido correctamente (consulta el capítulo Comportamiento del campo de edición) .
+
+
+
+
+
+ Memorias de traducciónSubdirectorio tm/autoArchivos del proyecto
+ directorio tm/auto
+ ProyectoPretraducción
+
+
+
+ Si está claro desde el principio, que las traducciones en una determinada MT (o MsT) son correctas, las puedes poner en el directorio tm/auto y evitar la confirmación de una gran cantidad de casos [parcial]. Esto efectivamente pretraduce el texto fuente: todos los segmentos en el texto original, por lo tanto las traducciones que se puedan encontrar en estas memorias de traducción "auto", aterrizarán en la MT principal del proyecto sin la intervención del usuario.
+
+
+
+
+ Si lo deseas, puedes permitir a OmegaT que tenga un archivo tmx adicional (estilo OmegaT) en cualquier lugar que especifiques, que contenga todos los segmentos traducibles del proyecto. Ve memorias de pseudotraducción más adelante.
+
+ Ten en cuenta que todas las memorias de traducción se cargan en memoria cuando abres el proyecto. Las copias de seguridad de la memoria de traducción del proyecto se producen con regularidad (consulta el capítulo siguiente), y también se guarda/actualiza project_save.tmx cuando cierras o recargas el proyecto. Esto significa por ejemplo que no es necesario salir de un proyecto en el que estás trabajando si decides añadir otra MT auxiliar al mismo: sólo tienes que recargar el proyecto, y los cambios que hayas hecho serán incluidos.
+
+ Las ubicaciones de las diversas memorias de traducción para un determinado proyecto están definidas por el usuario (consulta la ventana de diálogo en Guía de inicio rápido)
+
+ Dependiendo de la situación, hay diferentes estrategias por lo tanto es posible, por ejemplo:
+
+ varios proyectos sobre el mismo tema: mantener la estructura del proyecto, y cambiar directorios fuente y destino (fuente = fuente/orden1, destino = destino/orden1 etc.) Ten en cuenta que los segmentos del orden1, que no estén presentes en orden2 y otros trabajos posteriores, serán marcados como segmentos huérfanos, sin embargo, seguirán siendo útiles para obtener coincidencias parciales.
+
+ varios traductores trabajan en el mismo proyecto: dividiendo los archivos fuente en fuente/Alicia, fuente/Bob... y asignarlos a los miembros del equipo (Alicia, Bob...). Ellos pueden crear sus propios proyectos y, entregar su propio project_save.tmx, cuando hayan terminado o cuando se haya alcanzado un hito dado. Entonces se recogen los archivos project_save.tmx y se resuelven los posibles conflictos en cuanto a terminología, por ejemplo. Se crea una nueva versión de la MT principal, ya sea para ponerla en los subdirectorios tm/auto de los miembros del equipo o para reemplazar sus archivos project_save.tmx. El equipo también puede utilizar la misma estructura de directorios para los archivos destino. Esto les permite, por ejemplo, revisar en cualquier momento, si todavía está bien la versión destino para todo el proyecto
+
+
+
+ Copia de seguridad tmx<indexterm class="singular">
+ <primary>Memorias de traducción</primary> <secondary>Copia de seguridad</secondary>
+ </indexterm>
+
+ A medida que traduces tus archivos, OmegaT almacena tu trabajo continuamente en project_save.tmx en el subdirectorio /omegat del proyecto.
+
+ OmegaT también crea copias de seguridad de la memoria de traducción en project_save.tmx.AÑOMESDÍAHORAMIN.bak en el mismo subdirectorio cada vez que abres o recargas el proyecto. AÑO son los 4 dígitos del año, MES es un mes, DÍA el día del mes, y HORA son las horas y MIN los minutos, de cuando se salvó la memoria de traducción anterior.
+
+ Si crees que haz perdido los datos de traducción, sigue el siguiente procedimiento:
+
+
+
+ Cierra el proyecto
+
+
+
+ Cambia el nombre al archivo project_save.tmx actual (por ejemplo, project_save.tmx.temporal)
+
+
+
+ Selecciona la copia de seguridad de la memoria de traducción que sea más probable contenga los datos que buscas (por ejemplo, la más reciente o la última versión desde el día anterior)
+
+
+
+ Cópiala a project_save.tmx
+
+
+
+ Abre el proyecto
+
+
+
+
+
+ Archivos tmx y el idioma<indexterm class="singular">
+ <primary>Memorias de traducción</primary> <secondary>Idioma</secondary>
+ </indexterm>
+
+ Los archivos tmx contienen unidades de traducción, hechas de una serie de segmentos equivalentes en varios idiomas. Una unidad de traducción comprende al menos dos variaciones de la unidad de traducción (tuv por translation unit variations). O bien se puede utilizar como fuente o destino.
+
+ Los ajustes en el proyecto indican cual es la fuente y cual el idioma destino. OmegaT toma en consideración los códigos de idioma fuente y destino correspondientes a los segmentos tuv del proyecto y los utiliza como el original y su traducción, respectivamente. OmegaT reconoce los códigos de idioma usando las siguientes dos normas:
+
+
+
+ 2 letras (por ejemplo, JA para japonés), o
+
+
+
+ 2 - o 3 letras en el código de idioma seguidas del código del país de 2 letras (por ejemplo, EN-US - Consulta para una lista parcial de los códigos de idioma y país).
+
+
+
+ Si los códigos de idioma del proyecto y los códigos de idioma del tmx coinciden completamente, los segmentos se cargan en memoria. Si los idiomas coinciden, pero no el país, los segmentos aún se cargan. Si ni el código de idioma coincide ni el código de país, los segmentos serán ignorados.
+
+
+
+ Segmentos huérfanos<indexterm class="singular">
+ <primary>Memorias de traducción</primary> <secondary>Segmentos huérfanos</secondary>
+ </indexterm>
+
+ El archivo project_save.tmx contiene todos los segmentos que haz traducido desde que empezaste el proyecto. Si modificas la segmentación del proyecto o borras los archivos fuente, algunas coincidencias pueden aparecer como cadenas huérfanas en el visor de coincidencias: estas coincidencias se refieren a los segmentos que ya no existen más en los documentos fuente, ya que corresponden a segmentos traducidos y registrados antes de llevar a cabo la modificación.
+
+
+
+
+ Reutilizando memorias de traducción<indexterm class="singular">
+ <primary>Memorias de traducción</primary> <secondary>Importando y exportando</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Memorias de traducción</primary> <secondary>Reutilizando memorias de traducción</secondary>
+ </indexterm>
+
+ En un principio, cuando creas el proyecto, la MT principal del proyecto, project_save.tmx está vacía. Esta MT se llena gradualmente durante la traducción. Para acelerar este proceso, puedes reutilizar traducciones existentes. Si una frase dada ya se tradujo una vez, y está traducida correctamente, no hay necesidad de volverla a traducir. Las memorias de traducción también pueden contener traducciones de referencia: legislación multinacional, como la de la Comunidad Europea, es un ejemplo típico.
+
+ Al crear los documentos traducidos en un proyecto OmegaT, la memoria de traducción del proyecto se emitirá en forma de tres archivos en el directorio raíz de tu proyecto OmegaT (consulta la descripción anterior). Puedes considerar que estos tres archivos TMX (-omegat.tmx, -level1.tmx y -level2.tmx) como una "memoria de traducción de exportación", es decir, como producto de exportación del contenido de tu proyecto actual en forma bilingüe.
+
+ Si deseas volver a utilizar una memoria de traducción de un proyecto anterior (por ejemplo, porque el nuevo proyecto es similar al proyecto anterior, o utiliza una terminología que podrías haber usado antes), puedes utilizar estas memorias de traducción como "memorias de traducción de entrada", es decir, para importarlas a tu nuevo proyecto. En este caso, coloca las memorias de traducción que deseas utilizar en el directorio \tm o \tm\auto de tu nuevo proyecto: en el primer caso obtendrás sugerencias en el visor de coincidencias parciales de estas memorias de traducción, y en el último caso puedes utilizar las memorias de traducción para pretraducir el texto original.
+
+ De manera predeterminada, el directorio \tm está por debajo del directorio raíz del proyecto (por ejemplo ...\MiProyecto\tm), pero puedes elegir un directorio diferente en el cuadro de diálogo Propiedades del proyecto si lo deseas. Esto es útil si utilizas frecuentemente memorias de traducción producidas en el pasado, por ejemplo, porque están en el mismo tema o son para el mismo cliente. En este caso, un procedimiento útil sería:
+
+
+
+ Crea un directorio (un "directorio repositorio") en una ubicación conveniente en tu disco duro para las memorias de traducción para un cliente o tema particular.
+
+
+
+
+
+ Cada vez que termines un proyecto, copia uno de los tres archivos "exportables" de la memoria de traducción del proyecto al directorio del repositorio.
+
+
+
+
+
+ Cuando comiences un nuevo proyecto sobre el mismo tema o para el mismo cliente, navega al directorio del repositorio desde el cuadro de diálogo Propiedades del Proyecto → Editar Proyecto y selecciónalo como el directorio de memorias de traducción.
+
+
+
+ Cuando comiences un nuevo proyecto sobre el mismo tema o para el mismo cliente, navega al directorio del repositorio en el diálogo Proyecto → Propiedades → Editar Proyecto y selecciónalo como el directorio de memorias de traducción. Ten en cuenta que todos los archivos TMX en el repositorio/tm se analizan cuando abres el proyecto, por lo que poner todo lo que puedas allí, puede retrasar innecesariamente a OmegaT. Incluso, puedes considerar eliminar aquellos que no sean necesarios más, una vez que haz utilizado su contenido para llenar el archivo project_save.tmx.
+
+
+ Importando y exportando memorias de traducción
+
+ OmegaT es compatible con tmx importadas versiones 1.1-1.4b (en ambos niveles 1 y 2). Esto permite que OmegaT pueda leer las memorias de traducción producidas por otras herramientas. Sin embargo, OmegaT no es totalmente compatible con archivos tmx importados de nivel 2 (estos no sólo almacenan la traducción, sino también el formato). Puedes importar archivos TMX Nivel 2 y su contenido textual se puede ver en OmegaT, pero la calidad de las coincidencias parciales será algo menor.
+
+ OmegaT sigue procedimientos muy estrictos cuando carga archivos de memorias de traducción (TMX). Si se encuentra un error en un archivo, OmegaT indicará la posición dentro del archivo defectuoso en que se encuentra el error.
+
+ Algunas herramientas son conocidas por producir archivos TMX válidos bajo ciertas condiciones. Si deseas utilizar este tipo de archivos como traducciones de referencia en OmegaT, los debes reparar, u OmegaT informará de un error y no los cargará. Los parches son operaciones triviales y OmegaT te ayuda a solucionar los problemas con mensajes de error relacionados. Puedes preguntar en el grupo de usuarios para pedir ayuda si tienes problemas.
+
+ OmegaT exporta archivos TMX versión 1.4 (tanto en nivel 1 cómo nivel 2). La exportación en nivel 2 no es totalmente compatible con el nivel 2 estándar, pero está lo suficientemente cerca y generará coincidencias correctas en otras herramientas compatibles con memorias de traducción TMX nivel 2. Si sólo necesitas información textual (y no información de formato), utiliza el archivo nivel 1 que OmegaT ha creado.
+
+
+
+
+ Memoria pseudotraducida<indexterm class="singular">
+ <primary>Memorias de traducción</primary> <secondary>Pseudotraducción</secondary>
+ </indexterm>
+
+
+ ¡De interés sólo para usuarios avanzados!
+
+
+ Antes de traducir los segmentos, posiblemente desees preprocesarlos o dirigirlos de alguna otra manera posible con OmegaT. Por ejemplo, si deseas crear una pseudotraducción para propósitos de prueba, OmegaT te permite crear un archivo TMX adicional que contiene todos los segmentos del proyecto. La traducción en este tmx puede ser
+
+
+
+ una traducción igual al original (predeterminada)
+
+
+
+
+
+ con los segmentos de traducción vacíos
+
+
+
+ Puedes dar cualquier nombre que especifiques al archivo TMX. Puedes generar una memoria de pseudotraducción con los parámetros de línea de ordenes:
+
+ java -jar omegat.jar --pseudotranslatetmx=<nombrearchivo> [pseudotranslatetype=[equal|empty]]
+
+ Sustituye <nombrearchivo> con el nombre del archivo que deseas crear, ya sea absoluto o relativo al directorio de trabajo (el directorio dónde iniciaste OmegaT). El segundo argumento --pseudotranslatetype es opcional. Su valor es igual (valor predeterminado, para fuente=destino) o vacío (segmento destino está vacío). Puedes procesar la tmx generada con cualquier herramienta que desees. Para reutilizarla en OmegaT cámbiale el nombre a project_save.tmx y colócala en el directorio omegat de tu proyecto.
+
+
+
+ Actualizando memorias de traducción<indexterm class="singular">
+ <primary>Memorias de traducción</primary><secondary>Actualizando a segmentación de frases</secondary>
+ </indexterm>
+
+ Versiones muy tempranas de OmegaT fueron capaces de segmentar archivos fuente en párrafos únicamente y eran inconsistentes numerando las etiquetas en formato HTML y archivos "Open Document". OmegaT 2.3 puede detectar y actualizar al vuelo dichos archivos TMX para aumentar la calidad de coincidencias parciales y aprovechar tu mejor traducción existente, lo cual te ahorra el trabajo de hacerlo manualmente.
+
+ Un proyecto TMX se actualizará una sola vez, y será escrito en forma de actualización y los archivos TMX heredados se actualizarán al vuelo cada vez que cargues el proyecto. Ten en cuenta que en algunos casos, los cambios en los filtros de archivo en OmegaT 2.3 pueden conducir a una segmentación totalmente diferente, y como resultado, tendrás que actualizar manualmente tu traducción en tales casos excepcionales.
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/es/UserInterface.xml b/OmegaT/doc_src/es/UserInterface.xml
new file mode 100644
index 0000000..67d6be2
--- /dev/null
+++ b/OmegaT/doc_src/es/UserInterface.xml
@@ -0,0 +1,620 @@
+
+
+
+ La interfaz de usuario
+
+
+ Elementos de la interfaz de usuario
+
+
+ Ventanas utilizadas frecuentemente<indexterm class="singular">
+ <primary>Ventanas y paneles en OmegaT</primary>
+ </indexterm>
+
+
+
+ OmegaT Ventana principal
+
+
+ contiene el menú principal, la barra de estado y varios paneles:
+
+
+
+ Editor - donde escribes y editas la traducción
+
+
+
+ Visor de coincidencias - muestra los segmentos más similares desde las memorias de traducción
+
+
+
+ Visor del glosario - muestra la terminología
+
+
+
+ Visor del diccionario - muestra información proporcionada por los diccionarios
+
+
+
+ Traducción automática - muestra la traducción proporcionada por servicios de traducción automática, como Google Translate
+
+
+
+
+
+
+
+ AtajosCtrl+L - Ventana de Archivos del proyecto
+ Ventana archivos del proyecto
+
+
+ La lista de los archivos traducibles (se abre con Ctrl+L, y se cierra con Esc)
+
+
+
+
+
+ AtajosCtrl+F - Ventana de búsqueda
+ Ventana de búsqueda
+
+
+ Se utiliza para buscar segmentos específicos en el proyecto (se abre con Ctrl+F, se cierra con Esc)
+
+
+
+
+
+
+ Utilizadas con menos frecuencia
+
+
+
+
+ AtajosCtrl+T - ventana de validación de etiquetas
+ Ventana de validación de etiquetas
+
+
+ Se utiliza para comprobar los errores de etiqueta en las traducciones (se abre con Ctrl+T se cierra con Esc)
+
+
+
+
+
+ AtajosF1 - Ayuda
+ Navegador de ayuda
+
+
+ Se usa para leer el manual del usuario (se abre con
+F1, se cierra con Esc)
+
+
+
+
+ Ventana de estadísticas de coincidencias
+
+
+ Se utiliza para abrir la ventana con las estadísticas del proyecto, selecciona
+ Menú HerramientasEstadísticas de coincidencias
+ Herramientas → Estadísticas de coincidencias.
+
+
+
+
+
+
+ Diálogo Configuración del proyecto<indexterm class="singular">
+ <primary>Proyecto</primary> <secondary>Propiedades</secondary>
+ </indexterm>
+
+ Los cuadros de diálogo de abajo se utilizan para cambiar la configuración del proyecto OmegaT. Cada opción se describe en detalle en una sección aparte, la siguiente información resume su uso y la forma en que se invoca:
+
+
+
+
+ AtajosCtrl+E - Propiedades del proyecto
+
+ Menú ProyectoPropiedades
+ Propiedades del proyecto
+
+
+ Se utiliza para modificar los directorios e idiomas del proyecto, (se accede a través de Ctrl+EProyecto → Propiedades..., se cierra con Esc)
+
+
+
+
+
+ Configuración del proyectoTipo de letra
+ Tipo de letra
+ Menú OpcionesTipo de letra
+
+
+
+ Se utiliza para modificar el tipo de letra utilizado por OmegaT para mostrar la fuente, la traducción, las coincidencias y los términos del glosario, (se accede a través de Opciones → Tipo de letra..., se cierra con Esc)
+
+
+
+
+
+ Configuración del proyectoFiltros de archivo
+ Filtros de archivo
+ Menú OpcionesFiltros de archivo
+
+
+
+ Se utiliza para ajustar el manejo de los formatos de archivo (se accede a través de Opciones → Filtros de archivo..., se cierra con Esc)
+
+
+
+
+
+ Configuración del proyectoSegmentación
+ Segmentación
+ Menú OpcionesSegmentación
+
+
+
+ Se utiliza para cambiar la forma en que se divide tu texto en oraciones (se accede a través de Opciones → Segmentación, se cierra con Esc)
+
+
+
+
+
+ Configuración del proyectoComportamiento del campo de edición
+ Comportamiento del campo de edición
+ Menú OpcionesComportamiento del campo de edición
+
+
+
+ Se utiliza para cambiar la forma en que OmegaT se comporta cuando iteras entre los segmentos (se accede a través de Opciones → Comportamiento del campo de edición..., se cierra con Esc)
+
+
+
+
+
+
+
+ <application>OmegaT</application> Ventana principal<indexterm class="singular">
+ <primary>Ventanas y paneles en OmegaT</primary> <secondary>Ventana principal</secondary> <tertiary>- figura</tertiary>
+ </indexterm><indexterm class="singular">
+ <primary>Ventanas y paneles en OmegaT</primary> <secondary>Ventana principal</secondary>
+ </indexterm>
+
+
+ Paneles de OmegaT
+
+
+
+
+
+
+
+
+
+
+
+
+ La ventana principal consta de varios paneles, el menú principal y una barra de estado. Puedes cambiar la posición de cualquier panel o incluso lo puedes desacoplar a una ventana independiente, haz clic y arrastra el panel por su nombre. Dependiendo del estado del panel, pueden aparecer distintos signos en la esquina superior derecha:
+
+
+ Elementos gráficos del panel<indexterm class="singular">
+ <primary>Ventanas y paneles en OmegaT</primary> <secondary>Elementos gráficos del panel</secondary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ minimiza el panel, de modo tal que sólo aparece su nombre en la parte inferior de la ventana.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ maximizar panel
+
+
+
+
+
+
+
+
+
+
+
+
+
+ desacopla el panel de la ventana principal.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ pone de nuevo en el panel en la ventana principal.
+
+
+
+
+
+ Puedes solapar los paneles si lo deseas. Cuando haces esto los paneles muestran una pestaña en la parte superior. Los separadores entre paneles se pueden arrastrar para reajustar el tamaño de los mismos. En caso de perder la pista de los cambios en la interfaz de usuario, puedes utilizar
+ Ventanas de OmegaTVentanas y paneles en OmegaT
+
+ Ventanas de OmegaTRestableciendo la configuración de fábrica
+ Opciones → Restaurar ventana principal en cualquier momento para volver al diseño original.
+
+ Los contadores en la esquina inferior derecha mantienen el seguimiento del progreso de la traducción (los números en la columna de la izquierda se refieren a la figura anterior):
+
+
+ Ventana principal - contadores<indexterm class="singular">
+ <primary>Ventanas y paneles en OmegaT</primary> <secondary>Contadores</secondary>
+ </indexterm>
+
+
+
+
+
+
+ 33/33
+
+ número de segmentos - traducidos contra total del archivo actual
+
+
+
+ 2780/2780
+
+ número de segmentos únicos - traducidos contra total en el proyecto
+
+
+
+ 3760
+
+ Número total de segmentos (incluyendo repetidos) en el proyecto
+
+
+
+ 126/127
+
+ número de caracteres fuente y destino en el segmento actual
+
+
+
+
+
+ Desde un punto de vista práctico, la pareja más importante de los números es el segundo par: este dice, cuánto hemos hecho hasta ahora, en relación con el total o segundo número. El proyecto en el ejemplo, evidentemente ya lo haz terminado, ya que se han traducido todos los segmentos únicos.
+
+
+ Panel de edición<indexterm class="singular">
+ <primary>Ventanas y paneles en OmegaT</primary> <secondary>Panel de edición</secondary>
+ </indexterm>
+
+ Aquí es donde puedes escribir y editar la traducción. El panel de edición muestra el texto parcialmente traducido del documento: el texto traducido se muestra en la traducción, mientras que el texto no traducido se muestra en el idioma original. El texto mostrado se divide en segmentos y te puedes desplazar por el documento haciendo doble clic en cualquier segmento para abrirlo y editarlo. En el caso anterior, los segmentos ya traducidos se muestran en amarillo, pero puedes cambiar esto para adaptarse a tus preferencias (consulta ).
+
+ Uno de los segmentos de arriba es el segmento actual. Es el segmento que se muestra en dos partes. La parte superior está en el idioma fuente, en negrita con fondo de color verde, la parte inferior es el campo de edición, terminado con un marcador:
+ Marcador de segmento
+ el marcador es <segmento nnnn> donde nnnn es el número del segmento en el proyecto. Usa la parte superior como referencia y reemplaza o modifica el contenido del campo de edición con la traducción.
+
+ Dependiendo del comportamiento de edición preferido, el campo de edición para el segmento sin traducir posiblemente esté vacío, contiene el texto fuente, o contienen la traducción de la cadena más similar a la que estás traduciendo. Cuando te mueves a otro segmento, la traducción será validada y almacenada. Si deseas que la traducción sea la misma que la original, simplemente haz que el campo de edición se vacíe quitando todo el texto (selecciona todo con Ctrl+A y elimínalo con Del). OmegaT es capaz de almacenar las traducciones que son idénticas a la fuente. Esto es útil para documentos que contienen marcas, nombres u otros nombres propios, o partes de un tercer idioma que no requiere traducción. Consulta Opciones de comportamiento del campo de edición para más detalles.
+
+ Si haces clic con el botón derecho sobre el panel de edición, se abre un menú, ofreciendo cortar, copiar, pegar (es decir, las mismas funciones que Ctrl+X, Ctrl+C y Ctrl+V) y las funciones para Ir al segmento.
+
+
+
+ Visor de coincidencias
+
+
+ <indexterm class="singular">
+ <primary>Coincidencias</primary> <secondary>Panel de coincidencias parciales - figura</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Ventanas y paneles en OmegaT</primary> <secondary>Panel de coincidencias parciales - figura</secondary>
+ </indexterm>Panel de coincidencias
+
+
+
+
+
+
+
+
+
+
+
+
+ El visor muestra las coincidencias parciales más similares con los segmentos desde las memorias de traducción, tanto de la memoria de traducción interna del proyecto creada en tiempo real a medida que traduces tu proyecto y las memorias de traducción auxiliares que hayas importado de tus trabajos anteriores, o hayas recibido de tu cliente o agencia de traducción.
+
+ Cuando te mueves al siguiente segmento, la primer coincidencia parcial (la que tiene el mejor porcentaje de similitud) se selecciona automáticamente. Puedes seleccionar una coincidencia diferente pulsando Ctrl+2, 3, 4 ó 5.
+ AtajosCtrl+N - Selecciona la coincidencia
+ Por supuesto, al pulsar Ctrl+5 no tendrá ningún efecto, si no hay ninguna coincidencia #5. Para utilizar la coincidencia seleccionada en la traducción, usa Ctrl+R
+ AtajosCtrl+R - Reemplaza el texto
+ para reemplazar el campo destino con la coincidencia o usa Ctrl+I
+ AtajosCtrl+I - Inserta el texto
+ para insertarla en la posición del cursor.
+
+ El porcentaje de coincidencia es aproximadamente equivalente al número de palabras comunes en la coincidencia y el segmento correspondiente dividido entre el número de palabras en el más largo de los dos. La coincidencia parcial seleccionada se resalta en negrita, las palabras que faltan en el segmento que se está traduciendo son de color azul y las palabras junto a las partes que faltan de color verde. En el ejemplo anterior, el segmento fuente es Duración de exposición <15 min. La coincidencia es superior al 60%, ya que coinciden 3 de cada 5 palabras. La línea con el porcentaje de coincidencia también incluye el nombre de la memoria de traducción
+ Memorias de traducciónCoincidencias
+ que contiene la coincidencia. Si no muestra ningún nombre de archivo, la fuente es la memoria de traducción interna del proyecto. Segmentos huérfanos
+ Memorias de traducciónSegmentos huérfanos
+ (la coincidencia #4) describe los segmentos de la memoria de traducción predeterminada del proyectos que no tiene ningún segmento fuente correspondiente.
+
+ En realidad, hay tres estimaciones de coincidencia disponibles (60/60/54 en el caso de la parte superior de la coincidencia anterior). Estas se definen como sigue:
+
+
+
+ porcentaje de coincidencia cuando se utiliza el complemento segmentador
+
+
+
+
+
+ Coincidencia predeterminada de OmegaT - número de palabras coincidentes - omitiendo números y etiquetas - dividido entre el número total de palabras
+
+
+
+
+
+ Coincidencia OmegaT, incluyendo números y etiquetas
+
+
+
+
+
+ Glosario<indexterm class="singular">
+ <primary>Ventanas y paneles en OmegaT</primary> <secondary>Panel glosario</secondary>
+ </indexterm>
+
+ El panel del Glosario te permite acceder a tu propia colección de expresiones y términos técnicos que hayas acumulado en los archivos de glosario. Este muestra la traducción de términos que se encuentran en el segmento actual, pero sólo para fines de referencia: no hay ninguna característica para la inserción de la traducción o sustitución del término con estas.
+
+
+ <indexterm class="singular">
+ <primary>Glosarios</primary> <secondary>Ventana de glosario - figura</secondary>
+ </indexterm>Panel glosario
+
+
+
+
+
+
+
+
+
+
+
+
+ El segmento fuente en el ejemplo anterior fue "En la mayoría de los trabajos de traducción se considera importante contar con que la traducción del documento tiene un aspecto similar al original.", y dos palabras en el mismo, documento y traducción se encontraron en el archivo de glosario. OmegaT también es compatible con términos multipalabras:
+
+
+ <indexterm class="singular">
+ <primary>Glosarios</primary> <secondary>entradas multipalabra en el glosario - figura</secondary>
+ </indexterm>entrada multipalabra en el glosario
+
+
+
+
+
+
+
+
+
+
+
+
+ Si tienes activada la opción Consejos de traducción Opciones → Consejos de traducción), puedes hacer clic con el botón derecho sobre la palabra destacada en el segmento fuente para abrir un menú desplegable con las traducciones alternativas, como las ofrecidas por el glosario. Al seleccionar una de ellas se inserta en la posición actual en el segmento destino. También puedes destacar tu alternativa preferida en el panel de glosario e insertarla en el destino haciendo clic con el botón derecho en la selección.
+
+
+
+ Visor del diccionario<indexterm class="singular">
+ <primary>Ventanas y paneles en OmegaT</primary> <secondary>Panel diccionario</secondary>
+ </indexterm>
+
+ Los diccionarios son el equivalente electrónico de los diccionarios impresos como Merriam Webster, Duden, Larousse, etc., que puedas tener en tu escritorio.
+
+
+
+ Traducción automática<indexterm class="singular">
+ <primary>Ventanas y paneles en OmegaT</primary> <secondary>Traducción automática</secondary>
+ </indexterm>
+
+ El panel de traducción automática, al abrirse, contiene las sugerencias de las herramientas de traducción automática para el segmento actual. Presiona las teclas Ctrl+M para sustituir la traducción del segmento actual con la traducción sugerida.
+
+
+
+ Menú principal
+
+ El menú principal te permite acceder a todas las funciones de OmegaT. Consulta el apéndice Menú Principal para una descripción completa de todos los menús y sus elementos. Las funciones utilizadas frecuentemente son accesibles con atajos del teclado, así que una vez que te acostumbres a ellos, ya no tendrás que navegar por los menús mientras traduces.
+
+
+
+ Barra de estado
+
+ La barra de estado muestra el flujo de trabajo relacionado a los mensajes en la parte inferior de la ventana principal. Esta barra ofrece retroalimentación al usuario en las operaciones específicas que están en curso. También muestra el número de coincidencias parciales y del glosario para el segmento actual.
+
+
+
+
+ Otras ventanas
+
+
+ Archivos del proyecto<indexterm class="singular">
+ <primary>Ventanas y paneles en OmegaT</primary> <secondary>Archivos del proyecto</secondary>
+ </indexterm>
+
+ La ventana de Archivos del proyecto lista los archivos del proyecto y muestra información del proyecto. Esta se muestra automáticamente cuando cargas un proyecto OmegaT. Usa Ctrl+L
+ AtajosCtrl+L - Lista de archivos del proyecto
+ para abrirla y Esc para cerrarla. La ventana de Archivos del proyecto muestra la siguiente información:
+
+
+
+ la lista de todos los archivos traducibles en el proyecto. Estos son los archivos que se encuentran en el directorio de archivos fuente en un formato que OmegaT es capaz de reconocer. Al hacer clic en algún archivo este se abrirá para su traducción.
+
+
+
+
+
+ el archivo disponible actualmente en el panel de edición está resaltado con un fondo azul. Al presionar la tecla Entrar te llevará al panel de edición colocándote en la parte superior del archivo seleccionado
+
+
+
+
+
+ al lado del nombre del archivo muestra el número de segmentos de cada archivo
+
+
+
+
+
+ el número total de segmentos, el número de segmentos únicos en todo el proyecto, y el número de segmentos únicos ya traducidos se muestran en la parte inferior
+
+
+
+ El conjunto de segmentos únicos se calcula tomando todos los segmentos y eliminando todos los segmentos duplicados. (La definición de "único" es sensible a mayúsculas y minúsculas: "Ejecutar" y "ejecutar" son tratados como si fueran diferentes)
+
+ La diferencia entre el "Número de segmentos" y "Número de segmentos únicos" proporciona una idea aproximada del número de repeticiones en el texto. Ten en cuenta sin embargo, que los números no indican la relevancia de las repeticiones: que podrían significar declaraciones relativamente largas repetidas varias veces (en cuyo caso eres afortunado) o puede describir una tabla de palabras clave (no tan afortunado). El archivo project_stats.txt que se encuentra en el directorio omegat del proyecto contiene información por segmentos más detallada, desglosada por archivo.
+
+ Modificar las reglas de segmentación puede tener el efecto de modificar el número de segmentos/segmentos únicos. Esto, sin embargo, en general, lo debes evitar una vez que haz comenzado a traducir el proyecto. Ve el capítulo Reglas de segmentación para más información.
+
+
+ Archivos fuenteAñadiendo archivos al proyecto
+ Añadiendo archivos al proyecto: Puedes agregar archivos fuente al proyecto haciendo clic en "Importar archivos fuente..." Esto copia los archivos seleccionados al directorio fuente y vuelve a cargar el proyecto para importar los archivos nuevos. También puedes agregar archivos fuente desde páginas de Internet, escritas en MediaWiki, haciendo clic en "Importar archivos desde MediaWiki" y proporcionando la dirección correspondiente.
+
+
+
+ Ventana de búsqueda<indexterm class="singular">
+ <primary>Ventanas y paneles en OmegaT</primary> <secondary>Panel de búsqueda</secondary>
+ </indexterm>
+
+ Puedes utilizar la ventana de búsqueda para encontrar segmentos específicos en un proyecto. También puedes tener varias ventanas de búsqueda abiertas al mismo tiempo. Para abrir una ventana de búsqueda, utiliza Ctrl+F en la ventana principal. La ventana de búsqueda se compone de un campo de texto para la cadena de búsqueda o palabras clave, indicadores y botones de radio para crear la cadena de búsqueda y un área de pantalla que contiene los resultados de la búsqueda. Consulta el capítulo Búsquedas para obtener más información acerca de la ventana de búsqueda.
+
+
+
+ Validación de etiquetas<indexterm class="singular">
+ <primary>Validando etiquetas</primary> <seealso>Atajos, Etiquetas</seealso>
+ </indexterm><indexterm class="singular">
+ <primary>Ventanas y paneles en OmegaT</primary> <secondary>Validación de etiquetas</secondary> <seealso>Etiquetas</seealso>
+ </indexterm>
+
+ La ventana de validación de etiquetas detecta y muestra los errores e inconsistencias en las etiquetas de la traducción. Abre la ventana con Ctrl+T. La ventana cuenta con una tabla de 3 columnas, con un enlace al segmento, su fuente y el contenido destino:
+
+
+ <indexterm class="singular">
+ <primary>Validando etiquetas</primary> <secondary>Ventana - figura</secondary> <seealso>Etiquetas</seealso>
+ </indexterm>Ventana de validación de etiquetas
+
+
+
+
+
+
+
+
+
+
+
+
+ Las etiquetas están resaltadas en negrita azul para facilitar la comparación entre el original y el contenido traducido. Haz clic en el enlace para saltar al segmento en el panel de edición. Corrige el error, si es necesario y pulsa Ctrl+T para volver a la ventana de validación de etiquetas para corregir otros errores. En el primer y tercer caso anterior las etiquetas se emparejan incorrectamente, y en el segundo caso se omitió el signo < en la etiqueta inicial.
+
+ Los errores de etiqueta son casos en que las etiquetas en la traducción no corresponden en orden y número con el segmento original. Algunos escenarios señalados de etiquetas en la ventana de validación de etiquetas son necesarios y son benignos, otros causan problemas cuando se crea el documento traducido. Las etiquetas, generalmente representan algún tipo de formato en el texto original. Simplificar el formato del texto original en el archivo fuente antes de comenzar la traducción contribuye en gran medida a reducir el número de etiquetas.
+
+
+
+ Estadísticas de coincidencias<indexterm class="singular">
+ <primary>Estadísticas de coincidencias</primary> <seealso>Menú Herramientas</seealso>
+ </indexterm>
+
+ Las estadísticas se acceden a través de Herramientas → Estadísticas. La evaluación hace uso intensivo de la CPU y puede llevar mucho tiempo, por lo que se muestra una barra de progreso durante el cálculo. En cuanto a las categorías se refiere, se utiliza el estándar de facto de la clasificación de coincidencias en los siguientes grupos:
+
+
+
+ Coincidencia exacta
+
+
+
+ 95%-100%
+
+
+
+ 85%-94%
+
+
+
+ 75%-84%
+
+
+
+ 50%-74%
+
+
+
+ Ninguna coincidencia
+
+
+
+ El número de palabras contadas es idéntico a los números, provistos en la ventana Archivos del proyecto, y se basa estrictamente en el método contable de OmegaT, con algunas diferencias en la terminología para explicar los diferentes conceptos. Esta información se calcula por segmentos, palabras y caracteres (sin y con espacios). Ten en cuenta que los totales son una buena (o tan-bueno-como-pueden-ser) aproximación del trabajo involucrado en el proyecto y por lo tanto puede servir como base para tus cálculos de costos y precios.
+
+
+ Estadísticas de coincidencias
+
+
+
+
+
+
+
+
+
+
+
+
+ Los espacios entre los segmentos no se tienen en cuenta en la última columna. Las repeticiones están para segmentos idénticos presentes varias veces en el texto. El primer segmento y su contenido será clasificado como "sin coincidencia", y el resto como una repetición del primero. Si la traducción de varios segmentos fuente idénticos ya existe en la memoria de traducción del proyecto, estos segmentos, junto con otros, ya se han traducido segmentos únicos, serán clasificados como una "coincidencia exacta". El número de segmentos únicos, si es necesario, se proporciona en la ventana de estadísticas estándar, independientemente de si se han traducidos o no.
+
+ El resto de las categorías (50-100%) consiste en segmentos sin traducir, con una coincidencia parcial. Las coincidencias parciales pueden venir del directorio /tm también - y no sólo de la memoria de traducción interna de / OmegaT, como es el caso de las repeticiones y coincidencias exactas. La única diferencia con las coincidencias de la memoria de traducción project_save es que las MT externas no pueden dar coincidencias exactas, sólo 100%. Si no deseas utilizar memorias de traducción externas para contar, o bien una tendrás vaciar el directorio /tm o cambiar (temporalmente) la configuración del proyecto para que el valor de /tm apunte a una ubicación diferente.
+
+ Las estadísticas de coincidencias están separadas por tabuladores y puedes usar Ctrl+A
+ AtajosCtrl+A - Seleccionar todo
+ , Ctrl+C
+ AtajosCtrl+C - copiar texto
+ , Ctrl+V
+ AtajosCtrl+V - Pegar texto
+ copiar/pegar, por ejemplo en una hoja de cálculo o en tu aplicación de contabilidad de costos. Una vez calculados, los datos también están disponibles en omegat/project_stats_match.txt. Ten en cuenta que el archivo se marca con la hora, como el cálculo (al contrario de las estadísticas estándar) no es instantáneo y por lo tanto rápidamente se puede volver obsoleto.
+
+
+
+ Navegador de ayuda<indexterm class="singular">
+ <primary>Menú Ayuda</primary> <secondary>Navegador de Ayuda</secondary>
+ </indexterm>
+
+ El navegador de ayuda (el cual muestra este manual) se puede abrir pulsando
+ AtajosF1 - Ayuda
+ F1 o desplazándote hasta
+ Menú AyudaManual de usuario...
+ Ayuda → Manual de usuario... en el menú principal. En la ventana, el manual muestra dos botones: Volver y Contenido. El manual de usuario es un documento HTML con enlaces a los diferentes capítulos. Al hacer clic en un enlace como lo harías en un navegador web trae la página deseada al frente.
+
+ El manual de usuario se encuentra en el subdirectorio docs en la carpeta de instalación de OmegaT, por lo que puedes, por ejemplo, ver la documentación en Español abriendo el archivo docs/es/index.html en tu navegador. Al abrir el manual de usuario de este modo también te permite seguir los enlaces externos, puesto que el navegador de ayuda integrado no acepta los enlaces externos a Internet.
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/es/images/AppleKey.gif b/OmegaT/doc_src/es/images/AppleKey.gif
new file mode 100644
index 0000000..dabdac4
Binary files /dev/null and b/OmegaT/doc_src/es/images/AppleKey.gif differ
diff --git a/OmegaT/doc_src/es/images/AsciiFilteroptions.png b/OmegaT/doc_src/es/images/AsciiFilteroptions.png
new file mode 100644
index 0000000..6ebbaaf
Binary files /dev/null and b/OmegaT/doc_src/es/images/AsciiFilteroptions.png differ
diff --git a/OmegaT/doc_src/es/images/DictMerriamWebster.png b/OmegaT/doc_src/es/images/DictMerriamWebster.png
new file mode 100644
index 0000000..54d005e
Binary files /dev/null and b/OmegaT/doc_src/es/images/DictMerriamWebster.png differ
diff --git a/OmegaT/doc_src/es/images/Dock.gif b/OmegaT/doc_src/es/images/Dock.gif
new file mode 100644
index 0000000..4a6487c
Binary files /dev/null and b/OmegaT/doc_src/es/images/Dock.gif differ
diff --git a/OmegaT/doc_src/es/images/EditingBehaviourOptions.png b/OmegaT/doc_src/es/images/EditingBehaviourOptions.png
new file mode 100644
index 0000000..3fb7fa2
Binary files /dev/null and b/OmegaT/doc_src/es/images/EditingBehaviourOptions.png differ
diff --git a/OmegaT/doc_src/es/images/Glossary_pane.png b/OmegaT/doc_src/es/images/Glossary_pane.png
new file mode 100644
index 0000000..ddd8c8e
Binary files /dev/null and b/OmegaT/doc_src/es/images/Glossary_pane.png differ
diff --git a/OmegaT/doc_src/es/images/Main_pane_counters.png b/OmegaT/doc_src/es/images/Main_pane_counters.png
new file mode 100644
index 0000000..c46ab2b
Binary files /dev/null and b/OmegaT/doc_src/es/images/Main_pane_counters.png differ
diff --git a/OmegaT/doc_src/es/images/MatchStatistics.png b/OmegaT/doc_src/es/images/MatchStatistics.png
new file mode 100644
index 0000000..7297bf5
Binary files /dev/null and b/OmegaT/doc_src/es/images/MatchStatistics.png differ
diff --git a/OmegaT/doc_src/es/images/MatchesPane.png b/OmegaT/doc_src/es/images/MatchesPane.png
new file mode 100644
index 0000000..9a0854a
Binary files /dev/null and b/OmegaT/doc_src/es/images/MatchesPane.png differ
diff --git a/OmegaT/doc_src/es/images/Maximize.gif b/OmegaT/doc_src/es/images/Maximize.gif
new file mode 100644
index 0000000..24e1b0a
Binary files /dev/null and b/OmegaT/doc_src/es/images/Maximize.gif differ
diff --git a/OmegaT/doc_src/es/images/Minimize.gif b/OmegaT/doc_src/es/images/Minimize.gif
new file mode 100644
index 0000000..f41fac5
Binary files /dev/null and b/OmegaT/doc_src/es/images/Minimize.gif differ
diff --git a/OmegaT/doc_src/es/images/MobyDick.png b/OmegaT/doc_src/es/images/MobyDick.png
new file mode 100644
index 0000000..8722a18
Binary files /dev/null and b/OmegaT/doc_src/es/images/MobyDick.png differ
diff --git a/OmegaT/doc_src/es/images/MultiTerm_Glossary.png b/OmegaT/doc_src/es/images/MultiTerm_Glossary.png
new file mode 100644
index 0000000..5cfbba7
Binary files /dev/null and b/OmegaT/doc_src/es/images/MultiTerm_Glossary.png differ
diff --git a/OmegaT/doc_src/es/images/NewProject.png b/OmegaT/doc_src/es/images/NewProject.png
new file mode 100644
index 0000000..3f5c1bc
Binary files /dev/null and b/OmegaT/doc_src/es/images/NewProject.png differ
diff --git a/OmegaT/doc_src/es/images/OmT_Cyrillic.png b/OmegaT/doc_src/es/images/OmT_Cyrillic.png
new file mode 100644
index 0000000..fd74105
Binary files /dev/null and b/OmegaT/doc_src/es/images/OmT_Cyrillic.png differ
diff --git a/OmegaT/doc_src/es/images/OmT_Japanese.png b/OmegaT/doc_src/es/images/OmT_Japanese.png
new file mode 100644
index 0000000..b760d89
Binary files /dev/null and b/OmegaT/doc_src/es/images/OmT_Japanese.png differ
diff --git a/OmegaT/doc_src/es/images/OmegaT_icon.png b/OmegaT/doc_src/es/images/OmegaT_icon.png
new file mode 100644
index 0000000..5e8762b
Binary files /dev/null and b/OmegaT/doc_src/es/images/OmegaT_icon.png differ
diff --git a/OmegaT/doc_src/es/images/OmegaT_panes.png b/OmegaT/doc_src/es/images/OmegaT_panes.png
new file mode 100644
index 0000000..c84e19e
Binary files /dev/null and b/OmegaT/doc_src/es/images/OmegaT_panes.png differ
diff --git a/OmegaT/doc_src/es/images/OmegaT_projects_and_subdirectories.png b/OmegaT/doc_src/es/images/OmegaT_projects_and_subdirectories.png
new file mode 100644
index 0000000..dc7d6b2
Binary files /dev/null and b/OmegaT/doc_src/es/images/OmegaT_projects_and_subdirectories.png differ
diff --git a/OmegaT/doc_src/es/images/Omegatproject.png b/OmegaT/doc_src/es/images/Omegatproject.png
new file mode 100644
index 0000000..2859fbb
Binary files /dev/null and b/OmegaT/doc_src/es/images/Omegatproject.png differ
diff --git a/OmegaT/doc_src/es/images/RegexTester.png b/OmegaT/doc_src/es/images/RegexTester.png
new file mode 100644
index 0000000..6ba1b66
Binary files /dev/null and b/OmegaT/doc_src/es/images/RegexTester.png differ
diff --git a/OmegaT/doc_src/es/images/Restore.gif b/OmegaT/doc_src/es/images/Restore.gif
new file mode 100644
index 0000000..4099595
Binary files /dev/null and b/OmegaT/doc_src/es/images/Restore.gif differ
diff --git a/OmegaT/doc_src/es/images/SpellcheckerSetup2.png b/OmegaT/doc_src/es/images/SpellcheckerSetup2.png
new file mode 100644
index 0000000..560057e
Binary files /dev/null and b/OmegaT/doc_src/es/images/SpellcheckerSetup2.png differ
diff --git a/OmegaT/doc_src/es/images/SpellcheckingText.png b/OmegaT/doc_src/es/images/SpellcheckingText.png
new file mode 100644
index 0000000..7945f88
Binary files /dev/null and b/OmegaT/doc_src/es/images/SpellcheckingText.png differ
diff --git a/OmegaT/doc_src/es/images/TagValidation.png b/OmegaT/doc_src/es/images/TagValidation.png
new file mode 100644
index 0000000..e109554
Binary files /dev/null and b/OmegaT/doc_src/es/images/TagValidation.png differ
diff --git a/OmegaT/doc_src/es/images/TagValidator.png b/OmegaT/doc_src/es/images/TagValidator.png
new file mode 100644
index 0000000..44f994e
Binary files /dev/null and b/OmegaT/doc_src/es/images/TagValidator.png differ
diff --git a/OmegaT/doc_src/es/images/TextSearch.png b/OmegaT/doc_src/es/images/TextSearch.png
new file mode 100644
index 0000000..b3d84ea
Binary files /dev/null and b/OmegaT/doc_src/es/images/TextSearch.png differ
diff --git a/OmegaT/doc_src/es/images/Undock.gif b/OmegaT/doc_src/es/images/Undock.gif
new file mode 100644
index 0000000..6680e9c
Binary files /dev/null and b/OmegaT/doc_src/es/images/Undock.gif differ
diff --git a/OmegaT/doc_src/es/images/saveglossary.png b/OmegaT/doc_src/es/images/saveglossary.png
new file mode 100644
index 0000000..cbf9739
Binary files /dev/null and b/OmegaT/doc_src/es/images/saveglossary.png differ
diff --git a/OmegaT/doc_src/es/images/tagged_segment.png b/OmegaT/doc_src/es/images/tagged_segment.png
new file mode 100644
index 0000000..1b9e648
Binary files /dev/null and b/OmegaT/doc_src/es/images/tagged_segment.png differ
diff --git a/OmegaT/doc_src/es/images/tagged_segment_target.png b/OmegaT/doc_src/es/images/tagged_segment_target.png
new file mode 100644
index 0000000..ddbd1c6
Binary files /dev/null and b/OmegaT/doc_src/es/images/tagged_segment_target.png differ
diff --git a/OmegaT/doc_src/es/license.txt b/OmegaT/doc_src/es/license.txt
new file mode 100644
index 0000000..1af4657
--- /dev/null
+++ b/OmegaT/doc_src/es/license.txt
@@ -0,0 +1,340 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) year name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ , 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/OmegaT/doc_src/es/version.properties b/OmegaT/doc_src/es/version.properties
new file mode 100644
index 0000000..5448579
--- /dev/null
+++ b/OmegaT/doc_src/es/version.properties
@@ -0,0 +1,2 @@
+# NOI18N
+version=2.3.0
diff --git a/OmegaT/doc_src/eu/InstantStartGuide.xml b/OmegaT/doc_src/eu/InstantStartGuide.xml
new file mode 100644
index 0000000..fe5da53
--- /dev/null
+++ b/OmegaT/doc_src/eu/InstantStartGuide.xml
@@ -0,0 +1,402 @@
+
+
+
+ Hasteko gida azkarra
+
+
+ Hasi <application>OmegaT</application> erabiltzen 5 minututan!
+
+ Gida azkar honek oinarrizkoa azaltzen du soilik. Informazio gehiagorako, erabiltzailearen eskuliburua irakurri beharko zenukete OmegaT-k eskaintzen duen guztira ohitzeko. Oharra Mac erabiltzaileentzat: hemen deskribatutako lasterteklek "Ctrltekla" konbentzioa erabiltzen dute, baina Mac erabiltzaileek "Cmdtekla" erabili beharko lukete. " Cmd" teklak "command" etiketa edo sagar baten sinboloa dauka Apple teklatuetan.
+
+ OmegaT-ren pantaila bost leihoz osaturiko laneko area bakarra da
+ Lehioak OmegaT-n
+ . Horietako bakoitzaren tamaina aldatzeko sagua erabili daiteke. Ezkerrean editorea dago, itzulpenak idazteko erabiltzen dena. Azpian, glosarioen bisorea dago, glosario mailako parekatzeak erakusten den lekua. Leihoaren behealdean dauden bi fitxa gehiagok hiztegien eta itzulpen automatikoen panelak irekitzen dituzte. (Oharra: panelak nahieran birrantola ditzakezu - goian eman den deskribapenak OmegaT-k instalazioaren ondoren duen itxura azaltzen du.)
+
+ Editorearen leihoan OmegaT-k sorburu-testua aurkezten du, esalditan edo paragrafotan 'segmentatuta'. Segmentuak banaka itzultzen dira. Segmentu batetik bestera igarotzerakoan, itzulpenak itzulpen-memoria batean gordetzen dira. Segmentu guztiak itzuli ondoren (edo lehenago, nahi izanez gero), OmegaT-k dokumentu itzuliak sortuko ditu, itzulpen-memoria erabiliz, "helburu" karpeta batean.
+
+ OmegaT-k itzulpen-proiektuetan antolatzen ditu itzulpen-lanak. Proiektu bakoitzerako, OmegaT-k karpeten multzo bat sortzen du. Karpeta hauetan gordeko dira itzuli nahi diren sorburu-dokumentuak, erabili nahi diren glosarioak eta erabili nahi diren itzulpen-memoriak. Era berean, OmegaT-k "helburu" karpeta bat sortzen du azkenean sortuko diren dokumentu itzuliak gordetzeko.
+
+
+
+ Itzulpenak <application>Omegat-rekin</application>
+
+
+ Proiektu berria sortzea eta irekitzea<indexterm class="singular">
+ <primary>Proiektua</primary> <secondary>Sortu / ireki berria</secondary>
+ </indexterm>
+
+ Hautatu ProiektuaBerria...
+ Proiektua menuaBerria...
+ menuen barran.
+
+ Joan proiektuaren fitxategiak gorde nahi dituzun karpetara, eta eman izen bat itzulpen-proiektuari. Izen hau proiektuaren karpeta nagusia izendatzeko erabiliko da; proiektuaren fitxategi guztiak karpeta honetan edo bere azpikarpetetan gordeko dira.
+
+ OmegaT-k proiektuaren karpetaren sorrera baieztatzea edo aldatzea eskatuko dizu, ondoko koadroaren bidez:
+
+
+ <indexterm class="singular">
+ <primary>Proiektua</primary> <secondary>Proiektua elkarrizketa-koadroa - irudia</secondary>
+ </indexterm>Proiektu berria - elkarrizketa-koadroa
+
+
+
+
+
+
+
+
+
+
+
+ Sinpleena azpikarpeten kokapena dagoen bezala onartzea da, baina lehenengo egiaztatu sorburuaren eta helburuaren hizkuntza-kodeak zuzenak direla. Hautatu hizkuntza-kodea (2 letra) edo hizkuntza- eta herrialde-kodeak (2+2 letra) goitibeherako zerrenda erabiliz, edo tekleatu eskuz (hizkuntza-kodeak 2 edo 3 letra eduki ditzake). Ez ahaztu "helburu" azpikarpeta (zure dokumentu itzuliak gordetzen den lekua) non dagoen kokatuta. OmegaT-k paragrafoak segmentatu ordez esaldiak segmenta ditzan nahiago baduzu, irakurri segmentazio-arauen inguruko kapitulua
+ SegmentazioaSegmentazio-arauak
+ .
+
+ Proiektuaren antolaketa onartzeko "Onartu" botoia sakatu ondoren, OmegaT-k inportatu nahi diren sorburu-dokumentuak hautatzeko eskatzen du. Fitxategiak banan-banan inporta daitezke Proiektua > Inportatu sorburu-fitxategiak aukerarekin, edo fitxategiak zein karpeta-zuhaitz osoak kopia daitezke (azpikarpeta guztietako fitxategi guztiak barne) eskuz zure OmegaT proiektuaren sorburu-karpetan (adibidez, zure fitxategi-kudeatzailea erabiliz). Nahi gabe okerreko dokumentuak, edo dokumentu gehiegi, inportatu badira, konponbide errazena dokumentu horiek OmegaT-ren proiektuko sorburu-karpetatik kentzea da.
+
+ Itzuli beharreko fitxategiak aztertzeko, kontsultatu Proiektuaren fitxategiak
+ Proiektuaren fitxategiakSorburu-fitxategiak
+ leihoa (Menua: ProiektuaProiektuaren fitxategiak,
+ Proiektua menuaProiektuaren fitxategiak
+ automatikoki irekitzen ez bada). Sorburu-karpetaren edukiak aldatu nahi badituzu, gogoan izan lehenengo proiektua birkargatu behar dela (Menua: F5ProiektuaBirkargatu). OmegaT-ren portaera lehenetsia proiektuaren zerrendako lehen fitxategia irekitzea da. Gogoan izan, OmegaT-k behean adierazitako formatuetan dauden fitxategiak itzuli ditzake soilik, eta fitxategi-iragazkietan definitu diren ereduekin bat badatoz. Beste edozein fitxategi ezikusi egingo da.
+ Sorburu-fitxategiakFitxategi-formatuak
+
+
+
+
+ Testu arrunteko fitxategi-formatuak
+ Fitxategi-formatuaktestu arrunteko fitxategiak
+
+
+ ASCII testua (.txt, etab.)
+
+
+
+ Testu kodetua (*.UTF8)
+
+
+
+ Java-ren baliabide-paketeak (*.properties)
+
+
+
+ PO fitxategiak (*.po)
+
+
+
+ INI ('gako=balio' formatua) fitxategiak (*.ini)
+
+
+
+
+ DTD fitxategiak (*.DTD)
+
+
+
+ DocuWiki fitxategiak (*.txt)
+
+
+
+
+
+ SubRip azpitituluen fitxategiak (*.srt)
+
+
+
+
+
+ Magento CE Locale CSV (*.csv)
+
+
+
+
+
+
+
+
+ Etiketatutako testuko fitxategi-formatuak
+ Fitxategi-formatuakformatudunak
+
+
+
+
+ OpenOffice.org / OpenDocument (*.odt, *.ott, *.ods, *.ots,
+ *.odp, *.otp)
+
+
+
+
+
+ Microsoft Open XML (*.docx, *.xlsx, *.pptx)
+
+
+
+
+
+ (X)HTML (*.html, *.xhtml,*.xht)
+
+
+
+
+
+ HTML Help Compiler (*.hhc, *.hhk)
+
+
+
+
+
+ DocBook (*.xml)
+
+
+
+
+
+ XLIFF elebakarra (*.xlf, *.xliff, *.sdlxliff)
+
+
+
+
+
+ QuarkXPress CopyFlowGold (*.tag, *.xtg)
+
+
+
+
+
+ ResX fitxategiak (*.resx)
+
+
+
+
+
+ Android baliabideak (*.xml)
+
+
+
+
+
+ LaTex (*.tex, *.latex)
+
+
+
+ Laguntza (*.xml) eta eskuliburu (*.hmxp) fitxategiak
+
+
+
+ Typo3 LocManager (*.xml)
+
+
+
+
+
+ WiX Localization (*.wxl)
+
+
+
+ Iceni Infix (*.xml)
+
+
+
+ Flash XML export (*.xml)
+
+
+
+ Wordfast TXML (*.txml)
+
+
+
+ Camtasia Windows-erako (*.camproj)
+
+
+
+
+
+
+ Itzuli nahi duzun testuaz gain, etiketadun testu-fitxategiek formatu-informazioa eduki ohi dute, OmegaT-n "etiketa" gisa erakusten dena. Etiketek itzulitako testuan ere egon behar dute, nahiz eta formatua ez den "itzuli" behar. Etiketak falta badira edo gaizki kokatuta badaude, testua ez da erakutsiko behar den moduan eta itzulpena zuzendu egin beharko da - ikusi "Etiketak egiaztatzea" kapitulua beherago.
+
+
+
+ Segmentuak banaka itzultzea
+
+ Proiektua eta itzuliko diren fitxategiak definitu ondoren, OmegaT-k lehen sorburu-fitxategia irekitzen du editorean.
+
+ Segmentu aktiboa berdez nabarmendurik agertuko da; sorburu-testuaren kopia bat bere azpian erakutsiko da, "helburu-eremuan". (Une honetan, helburu-eremutik kanpo dagoen testua babestuta dago eta ezin da aldatu). Itzulpena <segment 0001> etiketaren aurretik tekleatu behar duzu.. OmegaT konfigura daiteke sorburu-testua automatikoki helburu-testuan kopiatua izan dadin (ikusi Aukerak > Editatu portaera...). Portaera hori erabilgarria izan daiteke sorburu-testuaren zenbait atal aldaketarik gabe mantendu behar direnean. Kasu horietan sorburu-testua gainidatziko duzu. Sakatu ENTER hurrengo segmentura mugitzeko. Oharra:
+
+
+
+ Testuaren beste edozein atalera mugitzeko, gora zein behera, egin klik bikoitza ireki nahi duzun esaldi edo paragrafoan.Testuaren beste edozein atalera mugitzeko, gora zein behera, egin klik bikoitza ireki nahi duzun esaldi edo paragrafoan.
+
+
+
+ Hutsik dagoen helburu-eremu batean itzuli nahi baduzu, hautatu aukera hori AukerakEditatu portaera
+ Aukerak menuaEditatu portaera...
+ leihoan.
+
+
+
+ Editore-panelak zer erakusten duen alda dezakezu (esaterako, sorburu-testua erakustea edo ez, itzulitako testua nabarmentzea edo ez, etab.) menu nagusiaren Ikusi aukeran.
+
+ ENTER sakatzean hainbat gauza gertatzen dira: OmegaT-k segmentu-bikotea (sorburu-segmentua eta bere itzulpena) gehitzen dio itzulpen-memoriari. Era berean, automatikoki proiektuaren beste fitxategietan detektatzen dituen segmentu berdinak itzultzen ditu Horrez gain, itzulpen-memoria eta glosarioa eskaneatzen ditu itzuli gabeko hurrengo segmentuarentzako parekoak aurkitzeko, eta hura irekitzen du.
+
+
+
+
+
+ Itzulpen-memorietako, glosarioetako eta hiztegietako parekatzeak erabiltzea
+
+
+ Itzulpen-memorien parekatzeak<indexterm class="singular">
+ <primary>Itzulpen-memoriak</primary> <secondary>Parekatze lausoak</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Itzulpen-memoriak</primary> <secondary>Parekatzeak</secondary>
+ </indexterm>
+
+
+ Parekatzeen panela
+
+
+
+
+
+
+
+
+
+
+
+
+ OmegaT-k hurrengo segmentuarentzako parekatze lausoak (%30etik gorakoak) aurkitzen baditu proiektuaren itzulpen-memorian, horiek parekatzeen bisorean erakusten ditu. Parekatzeen bisorearen portaera lehenetsia lehen parekatzea aurrehautatzea da.
+
+
+
+ Sakatu CtrlI
+ LasterbideakCtrl+I - Txertatu testua
+ aurrehautatutako parekatzea kurtsorearen kokapenean txertatzeko, edo...
+
+
+
+ Sakatu CtrlR
+ LasterbideakCtrl+R - Ordeztu testua
+
+ Ordeztu testua
+ segmentu osoa aurrehautatutako parekatzearekin ordezteko.
+
+
+
+ Parekatze bat baino gehiago aurkitu bada, eta aurrehautatutako parekatzea ez den beste bat erabili nahi baduzu:
+
+
+
+ Hautatu nahi duzun parekatzea parekatzeen bisorean: Ctrl2 bisorean erakusten den bigarren parekatzea hautatzeko, Ctrl3 hirugarren parekatzerako, etab.
+
+
+
+ Ondoren, erabili CtrlI edo CtrlR lasterteklak lehen adierazi den bezala.
+
+
+
+ Nahi izanez gero, OmegaT-k parekatzeen ehuneko jakin bat gainditzen duen lehen parekatzea automatikoki sartu dezake helburu-eremuan. Ezarri aukera hori Options erabiliz.
+
+
+
+ Glosarioen eta hiztegien parekatzeak<indexterm class="singular">
+ <primary>Parekatzeak</primary> <secondary>Glosarioen eta hiztegien parekatzeak</secondary>
+ </indexterm>
+
+ Proiektuan sartu dituzun glosarioetako eta hiztegietako parekatzeak glosarioen eta hiztegien bisoreetan erakusten dira erreferentzia gisa.
+
+
+
+ Bilaketen erabilera
+
+ OmegaT-k bilaketa-funtzio asko eta indartsuak eskaintzen ditu. Ireki bilaketa-leihoa CtrlF sakatuz eta sartu bilatu nahi duzun hitza edo esaldia "Bilatu hau" kutxan. Bestela, hautatu hitz edo esaldi bat editore-paneleko edozein tokitan eta sakatu CtrlF: hautatutako hitz edo esaldia automatikoki txertatuko da "Bilatu hau" kutxan eta bilaketa-leihoa irekiko da.
+
+
+
+ Itzulpen automatikoko zerbitzuen erabilera<indexterm class="singular">
+ <primary>Parekatzeak</primary> <secondary>Itzulpen automatikoa</secondary>
+ </indexterm>
+
+ Itzulpen automatikoen panelean, mota honetako zerbitzuetako bat aktibatuta badago (ikusi Aukerak > Itzulpen automatikoa), uneko segmentuaren itzulpenerako iradokizun bat jasoko duzu automatikoki. Sakatu Ctrl+M helburu-segmentua iradokizun horrekin ordezteko.
+
+
+
+
+ Dokumentu itzuliak sortzen<indexterm class="singular">
+ <primary>Proiektuaren fitxategiak</primary> <secondary>Helburu-fitxategiak</secondary>
+ </indexterm>
+
+ Segmentu guztiak itzuli ondoren (edo lehenago, hala nahi izanez gero), OmegaT-k helburu-dokumentua(k) sortuko ditu itzulpen-memorian gordetako itzulpenak erabiliz. Hori egiteko, hautatu CtrlDProiektuaSortu dokumentu itzuliak
+ LasterbideakCtrl+D - Sortu dokumentu itzuliak
+
+ Proiektua menuaSortu dokumentu itzuliak
+ menu nagusian. OmegaT-k proiektuaren sorburu-karpetan dauden dokumentu itzulgarri guztien bertsio itzuliak eratuko ditu, dokumentu hauek osorik itzuliak egon zein ez. Partzialki edo osorik itzulitako fitxategiak proiektuaren helburu-karpetan gordeko dira. Itzulpena amaitzeko, ireki helburu-fitxategi bakoitza bere aplikazio elkartuan (nabigatzailea, testu-prozesadorea...) eta itzulpenaren edukia eta formatua berrikusi. Gero, itzuli OmegaT-ra, beharrezkoak diren zuzenketak egiteko; ez ahaztu dokumentu itzulia berriro birsortu behar duzula.
+
+
+
+
+ Testu etiketatua nola erabili<indexterm class="singular">
+ <primary>Testu etiketatua</primary>
+ </indexterm>
+
+ OmegaT-k etiketa bereziak erabiltzen ditu sorburu-dokumentuen formatua (lodia, etzana, etab.) galtzen ez dela segurtatzeko. OmegaT-ren etiketen osaera hau da: letra bat edo gehiago eta ondoren digitu bat edo gehiago, eta "/" karakterea etiketak ixteko (esaterako: <f0>, </f0> <br>, </s2>, etab.) Etiketa hauek kontuz erabili behar dira eta helburu-segmentuetan modu egokian sarturik daudela segurtatu behar da (ikus Eragiketak etiketekin).
+
+
+ Adibide bat...<indexterm class="singular">
+ <primary>Testu etiketatua</primary> <secondary>Adibide bat</secondary>
+ </indexterm>
+
+ Adibide honetan etiketak nabarmendu egin dira, ikusteko errazagoak izan daitezen, baina kontuan izan OmegaT-k ez dituela nabarmentzen. HTML etiketak, urdinez nabarmendutakoak, ezikusi egiten ditu OmegaT-k, segmentua osorik inguratzen baitute. Behean berdez nabarmendutako etiketak, hala ere, OmegaT-k kudeatu behar ditu, segmentuaren barruan baitaude. Hemen dago HTML formatuko segmentu baten adibide bat (ingelesez):
+
+ <p>Bistaratzeko beste letra-tipo bat hauta daiteke <b>Erakutsi letra-tipoa</b> koadroa erabiliz. Hura irekitzeko, joan <i>Aukerak</i> →<i>Letra-tipoa...</i> aukerara. Koadroaren bidez letra-tipoa eta tamaina alda daitezke.</p>
+
+ Ondoren erakusten da OmegaT-k nola erakutsiko duen, afrikaans-eko itzulpen batekin:
+
+
+ Sorburuko <indexterm class="singular">
+ <primary>Segmentua, sorburua eta helburua - irudia</primary>
+ </indexterm>HTML segmentua
+
+
+
+
+
+
+
+
+
+
+
+
+ OmegaT-k dokumentu itzulia sortu ondoren, HMTL-ak itxura hau izango du:
+
+
+ Helburuko HTML segmentua
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Etiketen egiaztapena<indexterm class="singular">
+ <primary>Testu etiketatua</primary> <secondary>Etiketen egiaztapena</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Etiketen egiaztapena</primary>
+ </indexterm>
+
+ OmegaT-k ez ditu itzulitako dokumentuaren etiketa akasdunak automatikoki detektatzen. Beraz, dokumentua zure bezeroari eman baino lehen, etiketak egiaztatu beharko zenituzke akatsak detektatzeko. Hautatu CtrlTTresnakBalidatu etiketak... menuen barran. Taula bat sortuko da sorburuko eta helburuko etiketak bat ez datozen segmentuak erakutsiz. Egin klik segmentuaren zenbakian. Editorean ageri den segmentu akasdunera joango zara automatikoki, eta bertan etiketa zuzendu ahal izango duzu. Zuzenketa guztiak egin ondoren, egiazta itzazu CtrlT
+ LasterbideakCtrl+T - Etiketen egiaztapenaEtiketadun testua
+ sakatuta berriro. Kontuan izan etiketen egiaztatzaileak erroreen berri eman dezakeela baita etiketak zuzenak direnean ere - adibidez, etiketen ordena aldatu behar izan denean gramatikaren aldetik zuzena den itzulpena egiteko. Mesedez, har ezazu portaera hau alde onetik: egiaztatzaileak nahiago du errorea jakinarazi badaezpada ere.
+
+ Zenbait kasutan, etiketa-akatsek dokumentu bat ireki dadin eragotzi dezakete. Ez dago izurako arrazoirik - oraindik sorburu-fitxategia eta itzulpena, biak dituzu eskura, egin beharreko bakarra dokumentu itzuliak sortu baino lehen etiketa-akats guztiak zuzendu dituzula segurtatzea da. Azkenik, birritan egiaztatu beharko zenuke azken formatua, dokumentu itzulia bere formatuari dagokion bisore edo editorean irekiz.
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/eu/OmegaT.css b/OmegaT/doc_src/eu/OmegaT.css
new file mode 100644
index 0000000..1893c29
--- /dev/null
+++ b/OmegaT/doc_src/eu/OmegaT.css
@@ -0,0 +1,78 @@
+body {
+ font-family: sans-serif;
+ margin: 1em;
+}
+
+h1, h2, table, dt {
+ color: navy;
+}
+
+h3, h4, ul a {
+ color: green;
+}
+
+code, .code {
+ color: black;
+ background: #ffffcc;
+ border-style: solid;
+ border-width: 1px;
+ border-color: #ffff66;
+ vertical-align: top;
+}
+
+.new {
+ font-size: x-small;
+ color: red;
+ background: yellow;
+}
+
+.updated {
+ font-size: x-small;
+ color: orange;
+}
+
+.note {
+ font-size: small;
+ color: black;
+ background: silver;
+}
+
+.warning {
+ color: red;
+ background: yellow;
+}
+
+.chapter {
+ color: black;
+}
+
+.navbar-top, .navbar-bottom {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.rel-p {
+ width: 9%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.rel-n {
+ width: 6%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.nav-link {
+ width: 39%;
+ align: left;
+ valign: center;
+}
+
+.toc-link {
+ width: 7%;
+ align: left;
+ valign: center;
+}
\ No newline at end of file
diff --git a/OmegaT/doc_src/eu/images/MatchesPane.png b/OmegaT/doc_src/eu/images/MatchesPane.png
new file mode 100644
index 0000000..72658ae
Binary files /dev/null and b/OmegaT/doc_src/eu/images/MatchesPane.png differ
diff --git a/OmegaT/doc_src/eu/images/NewProject.png b/OmegaT/doc_src/eu/images/NewProject.png
new file mode 100644
index 0000000..84c2478
Binary files /dev/null and b/OmegaT/doc_src/eu/images/NewProject.png differ
diff --git a/OmegaT/doc_src/eu/images/tagged_segment.png b/OmegaT/doc_src/eu/images/tagged_segment.png
new file mode 100644
index 0000000..c0d4059
Binary files /dev/null and b/OmegaT/doc_src/eu/images/tagged_segment.png differ
diff --git a/OmegaT/doc_src/eu/images/tagged_segment_target.png b/OmegaT/doc_src/eu/images/tagged_segment_target.png
new file mode 100644
index 0000000..238e3fb
Binary files /dev/null and b/OmegaT/doc_src/eu/images/tagged_segment_target.png differ
diff --git a/OmegaT/doc_src/fop.xconf b/OmegaT/doc_src/fop.xconf
new file mode 100644
index 0000000..3176158
--- /dev/null
+++ b/OmegaT/doc_src/fop.xconf
@@ -0,0 +1,12 @@
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/OmegaT/doc_src/fr/InstantStartGuide.xml b/OmegaT/doc_src/fr/InstantStartGuide.xml
new file mode 100644
index 0000000..2083f8c
--- /dev/null
+++ b/OmegaT/doc_src/fr/InstantStartGuide.xml
@@ -0,0 +1,111 @@
+
+
+
+ Apprendre à utiliser OmegaT en 5 minutes !
+
+
+ Préparation d'un nouveau projet<indexterm class="singular">
+ <primary>Projet</primary> <secondary>Créer / ouvrir</secondary>
+ </indexterm>
+
+ Remarque :Sur un Mac, utilisez la touche cmd (commande) à la place de la touche ctrl.
+
+ Pour pouvoir travailler avec OmegaT, vous devez commencer par créer un projet qui contiendra vos fichiers, notamment le fichier source, les mémoires de traduction, les glossaires ainsi que le fichier traduit. Dans le menu Projet, sélectionnez Nouveau...
+ Menu ProjetNouveau...
+ et saisissez le nom du projet. Mémorisez bien l'emplacement du projet car vous devrez y accéder ultérieurement.
+
+ Une fois le nom du projet défini, OmegaT ouvre la fenêtre Création du projet. Indiquez la langue du fichier source ainsi que la langue de la traduction, puis cliquez sur OK pour continuer.
+
+ Utilisez le raccourci clavier Ctrl+E si vous avez besoin de revenir aux réglages de cette fenêtre plus tard.
+
+ OmegaT ouvre ensuite la fenêtre Fichiers du projet. Cliquez sur le bouton Importer des fichiers source... pour sélectionner le fichier source. OmegaT copie le fichier sélectionné dans le sous-dossier /source/ du projet que vous venez de créer. Une fois le fichier source chargé et affiché dans le volet d'édition, vous pouvez fermer la fenêtre Fichiers du projet.
+
+
+
+ Traduction du fichier
+
+ OmegaT vous propose un segment à traduire après l'autre. Appuyez sur la touche « Entrée » pour passer d'un segment à l'autre ou utilisez le raccourci clavier Ctrl+U pour accéder au prochain segment non traduit. Si vous souhaitez obtenir un aperçu de votre traduction dans son format final, utilisez le raccourci Ctrl+D pour générer le document traduit dans le sous-dossier /target/ du dossier projet. Les menus Édition et Atteindre vous donnent accès à diverses fonctions très utiles pendant le travail de traduction.
+
+
+
+ Validation des balises
+
+ Si votre fichier source est un fichier formaté, par exemple au format Microsoft Word, LibreOffice Writer ou HTML, OmegaT convertit le formatage en balises qui encadrent le texte que vous traduisez. Souvent, les documents contiennent également un certain nombre de balises essentielles sans rapport direct avec le formatage. Dans le fichier source (ainsi que dans le fichier traduit), une phrase peut se présenter comme ceci :
+
+
+
+
+
+
+
+
+
+
+
+ Ici, OmegaT présente cette phrase de la manière suivante :
+
+
+
+
+
+
+
+
+
+
+
+ Les balises dans OmegaT sont grisées pour être facilement reconnaissables. Elles ne sont pas protégées et vous pouvez donc les supprimer, en ajouter manuellement ou les déplacer dans la phrase cible. Toutefois, si vous avez fait des erreurs en saisissant les balises de formatage, l'ouverture du fichier traduit pourra échouer. Par conséquent, assurez-vous que vos balises sont correctes et validez-les avant de générer le fichier traduit (raccourci clavier Ctrl+T).
+
+
+
+ Création du fichier traduit
+
+ Après avoir vérifié que votre traduction ne contient pas d'erreur de balises, générez le fichier cible (raccourci clavier Ctrl+D) dans le sous-dossier /target/ du dossier projet.
+
+
+
+ D'autres points à retenir
+
+
+
+ Si le chargement d'un fichier source échoue, c'est-à-dire s'il ne s'affiche pas dans le volet d'édition, il s'agit vraisemblablement d'un fichier dont le format est incompatible avec OmegaT. Reportez-vous au chapitre 7 (Filtre de fichiers) du guide de l'utilisateur pour obtenir la liste des formats de fichier gérés par OmegaT.
+
+
+
+
+
+ Vous pouvez créer de nouveaux projets en fonction de votre travail et vous pouvez ajouter plusieurs fichiers source à un même projet.
+
+
+
+
+
+ Vous pouvez revoir les réglages du projet dans la fenêtre Modifier le projet (raccourci clavier Ctrl+E). Vous pouvez afficher la liste des fichiers du projet dans la fenêtre Fichiers du projet (raccourci clavier Ctrl+L).
+
+
+
+
+
+ OmegaT exporte trois versions (« level1 », « level2 » et « omegat ») de la mémoire de traduction dans le dossier projet. Les mémoires « level1 » et « level2 » sont compatibles avec les outils de TAO prenant en charge les TMX niveaux 1 et 2 et peuvent être partagées avec d'autres utilisateurs. La mémoire « omegat » est une mémoire native, propre à OmegaT et peut être réutilisée dans d'autres projets OmegaT. Si vous placez des mémoires de traduction dans le sous-dossier /tm/ du dossier projet, OmegaT les analyse automatiquement à la recherche de segments semblables et affiche les analogies et les correspondances partielles dans le volet Correspondances.
+
+
+
+
+
+ Vous pouvez créer un nouveau glossaire au cours de la traduction (raccourci clavier Ctrl+Shift+G), ou copier d'autres glossaires dans le sous-dossier /glossary/ du dossier projet : OmegaT y recherche automatiquement les mots associés au segment actif.
+
+
+
+
+
+ Vous disposez également de puissantes fonctions de recherche dans la fenêtre « Recherche textuelle » que vous pouvez utiliser au cours de la traduction (raccourci clavier Ctrl+F).
+
+
+
+
+
+ Le tutoriel pour débutants OmegaT for Beginners (en anglais) est disponible sur le site Web d'OmegaT et vous propose une introduction complète. N'hésitez pas à vous inscrire à la liste de diffusion du groupe des utilisateurs d'OmegaT, vous pouvez y échanger votre expérience et y trouver de l'aide.
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/fr/OmegaT.css b/OmegaT/doc_src/fr/OmegaT.css
new file mode 100644
index 0000000..1893c29
--- /dev/null
+++ b/OmegaT/doc_src/fr/OmegaT.css
@@ -0,0 +1,78 @@
+body {
+ font-family: sans-serif;
+ margin: 1em;
+}
+
+h1, h2, table, dt {
+ color: navy;
+}
+
+h3, h4, ul a {
+ color: green;
+}
+
+code, .code {
+ color: black;
+ background: #ffffcc;
+ border-style: solid;
+ border-width: 1px;
+ border-color: #ffff66;
+ vertical-align: top;
+}
+
+.new {
+ font-size: x-small;
+ color: red;
+ background: yellow;
+}
+
+.updated {
+ font-size: x-small;
+ color: orange;
+}
+
+.note {
+ font-size: small;
+ color: black;
+ background: silver;
+}
+
+.warning {
+ color: red;
+ background: yellow;
+}
+
+.chapter {
+ color: black;
+}
+
+.navbar-top, .navbar-bottom {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.rel-p {
+ width: 9%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.rel-n {
+ width: 6%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.nav-link {
+ width: 39%;
+ align: left;
+ valign: center;
+}
+
+.toc-link {
+ width: 7%;
+ align: left;
+ valign: center;
+}
\ No newline at end of file
diff --git a/OmegaT/doc_src/fr/images/InstantGuide_1.png b/OmegaT/doc_src/fr/images/InstantGuide_1.png
new file mode 100644
index 0000000..700879e
Binary files /dev/null and b/OmegaT/doc_src/fr/images/InstantGuide_1.png differ
diff --git a/OmegaT/doc_src/fr/images/InstantGuide_2.png b/OmegaT/doc_src/fr/images/InstantGuide_2.png
new file mode 100644
index 0000000..006ce2c
Binary files /dev/null and b/OmegaT/doc_src/fr/images/InstantGuide_2.png differ
diff --git a/OmegaT/doc_src/hu/InstantStartGuide.xml b/OmegaT/doc_src/hu/InstantStartGuide.xml
new file mode 100644
index 0000000..3d25cda
--- /dev/null
+++ b/OmegaT/doc_src/hu/InstantStartGuide.xml
@@ -0,0 +1,381 @@
+
+
+
+ Útmutató az azonnali kezdéshez
+
+
+ Vegye használatba az <application>OmegaT</application>-t 5 percen belül!
+
+ Ez az azonnali kezdéshez való útmutató csak az OmegaT alapjait ismerteti. Ideális esetben a felhasználóknak ajánlatos alaposan megismerkedni a felhasználói kézikönyvvel, mert megtudhatják belőle mindazt, amit az OmegaT számukra tartogat. Megjegyzés Mac-felhasználóknak: az itt leírt gyorsbillentyűk a "Ctrlbillentyű" kombinációval érhetők el, Mac esetén viszont a "Cmdbillentyű" használandó. A "Cmd" billentyűn az Apple billentyűzetén a "command" felirat vagy az "alma"-jel látható.
+
+ Az OmegaT képernyőjén megjelenő munkaterület öt ablakra van felosztva
+ Az OmegaT ablakai
+ . Ezek mindegyikét átméretezheti az egérrel. Balra található a szerkesztő, ahol begépeli a fordítást. Jobbra fent látható a Bizonytalan egyezések ablak, ahol a fordítási memóriában fellelt részleges egyezések jelennek meg. Ez alatt található a Szójegyzék ablak, benne pedig a szójegyzékben fellelt egyezések. Az ablak alján látható két gombbal a Szótár és a Gépi fordítás ablak érhető el. (Megjegyzés: az ablakokat természetesen tetszése szerint átszabhatja. A fenti leírás az OmegaT telepítés utáni megjelenésére vonatkozik).
+
+ A Szerkesztő ablakban az OmegaT a forrásszöveget jeleníti meg mondatokra (vagy bekezdésekre) 'darabolva'.. Ezeket a szövegrészeket fogja egymás után lefordítani. A szövegben előrehaladva a lefordított részek automatikusan egy fordítási memóriába kerülnek. Ha minden szövegegységet lefordított (vagy ha úgy kívánja, akár munka közben) az OmegaT a fordítási memória segítségével a “target” [célnyelvi] mappában előállítja a lefordított dokumentumo(ka)t.
+
+ Az OmegaT a fordításokat fordítási "projektekben" tárolja. Az OmegaT minden egyes projekthez létrehoz egy sor mappát és ezekben tárolja a lefordítandó forrásszövegeket, valamint az esetleg használni kívánt szójegyzékeket és fordítási memóriákat. Az OmegaT létrehoz egy “target” [célnyelvi] mappát is, ebbe kerülnek a végleges lefordított dokumentumok.
+
+
+
+ Fordítás az <application>OmegaT</application> segítségével
+
+
+ Új projekt létrehozása és megnyitása<indexterm class="singular">
+ <primary>Projekt</primary> <secondary>létrehozása / megnyitása</secondary>
+ </indexterm>
+
+ A menüből válassza ki a ProjektÚj...
+ ProjektmenüÚj...
+ pontot.
+
+ Térjen át arra a mappára, amelybe a projekt állományait menteni kívánja, majd adjon meg egy nevet a fordítási projektnek. A projekt fő mappája ezt a nevet fogja használni: minden projektfájl ebbe a mappába vagy annak almappáiba kerül majd.
+
+ Az OmegaT a létrehozandó projektmappák megerősítésére vagy módosítására az alábbi párbeszédablakot használja:
+
+
+ <indexterm class="singular">
+ <primary>Projekt</primary> <secondary>Projekt párbeszédablak - ábra</secondary>
+ </indexterm>új projekt párbeszédablaka
+
+
+
+
+
+
+
+
+ Elfogadhatja az almappák felkínált helyét, de előtte ellenőrizze, hogy a forrásnyelvi és a célnyelvi kódok helyesek-e. A lenyíló listából válassza ki a nyelvi kódot (2 betűs) vagy a nyelvi- és régiókódot (2 + 2 betűs), vagy írja be őket (a a nyelvi kód 2 vagy 3 betűs lehet). Jegyezze meg a 'target' célmappa helyét (ahová a lefordított szövegek kerülnek majd). Ha "bekezdésenkénti" szövegdarabolás helyett mondatonkéntit szeretne használni, olvassa el a szövegdarabolási szabályokról szóló fejezetet.
+
+ Amikor a projekt beállításait a Rendben gombra kattintva jóváhagyja, az OmegaT felszólítja az importálandó forrásdokumentumok kiválasztására. Importálhat akár egyetlen állományt, de importálhat egész könyvtárakat (az alkönyvtáraikban lévő összes állománnyal együtt). Erre a célra használhat egy fájlkezelő alkalmazást is. Ha véletlenül rossz vagy túl sok dokumentumot importált, törölje őket a projekt 'source' [forrásnyelvi] mappájából.
+
+ A fordítandó állományok ellenőrzéséhez térjen át a Projektállományok
+ ProjektállományokForrásállományok
+ ablakra (Menü: Projekt Projektállományok...,
+ ProjektmenüProjektállományok...
+ ha a mappa nem nyílik ki automatikusan).. Ha módosította a 'source' forrásmappa tartalmát, előbb ne feledje újból betölteni a projektet (Menü: F5Projekt Újratöltés). Az OmegaT alaphelyzetben a projektben felsorolt állományok közül az elsőt nyitja meg. Az OmegaT csak az alábbi formátumú állományok fordítását támogatja, amennyiben azok megfelelnek az állományszűrők között megadott mintáknak. Minden egyéb állományt figyelmen kívül hagy.
+ ForrásállományokÁllományformátumok
+
+
+
+
+ Egyszerű szöveges állományok
+ Állományformátumokegyszerű szöveges állományok
+
+
+ ASCII-szöveg (.txt stb.)
+
+
+
+ Kódolt szöveg (*.UTF8)
+
+
+
+ Java nyelvi forrásszövegek (*.properties)
+
+
+
+ PO-állományok (*.po)
+
+
+
+ INI (kulcs=érték) állományok (*.ini)
+
+
+
+ DTD-állományok (*.DTD)
+
+
+
+ DocuWiki-állományok (*.txt)
+
+
+
+
+
+
+
+ Címkékkel ellátott szöveges állományok
+ Állományformátumokformázott
+
+
+
+
+ OpenOffice.org / OpenDocument (*.odt, *.ott, *.ods, *.ots,
+ *.odp, *.otp)
+
+
+
+
+
+ Microsoft Open XML (*.docx. *.xlsx, *.pptx)
+
+
+
+
+
+ (X)HTML (*.html, *.xhtml,*.xht)
+
+
+
+
+
+ HTML Help Compiler (*.hhc, *.hhk)
+
+
+
+
+
+ DocBook (*.xml)
+
+
+
+
+
+ egynyelvű XLIFF (*.xlf, *.xliff, *.sdlxliff)
+
+
+
+
+
+ QuarkXPress CopyFlowGold (*.tag, *.xtg)
+
+
+
+
+
+ SubRip feliratok (*.srt)
+
+
+
+
+
+ ResX-állományok (*.resx)
+
+
+
+
+
+ Android forrásfájlok (*.xml)
+
+
+
+
+
+ LaTex (*.tex, *.latex)
+
+
+
+ Súgóállományok (*.xml) és kézikönyvek (*.hmxp)
+
+
+
+ Typo3 LocManager (*.xml)
+
+
+
+
+
+ WiX honosítási állományok (*.wxl)
+
+
+
+ Iceni Infix (*.xml)
+
+
+
+ Flash XML export (*.xml)
+
+
+
+
+
+
+ A lefordítandó szövegen túl a címkékkel ellátott szöveges állományok formázási információkat tartalmaznak, melyeket az OmegaT “címkék” formájában rejt el. A címkéknek a célnyelvi szövegben is szerepelni kell, még akkor is, ha a formázás nem “fordítandó”. Hiányzó vagy rossz helyre kerülő címkék esetén a a fordítást utólag javítani kell - lásd alább: "Címkék ellenőrzése".
+
+
+
+ Szövegegységek fordítása egyesével
+
+ Ha meghatározta a projektet és a fordítandó állományokat, az OmegaT a szerkesztőben megnyitja az első forrásszöveget.
+
+ Az aktuális szövegegység zöld színnel kiemelve látható; alatta a célnyelvi mezőben megismétlődik a forrásszöveg. (Ekkor a célnyelvi mezőn kívüli összes szöveg zárolva van és nem módosítható.) A fordítást a forrásszöveg felülírásával az <0001. egység> elé kell beírnia. Az OmegaT-t beállíthatja úgy, hogy a forrásszöveg automatikusan a célnyelvi szövegbe kerüljön (lásd: Beállítások > Szerkesztési mód...), ami hasznos lehet, ha a forrásszöveg egyes részei változatlanul megmaradnak. Ilyen esetekben a feladat a forrásszöveg felülírása. A következő szövegegységre az "ENTER" lenyomásával térhet át. Megjegyzés:
+
+
+
+ Bármely, akár feljebb, akár lejjebb lévő szövegrészre áttérhet, ha kétszer rákattint a megnyitni kívánt mondatra vagy bekezdésre.
+
+
+
+ Ha inkább üres célnyelvi mezőbe szeretné beírni a fordítást, módosítsa ennek megfelelően a Beállítások Szerkesztési mód...
+ Beállítások menüSzerkesztési mód...
+ menüpontot.
+
+
+
+ A főmenü Nézet menüpontjából módosíthatja a szerkesztőablak beállításait (pl. azt, hogy látsszon-e a forrásnyelvi szöveg, kiemeleten jelenjen-e meg a lefordított szöveg stb.).
+
+ Az ENTER megnyomásakor több dolog történik a háttérben: az OmegaT a szövegegységpárt (a forrást és annak fordítását) hozzáadja a belső fordítási memóriához. Emellett automatikusan lefordítja az összes ezzel egyező, de más projektfájlokban fellelt szöveget is. Továbbmenve, végignézi a fordítási memóriát és a szójegyzéket, nincs-e bennük egyezés a következő lefordítatlan szövegegységgel, melyet azután meg is nyit.
+
+
+
+
+
+ A fordítási memória, a szójegyzékek és a szótárak egyezéseinek felhasználása
+
+
+ Egyezések a fordítási memóriában<indexterm class="singular">
+ <primary>Fordítási memóriák</primary> <secondary>Bizonytalan egyezések</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Fordítási memóriák</primary> <secondary>Egyezések</secondary>
+ </indexterm>
+
+
+ Az egyezések panelje
+
+
+
+
+
+
+
+
+
+
+
+
+ Ha az OmegaT a fordítási memóriában a következő szövegegységhez bizonytalan (30% vagy azt meghaladó mértékű) egyezéseket talál, akkor megjeleníti azokat a Bizonytalan egyezések ablakban. Alaphelyzetben a Bizonytalan egyezések ablakból az első egyezést választja ki.
+
+
+
+ A CtrlI
+ BillentyűparancsokCtrl+I - Szöveg beszúrása
+ lenyomásával a kiválasztott egyezést beszúrja a kurzor helyére, illetve...
+
+
+
+ A CtrlR
+ BillentyűparancsokCtrl+R - Szöveg cseréje
+
+ Szöveg cseréje
+ lenyomásával a kiválasztott egyezéssel felülírja a teljes szövegegységet..
+
+
+
+ Ha több egyezés is előfordul, de nem az előre kiválasztottat kívánja használni:
+
+
+
+ Válassza ki a kívánt egyezést a Bizonytalan egyezések ablakból: Ctrl2 a másodikként megjelenített egyezés, Ctrl3 a harmadik egyezés kiválasztásához stb.
+
+
+
+ Ezután használhatja a CtrlI vagy a CtrlR billentyűparancsot a fent leírtak szerint..
+
+
+
+ Arra is utasíthatja az OmegaT-t, hogy bármely megadott százalék fölötti egyezést automatikusan szúrjon be a célnyelvi mezőbe. Ezt a lehetőséget a Beállítások menüben állíthatja be.
+
+
+
+ A szójegyzékben a szótárban előforduló egyezések<indexterm class="singular">
+ <primary>Egyezések</primary> <secondary>Szójegyzék és szótár egyezései</secondary>
+ </indexterm>
+
+ A projektbe felvett szójegyzékekben és szótárakban fellelhető egyezéseket tájékozódás céljából a Szójegyzék és a Szótár ablak jeleníti meg..
+
+
+
+ Keresések
+
+ Az OmegaT kiterjedt keresési lehetőségeket biztosít. Hívja elő a Szöveg keresése ablakot a CtrlF -fel és a Keresendő: mezőbe írja be a kikeresendő szót vagy kifejezést. Másik megoldásként kijelölheti a Szerkesztő ablakban a keresendő szót vagy kifejezést, majd használja a CtrlF billentyűparancsot.
+
+
+
+ Gépi fordítás használata<indexterm class="singular">
+ <primary>Egyezések</primary> <secondary>Gépi fordítás</secondary>
+ </indexterm>
+
+ Bekapcsolt szolgáltatás esetén (lásd: Beállítások> Gépi fordítás) a Gépi fordítás ablakban automatikusan megjelennek az adott szövegegység lefordításához kapcsolódó javaslatok. A Ctrl+M lenyomásakor a javasolt egyezéssel felülírja a célnyelvi szövegegységet.
+
+
+
+
+ Lefordított állományok előállítása<indexterm class="singular">
+ <primary>Projektállományok</primary> <secondary>Célnyelvi állományok</secondary>
+ </indexterm>
+
+ Ha minden szövegegységet lefordított (vagy akár már előtte), az OmegaT a fordítási memóriában tárolt fordítások alapján frissíti a célnyelvi dokumentumo(ka)t. Ehhez a menüből válassza ki a CtrlDProjektLefordított állományok előállítása
+ BillentyőparancsokCtrl+D - Lefordított állományok előállítása
+
+ Projektmenü Lefordított állományok előállítása
+ pontot. Az OmegaT előállítja a projekt forrásmappájában lévő összes állomány fordítását, akár teljesen elkészültek, akár nem. A teljesen vagy részben kész állományokat a projekt célmappájába (target) menti. A fordítás befejezéséhez nyissa meg a célnyelvi szövegeket a velük használatos alkalmazásban (böngészőben, szövegszerkesztőben...), majd ellenőrizze a fordítás tartalmát és szerkesztését. Ezután visszatérhet az OmegaT-hez és elvégezheti a szükséges javításokat; ne feledkezzen meg a lefordított szövegek újbóli előállításáról.
+
+
+
+
+ Címkét tartalmazó szöveg kezelése<indexterm class="singular">
+ <primary>Címkét tartalmazó szöveg</primary>
+ </indexterm>
+
+ Az OmegaT speciális címkék használatával gondoskodik arról, hogy a forrásszövegek formázása (vastag, dőlt stb.) megőrződjék. Az OmegaT címkéi egy vagy több betűből és egy vagy több azt követő számjegyből, valamint a címkét lezáró "/" karakterből állnak (például: <f0>, </f0> <br>, </s2>). Ezekre ügyelnie kell és a célnyelvi szövegbe a megfelelő helyre kell őket beszúrnia (lásd a címkeműveletekről szóló részt).
+
+
+ Egy példa...<indexterm class="singular">
+ <primary>Címkét tartalmazó szöveg</primary> <secondary>Példa</secondary>
+ </indexterm>
+
+ Ezekben a példákban a címkék ki vannak emelve a könnyebbség kedvéért, de az OmegaT-ben nem kiemelten jelennek meg. A kék HTML-címkéket az OmegaT figyelmen kívül hagyja, mivel ezek teljesen körbeveszik az adott egységet.. Az alább zöld színnel kiemelt címkéket az OmegaT-nek kezelnie kell, mert azok az egységen belül helyezkednek el. Íme egy példa egy HTML-állományban szereplő címkére:
+
+ <p>Egy másik megjelenítési betűtípust választhat a <b>Betű...</b> párbeszédablakból. Megnyitása a<i>Beállítások → Betű...</i> menüpontból történik. A párbeszédablakban beállíthatja a betű típusát és méretét.</p>
+
+ Ezt az OmegaT az alábbi módon jeleníti meg afrikaans fordítás esetén:
+
+
+ Forrásnyelvi szövegegység <indexterm class="singular">
+ <primary>Szövegegység, forrásnyelvi és célnyelvi - ábra</primary>
+ </indexterm>HTML-ben
+
+
+
+
+
+
+
+
+
+
+
+
+ Amikor az OmegaT előállítja a fordítást, a HTML ekként néz ki:
+
+
+ Célnyelvi szövegegység HTML-ben
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Címkék ellenőrzése<indexterm class="singular">
+ <primary>Címkét tartalmazó szöveg</primary> <secondary>Címkék ellenőrzése</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Címkék ellenőrzése</primary>
+ </indexterm>
+
+ Az OmegaT automatikusan nem szűri ki a lefordított dokumentumban lévő hibás címkéket. Ezért a szöveg leadása előtt a fordítónak kell ellenőrizni a címkék helyességét. Válassza ki a menüből az CtrlTEszközökCímkék ellenőrzése... pontot. Ekkor egy táblázat jelenik meg, amelyben látható, hol nem egyeznek a forrásnyelvi és a célnyelvi címkék. Kattintson a szövegegység számára. Ennek hatására automatikusan a szerkesztőben a hibás szövegegységhez kerül, ahol kijavíthatja a hibás címkét. A javítások elvégzése után ellenőrizze ismét a CtrlT
+ BillentyűparancsokCtrl+T - Címkék ellenőrzéseCímkét tartalmazó szöveg
+ lenyomásával. Ne feledje, hogy a címkeellenőrző hibát találhat helyes címkék esetén is - például amikor a nyelvtani alak helyessége érdekében a címkék sorrendje megváltozik. Ez esetben a hibát vegye óvatosságból kiadott figyelmeztetésnek.
+
+ Egyes esetekben címkehiba miatt nem lehet a dokumentumot megnyitni. Aggodalomra semmi ok: a forrásszöveg és a célnyelvi szöveg nem veszett el. Javítsa ki a hibás címkéket, mielőtt előállítja a lefordított állományokat. Végezetül nyissa meg a böngészőben vagy a szerkesztőben a lefordított szöveget és ellenőrizze a végső formázást.
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/hu/OmegaT.css b/OmegaT/doc_src/hu/OmegaT.css
new file mode 100644
index 0000000..1893c29
--- /dev/null
+++ b/OmegaT/doc_src/hu/OmegaT.css
@@ -0,0 +1,78 @@
+body {
+ font-family: sans-serif;
+ margin: 1em;
+}
+
+h1, h2, table, dt {
+ color: navy;
+}
+
+h3, h4, ul a {
+ color: green;
+}
+
+code, .code {
+ color: black;
+ background: #ffffcc;
+ border-style: solid;
+ border-width: 1px;
+ border-color: #ffff66;
+ vertical-align: top;
+}
+
+.new {
+ font-size: x-small;
+ color: red;
+ background: yellow;
+}
+
+.updated {
+ font-size: x-small;
+ color: orange;
+}
+
+.note {
+ font-size: small;
+ color: black;
+ background: silver;
+}
+
+.warning {
+ color: red;
+ background: yellow;
+}
+
+.chapter {
+ color: black;
+}
+
+.navbar-top, .navbar-bottom {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.rel-p {
+ width: 9%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.rel-n {
+ width: 6%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.nav-link {
+ width: 39%;
+ align: left;
+ valign: center;
+}
+
+.toc-link {
+ width: 7%;
+ align: left;
+ valign: center;
+}
\ No newline at end of file
diff --git a/OmegaT/doc_src/hu/images/MatchesPane.png b/OmegaT/doc_src/hu/images/MatchesPane.png
new file mode 100644
index 0000000..5fc5f87
Binary files /dev/null and b/OmegaT/doc_src/hu/images/MatchesPane.png differ
diff --git a/OmegaT/doc_src/hu/images/NewProject.png b/OmegaT/doc_src/hu/images/NewProject.png
new file mode 100644
index 0000000..c439c10
Binary files /dev/null and b/OmegaT/doc_src/hu/images/NewProject.png differ
diff --git a/OmegaT/doc_src/hu/images/tagged_segment.png b/OmegaT/doc_src/hu/images/tagged_segment.png
new file mode 100644
index 0000000..1b9e648
Binary files /dev/null and b/OmegaT/doc_src/hu/images/tagged_segment.png differ
diff --git a/OmegaT/doc_src/hu/images/tagged_segment_target.png b/OmegaT/doc_src/hu/images/tagged_segment_target.png
new file mode 100644
index 0000000..ddbd1c6
Binary files /dev/null and b/OmegaT/doc_src/hu/images/tagged_segment_target.png differ
diff --git a/OmegaT/doc_src/it/InstantStartGuide.xml b/OmegaT/doc_src/it/InstantStartGuide.xml
new file mode 100644
index 0000000..5375cc3
--- /dev/null
+++ b/OmegaT/doc_src/it/InstantStartGuide.xml
@@ -0,0 +1,400 @@
+
+
+
+ Guida di avvio rapido
+
+
+ Iniziare a usare <application>OmegaT</application> in cinque minuti!
+
+ Questa Guida di avvio rapido si occupa solo delle funzioni basilari principali di OmegaT. Per familiarizzare in modo completo con tutte le funzioni messe a disposizione da OmegaT, si consiglia di leggere il Manuale per l'Utente. Nota per gli utenti Mac: le scorciatoie qui descritte usano la combinazione "Ctrl + tasto" ma gli utenti di Mac dovrebbero leggere invece "Cmd + key". Nelle tastiere Apple, il tasto "Cmd" presenta la dicitura "comando" o la figura di una mela.
+
+ La schermata di OmegaT è composta da un'area di lavoro con cinque pannelli distinti.
+ Finestre in OmegaT
+ . Ogni pannello può essere ridimensionato servendosi del mouse. Alla sinistra si trova l'Editor, in cui si eseguirà la traduzione. In alto a destra è presente il pannello delle “Concordanze parziali (fuzzy)”, in cui vengono visualizzate le concordanze con la memoria di traduzione. Immediatamente sotto si trova il pannello “Glossario”, nel quale vengono visualizzate le concordanze con il glossario. Due linguette nella parte inferiore della finestra aprono rispettivamente i pannelli del "Dizionario" e della "Traduzione automatica". (Nota: è possibile riordinare i pannelli a proprio piacimento - la descrizione precedente si riferisce all'aspetto di OmegaT subito dopo l'installazione)
+
+ Nel pannello dell'Editor, OmegaT presenta il testo di partenza “segmentato” in frasi o paragrafi. Questi vengono poi tradotti, uno alla volta. Quando si avanza da un segmento all'altro, le proprie traduzioni sono registrate automaticamente in una memoria di traduzione. Al termine della traduzione di tutti i segmenti (o prima, quando necessario), OmegaT usa la memoria di traduzione per creare, nella cartella “Target”, i documenti tradotti.
+
+ OmegaT organizza il lavoro di traduzione in “progetti" di traduzione. Per ciascun progetto OmegaT crea un gruppo di cartelle che verranno utilizzate, a turno, per memorizzare i documenti di partenza da tradurre e i glossari e le memorie di traduzione che si desidera adottare. OmegaT crea anche una cartella “Target” nella quale vengono memorizzati i documenti finali tradotti.
+
+
+
+ Tradurre con <application>OmegaT</application>
+
+
+ Creazione e apertura di un nuovo progetto<indexterm class="singular">
+ <primary>Progetto</primary> <secondary>Crea / apri nuovo</secondary>
+ </indexterm>
+
+ Dalla barra dei menu, selezionare ProgettoNuovo...
+ Menu ProgettoNuovo...
+ .
+
+ Accedere alla cartella nella quale si desidera salvare i file progetto e inserire un nome da assegnare al progetto di traduzione. Il nome immesso verrà assegnato alla cartella del progetto, e tutti i file che fanno parte del progetto verranno memorizzati in questa cartella, oppure nelle sottocartelle dalla stessa dipendenti.
+
+ OmegaT richiederà di confermare, o di modificare, le cartelle del progetto che dovranno essere create, visualizzando la seguente finestra di dialogo:
+
+
+ <indexterm class="singular">
+ <primary>Progetto</primary> <secondary>Finestra di dialogo del progetto - figura</secondary>
+ </indexterm>Nuovo progetto - finestra di dialogo
+
+
+
+
+
+
+
+
+
+
+
+ A questo punto basta accettare i percorsi di memorizzazione suggeriti per le sottocartelle, accertandosi, però, che i codici della lingua di partenza e di arrivo siano corretti. Selezionare il codice della lingua (2 lettere), o della lingua e della regione (2 + 2 lettere), dall'elenco a discesa, oppure digitarli manualmente (il codice della lingua può essere di 2 o 3 lettere). Tenere a mente il percorso di memorizzazione della sottocartella “Target” (in cui vengono memorizzati i documenti tradotti). Se si preferisce che OmegaT segmenti il documento per “frasi” invece che per “paragrafi”, si deve leggere il capitolo sulle “Regole di segmentazione”.
+
+ Quando si fa clic su OK per accettare l'impostazione del progetto, OmegaT richiede di selezionare la serie di documenti da importare nel progetto. È possibile importare singoli file tramite dal menu Progetto > Importa i file di partenza, oppure copiare manualmente più file o, in alternativa, intere strutture di cartelle (con tutti i file contenuti nelle sottocartelle dipendenti) all'interno della cartella Source del proprio progetto OmegaT (utilizzando, ad esempio, il file manager del proprio sistema). Se si sono erroneamente importati documenti non corretti, oppure un numero maggiore di documenti rispetto a quello necessario, i file in eccesso potranno essere semplicemente rimossi dalla cartella Source.
+
+ Per verificare l'elenco dei file da tradurre, accedere alla finestra File del progetto
+ File del progettoFile di partenza
+ (se la finestra non si apre automaticamente avviare, dalla barra dei menu, il comando: ProgettoFile del progetto...,
+ Menu ProgettoFile del progetto...
+ ). Se si è dovuto modificare il contenuto della cartella sorgente, ricordare di ricaricare prima il progetto (dalla barra dei menu, selezionare il comando F5ProgettoRicarica). Per impostazione predefinita, OmegaT apre il primo file dell'elenco del progetto. Tenere presente che OmegaT è in grado di tradurre i file dei formati qui sotto indicati, se coincidono con i modelli definiti nei filtri dei file. Qualsiasi altro tipo di file verrà ignorato.
+ File di partenzaFormati dei file
+
+
+
+
+ Formati di file di solo testo
+ Formati dei filefile di solo testo
+
+
+ File di testo ASCII (.txt, ecc.)
+
+
+
+ Testo codificato (*.UTF8)
+
+
+
+ Java resource bundles (*.properties)
+
+
+
+ file PO (*.po)
+
+
+
+ INI (codice=valore) files (*.ini)
+
+
+
+
+ file DTD (*.DTD)
+
+
+
+ file DocuWiki (*.txt)
+
+
+
+
+
+ file di titoli SubRip (*.srt)
+
+
+
+
+
+ CSV locale Magento CE (*.csv)
+
+
+
+
+
+
+
+
+ Formati di file di testo con tag
+ Formati dei filecon formattazione
+
+
+
+
+ OpenOffice.org / OpenDocument (*.odt, *.ott, *.ods, *.ots,
+ *.odp, *.otp)
+
+
+
+
+
+ Microsoft Open XML (*.docx, *.xlsx, *.pptx)
+
+
+
+
+
+ (X)HTML (*.html, *.xhtml,*.xht)
+
+
+
+
+
+ HTML Help Compiler (*.hhc, *.hhk)
+
+
+
+
+
+ DocBook (*.xml)
+
+
+
+
+
+ XLIFF monolingua (*.xlf, *.xliff, *.sdlxliff)
+
+
+
+
+
+ QuarkXPress CopyFlowGold (*.tag, *.xtg)
+
+
+
+
+
+ file ResX (*.resx)
+
+
+
+
+
+ risorsa Android (*.xml)
+
+
+
+
+
+ LaTex (*.tex, *.latex)
+
+
+
+ file di Guide (*.xml) e Manuali (*.hmxp) files
+
+
+
+ Typo3 LocManager (*.xml)
+
+
+
+
+
+ localizzazione WiX (*.wxl)
+
+
+
+ Iceni Infix (*.xml)
+
+
+
+ esportazione Flash XML (*.xml)
+
+
+
+ Wordfast TXML (*.txml)
+
+
+
+ Camtasia per Windows (*.camproj)
+
+
+
+
+
+
+ In aggiunta al testo da tradurre, i file di testo formattato contengono informazioni di formattazione che OmegaT rende visibili sotto forma di “tag” (etichette). I tag devono essere presenti anche nel testo tradotto, anche se la formattazione non necessita di “traduzione”. Se si dovessero eliminare o spostare accidentalmente i tag, il testo potrebbe non venire visualizzato come ci si aspetta e si dovrà intervenire sulla traduzione - consultare il capitolo successivo "Verifica dei tag".
+
+
+
+ Traduzione dei singoli segmenti
+
+ Al termine della definizione del progetto, e dopo aver deciso quali file devono essere tradotti, OmegaT apre nell'Editor il primo file di partenza dell'elenco.
+
+ Il segmento attivo da tradurre è evidenziato in verde; subito sotto compare una copia del testo di partenza, inserito nel “campo di arrivo”. (A questo punto tutto il testo che si trova all'esterno del campo di arrivo non potrà essere in alcun modo modificato). La traduzione va inserita prima del tag <segmento 0001>. È possibile impostare OmegaT per copiare automaticamente il testo di partenza all'interno di quello di arrivo (consultare Opzioni > Comportamento di modifica...), opzione utile quando alcune parti del testo non devono essere alterate. In tali casi si dovrà sovrascrivere il testo di partenza. Per passare alla traduzione del segmento successivo, premere "INVIO". Nota:
+
+
+
+ per trasferirsi a un qualsiasi altro segmento all'interno del documento, sia esso precedente o successivo quello attivo, fare doppio clic sulla frase o sul paragrafo da aprire.
+
+
+
+ Se si preferisce inserire la traduzione in un campo di destinazione vuoto, impostare tale opzione utilizzando il comando OpzioniComportamento di modifica...
+ Menu OpzioniComportamento di modifica...
+
+
+
+
+ Nella voce di menu principale Vista è possibile modificare l'impostazione del pannello dell'Editor (affinché mostri o no, ad esempio, il testo di partenza, evidenzi il testo tradotto, ecc.).
+
+ Quando si preme il tasto "INVIO", accadono alcune cose in modo invisibile: OmegaT aggiunge la coppia di segmenti (il segmento di partenza e la sua traduzione) alla memoria di traduzione interna. Traduce automaticamente tutti gli altri segmenti identici che vengono rilevati. Viene eseguita anche una scansione della memoria di traduzione e del glossario, alla ricerca di concordanze per il segmento successivo non ancora tradotto, che viene poi aperto.
+
+
+
+
+
+ Uso delle concordanze delle memorie di traduzione, dei dizionari e dei glossari
+
+
+ Concordanze della memoria di traduzione (TM)<indexterm class="singular">
+ <primary>Memorie di traduzione</primary> <secondary>Concordanze parziali</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Memorie di traduzione</primary> <secondary>Concordanze</secondary>
+ </indexterm>
+
+
+ Pannello delle concordanze
+
+
+
+
+
+
+
+
+
+
+
+
+ Se OmegaT rileva, per il segmento successivo, la presenza nelle memorie di traduzione di una concordanza parziale (fuzzy match) (pari o superiore al 30%), essa viene riportata all'interno della finestra “Concordanze parziali (fuzzy)”. Per impostazione predefinita, nella finestra “Concordanze parziali (fuzzy)” viene selezionata la prima concordanza rilevata.
+
+
+
+ Premere CtrlI
+ ScorciatoieCtrl+I - Inserimento di testo
+ per inserire, alla posizione del cursore, la concordanza preselezionata, oppure...
+
+
+
+ Premere CtrlR
+ ScorciatoieCtrl+R - Sostituzione di testo
+
+ Sostituzione di testo
+ per sovrascrivere l'intero segmento con il contenuto della corrispondenza preselezionata.
+
+
+
+ Se sono state rilevate più concordanze, e si preferisce utilizzarne una diversa da quella preselezionata
+
+
+
+ selezionare la concordanza più appropriata all'interno della finestra “Corrispondenze parziali (fuzzy)”; premere Ctrl2 per la seconda concordanza proposta, Ctrl3 per la terza, e così via.
+
+
+
+ Quindi premere CtrlI oppure CtrlR come sopra indicato.
+
+
+
+ Si può indicare a OmegaT di inserire automaticamente, all'interno del campo di arrivo, tutte le prime concordanze superiori a un valore percentuale specificato. Questa opzione viene definita con il comando Opzioni
+
+
+
+ Concordanze del glossario e del dizionario<indexterm class="singular">
+ <primary>Concordanze</primary> <secondary>Concordanze di glossario e dizionario</secondary>
+ </indexterm>
+
+ Tutte le corrispondenze di termini nei glossari e nei dizionari, inclusi nel progetto, saranno visualizzati come riferimento nei rispettivi pannelli.
+
+
+
+ Uso della funzione di ricerca
+
+ OmegaT mette a disposizione un'ampia gamma di funzioni di ricerca. Richiamare la finestra “Ricerca testo” tramite la combinazione da tastiera CtrlF e inserire nel campo “Cerca” la parola o la frase che si desidera reperire. In alternativa, selezionare una parola o una frase in un punto qualsiasi nel pannello dell'Editor CtrlF: si aprirà la finestra di ricerca testo e la parola o la frase selezionata sarà inserita automaticamente nel campo "Cerca".
+
+
+
+ Uso dei servizi di traduzione automatica<indexterm class="singular">
+ <primary>Concordanze</primary> <secondary>Traduzione automatica</secondary>
+ </indexterm>
+
+ Nel pannello della Traduzione automatica, se è stato attivato uno dei servizi (vedere Opzioni > Traduzione automatica), si può ottenere un suggerimento automatico per la traduzione del segmento attivo. Premere Ctrl+M per sostituire il segmento di arrivo con il suggerimento.
+
+
+
+
+ Creazione dei documenti di arrivo<indexterm class="singular">
+ <primary>File del progetto</primary> <secondary>File di partenza</secondary>
+ </indexterm>
+
+ Quando si è conclusa la traduzione di tutti i segmenti (o anche prima, se si desidera), OmegaT creerà il documento, o i documenti, di arrivo utilizzando le traduzioni memorizzate all'interno della memoria di traduzione. Per avviare questa operazione, dalla barra dei menu avviare il comando CtrlDProgettoCrea i documenti di arrivo
+ ScorciatoieCtrl+D - Creare i documenti di arrivo
+
+ Menu ProgettoCrea i documenti di arrivo
+ . OmegaT genererà una versione tradotta di tutti i documenti traducibili contenuti nella cartella “Source” del progetto, sia che siano stati completamente o parzialmente tradotti. I documenti completamente, o parzialmente, tradotti verranno memorizzati nella cartella “Target” del progetto. Per concludere l'operazione di traduzione, aprire i documenti di arrivo con l'applicazione corrispondente (navigatore, elaboratore di testi ecc.) per verificare il contenuto e la corretta formattazione del documento finale. A questo punto si potrà tornare a OmegaT per apportare tutte le modifiche e le correzioni necessarie, alla fine delle quali non si deve dimenticare di creare di nuovo i documenti di arrivo tradotti.
+
+
+
+
+ Gestire il testo con tag<indexterm class="singular">
+ <primary>Testo con tag</primary>
+ </indexterm>
+
+ OmegaT assicura che la formattazione presente nei documenti di partenza (neretti, corsivi ecc.) venga conservata anche nel documento finale, utilizzando, a questo scopo, speciali tag. I tag di OmegaT sono composti da una o più lettere seguite da una o più cifre, e utilizzando come carattere di chiusura "/" (la barra inclinata; per esempio: <f0>, </f0> <br>, </s2> ecc.). È necessario gestire questi tag con attenzione e accertarsi che compaiano nella giusta posizione anche all'interno dei segmenti di arrivo (si vedano le operazioni sui tag).
+
+
+ Un esempio...<indexterm class="singular">
+ <primary>Testo con tag</primary> <secondary>Un esempio</secondary>
+ </indexterm>
+
+ Negli esempi seguenti i tag sono stati evidenziati per renderli più immediatamente visibili, anche se OmegaT, in effetti, non li segnala nello stesso modo. I tag HTML, evidenziati in blu, saranno ignorati da OmegaT, poiché racchiudono completamente il segmento. I tag, qui sotto evidenziati in verde devono essere gestiti da OmegaT, dato che si trovano all'interno del segmento. Qui di seguito viene fornito un esempio di un segmento di un file HTML:
+
+ <p>Tramite la finestra di dialogo <b>Anteprima caratteri</b> può essere selezionato un diverso carattere per la visualizzazione. Aprire la finestra avviando, dalla barra dei menu, il comando <i>Opzioni</i> →<i>Tipo di carattere...</i>. Da questa finestra si potrà modificare sia il tipo sia la dimensione del carattere.</p>
+
+ Qui viene mostrato come OmegaT visualizzerà il segmento, nella traduzione in Afrikaans:
+
+
+ <indexterm class="singular">
+ <primary>Segmento, Partenza e arrivo - figura</primary>
+ </indexterm>Segmento HTML di partenza
+
+
+
+
+
+
+
+
+
+
+
+
+ Una volta che OmegaT ha creato il documento tradotto, il file HTML apparirà come quello qui riportato:
+
+
+ Segmento HTML di arrivo
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Verifica dei tag<indexterm class="singular">
+ <primary>Testo con tag</primary> <secondary>Verifica dei tag</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Verifica dei tag</primary>
+ </indexterm>
+
+ OmegaT non rileva automaticamente i tag errati all'interno del documento tradotto. Prima di inviare il documento finale al proprio cliente, dunque, si dovrebbe sempre verificare la possibile presenza di errori all'interno del documento. Dalla barra dei menu selezionare il comando CtrlTStrumentiConvalida dei tag.... Viene aperta una tabella nella quale sono riportati i segmenti nei quali non vi è corrispondenza dei tag tra i segmenti di partenza e quelli di arrivo. Fare clic sul numero del segmento. Si verrà automaticamente riportati al segmento dubbio all'interno della finestra dell'Editor, dove si potrà correggere l'errore. Una volta eseguite le correzioni, verificarle premendo di nuovo CtrlT
+ ScorciatoieCtrl+T - Verifica dei tagTesto con tag
+ . Si noti che l'analizzatore di tag potrebbe rilevare un errore in casi in cui i tag sono corretti - ad esempio, quando si è dovuto cambiare l'ordine dei tag per una corretta costruzione grammaticale della traduzione. È bene considerare questo fatto come segno di cautela da parte dell'analizzatore.
+
+ In alcuni casi, gli errori dei tag possono anche determinare la mancata apertura del documento finale. Non vi è motivo di entrare nel panico - si ha ancora a disposizione del file di partenza e della traduzione e, prima di creare i file di arrivo, basta soltanto correggere appropriatamente ogni possibile errore dei tag. Infine, si dovrebbe sempre effettuare una verifica finale della formattazione aprendo il documento tradotto con l'applicazione di visualizzazione o di modifica adatta.
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/it/OmegaT.css b/OmegaT/doc_src/it/OmegaT.css
new file mode 100644
index 0000000..1893c29
--- /dev/null
+++ b/OmegaT/doc_src/it/OmegaT.css
@@ -0,0 +1,78 @@
+body {
+ font-family: sans-serif;
+ margin: 1em;
+}
+
+h1, h2, table, dt {
+ color: navy;
+}
+
+h3, h4, ul a {
+ color: green;
+}
+
+code, .code {
+ color: black;
+ background: #ffffcc;
+ border-style: solid;
+ border-width: 1px;
+ border-color: #ffff66;
+ vertical-align: top;
+}
+
+.new {
+ font-size: x-small;
+ color: red;
+ background: yellow;
+}
+
+.updated {
+ font-size: x-small;
+ color: orange;
+}
+
+.note {
+ font-size: small;
+ color: black;
+ background: silver;
+}
+
+.warning {
+ color: red;
+ background: yellow;
+}
+
+.chapter {
+ color: black;
+}
+
+.navbar-top, .navbar-bottom {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.rel-p {
+ width: 9%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.rel-n {
+ width: 6%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.nav-link {
+ width: 39%;
+ align: left;
+ valign: center;
+}
+
+.toc-link {
+ width: 7%;
+ align: left;
+ valign: center;
+}
\ No newline at end of file
diff --git a/OmegaT/doc_src/it/images/MatchesPane.png b/OmegaT/doc_src/it/images/MatchesPane.png
new file mode 100644
index 0000000..7dd1f11
Binary files /dev/null and b/OmegaT/doc_src/it/images/MatchesPane.png differ
diff --git a/OmegaT/doc_src/it/images/NewProject.png b/OmegaT/doc_src/it/images/NewProject.png
new file mode 100644
index 0000000..daaeff9
Binary files /dev/null and b/OmegaT/doc_src/it/images/NewProject.png differ
diff --git a/OmegaT/doc_src/it/images/tagged_segment.png b/OmegaT/doc_src/it/images/tagged_segment.png
new file mode 100644
index 0000000..3941b94
Binary files /dev/null and b/OmegaT/doc_src/it/images/tagged_segment.png differ
diff --git a/OmegaT/doc_src/it/images/tagged_segment_target.png b/OmegaT/doc_src/it/images/tagged_segment_target.png
new file mode 100644
index 0000000..804a52b
Binary files /dev/null and b/OmegaT/doc_src/it/images/tagged_segment_target.png differ
diff --git a/OmegaT/doc_src/license.txt b/OmegaT/doc_src/license.txt
new file mode 100644
index 0000000..1af4657
--- /dev/null
+++ b/OmegaT/doc_src/license.txt
@@ -0,0 +1,340 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) year name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ , 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/OmegaT/doc_src/nl/AboutOmegaT.xml b/OmegaT/doc_src/nl/AboutOmegaT.xml
new file mode 100644
index 0000000..5ae61c1
--- /dev/null
+++ b/OmegaT/doc_src/nl/AboutOmegaT.xml
@@ -0,0 +1,133 @@
+
+
+
+ Over <application>OmegaT</application> - introductie
+
+
+ OmegaT pluspunten
+
+ OmegaT is een vrij, multiplatform Computer Aided Translation programma met de volgende pluspunten.
+
+
+
+ Vertaalgeheugen:OmegaT slaat uw vertalingen op in een vertaalgeheugen. Tegelijkertijd kan het vertaalgeheugens van eerdere vertalingen als verwijzingen gebruiken. Vertaalgeheugens kunnen zeer handig zijn bij het vertalen van veel voorkomende herhalingen of tekstsegmenten die redelijk met elkaar overeen komen. OmegaT gebruikt vertaalgeheugens om uw eerdere vertalingen op te slaan en toont u dan de meest waarschijnlijke vertalingen voor de tekst waaraan u momenteel werkt.
+
+ Deze vertaalgeheugens kunnen zeer handig zijn als een, reeds vertaald, document moet worden bijgewerkt. Ongewijzigde zinnen worden automatisch vertaald, terwijl bijgewerkte zinnen worden getoond met de vertaling van de meest gelijkende oudere versie van dezelfde zin. Wijzigingen in het originele document worden dus gemakkelijker afgehandeld. Als u eerder gemaakte vertaalgeheugens gebruikt, bijvoorbeeld geleverd door uw vertaalbureau of uw cliënt, is OmegaT in staat om ze te gebruiken als referentie-geheugens.
+
+ OmegaT gebruikt de standaard bestandsindeling TMX om vertaalgeheugens op te slaan en om daar toegang toe te krijgen, hetgeen garandeert dat u uw vertalingsmateriaal kunt uitwisselen met andere CAT-toepassingen die deze bestandsindeling ondersteunen.
+
+
+
+
+
+ Terminologiebeheer: Terminologiebeheer is belangrijk voor consistentie in de vertalingen. OmegaT gebruikt woordenlijsten die vertalingen van woorden of korte frasen bevatten, een soort vereenvoudigd tweetalig woordenboek op een bepaald terrein. Voor uw verwijzing toont OmegaT de vertaling van woorden als die aanwezig zijn in het segment dat op dit moment de focus heeft.
+
+
+
+
+
+ Proces van vertalingen: Veronderstel dat u iets moet vertalen, van één enkel bestand tot een map die submappen bevat met meerdere bestanden in verschillende indelingen. Als u OmegaT laat weten welke bestanden u moet vertalen, zal het kijken naar de bestanden die het begrijpt, gebaseerd op regels voor bestandsfiltering, de tekstdelen daarin herkennen, de tekstgroepen opsplitsen op basis van segmentatieregels, en de segmenten één voor één tonen zodat u door kunt gaan met de vertaling. OmegaT slaat uw vertalingen op en stelt mogelijke vertalingen voor vanuit overeenkomende segmenten in eerdere vertaalgeheugens. Als u klaar bent om het uiteindelijke product te bekijken, kunt u de vertaalde bestanden exporteren, ze openen in het gewenste programma en zien hoe de vertaling er in de uiteindelijke indeling uitziet.
+
+
+
+
+
+ Overzicht van hoofdstukken
+
+ Deze documentatie is zowel bedoeld als handleiding als als gids met verwijzingen. Hier is een kort overzicht van de hoofdstukken en hun inhoud.
+
+
+
+ gids Snel starten: dit hoofdstuk is bedoeld als een gids Snel starten voor beginners en “ongeduldige types”, die de complete procedure weergeeft vanaf het openen van een nieuw project voor vertalingen tot en met het voltooien van die vertaling.
+
+
+
+
+
+ Installeren en uitvoeren van OmegaT: dit hoofdstuk is handig als u voor het eerst begint met het werken met OmegaT. Het bevat de specifieke instructies over hoe OmegaT te installeren en het uit te voeren op Windows, Mac OS X en Linux. Voor gevorderde gebruikers beschrijft dit hoofdstuk de opdrachten voor de modus met de opdrachtregel en de mogelijkheden daarvan.
+
+
+
+
+
+ De gebruikersinterface,Hoofdmenu en Sneltoetsen voor het toetsenbord: deze twee hoofdstukken zullen waarschijnlijk veelvuldig geraadpleegd worden, omdat zij de gebruikersinterface van OmegaT uitleggen en de via het hoofdmenu en de sneltoetsen voor het toetsenbord beschikbare functies.
+
+
+
+
+
+ Projecteigenschappen, OmegaT bestanden en mappen: een project in de context van OmegaT is het gedeelte werk dat OmegaT in staat is als CAT-gereedschap af te handelen. Dit hoofdstuk beschrijft de projecteigenschappen, zoals de bron- en doeltalen. Het tweede hoofdstuk beschrijft de verschillende submappen en bestanden in een vertaalproject en hun rol als ook andere gebruikers- en toepassingsbestanden die zijn geassocieerd met OmegaT.
+
+
+
+
+
+ Gedrag bewerkingsveld: een kort hoofdstuk dat beschrijft hoe het gedrag met betrekking tot bewerking van het segment dat wordt vertaald wordt ingesteld.
+
+
+
+
+
+ Werken met platte tekst en Werken met opgemaakte tekst: deze twee hoofdstukken beschrijven bepaalde belangrijke punten met betrekking tot te vertalen teksten, zoals de codering (in het geval van "platte tekst"-bestanden) en de afhandeling van tags (in het geval van opgemaakte tekst).
+
+
+
+
+
+ Vertaalgeheugens: beschrijft de rol van de verschillende submappen die vertaalgeheugens bevatten, en verschaft informatie over andere belangrijke aspecten met betrekking tot vertaalgeheugens.
+
+
+
+ Segmentatie: programma's met vertaalgeheugens werken met teksteenheden die segmenten worden genoemd. In OmegaT kunnen segmenten worden gebaseerd op alinea's of op segmentatieregels. Segmentatie op basis van alinea's wordt minder frequent gebruikt, maar kan handig zijn in het geval van zogenaamde "creatieve" teksten. De op regels gebaseerde segmentatie is gewoonlijk synoniem aan de op zinnen gebaseerde segmentatie. Een aantal verzamelingen van regels worden meegeleverd, terwijl aanvullende regels door de gebruiker kunnen worden gedefinieerd, zoals beschreven in dit hoofdstuk.
+
+
+
+ Zoeken enReguliere uitdrukkingen: Zoeken in OmegaT kan zo eenvoudig zijn als "som de segmenten op met het woord 'kangoeroe'". Zij mogen ook complex zijn, om het bijvoorbeeld mogelijk te maken te zoeken naar segmenten met twee of meer opeenvolgende spaties. In dat geval zou de reguliere uitdrukking ^s^s+ worden gebruikt te zoeken en de betrokken segmenten op te sommen. Reguliere uitdrukkingen worden ook uitgebreid in de segmentatieregels gebruikt.
+
+
+
+ Woordenboeken, Woordenlijsten, Machinevertaling en Spellingscontrole: in OmegaT kunnen woordenboeken en woordenlijsten worden uitgebreid. Als een internetverbinding beschikbaar is, kunnen diverse services voor machinevertaling zoals Google Translate worden gebruikt vanuit OmegaT. Indien spellingscontrole is geactiveerd, worden spelfouten en typefouten herkend en kunnen die gecorrigeerd worden tijdens de vertaling.
+
+
+
+ Diversen: behandelt andere interessante punten zoals het vermijden van het verliezen van gegevens.
+
+
+
+ Appendices bevat de volgende informatie
+
+
+
+ OmegaT op het web: informatie met betrekking tot on-line bronnen voor OmegaT
+
+
+
+
+
+ Talen: bevat de ISO-lijst van talen en taalcodes
+
+
+
+
+
+ Sneltoetsen toetsenbord: de lijst met sneltoetsen die worden gebruikt bij het bewerken
+
+
+
+ Aanpassen van sneltoetsen: sneltoetsen kunnen worden aangepast om te voldoen aan uw persoonlijke voorkeuren
+
+
+
+
+
+ Auteursrechten
+
+
+
+
+
+ Index sleutelwoorden: een uitgebreide index van sleutelwoorden wordt verschaft om de lezer te helpen de relevante informatie te vinden.
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/App_Aknowledgements.xml b/OmegaT/doc_src/nl/App_Aknowledgements.xml
new file mode 100644
index 0000000..c3770a8
--- /dev/null
+++ b/OmegaT/doc_src/nl/App_Aknowledgements.xml
@@ -0,0 +1,43 @@
+
+
+
+ Dankwoorden
+
+
+ Iedereen bedankt!
+
+ Welke inconsistente dingen, vergeten dingen en echte fouten u ook in deze huidige versie zult vinden, zij zijn allemaal van mijzelf. Deze handleiding zou echter niet mogelijk zijn zonder de hulp en ondersteuning van een aantal personen. Expliciete dank aan:
+
+
+
+ Mark Prior: het corrigeren van de eerste versie was liefde voor OmegaT en de Engelse taal.
+
+
+
+
+
+ Didier Briel: ik zou het niet hebben kunnen doen zonder het geduld en de voortdurende hulp van Didier met de details van DocBook. Niet te vergeten zijn zorg en zorgvuldigheid voor het intact en in goede orde houden van de opgeslagen dingen.
+
+
+
+ Samuel Murray: voor het hoofdstuk ter introductie "OmegaT gebruiken in 5 minuten".
+
+
+
+
+
+ Will Helton: het doorlezen van de uiteindelijke versie heeft mij een heleboel schaamte bespaard. Men kan zich alleen maar afvragen hoeveel voorzetsels zouden ontbreken zonder zijn onschatbare hulp.
+
+
+
+
+
+ Jean-Christophe Helary: speciale dank aan JC voor zijn bondige beschrijving om OmegaT uit te voeren, de parameters voor de opdrachtregel en alle andere details, die ik nog moet ontdekken.
+
+
+
+ Laatste maar niet de minste: mijn dank aan alle deelnemers aan de zoekmachine voor OmegaT documentatie voor alle inconsistente dingen die werden gevonden in eerdere versies van de documentatie. Blijf er mee doorgaan!
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/App_Keyboard.xml b/OmegaT/doc_src/nl/App_Keyboard.xml
new file mode 100644
index 0000000..750e083
--- /dev/null
+++ b/OmegaT/doc_src/nl/App_Keyboard.xml
@@ -0,0 +1,169 @@
+
+
+
+ Sneltoetsen voor het toetsenbord voor het bewerken
+
+ Deze korte tekst beschrijft het gedrag van de toetsen in het bewerkingsvenster. De term "Verplaats naar binnen het segment" betekent dat de cursor verplaatst naar het begin van het segment als het eerder vóór het segment stond en naar het einde van het segment als het er eerder achter stond.
+
+
+ Gedrag van de toets bij bewerken
+
+
+
+
+
+
+
+
+ Toetscombinatie
+
+ Actie
+
+
+
+
+
+ Links:
+
+ één teken naar links, maar niet verder dan het begin van het segment
+
+
+
+ Rechts:
+
+ één teken naar rechts, maar niet verder dan het einde van het segment
+
+
+
+ Ctrl+Links:
+
+ één woord naar links, maar niet verder dan het begin van het segment
+
+
+
+ Ctrl+Rechts:
+
+ één woord naar rechts, maar niet verder dan het einde van het segment
+
+
+
+ PgUp:
+
+ pagina omhoog door het document
+
+
+
+ PgDn:
+
+ pagina naar beneden door het document
+
+
+
+ Home*
+
+ verplaats naar het begin van de regel in het segment
+
+
+
+ End*
+
+ verplaats naar het einde van de regel in het segment
+
+
+
+ Ctrl+Home
+
+ verplaats naar het begin van het segment
+
+
+
+ Ctrl+End
+
+ verplaats naar het einde van het segment
+
+
+
+ Ctrl+PgUp
+
+ verplaats naar het begin van het document (Mac: Cmd+PgUp)
+
+
+
+ Ctrl+PgDn
+
+ verplaats naar het einde van het document (Mac: Cmd+PgDn)
+
+
+
+ Backspace*
+
+ verwijder het teken vóór de cursor
+
+
+
+ Delete*
+
+ verwijder het teken na de cursor
+
+
+
+ Ctrl+Backspace
+
+ verwijder de tekens tot aan het begin van het huidige woord (Mac: Alt+Backspace)
+
+
+
+ Ctrl+Delete
+
+ verwijder de tekens tot aan het begin van het volgende woord (Mac: Alt+Delete)
+
+
+
+ Ctrl+Enter
+
+ open het vorige segment (Mac: Cmd+Enter)
+
+
+
+ Ctrl+A
+
+ selecteer het complete segment (Mac: Cmd+A)
+
+
+
+ Ctrl+Shift+O
+
+ schakelen RTL-LTR
+
+
+
+
+
+ * Deze toetsen gedragen zich anders als de cursor buiten het bewerkbare segment staat:
+
+
+
+ Home: cursor naar het begin van het actieve segment
+
+
+
+ End: cursor naar het einde van het actieve segment
+
+
+
+ Backspace: niets
+
+
+
+ Delete: niets
+
+
+
+ Toets van elk teken, indien geklikt buiten het bewerkbare segment, zal worden genegeerd.
+
+
+
+ De toets "Shift" omvat niet per definitie enig speciaal gedrag: indien de "Shift"-toets is ingedrukt verplaatsen alle toetsen de cursor op de hun gewone manier.
+
+ Systeembrede opdrachten: Plakken (Ctrl+V of Ctrl+Insert), Knippen (Ctrl+X of Ctrl+C), Overeenkomst invoegen (Ctrl+I) en Bron invoegen (Ctrl+Shift+I) acteren in principe op elke selectie, inclusief die welke zich uitstrekken tot buiten het huidige segment. In een dergelijk geval zal de selectie natuurlijk worden beperkt tot de grenzen van het segment.
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/App_Languages.xml b/OmegaT/doc_src/nl/App_Languages.xml
new file mode 100644
index 0000000..c0951d5
--- /dev/null
+++ b/OmegaT/doc_src/nl/App_Languages.xml
@@ -0,0 +1,954 @@
+
+
+
+ Talen - ISO 639 codelijst<indexterm class="singular">
+ <primary>Talen</primary>
+ </indexterm>
+ <indexterm class="singular">
+ <primary>ISO taalcodes</primary>
+ </indexterm>
+ <indexterm class="singular">
+ <primary>Project</primary> <secondary>Eigenschappen</secondary> <seealso>Talen</seealso>
+ </indexterm>
+
+
+ Controleer alstublieft de ISO 639 Codetabellen voor meer en meest recente informatie over taalcodes.
+
+
+ ISO 639-1/639-2 lijst voor taalcode
+
+
+
+
+
+
+ Naam taal
+ ISO 639-1
+ ISO 639-2
+
+
+
+
+ Abchazisch
+ ab
+ abk
+
+
+ Afar
+ aa
+ aar
+
+
+ Afrikaans
+ af
+ afr
+
+
+ Akan
+ ak
+ aka
+
+
+ Albanees
+ sq
+ sqi
+
+
+ Amharisch
+ am
+ amh
+
+
+ Arabisch
+ ar
+ ara
+
+
+ Aragonees
+ an
+ arg
+
+
+ Armeens
+ hy
+ hye
+
+
+ Assamees
+ as
+ asm
+
+
+ Avarisch
+ av
+ ava
+
+
+ Avestaans
+ ae
+ ave
+
+
+ Aymarees
+ ay
+ aym
+
+
+ Azerbeidzjaans
+ az
+ aze
+
+
+ Bambara
+ bm
+ bam
+
+
+ Basjkiers
+ ba
+ bak
+
+
+ Baskisch
+ eu
+ eus
+
+
+ Wit-Russisch
+ be
+ bel
+
+
+ Bengaals
+ bn
+ ben
+
+
+ Bihari
+ bh
+ bih
+
+
+ Bislama
+ bi
+ bis
+
+
+ Bosnisch
+ bs
+ bos
+
+
+ Bretons
+ br
+ bre
+
+
+ Bulgaars
+ bg
+ bul
+
+
+ Birmaans
+ my
+ mya
+
+
+ Catalaans
+ ca
+ cat
+
+
+ Chamorro
+ ch
+ cha
+
+
+ Tsjetsjeens
+ ce
+ che
+
+
+ Chichewa, Chewa, Nyanja
+ ny
+ nya
+
+
+ Chinees
+ zh
+ zho
+
+
+ Tsjoevasjisch
+ cv
+ chv
+
+
+ Cornisch
+ kw
+ cor
+
+
+ Corsicaans
+ co
+ cos
+
+
+ Cree
+ cr
+ cre
+
+
+ Kroatisch
+ hr
+ hrv
+
+
+ Tsjechisch
+ cs
+ ces
+
+
+ Deens
+ da
+ dan
+
+
+ Divehi, Dhivehi, Maledivisch
+ dv
+ div
+
+
+ Nederlands
+ nl
+ nld
+
+
+ Dzongkhaans
+ dz
+ dzo
+
+
+ Engels
+ nl
+ eng
+
+
+ Esperanto
+ eo
+ epo
+
+
+ Ests
+ et
+ est
+
+
+ Ewe
+ ee
+ ewe
+
+
+ Faeröers
+ fo
+ fao
+
+
+ Fijisch
+ fj
+ fij
+
+
+ Fins
+ fi
+ fin
+
+
+ Frans
+ fr
+ fra
+
+
+ Fula, Fulah, Pulaar, Pular
+ ff
+ ful
+
+
+ Galisisch
+ gl
+ glg
+
+
+ Georgisch
+ ka
+ kat
+
+
+ Duits
+ de
+ deu
+
+
+ Grieks, modern
+ el
+ ell
+
+
+ Guaraní
+ gn
+ grn
+
+
+ Gujarati
+ gu
+ guj
+
+
+ Haïtiaans, Haïtiaans Creools
+ ht
+ hat
+
+
+ Hausa
+ ha
+ hau
+
+
+ Hebreeuws (modern)
+ he
+ heb
+
+
+ Herero
+ hz
+ her
+
+
+ Hindi
+ hi
+ hin
+
+
+ Hiri Motu
+ ho
+ hmo
+
+
+ Hongaars
+ hu
+ hun
+
+
+ Interlingua
+ ia
+ ina
+
+
+ Indonesisch
+ id
+ ind
+
+
+ Interlingue
+ ie
+ ile
+
+
+ Iers
+ ga
+ gle
+
+
+ Igbo
+ ig
+ ibo
+
+
+ Inupiaq
+ ik
+ ipk
+
+
+ Ido
+ io
+ ido
+
+
+ IJslands
+ is
+ isl
+
+
+ Italiaans
+ it
+ ita
+
+
+ Inuktitut
+ iu
+ iku
+
+
+ Japans
+ ja
+ jpn
+
+
+ Javaans
+ jv
+ jav
+
+
+ Kalaallisut, Groenlands
+ kl
+ kal
+
+
+ Kannada
+ kn
+ kan
+
+
+ Kanuri
+ kr
+ kau
+
+
+ Kasjmiers
+ s
+ kas
+
+
+ Kazachs
+ kk
+ kaz
+
+
+ Centraal Khmer
+ km
+ khm
+
+
+ Kikuyu, Gikuyu
+ ki
+ kik
+
+
+ Kinyarwanda
+ rw
+ kin
+
+
+ Kirgizisch, Kirgizies
+ ky
+ kir
+
+
+ Komi
+ kv
+ kom
+
+
+ Kongo
+ kg
+ kon
+
+
+ Koreaans
+ ko
+ kor
+
+
+ Koerdisch
+ ku
+ kur
+
+
+ Kwanyama, Kuanyama
+ kj
+ kua
+
+
+ Latijns
+ la
+ lat
+
+
+ Luxemburgs, Letzeburgs
+ lb
+ ltz
+
+
+ Lugandees
+ lg
+ lug
+
+
+ Limburgs
+ li
+ lim
+
+
+ Lingala
+ ln
+ lin
+
+
+ Laotiaans
+ lo
+ lao
+
+
+ Litouws
+ lt
+ lit
+
+
+ Luba-Katanga
+ lu
+ lub
+
+
+ Lets
+ lv
+ lav
+
+
+ Manx
+ gv
+ glv
+
+
+ Macedonisch
+ mk
+ mkd
+
+
+ Malagasisch
+ mg
+ mlg
+
+
+ Malayalam
+ ms
+ msa
+
+
+ Maleis
+ ml
+ mal
+
+
+ Maltees
+ mt
+ mlt
+
+
+ Māori
+ mi
+ mri
+
+
+ Marathisch (Marāṭhī)
+ mr
+ mar
+
+
+ Marshallees
+ mh
+ mah
+
+
+ Mongools
+ mn
+ mon
+
+
+ Nauru
+ na
+ nau
+
+
+ Navajo, Navaho
+ nv
+ nav
+
+
+ Noors Bokmål
+ nb
+ nob
+
+
+ Noord-Ndebele
+ nd
+ nde
+
+
+ Nepalees
+ ne
+ nep
+
+
+ Ndonga
+ ng
+ ndo
+
+
+ Noors Nynorsk
+ nn
+ nno
+
+
+ Noors
+ no
+ nor
+
+
+ Yi
+ ii
+ iii
+
+
+ Zuid-Ndebele
+ nr
+ nbl
+
+
+ Occitaans
+ oc
+ oci
+
+
+ Ojibweg, Ojibwa
+ oj
+ oji
+
+
+ Oudkerkslavisch, Kerkslavisch, Oerslavisch, Oudbulgaars
+ cu
+ chu
+
+
+ Afaan Oromo
+ om
+ orm
+
+
+ Oriyaans
+ of
+ ori
+
+
+ Ossetisch
+ os
+ oss
+
+
+ Punjabi
+ pa
+ pan
+
+
+ Pāli
+ pi
+ pli
+
+
+ Perzisch
+ fa
+ fas
+
+
+ Pools
+ pl
+ pol
+
+
+ Pasjtoe, Pashto, Pushto
+ ps
+ pus
+
+
+ Portugees
+ pt
+ por
+
+
+ Quechua
+ qu
+ que
+
+
+ Romaans
+ rm
+ roh
+
+
+ Rundi
+ rn
+ run
+
+
+ Roemeens, Moldavisch, Moldovaans
+ ro
+ ron
+
+
+ Russisch
+ ru
+ rus
+
+
+ Sanskriet (Saṁskṛta)
+ sa
+ san
+
+
+ Sardisch
+ sc
+ srd
+
+
+ Sindhi
+ sd
+ snd
+
+
+ Noord-Samisch
+ se
+ sme
+
+
+ Samoaans
+ sm
+ smo
+
+
+ Sango
+ sg
+ sag
+
+
+ Servisch
+ sr
+ srp
+
+
+ Schots Keltisch, Keltisch
+ gd
+ gla
+
+
+ Shona
+ sn
+ sna
+
+
+ Sinhala, Singalees
+ si
+ sin
+
+
+ Slowaaks
+ sk
+ slk
+
+
+ Sloveens
+ sl
+ slv
+
+
+ Somalisch
+ so
+ som
+
+
+ Zuid Sothees
+ st
+ sot
+
+
+ Spaans, Castiliaans
+ es
+ spa
+
+
+ Soendanees
+ su
+ sun
+
+
+ Swahili
+ sw
+ swa
+
+
+ Swatisch
+ ss
+ ssw
+
+
+ Zweeds
+ sv
+ swe
+
+
+ Tamil
+ ta
+ tam
+
+
+ Telugu
+ te
+ tel
+
+
+ Tadzjieks
+ tg
+ tgk
+
+
+ Thais
+ th
+ tha
+
+
+ Tigrinyaans
+ ti
+ tir
+
+
+ Tibetaans Standaard, Tibetaans, Centraal
+ bo
+ bod
+
+
+ Turkmeens
+ tk
+ tuk
+
+
+ Tagalog
+ tl
+ tgl
+
+
+ Tswanees
+ tn
+ tsn
+
+
+ Tonga (Tonga-eilanden)
+ to
+ ton
+
+
+ Turks
+ tr
+ tur
+
+
+ Tsongees
+ ts
+ tso
+
+
+ Tataars
+ tt
+ tat
+
+
+ Twi
+ tw
+ twi
+
+
+ Tahitiaans
+ ty
+ tah
+
+
+ Oeigoers
+ ug
+ uig
+
+
+ Oekraïns
+ uk
+ ukr
+
+
+ Urdu
+ ur
+ urd
+
+
+ Oezbeeks
+ uz
+ uzb
+
+
+ Venda
+ ve
+ ven
+
+
+ Vietnamees
+ vi
+ vie
+
+
+ Volapük
+ vo
+ vol
+
+
+ Waals
+ wa
+ wln
+
+
+ Welsh
+ cy
+ cym
+
+
+ Wolof
+ wo
+ wol
+
+
+ Westfries
+ fy
+ fry
+
+
+ Xhosa
+ xh
+ xho
+
+
+ Jiddisch
+ yi
+ yid
+
+
+ Yoruba
+ yo
+ yor
+
+
+ Zhuang, Chuang
+ za
+ zha
+
+
+ Zulu, Zoeloe
+ zu
+ zul
+
+
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/App_Using_tokenizers_in_OmegaT.xml b/OmegaT/doc_src/nl/App_Using_tokenizers_in_OmegaT.xml
new file mode 100644
index 0000000..a9dfddb
--- /dev/null
+++ b/OmegaT/doc_src/nl/App_Using_tokenizers_in_OmegaT.xml
@@ -0,0 +1,85 @@
+
+
+
+ Tokenizers gebruiken in OmegaT
+
+
+ Introductie
+
+ Tokenizers (of stemmers) verbeteren de kwaliteit van de overeenkomsten door het herkennen va betrokken woorden in de bron en gegevens in de vertaalgeheugens. Zij verbeteren ook de overeenkomsten voor de woordenlijsten.
+
+ Een stemmer voor bijvoorbeeld Engels zou de tekenreeks "cats" identificeren (en mogelijk "catlike", "catty" etc.) omdat die is gebaseerd op de stam "cat", en "stemmer", "stemming", "stemmed" omdat die is gebaseerd op "stem". Een stemming algoritme reduceert de woorden "fishing", "fished", "fish", en "fisher" tot de stam van het woord: "fish". Dit is speciaal bijzonder handig in het geval van talen die vormen voor voor- en achtervoegsel voor de stamwoorden gebruiken. Lenen we een voorbeeld uit het Sloveens, hier "good" in alle mogelijke grammaticaal juiste vormen:
+
+
+
+ lep, lepa, lepo - enkelvoud, mannelijk, vrouwelijk, neutraal
+
+
+
+
+
+ lepši, lepša, lepše . - comparatief, nominatief, mannelijk, vrouwelijk, neutraal, resp. meervoudsvorm van het bijvoeglijk naamwoord
+
+
+
+
+
+ najlepših - superlatief, meervoud, genitief voor M,F,N
+
+
+
+
+
+ Installatie en gebruik van de opdrachtregel
+
+ Een tokenizerpakket dat is afgeleid van het Luceneproject wordt gedistribueerd als een OmegaT plug-in op http://sourceforge.net/projects/omegat-plugins/files/. Download de meest recente bestanden (OmegaT-tokenizers_0.4_2-2.1.zip op het moment van schrijven).
+
+ Maak een map met de naam "plug-ins" in de map waar OmegaT.jar staat en pas de bovenstaande bestanden in die map uit om de tokenizer te installeren.
+
+ U moet de tokenizer specificeren die u zal gaan gebruiken voor de brontaal en welke tokenizer u zult gaan gebruiken voor de doeltaal om OmegaT uit te voeren. De syntaxis is als volgt:
+
+ java -jar OmegaT.jar --ITokenizer=[brontaal naam tokenizer] --ITokenizerTarget=[doeltaal naam tokenizer]
+
+ De namen van de tokenizers zijn vermeld in het bestand Readme.txt dat wordt gedistribueerd met de bestanden van de tokenizer. Als u bijvoorbeeld de Lucene CJK tokenizer wilt gebruiken voor de brontaal en de Lucene French tokenizer in de doeltaal, zal uw opdracht er als volgt uitzien:
+
+ java -jar OmegaT.jar
+ --ITokenizer=org.omegat.plugins.tokenizer.LuceneCJKTokenizer
+ --ITokenizerTarget=org.omegat.plugins.tokenizer.LuceneFrenchTokenizer
+
+
+
+ Specifiek voor Mac OSX
+
+ Indien u de tokenizers wilt gebruiken met het Mac OSX OmegaT.app pakket is de installatie van de tokenizer zoals die hierboven is vermeld van toepassing (klik met rechts op de OmegaT.app om de locatie van OmegaT.jar te vinden), maar u zult de namen van de tokenizers moeten specificeren in info.plist dat de startopties voor Java bevat. Volg bovenstaande instructies om toegang te krijgen tot het bestand info.plist en bewerk het zodanig dat het er als volgt uitziet voor het voorbeeld dat we zojuist gaven:
+
+
+<key>VMOptions</key>
+<string>-Xmx1024M</string>
+
+<key>Arguments</key>
+<array>
+ <string>--ITokenizer=org.omegat.plugins.tokenizer.LuceneCJKTokenizer</string>
+ <string>--ITokenizerTarget=org.omegat.plugins.tokenizer.LuceneFrenchTokenizer</string>
+</array>
+
+
+
+ Probleemoplossing
+
+ Open een project en controleer de informatie in het log van de console om er voor te zorgen dat de tokenizers ook echt worden gebruikt. Met het bovenstaande voorbeeld zou dat er uitzien als:
+
+
+84528: Info: Source tokenizer: org.omegat.plugins.tokenizer.LuceneCJKTokenizer
+84528: Info: Target tokenizer: org.omegat.plugins.tokenizer.LuceneFrenchTokenizer
+
+
+ De getallen aan de linkerzijde zijn waarschijnlijk anders op uw systeem dus zorg er voor dat de namen voor de tokenizers voor de bron- en de doeltaal, gespecificeerd in de startopties, overeenkomend met wat het log weergeeft. Als de tokenizers niet juist zijn geactiveerd, zal het log er als volgt uitzien:
+
+
+12719: Info: Source tokenizer: org.omegat.core.matching.Tokenizer
+12719: Info: Target tokenizer: org.omegat.core.matching.Tokenizer
+
+
+ Met het Mac OSX OmegaT.app pakket moet u dubbelklikken op de JavaApplicationStub die is geplaatst in /OmegaT.app/Contents/MacOS/ (kijk hierboven om toegang te verkrijgen) om OmegaT te starten vanuit de console en direct toegang te hebben tot het log.
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/App_Website.xml b/OmegaT/doc_src/nl/App_Website.xml
new file mode 100644
index 0000000..db501df
--- /dev/null
+++ b/OmegaT/doc_src/nl/App_Website.xml
@@ -0,0 +1,69 @@
+
+
+
+ <application><indexterm class="singular">
+ <primary>OmegaT op het web</primary>
+ </indexterm>OmegaT</application> op het web
+
+
+ <application>OmegaT</application>-sites en <application>OmegaT</application> SourceForge project<indexterm class="singular">
+ <primary>OmegaT op het web</primary> <secondary>SourceForge Project</secondary>
+ </indexterm>
+
+ DeOmegaT-website bevat koppelingen naar verschillende bronnen voor OmegaT. Ondersteuning voor gebruikers wordt gegeven op vrijwillige basis op de OmegaT Yahoo gebruikersgroep. De FAQ is een goed beginpunt om antwoorden te vinden op vragen die u misschien hebt. Bekijk de downloadpagina op www.omegat.org voor de laatste versie van OmegaT. U kunt ook foutenrapporten en verzoeken voor verbeteringen indienen.
+
+
+
+ Foutenrapporten<indexterm class="singular">
+ <primary>OmegaT op het web</primary> <secondary>Fouten rapporteren</secondary>
+ </indexterm>
+
+ Onthoud dat elk goed foutenrapport precies drie dingen nodig heeft:
+
+
+
+ Stappen om het te reproduceren
+
+
+
+ Wat u verwachtte te zien
+
+
+
+ Wat u in plaats daarvan zag
+
+
+
+ Meer in het artikel Painless Bug Tracking van Joel Spolsky
+
+ U zou kopieën van bestanden, delen uit het logbestand, schermafdrukken of iets waarvan u denkt dat dat de ontwikkelaars zou kunnen helpen bij het oplossen van uw probleem, moeten toevoegen. Merk op dat foutenrapporten en verzoeken voor verbeteringen publiekelijk te zien zijn, dus u zou daar geen vertrouwelijk bestanden aan moeten toevoegen. Als u bij wilt houden wat er gebeurd met het rapport moet u zich registreren als gebruiker van SourceForge, inloggen en een foutenrapport moeten indienen als u ingelogd bent, of eenvoudigweg op Monitor klikken bovenin het rapport.
+
+
+
+ Deelnemen aan het <application>OmegaT</application> project<indexterm class="singular">
+ <primary>OmegaT op het web</primary> <secondary>Deelnemen aan OmegaT</secondary>
+ </indexterm>
+
+ Deelnemen aan OmegaT:
+
+ Wordt eerst lid van de gebruikersgroep (via het web of door een e-mail te sturen naar OmegaT-subscribe@yahoogroups.com). Betrokken raken bij de ontwikkeling van OmegaT kunt u door deel te nemen aan de de ontwikkelingsgroep, via het web of door een e-mail te sturen aan omegat-development-request@lists.sourceforge.net met het onderwerp "subscribe".
+
+ Voor het vertalen van OmegaT's gebruikersinterface, gebruikershandleiding of andere gerelateerde documenten:
+
+ Lees eerst de gids Localizing and Customizing OmegaT en wordt dan lid van de OmegaT vertalersgroep, via het web of door een e-mail te sturen naar omegat-development-request@lists.sourceforge.net met als onderwerp "subscribe".
+
+
+ OmegaT op het webOntwikkeling, Vertalen
+
+
+ Financieel ondersteunen van het OmegaT-project
+ OmegaT op het webFinanciële ondersteuning
+
+
+ Als u de voortgaande ontwikkeling van OmegaT wilt helpen ondersteunen, zou het zeer op prijs worden gesteld - klik op deze koppeling om naar de OmegaT PayPalrekening te gaan.
+
+
+ OmegaT op het webDoneren aan OmegaT
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/Dictionaries.xml b/OmegaT/doc_src/nl/Dictionaries.xml
new file mode 100644
index 0000000..14154b2
--- /dev/null
+++ b/OmegaT/doc_src/nl/Dictionaries.xml
@@ -0,0 +1,109 @@
+
+
+
+ <indexterm class="singular">
+ <primary>Woordenboeken</primary>
+ </indexterm>Woordenboeken
+
+
+
+
+ Hoe woordenboeken te downloaden en te installeren<indexterm class="singular">
+ <primary>Woordenboeken</primary> <secondary>Downloaden en installeren</secondary>
+ </indexterm>
+
+ Woordenboeken in OmegaT zijn gebaseerd op het StarDict Platform. Doe het volgende om de benodigde bestanden te installeren:
+
+
+
+ Zoek naar de gewenste taalcombinatie -bijvoorbeeld op het
+ FreeDictwoordenboeken
+ StartDict Platform hierboven of op FreeDict
+ Stardictwoordenboeken
+
+
+
+
+
+
+ Download het bestand - het zou een tarball-archief (extensie tar.bz of tar.bz2) moeten zijn.
+
+
+
+
+
+ Gebruik untar (of iets soortgelijks, bijvoorbeeld winrar in Windows) om de inhoud uit te pakken naar de projectmap "Dictionary". Er zouden drie bestanden moeten zijn, met de extensies dz, idx en ifo.
+
+
+
+ Merk op dat u, aanvullend aan de "bron-doel" woordenboeken, via de mogelijkheid van Dictionary, toegang kunt krijgen tot informatie zoals:
+
+
+
+
+ Websterwoordenboeken
+ Webster's Revised Unabridged Dictionary (1913)
+
+
+
+
+
+
+ Longmanwoordenboeken
+ Longman Dictionary of Contemporary English
+
+
+
+
+
+
+ Britannicawoordenboeken
+ The Britannica Concise Encyclopedia
+
+
+
+
+
+ etc...
+
+
+
+ Sommige woordenboeken verplichten tot niets - dat is zijn "Vrij te gebruiken", en sommige, zoals de selectie hierboven, bevinden zich onder de GPLlicentie. Het volgende voorbeeld toont Merriam Webster 10th dictionary "in actie":
+
+
+ <indexterm class="singular">
+ <primary>woordenboek</primary> <secondary>Merriam Webster - afbeelding</secondary> <seealso>woordenboeken</seealso>
+ </indexterm>Merriam Webster woordenboek - gebruiken
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ <indexterm class="singular">
+ <primary>Woordenboeken</primary> <secondary>problemen met</secondary>
+ </indexterm>Problemen met woordenboeken
+
+
+
+ Controleer of uw bestanden van het woordenboek in de juiste map (of in één van de submappen daarvan) staan. Controleer in
+ SneltoetsenCtrl+E - Projecteigenschappen
+ CtrlEProjecteigenschappen.
+
+
+
+
+
+ Bevat de map drie bestanden met dezelfde naam, met extensies? Indien er slechts één bestand aanwezig is, controleer dan de extensie er van. Als het tar.bz is, dan bent u vergeten het uit te pakken (untar).
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/EditingBehavior.xml b/OmegaT/doc_src/nl/EditingBehavior.xml
new file mode 100644
index 0000000..6e0f2dc
--- /dev/null
+++ b/OmegaT/doc_src/nl/EditingBehavior.xml
@@ -0,0 +1,87 @@
+
+
+
+ Bewerken (gedrag)<indexterm class="singular">
+ <primary>menu Opties</primary> <secondary>Bewerken (gedrag)...</secondary>
+ </indexterm>
+
+ Het dialoogvenster in OptiesBewerken (gedrag)... laat de gebruiker bepalen hoe het huidige segment wordt geïnitialiseerd en afgehandeld.
+
+
+ Bewerken (gedrag) opties
+
+
+
+
+
+
+
+
+
+ Automatisch invoegen van overeenkomst<indexterm class="singular">
+ <primary>Automatisch invoegen van overeenkomst</primary>
+ </indexterm>
+
+ U vertaalt uw bestanden door van segment naar segment te gaan, waarbij elk segment op zijn beurt wordt bewerkt. Bij het verplaatsen tussen segmenten kunt u bepalen of het bewerkingsveld moet worden gevuld met een bestaande vertaling uit het venster Overeenkomsten of met de brontekst. In OptiesBewerken (gedrag)... biedt OmegaT u de volgende alternatieven:
+
+
+
+ De brontekst
+
+
+ U kunt de brontekst automatisch ingevoegd hebben in het bewerkingsveld. Dit is handig als teksten veel handelsnamen en andere woorden met hoofdletters bevat die intact gelaten moeten worden.
+
+
+
+
+ Segment leeg laten
+
+
+ OmegaT laat het bewerkingsveld leeg. Deze optie stelt u in staat om de vertaling in te voeren zonder de brontekst te hoeven verwijderen, hetgeen u een aantal toetsaanslagen scheelt (Ctrl+A en Del).
+
+
+
+
+ Beste overeenkomst invoegen
+
+
+ OmegaT voegt de vertaling van de tekenreeks in die het meeste lijkt op de huidige bron, indien die boven de drempel van het percentage van overeenkomst komt dat in het dialoogvenster is ingesteld. Het voorvoegsel (is standaard leeg) kan worden gebruikt om vertalingen te taggen, wat wordt gedaan via fuzzy overeenkomsten. Indien u een voorvoegsel toevoegt (bijvoorbeeld [fuzzy]), kunt u deze vertalingen later traceren om te zien of zij juist zijn.
+
+
+
+
+
+
+ Vertaling mag gelijk zijn aan brontekst<indexterm class="singular">
+ <primary>Vertaling gelijk aan brontekst</primary>
+ </indexterm>
+
+ Te vertalen documenten kunnen handelsnamen, namen of andere woorden met hoofdletters bevatten die hetzelfde moeten blijven in vertaalde documenten. Er zijn twee strategieën voor segmenten die slechts zulke onveranderlijke tekst bevatten.
+
+ U zou kunnen besluiten om zulke segmenten niet te vertalen. OmegaT zal deze segmenten dan aanmerken als niet-vertaald. Dit is de standaard. Het alternatief is om een vertaling in te voeren die identiek is aan de brontekst. OmegaT is in staat om te herkennen dat u dit gedaan hebt. Ga naar OptiesBewerken (gedrag)... en selecteer het vak Vertaling mag gelijk zijn aan brontekst, om dit mogelijk te maken.
+
+
+
+ Segment naar tekstbestanden exporteren<indexterm class="singular">
+ <primary>Het huidige segment exporteren</primary>
+ </indexterm>
+
+ De functie Tekst exporteren exporteert gegevens vanuit het huidige OmegaTproject naar platte tekst-bestanden. De gegevens worden geëxporteerd als het segment wordt geopend. De bestanden verschijnen in de submap /script in de map met gebruikersbestanden van OmegaT, en bevatten:
+
+
+
+ De inhoud van de brontekst van het segment (source.txt).
+
+
+
+ De inhoud van de brontekst van het segment (target.txt).
+
+
+
+ De tekst die door de gebruiker werd geaccentueerd, als Ctrl-Shift-C werd ingedrukt of als Bewerken > Selectie exporteren is geselecteerd (selection.txt).
+
+
+
+ De inhoud van de bestanden wordt overschreven als een nieuw segment wordt geopend (source.txt en target.txt) of als een nieuwe selectie wordt geëxporteerd (selection.txt). De bestanden zijn niet-opgemaakte platte tekst-bestanden. Het gehele proces kan worden gestuurd en beheerd via op Tck/Tcl-gebaseerde scripts. Bekijk De functie Tekst exporteren in OmegaT gebruiken voor specificaties, voorbeelden en suggesties.
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/FileFilters.xml b/OmegaT/doc_src/nl/FileFilters.xml
new file mode 100644
index 0000000..493df82
--- /dev/null
+++ b/OmegaT/doc_src/nl/FileFilters.xml
@@ -0,0 +1,287 @@
+
+
+
+ Bestandsfilters
+
+ OmegaT omvat zeer aanpasbare filters die u in staat stellen verschillende aspecten in te stellen. Bestandsfilters zijn gedeelten van code die in staat zijn om:
+
+
+
+ Het document in enkele specifieke bestandsformaten te lezen. Bijvoorbeeld platte tekst-bestanden.
+
+
+
+
+
+ De te vertalen inhoud uit het bestand te halen.
+
+
+
+
+
+ Automatische wijzigingen in de vertaalde bestandsnamen van de documenten te maken door de te vertalen inhoud te vervangen door de vertaling.
+
+
+
+ De meeste gebruikers zullen tevreden zijn met de standaard ingestelde opties. Als u dat niet bent opent u het hoofd dialoogvenster door in het hoofdmenu Opties → Bestandsfilters... te selecteren. U kunt ook project-specifieke bestandsfilters inschakelen, die alleen zullen worden gebruikt voor het huidige project, door de optie Bestandsfilters... in Project → Eigenschappen te selecteren.
+
+ Waarschuwing! Als u de segmentatie-opties wijzigt als een project geopend is moet u het project herladen vóórdat de wijzigingen effect hebben.
+
+
+ dialoogvenster Bestandsfilters<indexterm class="singular">
+ <secondary>dialoogvenster</secondary> <primary>Bestandsfilters</primary>
+ </indexterm>
+
+ Dit dialoogvenster toont de beschikbare bestandsfilters. Als u OmegaT niet wilt gebruiken om bestanden van een bepaald type te vertalen, kunt u het betreffende filter uitschakelen door het keuzevak naast de naam niet te selecteren. OmegaT zal dan de betreffende bestanden weglaten bij het laden van projecten en zal ze ongewijzigd kopiëren bij het maken van de doeldocumenten. Als u het filter opnieuw wilt gebruiken, selecteer dan het keuzevak. Klik op Standaardinstellingen om de bestandsfilters terug te zetten naar de standaard instellingen. Selecteer het filter uit de lijst en klik op Bewerken om aan te geven welke bestanden in welke coderingen het filter moet verwerken.
+
+
+
+ Filteropties<indexterm class="singular">
+ <primary>Bestandsfilters</primary> <secondary>Opties</secondary>
+ </indexterm>
+
+ Vijf filters (Tekstbestanden, XHTML-bestanden, HTML- en XHTML-bestanden, OpenDocument/OpenOffice.org-bestanden en Microsoft Open XML-bestanden) hebben één of meer specifieke opties. Selecteer, om de opties aan te passen, het filter uit de lijst en klik op Opties. De beschikbare opties zijn:
+
+ Tekstbestanden
+
+
+
+ Alineasegmentatie op regeleinden, lege regels of nooit:
+
+ als regels voor zinsegmentatie actief zijn, zal de tekst verder worden gesegmenteerd overeenkomstig de hier geselecteerde optie.
+
+
+
+ PO-bestanden
+
+
+
+ Blanco vertalingen in het doelbestand toestaan:
+
+ Indien ingeschakeld zal, wanneer een PO-segment (wat een gehele alinea kan zijn) niet is vertaald, de vertaling leeg zijn in het doelbestand. Technisch gesproken zal het segment msgstr in het PO-doelbestand, indien gemaakt, leeg zijn. Het staat standaard aan, omdat dit het standaard gedrag is voor PO-bestanden. Indien de optie is uitgeschakeld, zal de brontekst worden gekopieerd naar het doelsegment.
+
+
+
+ XHTML-bestanden
+
+
+
+ Vertaal de volgende attributen- de geselecteerde attributen zullen als segmenten in het venster Bewerken verschijnen.
+
+
+
+
+
+ Start een nieuwe alinea bij: De <br> HTML-tag zal een alinea voor segmentatiedoeleinden maken.
+
+
+
+
+
+ Tekst die overeenkomt met reguliere uitdrukking overslaan: De tekst die overeenkomt met de reguliere uitdrukking zal worden overgeslagen.
+
+
+
+
+
+ Vertaal het attribuut 'content' van metatags niet: ... : de 'sleutel-waarden'-paren van het attribuut, gescheiden door komma's, zullen niet vertaald worden
+
+
+
+ Microsoft Office Open XML-bestanden
+
+ U kunt selecteren welke elementen vertaald moeten worden. Zij zullen als afzonderlijke segmenten in de vertaling verschijnen.
+
+
+
+ Word: Niet-zichtbare tekst met instructies, Notities, Voetnoten, Eindnoten, Voetteksten
+
+
+
+
+
+ Excel: Notities, Werkbladnamen
+
+
+
+
+
+ Powerpoint: Dianotities, Diamodellen, Dia-lay-outs
+
+
+
+
+
+ Globaal: Grafieken, Diagrammen, Tekeningen, WordArt
+
+
+
+
+
+ Andere opties:
+
+
+
+ Hoeveelheid tags: Indien geselecteerd zullen tags, zonder vertaalbare tekst er tussen, worden samengevoegd tot enkele tags.
+
+
+
+ Spaties voor alle tags behouden: Indien geselecteerd zal "witruimte" (d.i. spaties en nieuwe regels) worden behouden, zelfs als dat niet technisch is ingesteld in het document.
+
+
+
+
+
+ HTML- en XHTML-bestanden
+
+
+
+ Codering-declaratie aan HTML- en XHTML-bestanden toevoegen of herschrijven: Altijd (standaard), Alleen als (X)HTML-bestand een kop heeft, Alleen als (X)HTML-bestand een codering-declaratie heeft, Nooit
+
+
+
+
+
+ Vertaal de volgende attributen: De geselecteerde attributen zullen als segmenten in het venster Bewerken verschijnen.
+
+
+
+
+
+ Start een nieuwe alinea bij: De <br> HTML-tag zal een alinea voor segmentatiedoeleinden maken.
+
+
+
+
+
+ Tekst die overeenkomt met reguliere uitdrukking overslaan: De tekst die overeenkomt met de reguliere uitdrukking zal worden overgeslagen.
+
+
+
+
+
+ Vertaal het attribuut 'content' van metatags niet ...: de 'sleutel-waarden'-paren van het attribuut, gescheiden door komma's, zullen niet vertaald worden
+
+
+
+ Tekstbestanden
+
+
+
+ Alineasegmentatie op regeleinden, lege regels of nooit:
+
+ als regels voor zinsegmentatie actief zijn, zal de tekst verder worden gesegmenteerd overeenkomstig de hier geselecteerde optie.
+
+
+
+ OpenDocument/OpenOffice.org bestanden
+
+
+
+ U kunt selecteren welke van de volgende elementen vertaald moeten worden.
+
+ Indexitems, bladwijzers, verwijzingen naar bladwijzers, notities, opmerkingen, notities in presentaties, koppelingen (URL), werkbladnamen
+
+
+
+
+
+ dialoogvenster Filter bewerken<indexterm class="singular">
+ <primary>Bestandsfilters</primary> <secondary>Bewerken</secondary>
+ </indexterm>
+
+ Het dialoogvenster stelt u in staat om de patronen van de bronbestandsnaam te bewerken van de bestanden die het filter zal verwerken, de bestandsnamen van vertaalde bestanden aan te passen en te selecteren welke coderingen het zal gebruiken bij het laden van het bestand en zijn vertaalde tegenhanger. Pas de velden direct aan of klik op Bewerken om een patroon voor het bestandsfilter aan te passen. Klik op Toevoegen om een nieuw patroon voor een bestandsfilter toe te voegen. Hetzelfde dialoogvenster wordt gebruikt om een patroon toe te voegen of een bepaald patroon te bewerken. Het dialoogvenster is handig omdat het een speciale bewerker voor het patroon van de doelbestandsnaam heeft waarmee u de namen van de te maken bestanden aan kunt passen.
+
+
+ <indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>Bestandstype, patroon bestandsnaam</secondary>
+ </indexterm>Type bronbestand, patroon voor bestandsnaam<indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>Bestandstype bron, bestandsnaam</secondary>
+ </indexterm>
+
+ Als OmegaT een bestand tegenkomt in zijn bronmap, probeert dat het filter te selecteren gebaseerd op de extensie van het bestand. Meer precies: OmegaT probeert of van elk filter het patroon van de bestandsnaam overeenkomt met de bestandsnaam. Het *.xhtml-patroon zal bijvoorbeeld overeenkomen met elk bestand met de extensie .xhtml. Als het juiste filter is gevonden wordt dat voor verdere verwerking toegepast op het betreffende bestand. Standaard zal bijvoorbeeld het XHTML-filter worden gebruikt bij het verwerken van bestanden met de extensie .xhtml. U kunt bestandsnaam-patronen toevoegen of wijzigen voor bestanden die door elk filter worden afgehandeld. Patronen voor bronbestandsnamen gebruiken jokertekens die overeenkomen met die in Zoeken. Het teken '*' komt overeen met nul of meer tekens. Het teken '?' komt overeen met exact één teken. Alle andere tekens vertegenwoordigen zichzelf. Als u bijvoorbeeld wilt dat het tekstfilter readme-bestanden (readme, read.me en readme.txt) afhandelt, zou u het patroon read* moeten gebruiken.
+
+
+
+ Coderen van bron- en doelbestanden
+
+
+ Bronbestandencoderen
+
+
+
+ Doelbestandencoderen
+
+
+
+ Bestandsfilterscoderen bron, doel
+
+
+ Slechts een beperkt aantal bestandsformaten specificeren een voorgeschreven codering. Bestandsformaten die hun codering niet specificeren zullen de codering gebruiken die u instelt voor de extensie die overeenkomt met hun naam. Standaard zullen bijvoorbeeld .txt-bestanden worden geladen met behulp van de standaard codering van uw besturingssysteem. U kunt de broncodering voor elk verschillend bronbestandsnaam-patroon wijzigen. Zulke bestanden kunnen ook in elke codering worden weggeschreven. Als standaard heeft het vertaalde bestand dezelfde codering als de codering van het bronbestand. Velden voor bron- en doelcodering gebruiken combinatievakken waarin alle ondersteunde coderingen zijn opgenomen. <auto> laat de keuze van de codering aan OmegaT over. Zo werkt het:
+
+
+
+ OmegaT identificeert de codering van het bronbestand door de declaratie van de codering te gebruiken, indien aanwezig (HTML-bestanden, op XML gebaseerde bestanden).
+
+
+
+
+
+ OmegaT is geïnstrueerd om een voorgeschreven codering te gebruiken voor bepaalde bestandsformaten ( Java-properties etc)
+
+
+
+
+
+ OmegaT gebruikt de standaard codering van het besturingssysteem voor tekstbestanden.
+
+
+
+
+
+ Doelbestandsnaam<indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>bestandsnamen</secondary>
+ </indexterm>
+
+ Soms wilt u misschien de bestanden die u vertaalde automatisch hernoemen, bijvoorbeeld door een taalcode achter de bestandsnaam te zetten. Doelbestandsnaam-patronen gebruiken een speciale syntaxis, dus als u dit veld zou willen bewerken, moet u op Bewerken... klikken en het dialoogvenster
+ dialoogvensterBestandsfilters
+ Patroon bewerken gebruiken. Klik op Standaardinstellingen als u terug wilt keren naar de standaard configuratie van het filter. U kunt de naam ook direct aanpassen in het veld voor het patroon van het doelbestand of het dialoogvenster Bestandsfilters. Het dialoogvenster Patroon bewerken biedt de volgende opties:
+
+
+
+ Standaard is ${filename} - volledige bestandsnaam van het bronbestand met extensie: in dit geval is de naam van het vertaalde bestand hetzelfde als dat van het bronbestand.
+
+
+
+
+
+ ${nameOnly} - laat u alleen de naam van het bronbestand invoegen zonder de extensie.
+
+
+
+
+
+ ${targetLocale} - locale-code voor doel (in de vorm "xx_YY").
+
+
+
+
+
+ ${targetLanguage} - de doeltaal en landcode samen (in de vorm "XX-YY").
+
+
+
+
+
+ ${targetLanguageCode} - alleen de doeltaal ("XX").
+
+
+
+
+
+ ${targetCoutryCode} - alleen de doel-landcode ("YY").
+
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/FilesAndDirectories.xml b/OmegaT/doc_src/nl/FilesAndDirectories.xml
new file mode 100644
index 0000000..db8a4cc
--- /dev/null
+++ b/OmegaT/doc_src/nl/FilesAndDirectories.xml
@@ -0,0 +1,343 @@
+
+
+
+ <application>OmegaT</application> bestanden en mappen
+
+ OmegaT werkt met drie bestandstypen.
+
+
+
+ Projectbestanden vertaling: Deze vormen een vertaalproject. Verlies van deze bestanden kan de integriteit van het project beïnvloeden alsmede de mogelijkheid van het voltooien van uw werk. Projectbestanden zijn de meest belangrijke bestanden in OmegaT. Het zijn de bestanden waarmee u dagelijks hebt te maken bij het vertalen.
+
+
+
+
+
+ Bestanden voor gebruikersinstellingen: Deze worden gemaakt als het gedrag van OmegaT wordt gewijzigd met voorkeursinstellingen voor de gebruiker. Verlies van deze bestanden zorgt er meestal voor dat OmegaT terugkeert naar de "fabrieksinstellingen". Dit kan soms enige problemen geven als u midden in een vertaling bent.
+
+
+
+
+
+ Toepassingsbestanden: Zij zijn opgenomen in het pakket dat u hebt gedownload. De meeste er van zijn nodig om OmegaT juist te laten functioneren. Als door enige oorzaak deze bestanden verloren gaan of beschadigd worden, download en herinstalleer OmegaT dan om ze allemaal terug te zetten.
+
+
+
+
+ Projectbestanden vertaling
+
+ Een OmegaT vertaalproject bestaat uit een aantal bestanden en mappen.
+
+
+ <indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>locatie</secondary>
+ </indexterm>Locatie van projectbestanden van de vertaling
+
+ Als u een vertaalproject maakt, maakt OmegaT automatisch een lijst van mappen aan die later zullen dienen als opslagplaatsen voor de bestanden, alsook een aantal bestanden die zullen worden gebruikt om enkele voorkeuren voor het project in te stellen en om het vertaalgeheugen van het project op te slaan. Standaard worden de mappen van een vertaalproject gegroepeerd onder de hoofdmap van het project. Alternatieve locaties voor sommige mappen kunnen worden gekozen bij het maken van het project of tijdens de vertaling. Het is daarom mogelijk om bestaande mappen te kiezen of mappen te maken op locaties die passen bij uw eigen werkwijze en projectbeheer. Open Project > Eigenschappen... of met Ctrl+E en maak de nodige aanpassingen om de locaties van de mappen te wijzigen nadat een project is gemaakt.
+
+
+
+ <indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>lijst</secondary>
+ </indexterm>Lijst van bestanden van het vertaalproject
+
+ In een met OmegaT geopend dialoogvenster ziet een vertaalproject er uit als een bestand met een pictogram van OmegaT er aan verbonden. In een bestandsbeheerder ziet een vertaalproject er echter uit als elke andere map en gedraagt zich ook zo.
+
+
+ OmegaT projecten en mappen
+
+
+
+
+
+
+
+
+ Dubbelklikken op het item met het pictogram van OmegaT is voldoende om het project te openen. Een vertaalproject Voorbeeld_Project, gemaakt met de standaard instellingen, zal worden gemaakt als een nieuwe submap met de volgende structuur:
+
+
+ OmegaT project
+
+
+
+
+
+
+
+
+ Alle submappen zullen bij aanvang leeg zijn.
+
+
+
+ Omegat<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>Submap omegat</secondary>
+ </indexterm>
+
+ De submap omegat bevat ten minste één en mogelijk meerdere andere bestanden. Het meest belangrijke bestand is het bestand van het vertaalgeheugen, project_save.tmx (...). Het bestand project_save.tmx is het werkende vertaalgeheugen voor het project. Met de geactiveerde functie Automatisch opslaan wordt het automatisch bijgewerkt als u stopt. Het is het vertaalgeheugen dat wordt gebruikt om de vertaalde bestanden te maken. Een aantal bestanden met namen in de vorm project_save.tmx.<datum en tijd>.bak (...) zullen later aan deze submap worden toegevoegd. Zij dienen als back-up voor het vertaalgeheugen van het project. Een nieuw exemplaar wordt, iedere keer als u een project opnieuw opent, gemaakt om de inhoud van het project weer te geven, voordat de huidige sessie die heeft veranderd.
+
+ Het projectbestand
+ Projectbestandenbestand Statistieken
+ stats.txt (...) bevat de statistieken over het huidige project en kan worden geopend in een werkbladtoepassing om segment- en informatie over de telling van woorden weer te geven. Het bestand bevat het aantal segmenten voor elk te vertalen bestand - Totaal en Resterend - het aantal unieke segmenten per bestand, het aantal unieke woorden en het aantal unieke tekens met / zonder spaties per bestand.
+
+ Merk op dat Unieke segmenten per bestand het aantal unieke segmenten in een opgegeven bestand vermeld die niet ergens anders in het project voorkomen. De unieke woorden of tekens per bestand hebben een soortgelijke definitie. Merk op dat in een project met meerdere bestanden de som van de unieke segmenten per bestand niet noodzakelijkerwijze gelijk zal zijn aan het totale aantal unieke segmenten in het project.
+
+ De bestanden
+ Projectbestandenignored_words en learned_words
+ ignored_words.txt en learned_words.txt worden gebruikt door de spellingscontrole. Onthoud dat zij specifiek zijn voor een bepaald project, dus als u al een verzameling woorden hebt waarvan u wilt dat de spellingscontrole die negeert / accepteert, moet u de corresponderende twee bestanden naar de submap omegat van uw huidige project kopiëren.
+
+
+
+ Bronbestanden<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>submap Source</secondary>
+ </indexterm>
+
+ De submap source is de locatie voor projectbestanden die moeten worden vertaald. U kunt een nieuwe submap maken en later de bestanden er aan toevoegen. Houdt er wel rekening mee dat de structuur van de submap source elke vorm mag hebben die u wilt. Indien de bestanden die vertaald moeten worden deel uitmaken van een boomstructuur (zoals op een website), hoeft u slechts de bovenste submap op te geven en zal OmegaT de gehele inhoud behouden, waarbij de boomstructuur intact blijft.
+
+
+
+ Doelbestanden<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>submap Target</secondary>
+ </indexterm>
+
+ Als CtrlDProjectVertaalde documenten maken wordt geselecteerd, worden alle bestanden in de map source, of zij zijn vertaald of niet, gereproduceerd in de doelmap met dezelfde hiërarchie van mappen om de huidige status van de vertaling weer te geven. Met andere woorden: OmegaT voegt de informatie voor de vertaling, die is opgeslagen in /omegat/project_save,tmx, samen met de brondocumenten om de inhoud voor het doel te produceren.
+
+
+
+ omegat.project<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>bestand omegat.project</secondary>
+ </indexterm>
+
+ OmegaT maakt dit bestand automatisch als het project wordt gemaakt en het bevat de parameters voor het project. De parameters die zijn opgenomen in dit bestand kunnen worden aangepast in het venster Projecteigenschappen.
+
+ project_naam-omegat.tmx (...)
+
+ project_naam-level1.tmx
+
+ project_naam-level2.tmx
+
+
+ Projectbestandenbestanden project_name....tmx
+
+
+ Deze bestanden bevatten de bron- en doelsegmenten die overeenkomen met de inhoud van de map source op het moment dat ze gemaakt werden (gewoonlijk is dat als de vertaalde documenten worden gemaakt). Zij vormen de geëxporteerde vertaalgeheugens die u kunt gebruiken in toekomstige projecten.
+
+
+
+
+ Gebruikersbestanden<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>gebruikersbestanden</secondary>
+ </indexterm>
+
+
+ Locatie van gebruikersbestanden<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>gebruikersbestanden</secondary> <tertiary>locatie</tertiary>
+ </indexterm>
+
+ Gebruikersbestanden worden opgeslagen op een afzonderlijke locatie waar door elke versie van OmegaT toegang toe kan worden verkregen. De locatie is afhankelijk van het platform dat u gebruikt:
+
+
+
+
+
+
+
+ Windows 2000 en XP
+
+ Documents and Settings\<gebruikersnaam>\Application Data\OmegaT
+
+
+
+ Windows Vista en 7
+
+ Users\<gebruikersnaam>\AppData\Roaming\OmegaT
+
+
+
+ andere Windows
+
+ <Iets>\OmegaT (<Iets> komt overeen met de locatie van de map "home" zoals die wordt vastgesteld door Java.)
+
+
+
+ Linux/Solaris/FreeBSD
+
+ <User Home>/.omegat (.omegat is een map, de punt die voor de naam staat maakt die onzichtbaar tenzij u typt ls -a of een overeenkomende opdracht.)
+
+
+
+ MAC OSX
+
+ <gebruiker Home>/Library/Preferences/OmegaT
+
+
+
+ Andere
+
+ <gebruiker Home>
+
+
+
+
+
+
+
+ Lijst van gebruikersbestanden<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>lijst gebruikersbestanden</secondary>
+ </indexterm>
+
+
+
+
+
+
+
+ logs/OmegaT.log
+
+ Dit bestand slaat foutberichten van Java op terwijl OmegaT wordt uitgevoerd. Als OmegaT zich niet goed lijkt te gedragen is het belangrijk om dit bestand of het relevante gedeelte daarvan op te nemen in een foutenrapport.
+
+
+
+ omegat.prefs
+
+ Een xml-bestand met alle toegankelijke optie-instellingen voor de GUI.
+
+
+
+ uiLayout.xml
+
+ Een xml-bestand met gegevens voor vensterposities.
+
+
+
+ filters.xml
+
+ Een xml-bestand met alle gegevens die zijn ingesteld door de voorkeuren voor het filter.
+
+
+
+ segmentation.conf
+
+ Een xml-bestand dat segmentatieregels bevat.
+
+
+
+
+
+
+
+
+ <indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>toepassingsmappen</secondary>
+ </indexterm>Toepassingsbestanden<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>toepassingsbestanden</secondary>
+ </indexterm>
+
+ OmegaT wordt uitgegeven als een pakket dat u kunt downloaden vanaf SourceForge. In dit hoofdstuk gaan we uit van het platform onafhankelijke pakket dat de toepassing in een standaard Java-vorm bevat. Andere pakketten bevatten een Linux .tar-pakket, een Windows-installatieprogramma - met of zonder een Java Runtime Environment -, een MacOSX-installatieprogramma en een broncodepakket voor ontwikkelaars. Het platform onafhankelijke pakket kan worden gebruikt op elk platform met een werkende Java 1.5 runtime omgeving, inclusief de platforms waarvoor een specifiek pakket bestaat. Het platform onafhankelijke pakket bestaat uit een gecomprimeerd bestand (zip- of tar-archief) dat u in de map van uw keuze moet uitpakken om te installeren. Het bestand kan gewoonlijk worden uitgepakt door op het gedownloade pakket te dubbelklikken. Als het archief is uitgepakt zal een map zijn gemaakt met de volgende inhoud:
+
+
+
+
+
+
+
+ Bestand/ submap
+
+ Inhoud
+
+
+
+ /docs/
+
+ Alle bestanden van de gebruikershandleiding staan in deze map. U kunt ze in een internetbrowser openen om toegang te krijgen tot externe koppelingen.
+
+
+
+ /images/
+
+ Pictogrammen en logo-afbeeldingen zijn hierin opgenomen.
+
+
+
+ /lib/
+
+ Bevat Java-bestanden die nodig zijn om OmegaT uit te voeren.
+
+
+
+ join.html
+
+ Dit is een normaal html-bestand dat, eenmaal geopend in uw internetbrowser, u naar de OmegaT gebruikersgroep brengt die wordt gehost op Yahoo Groups. Abonneren is niet noodzakelijk maar geeft u toegang tot aanvullende services, zoals bestanden en onregelmatige polls, daarnaast kunt u deelnemen aan discussies die zijn gerelateerd aan OmegaT. De groepsarchieven zijn publiek en het raadplegen daarvan vereist geen abonnement op de groep.
+
+
+
+ changes.txt
+
+ Een relatief gedetailleerde lijst van aanpassingen tussen deze versie en de voorafgaande versies.
+
+
+
+ license.txt
+
+ De GNU GENERAL PUBLIC LICENSE. Deze licentie staat u toe om bepaalde dingen met OmegaT te doen, inclusief het aanpassen en distribueren ervan. Indien u bent geïnteresseerd in het aanpassen of distribueren van OmegaT, lees dit document dan zorgvuldig door en zorg er voor dat u bekend bent met alle implicaties vóórdat u iets anders doet. Als u twijfelt, aarzel dan niet om de projectleden direct te benaderen ofwel door hen een mail te sturen vanaf de pagina van SourceForge of door een publieke mail te sturen aan de gebruikersgroep.
+
+
+
+ doc-license.txt
+
+ De GNU GENERAL PUBLIC LICENSE. Deze licentie behandelt de documentatie. Zie boven.
+
+
+
+ readme.txt
+
+ Dit bestand is heel belangrijk en u zou het gelezen moeten hebben voordat u met OmegaT begon. Het bevat algemene informatie over OmegaT, waar meer informatie te vinden is, hoe mee te doen etc. Het is vertaald in een aantal talen.
+
+
+
+ Omegat
+
+ Een tekstbestand dat twee regels bevat:
+
+
+
+
+
+ #!/bin/bash java
+
+
+
+
+
+ java -jar
+ OmegaT.jar $*
+
+
+
+
+
+ Linux- en OSX-gebruikers zouden dit handig kunnen vinden. Maak het uitvoerbaar (chmod +x OmegaT) vanaf de opdrachtregel nadat u zich er van overtuigd hebt dat u in de map /OmegaT_2.5/ bent. U kunt dan OmegaT starten door dit bestand vanaf de opdrachtregel uit te voeren.
+
+
+
+ OmegaT.bat
+
+ Een batch-bestand gebruikt om OmegaT te starten vanaf de opdrachtregel van Windows. Het bevat slechts de volgende regel:
+
+
+
+
+
+ java -jar OmegaT.jar
+ %*
+
+
+
+ OmegaT.jar
+
+ De hoofdtoepassing OmegaT. U moet dit bestand aanroepen vanaf de opdrachtregel of starten vanuit uw bestandsbeheerder, gewoonlijk door er op te dubbelklikken, om OmegaT te starten.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/FilesToTranslate.xml b/OmegaT/doc_src/nl/FilesToTranslate.xml
new file mode 100644
index 0000000..767aa90
--- /dev/null
+++ b/OmegaT/doc_src/nl/FilesToTranslate.xml
@@ -0,0 +1,282 @@
+
+
+
+ Te vertalen bestanden
+
+
+ Bestandsformaten<indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>bestandsformaten</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>bestandsformaten</secondary>
+ </indexterm>
+
+ U kunt OmegaT gebruiken om bestanden te vertalen in een aantal bestandsformaten. Er zijn twee basale typen bestandsformaten, platte tekst en opgemaakte tekst.
+
+
+ Platte-tekst bestanden<indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>Platte tekst-bestanden</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>Platte tekst-bestanden</secondary>
+ </indexterm>
+
+ Platte tekst-bestanden bevatten alleen maar tekst, zodat hun vertaling zo eenvoudig is als het typen van die vertaling. Er zijn meerdere methoden om de codering van een bestand te specificeren zodat de inhoud niet door elkaar wordt gegooid bij het openen in OmegaT. Zulke bestanden hebben geen informatie over opmaak naast de "witte ruimte" die wordt gebruikt om tekst uit te lijnen, alinea's aan te geven of paginaeinden in te voegen. Zij zijn niet in staat informatie te bevatten / te behouden met betrekking tot de kleur, lettertype etc. van de tekst. Momenteel ondersteunt OmegaT de volgende platte tekst-formaten:
+ Bestandsformatenniet opgemaaktebronbestanden
+
+
+
+
+ ASCII tekst (.txt, etc.)
+
+
+
+
+
+ Gecodeerde tekst (*.UTF8)
+
+
+
+
+
+ Java bronbundels (*.properties)
+
+
+
+
+
+ PO-bestanden (*.po)
+
+
+
+
+
+ INI (sleutel=waarde) bestanden (*.ini)
+
+
+
+
+
+ DTD-bestanden (*.DTD)
+
+
+
+ DocuWiki-bestanden (*.txt)
+
+
+
+
+
+ SubRip titelbestanden (*.srt)
+
+
+
+
+
+ Magento CE Locale CSV-bestanden (*.csv)
+
+
+
+ Andere platte-tekst bestanden kunnen worden behandeld door OmegaT door hun bestandstype te koppelen aan een ondersteund bestandstype (bijvoorbeeld .pod-bestanden zouden kunnen worden gekoppeld aan het ASCII tekstfilter) en ze voor te bewerken met specifieke segmentatieregels.
+
+
+
+ Opgemaakte tekstbestanden<indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>opgemaakte tekstbestanden</secondary> <seealso>getagde tekst</seealso>
+ </indexterm><indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>opgemaakte tekstbestanden</secondary>
+ </indexterm>
+
+ Opgemaakte tekstbestanden bevatten zowel tekst als informatie, zoals lettertype, afmeting, kleur etc. Zij worden normaal gesproken gemaakt met tekst- of HTML-verwerkingsprogramma's. Zulke bestanden zijn ontworpen om hun informatie over de opmaak te behouden. Zulke informatie over de opmaak kan eenvoudig zijn zoals "dit is vet" of zo complex als tabelgegevens met verschillende lettertype-afmetingen, kleuren, posities etc. In de meeste vertalingen wordt het belangrijk geacht dat het vertaalde document er uitziet zoals het origineel. OmegaT stelt u in staat om dit te doen door het markeren van de tekens/woorden die een speciale opmaak hebben met eenvoudig te bewerken tags. Vereenvoudigen van de opmaak van de originele tekst draagt enorm bij aan het verminderen van het aantal tags. Indien mogelijk zou het gelijk maken van gebruikte lettertypen, lettertype-afmetingen, kleuren etc. het vertalen vereenvoudigen en het aantal mogelijke fouten in tags verminderen. Elk bestandstype wordt verschillend behandeld in OmegaT. Specifiek gedrag kan worden ingesteld in de bestandsfilters. Momenteel ondersteunt OmegaT de volgende opgemaakte tekst-formaten:
+ Bestandsformatenopgemaaktebronbestanden
+
+
+
+
+ OpenOffice.org / OpenDocument (*.ods, *.ots, *.odt, *.ott,
+ *.odp, *.otp)
+
+
+
+ Microsoft Office Open XML (*.docx, *.dotx, *.xlsx, *.xltx,
+ *.pptx)
+
+
+
+ (X)HTML (*.html, *.xhtml,*.xht)
+
+
+
+ HTML Help Compiler (*.hhc, *.hhk)
+
+
+
+ DocBook (*.xml)
+
+
+
+ XLIFF (*.xlf, *.xliff, *.sdlxliff) - eentalig, d.i. één taalcombinatie mogelijk voor een bepaald project
+
+
+
+ QuarkXPress CopyFlowGold (*.tag, *.xtg)
+
+
+
+ ResX-bestanden (*.resx)
+
+
+
+ Android-bronbestanden (*.xml)
+
+
+
+ LaTex (*.tex, *.latex)
+
+
+
+ Help- (*.xml) en Manual- (*.hmxp) bestanden
+
+
+
+ Typo3 LocManager (*.xml)
+
+
+
+ WiX Localization (*.wxl)
+
+
+
+ Iceni Infix (*.xml)
+
+
+
+ Flash XML exporteren (*.xml)
+
+
+ Wordfast TXML (*.txml)
+
+
+ Camtasia voor Windows (*.camproj)
+
+
+
+
+ Andere opgemaakte tekst-bestanden kunnen worden afgehandeld door OmegaT door hun bestandstype te koppelen aan een ondersteund bestandstype, er van uitgaande dat de overeenkomende segmentatieregels ze juist zullen segmenteren.
+
+
+
+
+ Andere bestandsformaten<indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>andere bestandsformaten</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>andere bestandsformaten</secondary>
+ </indexterm>
+
+ Andere platte tekst- of opgemaakte tekst-bestandsformaten die mogelijk door OmegaT kunnen worden verwerkt zouden ook kunnen bestaan.
+
+
+ Doelbestandenprogramma's voor bestandsconversie
+ Externe programma's kunnen worden gebruikt om bestanden te converteren naar ondersteunde formaten. De vertaalde bestanden moeten daarna weer terug worden geconverteerd naar het originele formaat. Als u bijvoorbeeld een verouderde versie van Microsoft Word hebt, die niet het ODT-formaat kan afhandelen, is hier een manier voor Word-bestanden met de extensie DOC:
+
+
+
+ importeer het bestand in OpenOffice.org Writer
+
+
+
+
+
+ sla het bestand op in de indeling ODT
+
+
+
+
+
+ vertaal het in het doel-ODT-bestand
+
+
+
+
+
+ laad het doelbestand in OpenOffice.org Writer
+
+
+
+
+
+ sla het bestand op als een DOC-bestand
+
+
+
+ De kwaliteit van het vertaalde bestand zal afhankelijk zijn van de kwaliteit van het heen-en-weer converteren. Voor het uitvoeren van dergelijke conversies: zorg er voor dat alle opties zijn uitgeprobeerd. Controleer de OmegaT homepage voor een bijgewerkte lijst van hulpprogramma's voor vertalingen.
+
+
+
+ Van rechts naar links talen<indexterm class="singular">
+ <primary>Van rechts naar links talen</primary>
+ </indexterm><indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>talen van rechts naar links</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>talen van rechts naar links</secondary>
+ </indexterm>
+
+ Uitvulling van de bron- en doelsegmenten is afhankelijk van de projecttalen. Ze worden standaard links uitgevuld voor talen van Left-To-Right (LTR) en rechts uitgevuld voor talen van Right-To-Left (RTL). U kunt schakelen tussen de verschillende weergavemodi door in te drukken ShiftCtrlO (dit is de letter O en niet de numerieke 0). De schakeling met ShiftCtrlO heeft drie statussen:
+
+
+
+ standaard uitvulling, die wordt gedefinieerd door de taal
+
+
+
+
+
+ links uitvullen
+
+
+
+
+
+ rechts uitvullen
+
+
+
+ Gebruiken van de modus RTL in OmegaT heeft geen enkele invloed op de modus weergeven van de vertaalde documenten die werden gemaakt in OmegaT. De modus weergeven van de vertaalde documenten zal moeten worden aangepast binnen de gewoonlijk gebruikte toepassing (zoals Microsoft Word) om ze weer te geven of te wijzigen (bekijk de relevante handleidingen voor de details). Gebruiken van ShiftCtrlO zorgt er voor dat zowel de tekstinvoer als de weergave in OmegaT worden gewijzigd. Door te klikken op het venster en te schakelen met de weergavemodus kan het afzonderlijk worden gebruikt voor alle drie vensters (Bewerken, Overeenkomsten en Woordenlijst). Het kan ook worden gebruikt in alle aanwezige invoervelden in OmegaT - in het zoekvenster, voor de segmentatieregels etc.
+
+ Opmerking voor Mac OS X-gebruikers: gebruik de sneltoets ShiftCtrlO en niet cmd+Ctrl+O.
+
+
+ LTR- en RTL-tekenreeksen in segmenten mixen<indexterm class="singular">
+ <primary>Van rechts naar links talen</primary> <secondary>mixen van RTL- en LTR-tekenreeksen</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>mixen van RTL- en LTR-tekenreeksen</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>mixen van RTL- en LTR-tekenreeksen</secondary>
+ </indexterm>
+
+ Bij het schrijven van pure RTL-tekst, kan de standaard (LTR) weergave worden gebruikt. In veel gevallen is het echter noodzakelijk om LTR-tekst in RTL-tekst in te bedden. Bijvoorbeeld in OmegaT-tags, productnamen die moeten worden behouden in de LTR-brontaal, tijdelijke plaatsaanduidingen in lokalisatie-bestanden en getallen in tekst. In dit soort gevallen is het noodzakelijk om te schakelen naar de modus RTL, zodat de RTL- (in feite twee richtingen) tekst correct wordt weergegeven. Waarbij dient te worden opgemerkt dat als OmegaT in de modus RTL staat, zowel de bron als het doel worden weergegeven in de modus RTL. Dit betekent dat als de brontaal in LTR is en de doeltaal is RTL, of vice versa, het nodig zou kunnen zijn om heen en weer te schakelen tussen de modi RTL en LTR om de bron te bekijken en eenvoudiger het doel in te voeren in hun respectievelijke modus.
+
+
+
+ <application>OmegaT</application>-tags in RTL-segmenten<indexterm class="singular">
+ <primary>Van rechts naar links talen</primary> <secondary>OmegaT-tags in RTL-talen</secondary>
+ </indexterm>
+
+ Zoals hierboven vermeld zijn OmegaT-tags LTR-tekenreeksen. Bij het vertalen tussen RTL- en LTR-talen kan het nodig zijn dat de vertaler, om de tags juist te lezen uit de bron en om ze dan juist in te voeren in het doel, vele malen moet schakelen tussen de modi LTR en RTL.
+
+ Indien het document het toelaat wordt het de vertaler sterk aangeraden om informatie over de opmaak uit het originele document te verwijderen zodat er zo weinig mogelijk tags als nodig is in de OmegaT-interface verschijnen. Volg de aanwijzingen die worden gegeven in Hints voor tagbeheer. Valideer de tags regelmatig (zie Tag-validatie) en maak met regelmatige tussenpozen vertaalde documenten (zie hieronder en Menu) om het eenvoudiger te maken om problemen te zien die opkomen. Een hint: vertalen van een 'platte tekst'-versie van de tekst en het op een later moment toevoegen van het noodzakelijke opmaakprofiel in de relevante toepassing zou misschien minder problematisch blijken te zijn.
+
+
+
+ Vertaalde RTL-documenten maken<indexterm class="singular">
+ <primary>Van rechts naar links talen</primary> <secondary>RTL-doelbestanden maken</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Van rechts naar links talen</primary> <secondary>doelbestanden</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Van rechts naar links talen</primary> <secondary>RTL-doeltekst maken</secondary>
+ </indexterm>
+
+ Als het vertaalde document wordt gemaakt zal de weergaverichting hetzelfde zijn als die van het originele document. Als het originele document LTR was, moet de weergaverichting van het doeldocument handmatig worden gewijzigd naar RTL in de toepassing waarin het wordt weergegeven. Elke indeling voor de uitvoer heeft specifieke manieren om om te gaan met RTL-weergave, controleer de relevante handleidingen voor de toepassing voor details.
+
+ Het is soms mogelijk om de parameters voor weergave voor het bronbestand te wijzigen zodat dergelijke parameters worden geërfd door de doelbestanden, om te vermijden dat de parameters voor weergave voor de doelbestanden elke keer moeten worden gewijzigd als de bestanden worden geopend. Dergelijke aanpassingen zijn bijvoorbeeld mogelijk in bestanden van OpenOffice.org.
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/Font.xml b/OmegaT/doc_src/nl/Font.xml
new file mode 100644
index 0000000..0389bee
--- /dev/null
+++ b/OmegaT/doc_src/nl/Font.xml
@@ -0,0 +1,61 @@
+
+
+
+ Lettertype-instellingen
+
+
+ Lettertype-instellingen
+
+ Lettertype-instellingen
+
+
+ In dit dialoogvenster kan het lettertype worden gedefinieerd dat door OmegaT in de volgende vensters wordt gebruikt:
+
+
+
+ OmegaT hoofdvenster (zonder het venster Woordenboek)
+
+
+ venster Zoeken
+
+
+ venster Tags valideren
+
+
+
+ Het dialoogvenster kan worden benaderd via het item in het menu van de toepassing. Het dialoogvenster bevat: OptiesLettertype...
+
+ menu OptiesLettertype...
+
+
+
+
+
+
+ Lettertype
+ Gebruik de keuzelijst om één van de beschikbare lettertypen op uw machine te selecteren.
+
+
+
+
+ Grootte
+ Bewerken om de grootte van het lettertype te wijzigen.
+
+
+
+
+
+
+
+ Voorbeeldtekst
+ Direct voorbeeld van het geselecteerde lettertype.
+
+
+
+
+
+ Opmerking
+ Het bijwerken van de weergave kan meer tijd vergen als het aantal weergegeven segmenten van belang is. Ook kunnen sommige lettertypen een betere dekking geven voor uw taalpaar.
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/FormattedText.xml b/OmegaT/doc_src/nl/FormattedText.xml
new file mode 100644
index 0000000..a7fc954
--- /dev/null
+++ b/OmegaT/doc_src/nl/FormattedText.xml
@@ -0,0 +1,155 @@
+
+
+
+ Werken met opgemaakte tekst<indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>opgemaakte tekst</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>opgemaakte tekst</secondary>
+ </indexterm>
+
+ Informatie over opmaak die aanwezig is in het bronbestand moet meestal worden gereproduceerd in het doelbestand. De in-regelige informatie over opmaak van ondersteunde formaten (momenteel DocBook, HTML, XHTML, Open Document (OpenOffice.org) en Office Open XML (MS Office 2007 en later) wordt door OmegaT weergegeven als tags. Normaal gesproken worden tags genegeerd bij het bepalen van de gelijkheid tussen de verschillende teksten ten behoeve van overeenkomsten. Tags die zijn gereproduceerd in het vertaalde segment zullen aanwezig zijn in het vertaalde document.
+
+
+ Tags voor opmaak<indexterm class="singular">
+ <primary>Tags</primary>
+ </indexterm>
+
+
+ Tagsnamen
+ Namen van tags:
+
+ De tags bestaan uit één tot drie tekens en een getal. Met unieke nummers kunnen de tags die met elkaar overeenkomen worden gegroepeerd en onderscheiden zich van de tags die dezelfde tekencombinatie hebben, maar in feite verschillend zijn. De gebruikte tekens in de tags proberen de onderliggende betekenis van de tag weer te geven (bijv. b voor vet, i voor cursief, etc.)
+
+
+ Tagsnummering
+ Nummering van tags:
+
+ Tags worden oplopend genummerd per groep van tags. "Taggroepen" in deze context zijn één enkele tag (zoals <i0> en </i0>). Binnen een segment krijgt de eerste groep (paar of enkele) het nummer 0, de tweede het nummer 1, etc. Het eerste voorbeeld hieronder heeft 3 tag-groepen (een paar, een enkele en dan nog een ander paar), het tweede voorbeeld heeft slechts één groep (een paar).
+
+
+ Tagsparen en enkele
+ Paren en enkele:
+
+ Tags zijn altijd óf enkel óf gepaard. Enkele tags geven informatie over de opmaak aan die niet van invloed is op de tekst er omheen (een extra spatie of regeleinde bijvoorbeeld).
+
+ <b0><Ctr+N></b0>,
+ <br1><b2><Enter></b2><segment 2132>
+
+
+ <br1> is een enkele tag en heeft geen effect op de omringende tekst. Tagparen geven gewoonlijk informatie over de stijl weer die van toepassing is op de tekst tussen de openingstag en de sluitingstag van een paar. <b0> en </b0> hieronder zijn gepaard en beïnvloeden de tekst log.txt. Onthoud dat de openingstag altijd vóór de bijbehorende sluitingstag moet komen:
+
+ <Logbestand (<b0>log.txt</b0>) voor het bijhouden van bewerkingen en fouten.<segment 3167>
+
+ OmegaT maakt zijn tags voordat het proces van segmentatie van zinnen wordt uitgevoerd. Afhankelijk van de segmentatieregels kan het paar tags worden gescheiden naar twee opeenvolgende segmenten en zal de tagvalidatie een fout aangeven en de twee segmenten markeren.
+
+
+
+ Tag-bewerkingen<indexterm class="singular">
+ <primary>Tags</primary> <secondary>bewerkingen</secondary>
+ </indexterm>
+
+ Voorzichtigheid is geboden met tags. Als zij per ongeluk worden gewijzigd kan de opmaak van het uiteindelijke document corrupt worden. De basisregel is dat de volgorde van de tags in dezelfde volgorde moet worden behouden. Het is echter mogelijk, als bepaalde regels strikt worden gevolgd, om van deze basisregel af te wijken.
+
+
+ Tagsdupliceren
+ Tags dupliceren:
+
+ Kopieer ze eenvoudigweg naar de positie van uw keuze om tags te dupliceren. Onthoud dat in een paar de openingstag vóór de sluitingstag moet komen. De opmaak die wordt vertegenwoordigd door de groep die u dupliceerde zal op beide gedeelten worden toegepast.
+
+ Voorbeeld:
+
+ <b0>Deze opmaak</b0> zal hier worden gedupliceerd.<segment 0001>
+
+ Na het dupliceren:
+
+ <b0>Deze opmaak</b0> is <b0>hier gedupliceerd</b0>.<segment 0001>
+
+
+ Tagsverwijderen van groepen
+ Verwijderen van taggroepen:
+
+ Verwijder ze eenvoudigweg uit het segment om taggroepen te verwijderen. Onthoud dat van een paar zowel de openings- als de sluitingstag moet worden verwijderd om er voor te zorgen dat alle sporen van de opmaak correct worden uitgewist, anders zou het vertaalde bestand mogelijk beschadigd kunnen raken. Door een taggroep te verwijderen verwijdert u de gerelateerde opmaak uit het vertaalde document.
+
+ Voorbeeld:
+
+ <b0>Deze opmaak</b0> zal worden verwijderd.<segment 0001>
+
+ Na het verwijderen:
+
+ Deze opmaak is verwijderd.<segment 0001>
+
+
+
+ Taggroep nesten<indexterm class="singular">
+ <primary>Tags</primary> <secondary>nesten van groepen</secondary>
+ </indexterm>
+
+ Wijzigen van de volgorde van een taggroep kan resulteren in het nesten van een taggroep binnen een andere taggroep. Dit is acceptabel zolang de omsluitende groep in zijn geheel de omsloten groep bevat. Met andere woorden, zorg er bij het verplaatsen van tagparen voor dat zowel de openings- als de sluitingstag ofwel binnen of buiten andere tagparen staan, anders zou het vertaalde bestand mogelijk beschadigd kunnen zijn en niet willen openen.
+
+ Voorbeeld:
+
+ <b0>Opmaak</b0> <b1>een</b1> zal worden genest binnen opmaak nul.<segment 0001>
+
+ Na het nesten:
+
+ <b0>Opmaak <b1>een</b1></b0> is genest binnen opmaak nul.<segment 0001>
+
+
+
+ Taggroep overlappen<indexterm class="singular">
+ <primary>Tags</primary> <secondary>overlappen van groepen</secondary>
+ </indexterm>
+
+ Overlappen is het resultaat van slechte bewerkingen van tagparen en zal gegarandeerd leiden tot beschadiging van de opmaak en soms tot het helemaal niet openen van het vertaalde document.
+
+ Voorbeeld:
+
+ <b0>Opmaak</b0> <b1>one</b1> zal worden verminkt.<segment 0001>
+
+ Na een slechte bewerking:
+
+ <b0>Opmaak <b1>een</b0> </b1>is nu zeer verminkt.<end segment 0001>
+
+
+
+ Taggroep validatie<indexterm class="singular">
+ <primary>Tags</primary> <secondary>groep valideren</secondary>
+ </indexterm>
+
+ De functie Tags valideren detecteert gewijzigde tags (of dat met opzet is gedaan of per ongeluk) en toont de betrokken segmenten. Het activeren van deze functie – Ctrl+T
+ SneltoetsenCtrl+T - Tagvalidatie
+ - zal een venster openen dat alle segmenten uit het bestand, waarvan wordt vermoed dat ze zijn verbroken of slechte tags zijn, bevat. Repareren van de tags en het opnieuw samenstellen van de doeldocumenten is eenvoudig met de functie Tags valideren. Het venster, dat wordt geopend door te drukken op Ctrl+T, heeft een kolom met 3 tabellen met een koppeling naar het segment, het originele segment en het doelsegment
+
+
+ Invoer bij tagvalidatie
+
+
+
+
+
+
+
+
+
+
+
+
+ De tags worden vet blauw geaccentueerd voor eenvoudige vergelijking tussen de originele en de vertaalde inhoud. Klik op de koppeling om het segment in het venster Bewerken te activeren. Verbeter, indien nodig, de fout (in het geval hierboven is dat het ontbrekende paar <i2></i2>) en druk op Ctrl+T om terug te keren naar het venster Tags valideren om andere fouten te corrigeren. Tagfouten zijn volgordes van tags in de vertaling die niet dezelfde volgorde en nummering van tags produceren als die in het originele segment. Sommige tagbewerkingen zijn noodzakelijk en zijn goedaardig, sommige zullen problemen veroorzaken als het vertaalde document wordt gemaakt.
+
+
+
+ Hints voor tagbeheer<indexterm class="singular">
+ <primary>Tags</primary> <secondary>hints</secondary>
+ </indexterm>
+
+ Vereenvoudig de originele tekst
+
+ Tags vertegenwoordigen over het algemeen een bepaalde vorm van opmaak van de originele tekst. Vereenvoudigen van de originele opmaak draagt bij aan het verminderen van het aantal tags. Waar de omstandigheden dat toestaan, zou het gelijk maken van gebruikte lettertypen, lettertype-afmetingen, kleuren etc. moeten worden overwogen, omdat het het vertalen vereenvoudigt en mogelijke fouten in tags vermindert. Lees het gedeelte Tagbewerkingen om te zien wat er met tags gedaan kan worden. Onthoud dat als u tags een probleem vindt in OmegaT en de opmaak niet buitengewoon relevant is voor de huidige vertaling, het verwijderen van tags de eenvoudigste manier kan zijn om uit de problemen te geraken.
+
+ Wees extra voorzichtig met tagparen.
+
+ Als u de tags moet zien in OmegaT maar de meeste opmaak niet behoeft te behouden in het vertaalde document staat het u vrij om de tags niet op te nemen in het vertaalde document. Let in dit geval extra op de tagparen omdat het verwijderen van één deel van het paar, maar het vergeten te verwijderen van het andere, gegarandeerd de opmaak van uw document zal beschadigen. Omdat tags in de tekst zelf zijn opgenomen, is het mogelijk om segmentatieregels te gebruiken om segmenten te maken met minder tags. Dit is een geavanceerde voorziening en enige ervaring is vereist om die juist toe te passen.
+
+ OmegaT is nog niet in staat om fouten in de opmaak volautomatisch te detecteren, dus het zal geen signaal geven als u een fout maakt of de opmaak wijzigt zodat die beter bij uw doeltaal past. Soms kan uw vertaalde document er echter vervormd uitzien en, - in het ergste geval-, zou zelfs misschien weigeren te openen.
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/Glossaries.xml b/OmegaT/doc_src/nl/Glossaries.xml
new file mode 100644
index 0000000..da8e755
--- /dev/null
+++ b/OmegaT/doc_src/nl/Glossaries.xml
@@ -0,0 +1,181 @@
+
+
+
+ Woordenlijsten<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Woordenlijst</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Woordenlijsten</primary>
+ </indexterm>
+
+ Woordenlijsten zijn bestanden die handmatig gemaakt en bijgewerkt worden voor gebruik in OmegaT.
+
+ Als een project in OmegaT één of meer woordenlijsten bevat, worden termen uit de woordenlijst die ook worden gevonden in het huidige segment automatisch weergegeven in het venster Woordenlijst.
+
+ U definieert de locatie ervan in het dialoogvenster Projecteigenschappen. De extensie moet .txt zijn (indien niet zal die worden toegevoegd). De locatie van het bestand moet liggen binnen de map /glossary , maar het mag in een diepere map staan (bijv. glossary/sub/glossary.txt). Het bestand hoeft niet te bestaan als het wordt ingesteld, het zal worden gemaakt (indien nodig) bij het toevoegen van een item voor de woordenlijst. Als het bestand al bestaat, wordt er geen poging gedaan om de indeling of de tekenset van het bestand te verifiëren: de nieuwe items zullen altijd in de indeling tab-gescheiden en UTF-8 zijn. Omdat de bestaande inhoud niet wordt geraakt, zal schade aan een bestaand bestand beperkt zijn.
+
+
+ Gebruik
+
+ Plaats een bestaande woordenlijst eenvoudigweg in de map
+ Projectbestandensubmap Glossary
+ /glossary, na het maken van het project, om die te gebruiken. OmegaT detecteert automatisch woordenlijstbestanden in deze map als een project wordt geopend. Termen in het huidige segment die OmegaT vindt in het/de woordenlijstbestand(en) worden weergegeven in het venster Woordenlijst:
+
+
+ venster Woordenlijst
+
+
+
+ venster Woordenlijst
+
+
+
+
+
+
+
+
+
+
+
+
+ Het woord voor het =-teken is de bronterm en de vertaling is (of zijn) de woorden na =. Het woordenlijst-item kan een opmerking toegevoegd hebben (zie "bedrijvend werkwoord" voor het tweede item). De functie woordenlijst vindt alleen exacte overeenkomsten met het woordenlijst-item (bijv. vindt geen afgeleide vormen etc.). Nieuwe termen kunnen handmatig aan de woordenlijstbestanden worden toegevoegd tijdens het vertalen (bijvoorbeeld in een tekstverwerkingsprogramma), maar nieuw toegevoegde termen worden niet herkend totdat het project opnieuw wordt geladen.
+
+ De bronterm behoeft geen item met één woord te zijn, zoals het volgende voorbeeld laat zien:
+
+
+ items met meerdere woorden in woordenlijsten - voorbeeld<indexterm class="singular">
+ <primary>venster Woordenlijst - items met meerdere woorden</primary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+ Het onderstreepte item "pop-upmenu" kan worden gevonden in het venster Woordenlijst als "pojavni menu". Door het te accentueren in het venster Woordenlijst en er dan met rechts op te klikken voegt het in op de cursorpositie in het doelsegment.
+ Onthoud dat in het bovenstaande geval, dit slechts het halve verhaal (of zelfs nog minder is) is, omdat de doeltaal (Sloveens) verbuigingen gebruikt. Het ingevoegde "pojavni meni" moet dus worden gewijzigd naar "pojavcnem meniju". Met andere woorden: het typen van de juiste term, zonder te accentueren en met rechts te klikken, is waarschijnlijk sneller.
+
+
+
+
+ <indexterm class="singular">
+ <primary>Woordenlijsten</primary> <secondary>bestandsformaat</secondary>
+ </indexterm>Bestandsformaat<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>gebruikersbestanden</secondary> <seealso>woordenlijsten</seealso>
+ </indexterm>
+
+ Woordenlijstbestanden zijn eenvoudige platte tekst-bestanden die drie-kolommen, tabgescheiden lijsten bevatten met de bron- en doeltermen in respectievelijk de eerste en tweede kolom. De derde kolom kan worden gebruikt voor aanvullende informatie. Woordenlijstbestanden kunnen of in de standaard systeemcodering (en aangegeven door de extensie .tab) zijn of in UTF-8 (de extensie .utf8). De codering Unicode (UTF8) wordt om voor de hand liggende redenen geprefereerd.
+
+ Ook het CSV-formaat wordt ondersteund. Dit formaat is hetzelfde als de tabgescheiden: bronterm, doelterm. Velden met opmerkingen worden gescheiden door een komma ','. Tekenreeksen kunnen worden omsloten door aanhalingstekens ", die het mogelijk maken een komma binnen een tekenreeks te hebben:
+
+ "This is a source term, which contains a comma","Dit is een bronterm, die een komma bevat"
+
+ In aanvulling op het platte tekst-formaat, wordt TBX-formaat
+ WoordenlijstenTBX-formaat
+ ook ondersteund. TBX - Term Base eXchange - is de open, op XML gebaseerde standaard voor de uitwisseling van gestructureerde terminologische gegevens. TBX is goedgekeurd als een internationale standaard door LISA
+ LISA-bestandsformaat
+ en ISO. Als u een bestaand systeem hebt voor de afhandeling van terminologie - MultiTerm bijvoorbeeld - is het zeer wel mogelijk dat het de mogelijkheid biedt om gegevens van terminologie in TBX-formaat te exporteren. Microsoft Terminology Collection
+ WoordenlijstenMicrosoft Terminology collectie
+ kan worden gedownload in bijna 100 talen en kan dienen als hoeksteen IT-woordenlijst.
+
+
+
+ Hoe zijn woordenlijsten te maken<indexterm class="singular">
+ <primary>Woordenlijsten</primary> <secondary>een woordenlijst maken</secondary>
+ </indexterm>
+
+ De projectinstellingen maken het mogelijk een naam in te voeren voor een te beschrijven woordenlijstbestand (zie het begin van dit hoofdstuk). Toevoegen van nieuwe items wordt gedaan met behulp van de sneltoets voor het toetsenbord Ctrl+Shift+G. Een dialoogvenster opent en maakt het u mogelijk maken een bronterm, doelterm en opmerkingen die u zou kunnen hebben in te voeren:
+
+
+
+
+
+
+
+
+
+
+
+ De inhoud van bestanden met woordenlijsten worden in het geheugen bewaard en geladen als het project wordt geopend of opnieuw geladen. Bijwerken van een woordenlijstbestand is dus vrij eenvoudig: druk op Ctrl+Shift+G en voer de nieuwe term in, de vertaling ervan en opmerkingen die u zou kunnen hebben (zorg er voor dat u op 'tab' drukt tussen de velden) en sla het bestand op. De inhoud van het venster Woordenlijst zal overeenkomstig worden bijgewerkt.
+
+ Opmerking: Natuurlijk zijn er andere wegen en manieren om een eenvoudig bestand met tabgescheiden items te maken, en zij zijn allemaal eenvoudiger, en veel er van een heel stuk eenvoudiger dan bovenstaande suggestie. Men kan bijvoorbeeld de inhoud hierboven exporteren als een CSV, in plaats van als een UTF8-tekstbestand. Er is niets tegen het gebruiken van Notepad++ op Windows of GEdit op Linux bijvoorbeeld: elke tekstverwerker die UTF8 kan afhandelen en witruimte weer kan geven (zodat de vereiste TAB-tekens u niet ontgaan) kan worden gebruikt.
+
+
+
+ <indexterm class="singular">
+ <primary>Woordenlijsten</primary> <secondary>Trados MultiTerm</secondary>
+ </indexterm>Gebruik van Trados Multiterm
+
+ Woordenlijsten die zijn geëxporteerd vanuit Trados Multiterm kunnen zonder verdere aanpassingen worden gebruikt als woordenlijsten voor OmegaT, vooropgesteld dat zij de bestandsextensie .tab hebben gekregen en de velden voor bron- en doelterm respectievelijk de eerste twee velden zijn. Indien u exporteert met behulp van de systeemoptie "Tabgescheiden exporteren", moet u de eerste 5 kolommen verwijderen (Seq. Nr, Date created etc). De nieuwere versies van MultiTerm ondersteunen het exporteren naar TBX-formaat.
+
+
+
+ <indexterm class="singular">
+ <primary>Woordenlijsten</primary> <secondary>problemen met woordenlijsten</secondary>
+ </indexterm>Algemene problemen met woordenlijsten
+
+ Probleem: Er worden geen items van de woordenlijst weergegeven - mogelijke oorzaken:
+
+
+
+ Geen bestand met woordenlijst gevonden in de map "glossary".
+
+
+
+
+
+ Het bestand met de woordenlijst is leeg.
+
+
+
+
+
+ De items worden niet gescheiden door een TAB-teken.
+
+
+
+
+
+ Het bestand met de woordenlijst heeft niet de juiste extensie (.tab of .utf8).
+
+
+
+
+
+ Er bestaat geen EXACTE overeenkomst tussen het item in de woordenlijst en de brontekst in uw document - bijvoorbeeld als het item meervoud is.
+
+
+
+
+
+ Het bestand met de woordenlijst heeft niet de juiste codering.
+
+
+
+
+
+ Er staan in het huidige segment geen termen die overeenkomen met enige term in de woordenlijst.
+
+
+
+
+
+ Eén of meer van bovenstaande problemen kan zijn gerepareerd, maar het project werd nog niet herladen.
+
+
+
+ Probleem: In het venster Woordenlijst worden sommige tekens niet juist weergegeven
+
+
+
+ ...maar dezelfde tekens worden wel goed weergegeven in het venster Bewerken: de extensie en de codering van het bestand komen niet overeen.
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/InstallingAndRunning.xml b/OmegaT/doc_src/nl/InstallingAndRunning.xml
new file mode 100644
index 0000000..b71d365
--- /dev/null
+++ b/OmegaT/doc_src/nl/InstallingAndRunning.xml
@@ -0,0 +1,618 @@
+
+
+
+ Installeren en uitvoeren van <application>OmegaT</application>
+
+
+ Windows-gebruikers<indexterm class="singular">
+ <primary>Installeren van OmegaT</primary> <secondary>Windows</secondary>
+ </indexterm>
+
+
+ Downloaden van het pakket
+
+ Heeft u een Java-implementatie die compatibel is met Oracle's Java 1.5 JRE?
+
+
+
+ Ja: download OmegaT_2.5.x_Windows_without_JRE.exe.
+
+
+
+ Nee / Ik weet het niet: download OmegaT_2.5.x_Windows.exe.
+
+ Dit pakket is gebundeld met Oracle's Java Runtime Environment. Deze JRE zal geen problemen veroorzaken met andere Java-implementaties die misschien al op uw systeem geïnstalleerd zijn.
+
+
+
+
+
+ <application>Installeren van OmegaT</application>
+
+ Dubbelklik op het programma dat u hebt gedownload en volg de instructies om OmegaT te installeren.
+
+
+
+ <application>OmegaT</application> toevoegen aan het menu Start of bureaublad<indexterm class="singular">
+ <primary>OmegaT aanpassen</primary> <secondary>Windows</secondary>
+ </indexterm>
+
+ Gedurende de installatie zal het programma u vragen of u een map in het menu Start wilt maken en of u een snelkoppeling op het bureaublad en in het systeemvak wilt maken.
+
+ U kunt daarna nog steeds een snelkoppeling maken door OmegaT.exe naar het bureaublad of menu Start te slepen om het van daaruit te koppelen.
+
+
+
+ <application>OmegaT<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>Windows</secondary>
+ </indexterm></application> uitvoeren
+
+ Als OmegaT eenmaal is geïnstalleerd, kunt u klikken op OmegaT.jar om het direct te starten, of u kunt het direct vanaf de opdrachtregel starten.
+
+ De eenvoudigste manier om OmegaT te starten is echter om het programmaOmegaT.exe uit te voeren.
+ OmegaT uitvoerenWindowsINI-bestand
+ De opties voor het opstarten van het programma zullen in dit geval worden gelezen uit het OmegaT.l4J.ini-bestand, dat zich bevindt in dezelfde map als het exe-bestand en wat u kunt bewerken om uw instellingen weer te geven. Het volgende voorbeeld voor het INI-bestand reserveert 1GB aan geheugen, zal Frans als taal van de gebruiker instellen en Portugal als het land:
+
+ # OmegaT.exe runtime configuration
+# To use a parameter, remove the '#' before the '-'
+# Memory
+-Xmx1024M
+# Language
+-Duser.language=FR
+# Country
+-Duser.country=CA
+
+
+
+ Upgraden van OmegaT<indexterm class="singular">
+ <primary>Upgraden van OmegaT</primary> <secondary>Windows</secondary>
+ </indexterm>
+
+ Deze informatie is alleen van toepassing op de "traditionele" Windows-versies van OmegaT. Het is niet van toepassing op de Web Start-versies, die automatisch worden geüpgraded, noch op de versies voor meerdere platformen die zijn geïnstalleerd op Windows.
+
+ Als u al een versie van OmegaT hebt geïnstalleerd op uw PC en wilt upgraden naar een meer recente versie, heeft u twee opties:
+
+
+
+ Installeren over de bestaande installatie heen. Selecteer eenvoudigweg dezelfde installatiemap als de bestaande installatie bij het installeren van de nieuw versie om dit te doen. De "oude" versie van OmegaT zal worden overschreven, maar alle instellingen ervan zullen worden behouden. Dit omvat ook de voorkeuren die zijn ingesteld binnen OmegaT, alle wijzigingen die u hebt gemaakt aan uw OmegaT.l4J.ini-bestand, en ook uw script om op te starten (.bat-bestand), als u er een gebruikt.
+
+
+
+ Met deze methode kunt u ook de versie "Windows without JRE" downloaden, omdat de nieuwe installatie uw bestaande JRE zal gebruiken.
+
+
+
+ Installeren in een nieuwe map. Hiermee zult u beide versies naast elkaar hebben staan, wat u zou kunnen doen totdat u zich op uw gemak voelt met de nieuwe versie. Deze methode zal ook de voorkeuren en instellingen gebruiken die u hebt gemaakt binnen OmegaT. In dit geval echter:
+
+
+
+ Als u wijzigingen hebt gemaakt in uw OmegaT.l4J.ini-bestand en/of een .bat-bestand gebruikt, moet u die kopiëren naar de nieuwe installatie.
+
+
+
+
+
+ Als uw bestaande installatie van OmegaT een "Windows with JRE"-versie is, moet de nieuwe versie ook een "Windows with JRE"-versie zijn.
+
+
+
+
+
+
+
+
+ Linux (Intel)-gebruikers<indexterm class="singular">
+ <primary>Installeren van OmegaT</primary> <secondary>Linux</secondary>
+ </indexterm>
+
+
+ Downloaden van het juiste pakket
+
+ Heeft u een Java-implementatie die compatibel is met Oracle's Java 1.5 JRE?
+
+
+
+ Ja: download OmegaT_2.5.x_Without_JRE.zip.
+
+
+
+ Nee / Ik weet het niet: download OmegaT_2.5.x_Linux.tar.bz2.
+
+ Dit pakket is gebundeld met Oracle's Java Runtime Environment. Deze JRE zal geen problemen veroorzaken met andere Java-implementaties die misschien al op uw systeem geïnstalleerd zijn.
+
+
+
+
+
+ <application>Installeren van OmegaT</application>
+
+ Uitpakken/untarren van het gedownloade bestand. Dit zal een map omegat/ maken in de werkmap waarin u alle nodige bestanden vindt om OmegaT uit te voeren. Uitpakken van het .tar.gz bestand:
+
+ $ tar xf downloaded_file.tar.gz
+
+
+
+ <application>OmegaT</application> toevoegen aan uw menu's (KDE) of panelen (Gnome)
+
+
+ KDE 4-gebruikers<indexterm class="singular">
+ <primary>OmegaT aanpassen</primary> <secondary>KDE 4</secondary>
+ </indexterm>
+
+ U kunt OmegaT als volgt aan uw menu's toevoegen:
+
+
+
+ Druk op Alt+F2 om KRunner weer te geven. Typ kmenuedit+enter om de opdracht uit te voeren. De KMenuEditor verschijnt. Selecteer in KMenuEditor Bestand -> Nieuw item.
+
+
+
+ Dan, na het selecteren van een passend menu, voeg een submenu/item toe met Bestand - Nieuw submenu en Bestand - Nieuw item. Voer OmegaT in als de naam van het nieuwe item.
+
+
+
+ Gebruik, in het veld "Commando", de navigatieknop om uw OmegaT startscript te vinden (het bestand genaamd OmegaT in de uitgepakte map) en selecteer dat.
+
+
+
+ Klik op de pictogramknop (rechts van de velden Naam/Beschrijving/Commentaar)
+
+
+
+ Andere pictogrammen - Bladeren en navigeer naar de submap /images in de OmegaT-toepassingsmap. Selecteer het pictogram OmegaT.png.
+
+
+
+ Sla tenslotte de wijzigingen op met Bestand - Opslaan.
+
+
+
+
+
+ Gnome-gebruikers<indexterm class="singular">
+ <primary>OmegaT aanpassen</primary> <secondary>GNOME</secondary>
+ </indexterm>
+
+ U kunt OmegaT als volgt aan uw menu's toevoegen:
+
+
+
+ Klik met rechts op het paneel - Nieuwe starter.
+
+
+
+ Voer "OmegaT" in in het veld "Naam"; gebruik, in het veld "Commando", de navigatieknop om uw startscript voor OmegaT te vinden (het bestand genaamd OmegaT in de uitgepakte map). Selecteer dat en bevestig met OK.
+
+
+
+ Klik op de pictogramknop, en druk dan op Bladeren... en navigeer naar de submap /images in de toepassingenmap OmegaT. Selecteer het pictogram OmegaT.png. GNOME kan weigeren om de pictogrambestanden weer te geven in de beschikbare indelingen en in het begin een SVGbestand verwachten, maar als de map wordt geselecteerd, zouden de bestanden moeten verschijnen en kan OmegaT.png worden geselecteerd.
+
+
+
+
+
+
+ <application>OmegaT<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>Linux</secondary>
+ </indexterm></application> uitvoeren
+
+ U kunt OmegaT opstarten vanaf de opdrachtregel met een script dat de opties voor opstarten bevat of u kunt klikken op OmegaT.jar om het direct op te starten. Methoden verschillen, afhankelijk van de distributie. Zorg ervoor dat de instellingen van uw PATH juist zijn en dat .jar-bestanden juist zijn gekoppeld aan een Java-starter. Bekijk "Starten vanaf de opdrachtregel" hieronder voor meer informatie.
+
+
+
+
+ Mac OS X-gebruikers<indexterm class="singular">
+ <primary>OS X</primary> <secondary>Installeren van OmegaT</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Installeren van OmegaT</primary> <secondary>OS X</secondary>
+ </indexterm>
+
+
+ Downloaden van het pakket
+
+ OmegaT 2.5 vereist Java 1.5 om te kunnen worden uitgevoerd. Gebruik "Software Update..." uit het menu Apple om uw versie van Java bij te werken.
+
+ Download OmegaT_2.5.x_Mac.zip.
+
+
+
+ <application>Installeren van OmegaT</application>
+
+ Dubbelklik op OmegaT_2.5.x_Mac.zip om het uit te pakken. Dit zal een map maken dieOmegaTheet. De map bevat 2 bestanden: index.html en OmegaT.app. Kopieer de map naar een toepasselijke map (bijv. Toepassingen). Als u dit gedaan heeft kunt u het bestand OmegaT_2.5.x_Mac.zip verwijderen, het is niet langer nodig.
+
+
+
+ <application>OmegaT</application> toevoegen aan het dock<indexterm class="singular">
+ <primary>OS X</primary> <secondary>OmegaT toevoegen aan het dock</secondary> <seealso>OmegaT aanpassen</seealso>
+ </indexterm>
+
+ Sleep en zet OmegaT.app op het Dock neer.
+
+
+
+ <application>OmegaT<indexterm class="singular">
+ <primary>OS X</primary> <secondary>OmegaT uitvoeren</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>OS X</secondary>
+ </indexterm></application> uitvoeren
+
+ Dubbelklik opOmegaT.app of klik op zijn locatie in het dock
+
+ Klik met rechts op OmegaT.app en selecteer "Pakketinhoud weergeven" om toegang te krijgen tot Info.plist, en open het bestand door er met rechts op te klikken en selecteer uw tekstverwerker van uw keuze. U kunt ook met "cd" daar rechtstreeks naartoe gaan vanaf de opdrachtregel en Info.plist openen in een verwerker voor de opdrachtregel zoals emacs of vi.
+ OS XOmegaT aanpassenStartparameters
+
+ OS XOmegaT aanpassen
+
+
+ U kunt het gedeelte Properties en ook het gedeelte VMOptions aanpassen.
+
+ Indien u waarden wilt toevoegen aan VMOptions, plaatst u er een spatie tussen. Bijvoorbeeld: -Xmx1024M -Duser.language=ja zal OmegaT opstarten met 1024MB aan geheugen en de gebruikersinterface in het Japans.
+
+ Als u meerdere instanties van OmegaT.app moet uitvoeren, gebruik dan in plaats daarvan het bestand JavaApplicationStub dat zich bevind in OmegaT.app/ Contents/MacOS/.
+
+ Gebruik het bestand OmegaT.jar dat zich bevindt in OmegaT.app/Contents/Resources/Java/ om OmegaT vanaf de opdrachtregel te starten. Bekijk "Starten vanaf de opdrachtregel" hieronder voor meer informatie.
+
+
+
+ Mac OS X goede dingen
+
+ OmegaT.app kan worden bereikt vanuit Mac OS X Services. U kunt dus ergens in OmegaT een woord selecteren en de Services gebruiken om het te controleren, bijvoorbeeld in Spotlight of in Google. U kunt ook AppleScript of Automator gebruiken om Services of scripts te maken die acties die veel voorkomen te automatiseren.
+
+
+
+
+ Andere systemen<indexterm class="singular">
+ <primary>Installeren van OmegaT</primary> <secondary>Andere systemen</secondary>
+ </indexterm>
+
+ Deze informatie is van toepassing op systemen zoals Solaris SPARC/x86/x64, Linux x64/PowerPC, Windows x64
+
+
+ Downloaden van het juiste pakket
+
+ OmegaT is beschikbaar, gebundeld met een Oracle Java JRE voor Linux (Intel x86)- en Windows-platformen. Gebruikers van andere platformen (Linux PowerPC, Linux x64, Solaris SPARC/x86/x64, Windows x64 etc) moeten een werkende compatibele Java JRE op hun systeem hebben om OmegaT te kunnen gebruiken.
+
+ Heeft u een Java-implementatie die compatibel is met Oracle's Java 1.5 JRE?
+
+
+
+ Ja: download OmegaT_2.5.x_Windows_without_JRE.zip. Dit pakket kan worden gebruikt op elk platform waar een Java 1.5 JRE compatibele JRE is geïnstalleerd.
+
+
+
+ Ik weet het niet: open een terminal en type "java -version". Als een "command not found" of soortgelijk bericht wordt teruggegeven, is het waarschijnlijk dat Java niet is geïnstalleerd op uw systeem.
+
+
+
+ Nee: Zorg voor een Java JRE voor uw systeem (zie hieronder) en download OmegaT_2.5.x_Without_JRE.zip.
+
+ Oracle levert JRE's voor Solaris SPARC/x86 (Java 1.5) en voor Linux x64, Solaris x64, Windows x64 (Java 1.5) op http://www.oracle.com/technetwork/java/archive-139210.html.
+
+ IBM levert JRE's voor Linux PowerPC op http://www.ibm.com/developerworks/java/jdk/linux/download.htm
+
+ Volg de installatie-instructies voor het pakket dat u nodig hebt.
+
+
+
+
+
+ <application>Installeren van OmegaT</application><indexterm class="singular">
+ <primary>Installeren van OmegaT</primary> <secondary>Andere systemen</secondary>
+ </indexterm>
+
+ Pak eenvoudigweg het bestand OmegaT_2.5.x_Without_JRE.zip uit om OmegaT te installeren. Dit maakt een map ./OmegaT_2.5.x_Without_JRE/ in de werkmap waarin u alle benodigde bestanden zult vinden om OmegaT uit te voeren.
+
+
+
+ Installeren van handige sneltoetsen
+
+ Volg de instructies voor uw systeem om sneltoetsen voor OmegaT op handige plaatsen te installeren.
+
+
+
+ <application>OmegaT<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>Andere systemen</secondary>
+ </indexterm></application> uitvoeren
+
+ Als OmegaT eenmaal is geïnstalleerd, kunt u het direct vanaf de opdrachtregel starten, u kunt een script maken dat de startparameters voor de opdrachtregel bevat of u kunt op OmegaT.jar klikken om het direct uit te voeren. Methoden verschillen, afhankelijk van de distributie. Zorg ervoor dat de instellingen van uw PATH juist zijn en dat .jar-bestanden juist zijn gekoppeld aan een Java-starter. Bekijk "Starten vanaf de opdrachtregel" hieronder voor meer informatie.
+
+
+
+
+ Java Web Start gebruiken<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>Java Web Start gebruiken</secondary>
+ </indexterm>
+
+ Java Web Start-technologie (onderdeel van Java 1.5 en hoger) kan worden gebruikt om met één enkele klik zelfstandige Java softwaretoepassingen uit te voeren over het netwerk. Java Web Start zorgt er voor dat de meest recente versie van de toepassing zal worden uitgevoerd, evenals de juiste versie van de Java Runtime Environment (JRE). Laad de volgende URL in uw browser om OmegaT voor de eerste keer te starten met Java Web Start:
+
+ http://omegat.sourceforge.net/webstart/OmegaT.jnlp
+
+ Download het bestandOmegaT.jnlp en klik er dan op. Gedurende de installatie, afhankelijk van uw besturingssysteem, zou u verschillende beveiligingswaarschuwingen kunnen ontvangen. De rechten die u aan deze versie geeft (welke kunnen lijken op "onbeperkte toegang tot de computer") zijn identiek aan de rechten die u geeft voor de locale versie, d.i. zij geven toegang tot de harde schijf van de computer. Opvolgende klikken op OmegaT.jnlp zal leiden tot het controleren op upgrades, ze installeren als ze er zijn, en dan OmegaT starten. Na de initiële installatie kunt u natuurlijk OmegaT.jnlp ook gebruiken als u offline bent.
+
+ Privacy: OmegaT Java Web Start slaat geen informatie van u op buiten de computer waarop het wordt uitgevoerd. De toepassing wordt slechts uitgevoerd op uw machine. Uw documenten en vertaalgeheugens blijven op uw computer, en het OmegaTproject zal geen toegang hebben tot uw werk of informatie.
+
+ Merk op dat als u argumenten voor het opstarten wilt gebruiken (zie boven), u de normale installatie moet gebruiken.
+
+
+
+ OmegaT starten vanaf de opdrachtregel<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>Starten vanaf de opdrachtregel</secondary>
+ </indexterm>
+
+ Normaal gesproken is het niet nodig om OmegaT te starten vanaf de opdrachtregel. Het alternatief van de opdrachtregel stelt echter de gebruiker in staat om het gedrag van het programma te beheren en aan te passen. Er zijn twee manieren om OmegaT te starten met behulp van de opdrachtregel.
+
+
+ Openen van een venster voor de opdrachtregel
+
+ Een venster voor de opdrachtregel wordt ook wel een "terminalvenster" genoemd. Op Windows wordt het een "MS-DOSvenster" genoemd en is het beschikbaar via het menu Start, in Alle programma's → Bureau-accessoires, via het item "Opdrachtprompt". Het equivalent voor Mac OS X is de toepassing Terminal die zich bevind in Programma's → Hulpprogramma's.
+
+ U moet normaal gesproken twee opdrachten typen om OmegaT te starten. De eerste hiervan is:
+
+ cd {map}
+
+ waar {map} de naam is van de map, met het complete pad, waarin uw OmegaT-programma - specifiek het bestand OmegaT.jar - is geplaatst. In de praktijk zal deze opdracht er ongeveer zo uitzien:
+
+ Op Windows
+
+ cd C:\Program
+ Files\OmegaT
+
+ Op Mac OS X
+
+ cd <locatie OmegaT.app>/OmegaT.app/Contents/Resources/Java/
+
+
+ Op Linux
+
+ cd /usr/local/omegat
+
+ Deze opdracht wijzigt de map naar de map die het uitvoerbare OmegaT-bestand bevat. De tweede opdracht is de opdracht die OmegaT echt start. In zijn meest basale vorm is deze opdracht:
+
+ java -jar
+ OmegaT.jar
+
+ Let op de hoofdletters - het programma zal niet starten als u invoert omegat in plaats van OmegaT !
+
+ Deze methode heeft het bijzondere voordeel dat het geschikt is om oorzaken voor problemen op te sporen: als een fout optreedt gedurende het gebruiken van het programma wordt een foutbericht weergegeven in het terminalvenster dat bruikbare informatie kan bevatten over de oorzaak.
+
+ De bovenstaande methode is een niet zo praktische manier om een programma routinematig te starten. Om deze reden zijn de twee hierboven beschreven opdrachten opgenomen in een bestand (een "script", ook wel een ".bat-bestand" genoemd op Windows-systemen).
+
+ Als dit bestand wordt uitgevoerd worden de daarin opgenomen opdrachten automatisch uitgevoerd. Derhalve is het voldoende om dit bestand aan te passen om wijzigingen aan te brengen in de startopdracht.
+
+
+
+ Argumenten voor de startopdracht<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>Argumenten voor bestand om op te starten</secondary>
+ </indexterm>
+
+ De basisopdracht is hierboven al genoemd. Wijzigingen voor deze opdracht behelzen het daaraan toevoegen van "argumenten". Argumenten worden toegevoegd ná het initiële "java" en vóór het gedeelte "-jar OmegaT.jar". Onthoud dat u in Windows het bestand OmegaT.l4J.ini kunt wijzigen om uw voorkeuren weer te geven. Op Mac OSX kunt u Info.plist wijzigen, dat zich bevindt in OmegaT.app/Contents/, om hetzelfde te doen.
+
+ Een lijst van mogelijke argumenten wordt hieronder weergegeven. Gevorderde gebruikers kunnen meer informatie over de argumenten vinden door man java in het terminalvenster te typen.
+
+
+
+ Taal van de gebruikersinterface
+
+ -Duser.language=XX
+ OmegaT uitvoerenArgumenten voor bestand om op te startenUser.language
+ Normaal gesproken, d.i. als OmegaT wordt gestart zonder enig argument, detecteert het programma eerst de taal van het besturingssysteem van de gebruiker. Als een gebruikersinterface in deze taal beschikbaar is gebruikt OmegaT die. Dus, als het besturingssysteem van de gebruiker Russisch is en OmegaT is vertaald in het Russisch, wordt OmegaT weergegeven met een Russische gebruikersinterface, Russische menu's, etc. Als de taal van het besturingssysteem van de gebruiker niet beschikbaar is gebruikt OmegaT standaard Engels. Dit is het standaard gedrag.
+
+ Het argument "-Duser.language=XX" zorgt ervoor dat OmegaT de gespecificeerde taal gebruikt, in plaats van de taal van het besturingssysteem van de gebruiker. "XX" in de opdracht staat voor de code van twee letters van de gewenste taal. De opdracht, om OmegaT te starten met een Franse interface (bijvoorbeeld op een Russisch besturingssysteem), zou daarom zijn:
+
+ java -Duser.language=fr -jar
+ OmegaT.jar
+
+
+
+
+
+ Instellen land gebruiker
+
+ -Duser.country=XX
+ OmegaT uitvoerenArgumenten voor bestand om op te startenUser.country
+ Naast de taal kunt u ook het land specificeren, bijvoorbeeld CN of TW in geval van de Chinese taal. U moet zowel de taal als het land specificeren om de gids Snel starten in de gewenste taal weer te geven. Dit is zelfs nodig als er slechts één combinatie beschikbaar is, zoals pt_BR in geval van Portugees / Braziliaans.
+
+
+
+
+
+ Antialiasing lettertype - (alleen Java 1.5)
+
+ -Dswing.aatext=true
+ OmegaT uitvoerenArgumenten voor bestand om op te startenAntialiasing lettertype
+ Dit argument beïnvloedt de anti-aliasing van de lettertypen, waarbij hun weergave wordt verbeterd.
+
+
+
+ Toewijzen van geheugen
+
+ -XmxZZM
+ OmegaT uitvoerenArgumenten voor bestand om op te startenToewijzen van geheugen
+ Deze opdracht wijst meer geheugen toe aan OmegaT. Standaard wordt 256 Mb toegewezen, dus er is geen voordeel te behalen door minder dan dit getal toe te wijzen. "ZZ" staat voor de toegewezen geheugenruimte in megabytes. De opdracht om OmegaT te starten met toewijzing van 1024 Mb (1 gigabyte) aan geheugen luidt dan ook:
+
+ java -Xmx1024M -jar
+ OmegaT.jar
+
+
+
+ Proxy host IP-adres
+
+ -Dhttp.proxyHost=nnn.nnn.nnn.nnn
+ OmegaT uitvoerenArgumenten voor bestand om op te startenProxyserver IP-adres
+ Het IP-adres van uw proxyserver, als uw systeem een proxy gebruikt
+
+
+
+ Proxyserver poortnummer
+
+ Dhttp.proxyPort=NNNN
+ OmegaT uitvoerenArgumenten voor bestand om op te startenProxyserver - Poortnummer
+ Het poortnummer dat uw systeem gebruikt om toegang te krijgen tot de proxyserver.
+
+
+
+ Google Translate V2
+
+ -Dgoogle.api.key=A123456789B123456789C123456789D12345678
+ OmegaT uitvoerenArgumenten voor bestand om op te startenGoogle Translate V2
+ Indien u bent geabonneerd op de services van Google Translate, dient u hier uw eigen private Google API-sleutel in te voeren. Onthoud dat de sleutel 38 tekens lang is.
+
+
+
+ Argumenten mogen worden gecombineerd: Voor het starten van OmegaT met alle hierboven genoemde voorbeelden zou de opdracht zijn:
+
+ java -Dswing.aatext=true -Duser.language=pt
+ -Duser.country=BR -Xmx1024M -DDhttp.proxyHost=192.168.1.1
+ -Dhttp.proxyport=3128 -jar
+ -OmegaT.jar
+
+
+
+ OmegaT in de modus Opdrachtregel<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>modus Opdrachtregel</secondary>
+ </indexterm>
+
+ Het doel van de console-modus is om OmegaT als vertaalgereedschap te gebruiken in een script-omgeving. Indien wordt begonnen in de console-modus, wordt geen GUI geladen (dus het zal werken op elke console) en het opgegeven project wordt automatisch verwerkt zoals verzocht.
+
+
+ Vooraf vereist
+
+ Een geldig OmegaT-project moet aanwezig zijn om OmegaT uit te kunnen voeren in de modus Opdrachtregel. De locatie maakt niet uit omdat het bij de start toch al moet worden ingevuld in de opdrachtregel.
+
+ Indien u gewijzigde instellingen nodig hebt, moeten de configuratiebestanden beschikbaar zijn. Dat kan op twee manieren worden bereikt:
+
+
+
+ Voer OmegaT normaal uit (met de GUI) en maak de instellingen. Indien u OmegaT in console-modus start, zal het dezelfde instellingen gebruiken.
+
+
+
+ Indien u OmegaT niet normaal kunt uitvoeren (geen grafische omgeving beschikbaar): kopieer de instellingen vanaf een andere installatie van OmegaT op een andere machine naar een bepaalde map. De locatie maakt niet uit, omdat u die toch in kunt vullen in de opdrachtregel bij het starten. De relevante bestanden zijn filters.conf en segmentation.conf en kunnen worden gevonden in de startmap van de gebruiker (bijv. C:\Documents and Settings\%User%\OmegaT onder Windows, %user%/.omegat/ onder Linux).
+
+
+
+
+
+ Beginnen in console-modus
+
+ Enkele extra parameters moeten bij het starten worden opgegeven om OmegaT in console-modus te starten. De meest belangrijke is <project-dir>, en optioneel --config-dir=<config-dir>. Voorbeeld:
+
+ java -jar OmegaT.jar /pad/naar/project \
+
+ --config-dir=/pad/naar/config-bestanden/ \
+
+
+ --mode=console-translate|console-createpseudotranslatetmx|console-align
+
+ --source-pattern={reguliere uitdrukking}
+
+ Merk op dat alle parameters beginnen met een dubbel "-"-teken.
+
+ Uitleg:
+
+
+
+ <project-dir> vertelt OmegaT waar het project kan worden gevonden dat moet worden vertaald. Indien opgegeven start OmegaT in de console-modus en zal het opgegeven project gaan vertalen.
+
+
+
+
+
+ --config-dir=<config-dir> vertelt OmegaT in welke map de configuratiebestanden zijn opgeslagen. Indien niet opgegeven gaat OmegaT terug naar de standaard waarden (OmegaT-dir onder beginmap van de gebruiker, of indien niet beschikbaar: de huidige werkmap). Onthoud het dubbele "-"-teken
+
+
+
+
+
+ --mode=...-OmegaT begint in de console-modus om één van de volgende services automatisch uit te voeren
+
+
+
+ --mode=console-translate
+
+ In deze modus zal OmegaT proberen om de bestanden in /source/ te vertalen met de beschikbare vertaalgeheugens. Dit is handig om OmegaT uit te voeren op een server waarmee TMX-bestanden automatisch worden toegevoegd aan het project.
+
+
+
+ --mode=console-createpseudotranslatetmx
+
+ In deze modus zal OmegaT een TMX voor het gehele project maken, alleen gebaseerd op de bronbestanden. U specificeert dat het TMX/bestand moet worden gemaakt met
+
+ --pseudotranslatetmx=allsegments.tmx
+ --pseudotranslatetype=[equal|empty]
+
+ Het argument pseudotranslatetype specificeert, of de doelsegmenten gelijk moeten zijn aan de bron of leeg moeten worden gelaten.
+
+
+
+ --mode=console-align
+
+ In deze modus zal OmegaT het bestand met de Java-eigenschappen die zijn gevonden in de map /source/ van het project vergelijken met de inhoud op de opgegeven locatie. De resulterende TMX wordt opgeslagen in de map /omegat/ onder de naam align.tmx.
+
+ Een aanvullende parameter, die de locatie van de doelgegevens specificeert, is in dit geval vereist:
+
+ --alignDir={locatie van vertaalde bestanden}
+
+ alignDir moet een vertaling bevatten in de doeltaal van het project. Als, bijvoorbeeld, het project EN->FR is, moet alignDir een bundle bevatten die eindigt op _fr. De resulterende TMX wordt opgeslagen in de map omegat onder de naam align.tmx.
+
+
+
+
+
+ --source-pattern={reguliere uitdrukking}
+
+ Als deze modus werd gebruikt, zal deze optie de bestanden specificeren die automatisch moeten worden verwerkt. Als de parameter niet is gespecificeerd, zullen alle bestanden worden verwerkt. Hier zijn een paar typische voorbeelden om uw keuze te beperken:
+
+
+
+ .*\.html
+
+ Alle HTML-bestanden zullen worden vertaald - merk op dat de punt in het gebruikelijke *.html moet worden vooraf gegaan door een backslash (\.) zoals gespecificeerd door de regels voor reguliere uitdrukkingen
+
+
+
+ test\.html
+
+ Alleen het bestand test.html aan het begin van de map source zal worden vertaald. Indien er andere bestanden, genaamd test.html, in andere mappen staan, worden die genegeerd.
+
+
+
+ dir-10\\test\.html
+
+ Alleen het bestand test.html in de map dir-10 zal worden verwerkt. Merk opnieuw op dat ook de backslash moet worden voorafgegaan door een backslash.
+
+
+
+
+
+
+
+ optie Quiet
+
+ Een extra parameter voor de opdrachtregel, specifiek voor de console-modus: --quiet.In de modus quiet, wordt er minder informatie gelogd op het scherm. De berichten die u normaal gesproken zou vinden in de statusbalk worden niet weergegeven.
+
+ Gebruik: java -jar OmegaT.jar /pad/naar/project --mode=console-translate --quiet
+
+
+
+ Optie Tags valideren
+
+ Een andere parameter voor de opdrachtregel, specifiek voor de console-modus: --tag-validation=[abort|warn]. Als deze parameter wordt toegevoegd, wordt het valideren van tags toegepast voorafgaande aan vertalen/uitlijnen. Als de waarde abort is dan worden bij tagfouten de fouten afgedrukt en het programma stopt. Als de waarde warn is dan worden fouten afgedrukt maar OmegaT gaat door.
+
+ Gebruik: java -jar OmegaT.jar /pad/naar/project --mode=console-translate --tag-validation=abort
+
+
+
+
+
+ <application>OmegaT</application> bouwen vanuit de bron<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>OmegaT bouwen vanuit de bron</secondary>
+ </indexterm>
+
+ Onthoud dat u ook het programma ant (http://ant.apache.org/bindownload.cgi) nodig hebt om uw eigen versie van OmegaT te bouwen. Pak het bestand OmegaT_2.5.x_Source.zip uit en geef de map OmegaT_2.5.x_Source op of voer de map ./omegat/ in voor de checkout-code van SVN. Controleer of een bestand build.xml in die map aanwezig is. Typ dan op de opdrachtregel:
+
+ $ ant jar release
+
+ Dit zal een volledige distributie van OmegaT maken in de map ./dist/, waarin u alle benodigde bestanden zult vinden om OmegaT uit te voeren.
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/InstantStartGuide.xml b/OmegaT/doc_src/nl/InstantStartGuide.xml
new file mode 100644
index 0000000..d712366
--- /dev/null
+++ b/OmegaT/doc_src/nl/InstantStartGuide.xml
@@ -0,0 +1,111 @@
+
+
+
+ Leren om OmegaT te gebruiken in 5 minuten!
+
+
+ Stel een nieuw project in<indexterm class="singular">
+ <primary>Project</primary> <secondary>Maak / open nieuw</secondary>
+ </indexterm>
+
+ Opmerking: Op een Apple Mac, gebruik de toets Cmd of Apple in plaats van de toets Ctrl
+
+ Maak eerst een project dat al uw bestanden zal bevatten, zoals uw bronbestanden, vertaalgeheugens, woordenlijsten en uiteindelijk uw vertaalde bestand, om te beginnen met het gebruiken van OmegaT. Selecteer, in het menu Project, Nieuw...
+ menu ProjectNieuw...
+ typ een naam voor uw project. Onthoud waar u het project maakte, omdat u er later naar terug moet keren.
+
+ Nadat u het project een naam hebt gegeven, zal het dialoogvenster Nieuw project maken openen. Selecteer, aan het begin van dat dialoogvenster, uw taal voor de bronbestanden en de taal waarin uw vertaalde bestand moet zijn, en klik op OK om door te gaan.
+
+ Indien u geïnteresseerd bent in andere instellingen van dit dialoogvenster, kunt u er op elk moment naar terugkeren door te drukken op Ctrl+E.
+
+ Vervolgens opent het dialoogvenster Projectbestanden. Klik op de knop Bronbestanden importeren... om uw bronbestand te selecteren. OmegaT zal dan het geselecteerde bestand kopiëren naar de submap /source/ van uw nieuw gemaakte project. Nadat het bronbestand is geladen in het venster Bewerken kunt u het dialoogvenster Projectbestanden sluiten.
+
+
+
+ Vertaal het bestand
+
+ OmegaT zal één segment per keer presenteren om door u te worden vertaald. Nadat u elk segment hebt vertaald, druk op Ctrl+U om naar het volgende niet-vertaalde segment te gaan. Wanneer u wilt zien hoe uw vertaling eruit zal zien in zijn uiteindelijke opmaak, druk op Ctrl+D om het vertaalde document te genereren, dat zal worden gemaakt in de submap /target/ van uw projectmap. Gebruik, gedurende het vertalen, de menu's Bewerken en Ga naar om verschillende handige functies uit te voeren.
+
+
+
+ Valideren van uw tags
+
+ Als uw bronbestand een opgemaakt bestand is, bijv. Microsoft Word, LibreOffice Writer of HTML, zal OmegaT de opmaak converteren naar tags die de tekst die u vertaalt omsluiten. Documenten hebben ook vaak tags die niets te maken hebben met opmaak, maar die ook belangrijk zijn. In het bronbestand (en in het vertaalde bestand), zou een bronzin eruit kunnen zien als
+
+
+
+
+
+
+
+
+
+
+
+ OmegaT zal deze zin echter op de volgende manier presenteren:
+
+
+
+
+
+
+
+
+
+
+
+ De tags in OmegaT zijn grijs, zodat zij eenvoudig te herkennen zijn. Zij zijn niet beveiligd, zodat u ze kunt verwijderen, ze handmatig kunt invoeren of ze kunt verplaatsen in de doelzin. Indien u echter fouten maakte bij het typen van de tags voor de opmaak, kan het zijn dat uw vertaalde bestand niet wil openen. Druk daarom op Ctrl+T vóórdat uw uw vertaalde document genereert, om te valideren dat uw tags juist zijn.
+
+
+
+ Genereren van het vertaalde bestand
+
+ Als u zich er eenmaal van overtuigd hebt dat er geen tagfouten meer in uw vertaling staan, druk dan op Ctrl+D om het doelbestand te genereren, dat zal worden gemaakt in de submap /target/ van uw projectmap.
+
+
+
+ Enkele andere dingen om te onthouden
+
+
+
+ Indien een bestand niet wordt geladen in het venster Bewerken, dan zou het kunnen zijn dat uw bronbestand in een indeling is die niet werkt in OmegaT. Zie hoofdstuk 7: Bestandsfilters in de Gebruikershandleiding voor een lijst van bestandsindelingen die OmegaT kan afhandelen.
+
+
+
+
+
+ U kunt een nieuw project maken voor elke nieuwe taak en u kunt verschillende bronbestanden tegelijkertijd aan een project toevoegen.
+
+
+
+
+
+ Open het dialoogvenster Projecteigenschappen door te drukken op Ctrl+E om uzelf te herinneren aan de initiële instellingen van het project. Open het dialoogvenster Projectbestanden door te drukken op Ctrl+L om een lijst van bestanden in het project te zien.
+
+
+
+
+
+ Aan het einde van uw vertaling exporteert OmegaT drie vertaalgeheugens, genaamd "level1", "level2" en "omegat" naar uw projectmap. De geheugens "level1" en "level2" kunnen worden gedeeld met gebruikers van andere vertaalprogramma's. Het geheugen genaamd "omegat" kan worden gebruikt in OmegaT zelf, in toekomstige projecten die u maakt. Als u bestanden van vertaalgeheugens plaats in de submap /tm/ van uw projectmap, zal OmegaT automatisch daarin zoeken naar overeenkomstige segmenten, genaamd "fuzzy overeenkomsten".
+
+
+
+
+
+ U kunt een woordenlijst maken door te drukken op Ctrl+Shift+G, of bestaande woordenlijsten kopiëren naar de submap /glossary/ van uw projectmap en OmegaT zal automatisch daarin woorden opzoeken.
+
+
+
+
+
+ Het is vaak handig om te zoeken naar woorden en frasen in de brontekst en in uw vertaling, dus druk op elk moment op Ctrl+F voor het dialoogvenster "Tekst zoeken".
+
+
+
+
+
+ Voor een meer uitgebreide introductie, bekijk OmegaT for Beginners op de OmegaT website. Als u ondersteuning nodig hebt met enig aspect van OmegaT, neem dan vrijblijvend deel aan de OmegaT gebruikersgroep.
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/MachineTranslation.xml b/OmegaT/doc_src/nl/MachineTranslation.xml
new file mode 100644
index 0000000..210dbf0
--- /dev/null
+++ b/OmegaT/doc_src/nl/MachineTranslation.xml
@@ -0,0 +1,125 @@
+
+
+
+ Machinevertaling<indexterm class="singular">
+ <primary>Machinevertaling</primary>
+ </indexterm>
+
+
+ Introductie<indexterm class="singular">
+ <primary>Machinevertaling</primary> <secondary>introductie</secondary>
+ </indexterm>
+
+ Tegengesteld aan de door de gebruiker gegenereerde vertaalgeheugens (zoals in het geval van OmegaT) gebruiken programma's voor machinevertaling (MT) op regels gebaseerde linguïstische programma's om een vertaling van de bron te maken zonder dat een vertaalgeheugen nodig is. Statistische leertechnieken, gebaseerd op bron- en doelteksten, worden gebruikt om een vertaalmodel te bouwen. Services voor machinevertalingen hebben goed en steeds betere resultaten behaald in research evaluaties.
+
+ Ga naar Opties > Machinevertaling... en activeer de gewenste service om een van de services voor machinevertaling te activeren. Onthoud dat zij allemaal op het web gebaseerd zijn: u zult online moeten zijn als u ze wilt gebruiken.
+
+
+
+ Google Translate<indexterm class="singular">
+ <primary>Machinevertaling</primary> <secondary>Google Translate</secondary>
+ </indexterm>
+
+ Google Translate is een service waarvoor betaald moet worden en die wordt aangeboden door Google, voor het vertalen van zinnen, websites en complete teksten tussen een nof steeds groeiend aantal talen. Op het moment van schrijven bevat de lijst meer dan 50 talen, van Albanees tot Jiddisch, inclusief natuurlijk alle grote talen. De huidige versie van de service is, op het moment van schrijven, gebaseerd op het gebruiken ervan, met een prijs van 20 USD per miljoen tekens.
+
+ Belangrijk: Google Translate API v2 vereist rekeninggegevens voor alle accounts vóórdat u de service kunt gebruiken (zie Pricing and Terms of Service voor meer informatie). U gebruikt uw eigen private unieke sleutel, die door Google aan u is verzonden toen u zich registreerde bij de service, om uzelf te identificeren als een geldige gebruiker voor de services van Google. Bekijk hoofdstuk Installeren en uitvoeren van OmegaT, gedeelte OmegaT starten vanaf de opdrachtregel, voor details om deze sleutel aan de omgeving van OmegaT toe te voegen.
+
+ De kwaliteit van de vertaling is aan de ene kant afhankelijk van het reservoir aan teksten in de doeltaal en de beschikbaarheid van hun meertalige versies, aan de andere kant ook van de kwaliteit van de gebouwde modellen. Het is haast wel zeker dat, hoewel de kwaliteit in sommige gevallen onvoldoende kan zijn, het uiteindelijk mettertijd beter zal worden en niet slechter.
+
+
+
+ <application>OmegaT</application>-gebruikers en Google Translate
+
+ De gebruiker van OmegaT is niet gedwongen om Google Translate te gebruiken. Indien het wordt gebruikt zal de beslissing van de gebruiker om de vertaling te accepteren, noch de uiteindelijke vertaling beschikbaar worden gemaakt voor Google. Het volgende venster geeft een voorbeeld weer van a) de Engelse bron b) Spaanse en c) Sloveense vertaling in Google Translate.
+
+
+ Google Translate - voorbeeld
+
+
+
+
+
+
+
+
+
+
+
+
+ De Spaanse vertaling is beter dan de Sloveense. Merk op dat interesar en navegar in het Spaans correct zijn vertaald als respectievelijk de werkwoorden interest en sail. In de Sloveense versie worden beide woorden vertaald als zelfstandige naamwoorden. Het is eigenlijk zeer waarschijnlijk dat de Spaanse vertaling, ten minste gedeeltelijk, is gebaseerd op de actuele vertaling van het boek.
+
+ Vanaf het moment dat de service is geactiveerd zal er een suggestie voor de vertaling verschijnen in het venster Machinevertaling voor elk nieuw bronsegment dat wordt geopend. Indien u de suggestie acceptabel vindt, druk op
+ SneltoetsenCtrl+M - Machinevertaling
+ CtrlM om het doelgedeelte van het geopende segment te vervangen. In het segment hierboven, bijvoorbeeld, zou CtrlM de Spaanse versie overschrijven met de Sloveense suggestie.
+
+ Indien u niet wilt dat OmegaT uw bronsegmenten verstuurt naar Google om te worden vertaald, verwijdert u het vinkje vóór het menuitem Google Translate in Opties.
+
+ Onthoud dat er niets anders dan het bronsegment wordt verzonden naar de service van de machinevertaling. De online versie van Google Translate maakt het de gebruiker mogelijk om de suggestie te corrigeren en het gecorrigeerde segment in te sturen. Deze mogelijkheid is echter niet geïmplementeerd in OmegaT.
+
+
+
+ Belazar<indexterm class="singular">
+ <primary>Machinevertaling</primary> <secondary>Belazar</secondary>
+ </indexterm>
+
+ Belazar is een programma voor machinevertaling voor een Russisch - Wit-Russisch taalpaar.
+
+
+
+ Apertium<indexterm class="singular">
+ <primary>Machinevertaling</primary> <secondary>Apertium</secondary>
+ </indexterm>
+
+ Apertium is een gratis/open-bron platform voor machinevertaling, initieel gericht op gerelateerde taalparen, zoals CA, ES, GA, PT, OC en FR maar recent uitgebreid om ook minder gangbare taalparen (zoals Engels-Catalaans) te behandelen. Controleer op de website voor de laatste lijst van geïmplementeerde taalparen.
+
+ Het platform levert
+
+
+
+ een taal-onafhankelijk programma voor machinevertaling
+
+
+
+ om de linguïstische gegevens te beheren die nodig zijn om een systeem voor machinevertaling te bouwen voor een bepaald taalpaar en
+
+
+
+
+
+ linguïstische gegevens voor een groeiend aantal taalparen
+
+
+
+ Apertium gebruikt een oppervlakkig overdrachtprogramma voor machinevertaling die de invoer in gedeelten verwerkt, zoals in een lopende band: opmaak verwijderen, morfologische analyses, doorverwijzen van spraakgedeelten, oppervlakkige structurele overdracht, lexicografische overdracht, morfologische generatie, en opnieuw opmaken.
+
+ Het is mogelijk om Apertium te gebruiken om systemen voor machinevertalingen te bouwen voor een variëteit aan taalparen; voor dat doel gebruikt Apertium eenvoudige op XML gebaseerde standaard formaten om de benodigde linguïstische gegevens te coderen (ofwel met de hand of door het converteren van bestaande gegevens), die zijn gecompileerd met behulp van de verschafte programma's in de formaten voor hoge snelheid zoals die gebruikt worden door het programma.
+
+
+
+ Machinevertaling - probleemoplossing<indexterm class="singular">
+ <primary>Machinevertaling</primary> <secondary>Probleemoplossing</secondary>
+ </indexterm>
+
+ Indien er niets verschijnt in het venster Machinevertaling, controleer dan het volgende:
+
+
+
+ Bent u online? U moet online zijn om een programma voor machinevertaling te kunnen gebruiken.
+
+
+
+
+
+ Wat is het taalpaar dat u nodig hebt? Controleer of de geselecteerde service het aanbiedt.
+
+
+
+ Google Translate werkt niet: controleer Opties > Machinevertaling: de service Google Translate is gelabeld Google Translate V2. De oudere versie van de service, gelabeld "Google Translate" en beschikbaar in verouderde versies van OmegaT, is vervallen en werkt niet meer.
+
+
+
+ "Google Translate gaf HTTP antwoordcode: 403 terug ...": controleer of de sleutel van 38 tekens, ingevoerd in het bestand pinfo.list, juist is. Controleer of de service Translate API geactiveerd is.
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/Menu.xml b/OmegaT/doc_src/nl/Menu.xml
new file mode 100644
index 0000000..fb79fc7
--- /dev/null
+++ b/OmegaT/doc_src/nl/Menu.xml
@@ -0,0 +1,1235 @@
+
+
+
+ Sneltoetsen voor menu en het toetsenbord
+
+
+ <indexterm class="singular">
+ <primary>Hoofdmenu</primary>
+ </indexterm>Hoofdmenu
+
+
+ SneltoetsenHoofdmenu
+
+
+ Alle functionaliteiten van OmegaT zijn beschikbaar via de menubalk boven het venster Bewerken. De meeste functies zijn ook beschikbaar via sneltoetsen voor het toetsenbord. Sneltoetsen worden geactiveerd door te drukken op Ctrl en een letter. Sommige sneltoetsen gebruiken ook andere toetsen. Voor de leesbaarheid worden letters hier geschreven als hoofdletters. Ctrl wordt gebruikt op Windows, UNIX en UNIX-achtige besturingssystemen die een toetsenbord hebben met de Ctrl- of Control-toets. Mac-gebruikers moeten in plaats daarvan de cmd-toets gebruiken. De "Cmd"-toets heeft ofwel een label "command" of een Apple-merkteken op toetsenborden van Apple.
+
+ U kunt bestaande sneltoetsen aanpassen of nieuwe, naar uw behoeften, toevoegen. Zie Appendix - Sneltoetsen aanpassen
+
+
+ Hoofdmenu
+
+
+
+
+ Project
+
+ Bewerken
+
+ Ga naar
+
+ Weergave
+
+ Extra
+
+ Opties
+
+ Help
+
+
+
+
+ menu Project
+
+
+
+
+
+
+
+
+ Nieuw
+
+
+
+ Maakt en opent een nieuw project. Het dialoogvenster om een project te maken is hetzelfde als voor het bewerken van het project. Zie
+
+
+
+ Openen
+
+
+ Ctrl
+
+ O
+
+
+ Opent een eerder gemaakt project.
+
+
+
+ Bronbestanden importeren...
+
+
+
+ Kopieert de geselecteerde bestanden naar de map /source en herlaadt het project om de nieuwe bestanden te laden.
+
+
+
+ Importeren vanuit MediaWiki...
+
+
+
+ Importeert eenheden vanaf pagina's van MediaWiki, gebaseerd op de ingevoerde URL.
+
+
+
+ Herladen
+
+ F5
+
+ Herlaadt het project om externe wijzigingen in bronbestanden, gebruikte vertaalgeheugens, woordenlijsten en instellingen voor het project te verwerken.
+
+
+
+ Sluiten
+
+
+ Ctrl
+
+ Shift
+
+ W
+
+
+ Slaat de vertaling op en sluit het project.
+
+
+
+ Opslaan
+
+
+ Ctrl
+
+ S
+
+
+ Slaat het interne vertaalgeheugen op de harde schijf op. OmegaT slaat automatisch elke 10 minuten de vertaalgeheugens op en ook als u het project sluit of OmegaT afsluit.
+
+
+
+ Vertaalde documenten maken
+
+
+ Ctrl
+
+ D
+
+
+ Maakt de doeldocumenten op basis van uw vertaling van de tekst in de documenten. De gemaakte doeldocumenten zijn geplaatst in de map /target.
+
+
+
+ Eigenschappen...
+
+
+ Ctrl
+
+ E
+
+
+ Geeft het dialoogvenster Projecteigenschappen weer om de projecttalen en maplocaties te kunnen bewerken.
+
+
+
+ Projectbestanden...
+
+
+ Ctrl
+
+ L
+
+
+ Sluit of opent het venster Projectbestanden (afhankelijk van het feit of het geopend of gesloten is).
+
+
+
+ Afsluiten
+
+
+ Ctrl
+
+ Q
+
+
+ Slaat het project op en sluit OmegaT af. Als u het project nog niet hebt opgeslagen wordt hier handmatig bevestiging gevraagd of u werkelijk af wilt sluiten.
+
+
+
+
+
+
+
+ Bewerken<indexterm class="singular">
+ <primary>Hoofdmenu</primary> <secondary>Bewerken</secondary>
+ </indexterm>
+
+ Opmerking: Items die in de meeste toepassingen aanwezig zijn (kopiëren/knippen/plakken) worden in dit menu niet weergegeven maar zijn beschikbaar met de sneltoetsen van uw systeem. Bijvoorbeeld:
+
+
+ Sneltoetsen kopiëren/knippen/plakken
+
+
+
+
+
+
+
+
+ Kopiëren
+
+
+ Ctrl
+
+ C
+
+
+ Kopieert de geselecteerde tekst naar het klembord.
+
+
+
+ Knippen
+
+
+ Ctrl
+
+ X
+
+
+ Kopieert de geselecteerde tekst naar het klembord en verwijdert de geselecteerde tekst.
+
+
+
+ Plakken
+
+
+ Ctrl
+
+ V
+
+
+ Plakt de tekst van het klembord op de cursorpositie.
+
+
+
+
+
+ Het menu Bewerken zelf bevat de volgende sneltoetsen:
+
+
+ menu Bewerken
+
+
+
+
+
+
+
+
+ Laatste actie ongedaan maken
+
+
+ Ctrl
+
+ Z
+
+
+ Herstelt de status naar vóórdat de laatste actie werd uitgevoerd. Deze opdracht werkt niet als het gewijzigde segment al is gevalideerd.
+
+
+
+ Laatste actie opnieuw
+
+
+ Ctrl
+
+ Y
+
+
+ Herstelt de status naar vóórdat de laatste actie werd geannuleerd. Deze opdracht werkt niet als het gewijzigde segment al is gevalideerd.
+
+
+
+ Vervangen door overeenkomst
+
+
+ Ctrl
+
+ R
+
+
+ Vervangt het gehele doelsegment door de huidige geselecteerde overeenkomst (de eerste overeenkomst is standaard geselecteerd)
+
+
+
+ Overeenkomst invoegen
+
+
+ Ctrl
+
+ I
+
+
+ Voegt de huidige geselecteerde overeenkomst in op de cursorpositie. Indien een gedeelte van het doelsegment is geselecteerd, overschrijft deze functie het geselecteerde gedeelte.
+
+
+
+ Vervangen door machinevertaling
+
+
+ Ctrl
+
+ M
+
+
+ Vervangt het doelsegment door de vertaling die wordt verschaft door de service van de machinevertaling. Geen actie wordt ondernomen indien er geen service voor machinevertaling is geactiveerd (zie Menu > Opties hieronder).
+
+
+
+ Vervangen door bron
+
+
+ Shift
+
+ Ctrl
+
+ R
+
+
+ Vervangt het huidige doelsegment door de brontekst.
+
+
+
+ Bron invoegen
+
+
+ Shift
+
+ Ctrl
+
+ I
+
+
+ Voegt de brontekst in op de cursorpositie.
+
+
+
+ Brontags invoegen
+
+
+ Shift
+
+ Ctrl
+
+ T
+
+
+
+ TagsBrontags invoegen
+ Voegt de brontags in op de cursorpositie. Alle tags in de brontekst zullen worden ingevoegd in het huidige segment, ongeacht of ze daar al staan of niet. Tekst, omsloten door tags, wordt vervangen door spaties: <f0><f1>Dit is tekst</f0></f1> dus zal worden gekopieerd als <f0><f1>één_spatie</f0></f1>
+
+
+
+ Selectie exporteren
+
+
+ Shift
+
+ Ctrl
+
+ C
+
+
+ Exporteert de huidige selectie naar een tekstbestand voor verwerking. Indien geen tekst is geselecteerd, wordt het huidige bronsegment naar dit bestand geschreven. Wanneer de gebruiker OmegaT afsluit, wordt dit bestand niet geleegd, om consistent te zijn aan het gebruikelijke gedrag van het klembord. De geëxporteerde inhoud wordt gekopieerd naar het bestand selection.txt dat is geplaatst in de voorkeursmap van de gebruiker (zie ).
+
+
+
+ Item voor woordenlijst maken
+
+
+ Shift
+
+ Ctrl
+
+ G
+
+
+ Laat de gebruiker een item maken in het standaard bestand voor de woordenlijst.
+
+
+
+ Zoeken in project...
+
+
+ Ctrl
+
+ F
+
+
+ Opent een nieuw venster Zoeken.
+
+
+
+ Schakel Hoofd-/kleine letters naar...
+
+ ShiftF3 (zie tekst)
+
+ Wijzigt hoofd-/kleine letters van de geaccentueerde tekst in het doelsegment naar de geselecteerde optie (Kleine letters, Hoofdletters of Alle woorden hoofdletters). Gebruik Shift+F3
+ SneltoetsenShift+F3 - Selectie Hoofd-/kleine letters
+ om tussen de drie keuzes te schakelen. Indien geen tekst is geselecteerd, selecteert OmegaT het woord dat de letter bevat direct rechts naast de cursor.
+
+
+
+ Overeenkomst #N selecteren
+
+
+ Ctrl
+
+ #N
+
+
+ (#N is een getal van 1 tot en met 5) - Selecteert de Ne overeenkomst die is weergegeven in het venster Overeenkomsten om het segment te vervangen of het daar in te voegen. De beschrijft de codering van de kleuren in detail.
+
+
+
+ Als standaard vertaling gebruiken
+
+
+
+ Indien er meerdere alternatieve vertalingen beschikbaar zijn voor het actieve segment, kunt u het geselecteerde alternatief als de standaard vertaling instellen. Het item zal grijs worden als er slechts één vertaling beschikbaar is.
+
+
+
+ Alternatieve vertaling maken
+
+
+
+ Het ene en hetzelfde segment kan, afhankelijk van de context, verschillende vertalingen vereisen. Selecteer dit menuitem als de huidige vertaling niet van toepassing is en voer de alternatieve vertaling in.
+
+
+
+
+ menu Ga naar
+
+
+
+
+
+
+
+
+ Volgende niet-vertaalde segment
+
+
+ Ctrl
+
+ U
+
+
+ Verplaatst naar het volgende segment dat geen equivalent heeft in het vertaalgeheugen.
+
+
+
+ Volgende segment
+
+ CtrlN of Enter of Tab
+
+ Verplaatst naar het volgende segment. Als het huidige segment het laatste in een bestand is, verplaatst het naar het eerste segment van het volgende bestand.
+
+
+
+ Vorige segment
+
+ CtrlP of CtrlEnter of CtrlTab
+
+ Verplaatst naar het vorige segment. Als het huidige segment het eerste in een bestand is, verplaatst het naar het laatste segment van het vorige bestand.
+
+
+
+ Segmentnummer...
+
+
+ Ctrl
+
+ J
+
+
+ Het segment wordt geopend als zijn segmentnummer wordt ingevoerd.
+
+
+
+ Volgende notitie
+
+
+
+ Het volgende segment waar een notitie aan is verbonden, zal openen.
+
+
+
+ Vorige notitie
+
+
+
+ Het vorige segment met een notitie zal openen.
+
+
+
+ Verder in geschiedenis...
+
+
+ Ctrl
+
+ Shift
+
+ N
+
+
+ OmegaT onthoudt de verwerkte segmenten. Met deze opdracht kunt u vooruit naar het segment dat u eerder verliet met de opdracht Terug in geschiedenis...
+
+
+
+ Terug in geschiedenis...
+
+
+ Ctrl
+
+ Shift
+
+ P
+
+
+ Met deze opdracht kunt u één segment terug in de tijd gaan, om later terug te keren naar het huidige segment met behulp van de opdracht Verder in geschiedenis... hieronder.
+
+
+
+
+ menu Weergave
+
+
+
+
+
+
+ Vertaalde segmenten markeren
+
+ Indien aangevinkt, zullen de vertaalde segmenten in geel worden geaccentueerd.
+
+
+
+ Niet-vertaalde segmenten markeren
+
+ Indien aangevinkt, zullen de niet-vertaalde segmenten in paars worden geaccentueerd.
+
+
+
+ Bronsegmenten weergeven
+
+ Indien aangevinkt, zullen de bronsegmenten in groen worden geaccentueerd. Indien niet aangevinkt, zullen de bronsegmenten niet worden weergegeven.
+
+
+
+ Niet-unieke segmenten markeren
+
+ Indien aangevinkt zullen niet-unieke segmenten bleekgrijs worden gemarkeerd.
+
+
+
+ Segmenten met opmerkingen markeren
+
+ In aangevinkt zullen segmenten met opmerkingen cyaankleurig worden gemarkeerd.
+
+
+
+ Niet-afbreekbare spaties markeren
+
+ Indien aangevinkt worden niet-afbreekbare spaties in het segment met een grijze achtergrond weergegeven.
+
+
+
+ Info over wijzigingen
+
+ Instellen van de optie Info over wijzigingen op Weergave voor huidige segment zal datum en tijd en de auteur weergeven van de laatste wijziging aan het huidige segment. Het instellen op Weergave voor alle segmenten geeft deze informatie weer voor alle segmenten en Niets weergeven schakelt deze optie uit.
+
+
+
+
+ menu Extra
+
+
+ OvereenkomstenStatistieken voor overeenkomsten
+
+
+
+ ProjectStatistieken voor overeenkomsten
+
+
+
+ ProjectStatistieken
+
+
+
+
+
+
+
+ Tags valideren
+
+ Ctrl+T: Controleert op ontbrekende of misplaatste tags in opgemaakte bestanden. Zal een lijst weergeven waarin de segmenten met tagfouten en mogelijke onvolkomenheden staan. Zie Tagvalidatie en .
+
+
+
+ Tags verwijderen
+
+ Indien ingeschakeld worden alle tags voor opmaak verwijderd uit de bronsegmenten. Dit is handig als teksten worden afgehandeld waarin in-regelige opmaak geen echt nut heeft (bijv. ge-OCRde PDF, slecht geconverteerde .odt of .docx, etc.) Alleen in-regelige tags worden verwijderd, dus normaal gesproken zou er geen probleem moeten zijn met het openen van de doeldocumenten. Niet-zichtbare opmaak (d.i. die niet als tags verschijnen in de bewerker van OmegaT) wordt in het doeldocument behouden.
+
+
+
+ Statistieken
+
+ Opent een nieuw venster en geeft de statistieken voor het project weer, d.i. de totalen voor het project en de totalen voor elk bestand in het project.
+
+
+
+ Statistieken voor overeenkomsten
+
+ Geeft de Statistieken voor overeenkomsten weer voor het project: het aantal herhalingen, exacte overeenkomsten, overeenkomsten en geen overeenkomsten, voor segmenten, woorden en in tekens.
+
+
+
+
+ menu Opties
+
+
+
+
+
+
+ Tab gebruiken om door te gaan
+
+ Stelt de toets voor het valideren van het segment in op Tab in plaats van de standaardtoets Enter. Deze optie is handig voor sommige invoersystemen voor Chinese, Japanse of Koreaanse tekens.
+
+
+
+ Afsluiten altijd bevestigen
+
+ Het programma zal u altijd om bevestiging vragen om af te sluiten.
+
+
+
+ Machinevertaling
+
+ Stelt u in staat om de aangeboden programma's voor machinevertaling te activeren/deactiveren. Indien actief, zal CtrlM de suggestie in het doelgedeelte van het huidige segment invoegen.
+
+
+
+ Woordenlijst
+
+
+
+
+
+ TransTips
+
+ Stelt u in staat de mogelijkheid TransTips te activeren/deactiveren en stelt de optie er van in op Exacte overeenkomst. Met de geactiveerde TransTips zal een klik met rechts op een geaccentueerd woord in de brion een pop-upmenu openen met de items van de woordenlijst voor het woord waarop u hebt geklikt. U kunt dan op de geprefereerde vertaling klikken om die in te voegen in het doelsegment op de huidige positie. Met TransTips/Exacte overeenkomst ingeschakeld, zullen alleen volledige woorden worden gecontroleerd, anders zullen ook gedeelten van woorden overeenkomen.
+
+
+
+ Lettertype...
+
+ Toont het dialoogvenster om het lettertype voor de weergave van de tekst aan te passen. Gebruikers van oudere computers die het aanpassen van de venstergrootte heel traag vinden kunnen proberen om het lettertype te wijzigen. Zie .
+
+
+
+ Bestandsfilters...
+
+ Geeft het dialoogvenster Bestandsfilters weer om de bestandsafhandeling en het parsen te configureren.
+
+
+
+ Segmentatie...
+
+ Opent het venster Segmentatie-instellingen om de segmentatie van de tekst te configureren.
+
+
+
+ Spellingscontrole...
+
+ Geeft het venster Spellingscontrole instellen weer om de spellingscontrole te installeren, te configureren en te activeren.
+
+
+
+ Bewerken (gedrag)...
+
+ Geeft het dialoogvenster Vertaling bewerken weer om te configureren.
+
+
+
+ Tags valideren...
+
+ Voor programmeurs: Stelt u in staat om de opties voor Tags valideren te configureren en ook variabelen in het programma (%...) te controleren.
+
+
+
+ Team...
+
+ Voer hier uw naam in en die zal worden gekoppeld aan alle door u vertaalde segmenten.
+
+
+
+ Externe TMXen...
+
+ Laat de gebruiker beslissen hoe tags in vreemde TMX-bestanden (d.i. niet gegenereerd door OmegaT) moeten worden behandeld.
+
+
+
+ Weergave...
+
+ Bevat de optie om alle bronsegmenten in vet weer te geven en het eerste niet-unieke segment te markeren.
+
+
+
+ Inloggen Proxy...
+
+ Voer u gebruikersnaam en uw wachtwoord in, als u een proxy gebruikt om toegang te krijgen tot uw projecten.
+
+
+
+ Hoofdvenster herstellen
+
+ Herstelt de componenten van het hoofdvenster van OmegaT naar hun standaard status. Gebruik deze mogelijkheid in de gevallen dat u één of meer componenten heeft losgemaakt, verplaatst of verborgen en u ze niet terug kan krijgen op de manier die u wilt. Het kan ook worden gebruikt als vensters er niet uitzien zoals u verwachtte na een upgrade van OmegaT.
+
+
+
+
+ menu Help
+
+
+
+
+
+
+ Gebruikershandleiding...
+
+ F1: Opent de Help-browser met deze handleiding in een afzonderlijk venster.
+
+
+
+ Over...
+
+ Geeft auteursrechten, dankwoorden en licentie-informatie weer.
+
+
+
+
+
+
+
+
+ Toetsenbord sneltoetsen<indexterm class="singular">
+ <primary>Toetsenbord sneltoetsen</primary>
+ </indexterm>
+
+ De volgende sneltoetsen zijn beschikbaar in het hoofdvenster. Als een ander venster op de voorgrond staat, klik dan op het hoofdvenster om het weer op de voorgrond te plaatsen of druk op Esc om dat venster te sluiten.
+
+ Sneltoetsen worden geactiveerd door te drukken op Ctrl en een letter. Sommige sneltoetsen gebruiken ook andere toetsen. Voor de leesbaarheid worden letters hier geschreven als hoofdletters.
+
+ Ctrl wordt gebruikt op Windows, UNIX en UNIX-achtige besturingssystemen die een toetsenbord hebben met de Ctrl / Control-toets. Mac-gebrukers zouden in plaats daarvan de cmd+toets moeten gebruiken. Op toetsenborden van Apple heeft de cmd-toets een label "command" of een Apple-merkteken er op.
+
+
+
+ Projectbeheer
+
+
+
+
+
+ Bewerken
+
+
+
+
+
+ Verplaatsen
+
+
+
+
+
+ Verwijzingsvensters
+
+
+
+
+
+ Andere
+
+
+
+
+ <indexterm class="singular">
+ <primary>Toetsenbord sneltoetsen</primary> <secondary>Project</secondary>
+ </indexterm>Projectbeheer<indexterm class="singular">
+ <primary>Project</primary> <secondary>Sneltoetsen voor projectbeheer</secondary>
+ </indexterm>
+
+
+ Sneltoetsen voor projectbeheer
+
+
+
+
+
+
+
+
+ Project openen
+
+
+ Ctrl
+
+ O
+
+
+ Geeft een dialoogvenster weer om een reeds bestaand project te zoeken.
+
+
+
+ Opslaan
+
+
+ Ctrl
+
+ S
+
+
+ Slaat het huidige werk op in het interne vertaalgeheugen (bestand project_save.tmx dat staat in de map omegat van het project).
+
+
+
+ Project sluiten
+
+
+ Shift
+
+ Ctrl
+
+ W
+
+
+ Sluit het huidige project.
+
+
+
+ Vertaalde documenten maken
+
+
+ Ctrl
+
+ D
+
+
+ Maakt de vertaalde documenten in de map Target van het project en maakt de bestanden voor het vertaalgeheugen (level1, level2 en omegat tmx-bestanden) in de hoofdmap van het project.
+
+
+
+ Projecteigenschappen
+
+
+ Ctrl
+
+ E
+
+
+ Geeft de instellingen voor het project weer om die aan te passen, indien gewenst.
+
+
+
+
+ Sneltoetsen Bewerken
+
+
+
+
+
+
+
+
+ Laatste actie ongedaan maken
+
+
+ Ctrl
+
+ Z
+
+
+ Maakt de laatste actie in het huidige doelsegment ongedaan
+
+
+
+ Laatste actie opnieuw
+
+
+ Ctrl
+
+ Y
+
+
+ Voert opnieuw de laatste bewerking uit die zojuist in het huidige doelsegment ongedaan werd gemaakt
+
+
+
+ Overeenkomst #N selecteren
+
+
+ Ctrl
+
+ #N
+
+
+ #N is een getal van 1 tot en met 5. De sneltoets selecteert de Ne overeenkomst die wordt weergegeven in het venster Overeenkomsten (de eerste overeenkomst wordt standaard geselecteerd)
+
+
+
+ Vervangen door overeenkomst
+
+
+ Ctrl
+
+ R
+
+
+ Vervangt de inhoud van het huidige doelsegment door de geselecteerde overeenkomst (de eerste overeenkomst wordt standaard geselecteerd)
+
+
+
+ Overeenkomst invoegen
+
+
+ Ctrl
+
+ I
+
+
+ Voegt de geselecteerde overeenkomst in op de cursorpositie in het huidige doelsegment (de eerste overeenkomst wordt standaard geselecteerd)
+
+
+
+ Vervangen door bron
+
+
+ Ctrl
+
+ Shift+R
+
+
+ Vervangt de inhoud van het huidige doelsegment door de inhoud van de brontekst
+
+
+
+ Bron invoegen
+
+
+ Ctrl
+
+ Shift+I
+
+
+ Voegt de inhoud van de brontekst in op de cursorpositie in het huidige doelsegment
+
+
+
+ Brontags invoegen
+
+
+ Ctrl
+
+ Shift+T
+
+
+ Voegt de brontags in op de cursorpositie in het huidige doelsegment.
+
+
+
+ Zoeken in project
+
+
+ Ctrl
+
+ F
+
+
+ Geeft een dialoogvenster weer waarmee zoekacties kunnen worden uitgevoerd binnen het project
+
+
+
+ Vervangen door machinevertaling
+
+
+ Ctrl
+
+ M
+
+
+ Vervangt het doelsegment door de machinevertaling van de bron. Geen actie indien machinevertaling is gedeactiveerd (zie Menu > Opties > Machinevertaling).
+
+
+
+ Selectie exporteren
+
+
+ Shift
+
+ Ctrl
+
+ C
+
+
+ Exporteert de huidige selectie naar een tekstbestand voor verwerking.
+
+
+
+ Item voor woordenlijst maken
+
+
+ Shift
+
+ Ctrl
+
+ G
+
+
+ Laat de gebruiker een item maken in het standaard bestand voor de woordenlijst.
+
+
+
+
+ Sneltoetsen Verplaatsen
+
+
+
+
+
+
+
+
+ Volgende niet-vertaalde segment
+
+
+ Ctrl
+
+ U
+
+
+ Verplaatst het bewerkingsveld naar het volgende segment dat nog niet geregistreerd is in het vertaalgeheugen van het project
+
+
+
+ Volgende segment
+
+ CtrlN, Enter of Return
+
+ Verplaatst het bewerkingsveld naar het volgende segment
+
+
+
+ Vorige segment
+
+
+ Ctrl
+
+ P
+
+
+ Verplaatst het bewerkingsveld naar het vorige segment
+
+
+
+ Segmentnummer...
+
+
+ Ctrl
+
+ J
+
+
+ Verplaatst naar het ingevoerde segmentnummer
+
+
+
+ Terug in geschiedenis...
+
+
+ Ctrl
+
+ Shift+P
+
+
+ Verplaats één segment terug in de geschiedenis.
+
+
+
+ Verder in geschiedenis...
+
+
+ Ctrl
+
+ Shift+N
+
+
+ Verplaatst één segment naar voren in de geschiedenis.
+
+
+
+
+ Diverse sneltoetsen
+
+
+
+
+
+
+
+
+ Lijst projectbestanden
+
+
+ Ctrl
+
+ L
+
+
+ Geeft de lijst met projectbestanden weer
+
+
+
+ Tags valideren
+
+
+ Ctrl
+
+ T
+
+
+ Opent het venster Tags valideren.
+
+
+
+ Selectie exporteren
+
+
+ Shift
+
+ Ctrl+C
+
+
+ Exporteert de huidige selectie of de huidige bron, als er geen tekst is geselecteerd. De tekst wordt geëxporteerd naar een bestand met platte tekst.
+
+
+
+ Zoeken in project
+
+
+ Ctrl
+
+ F
+
+
+ Opent een nieuw venster Zoeken.
+
+
+
+ Helpbestanden
+
+ F1
+
+ Geeft de OmegaT helpbestanden weer in een afzonderlijk venster
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/Miscelanea.xml b/OmegaT/doc_src/nl/Miscelanea.xml
new file mode 100644
index 0000000..6c92dcf
--- /dev/null
+++ b/OmegaT/doc_src/nl/Miscelanea.xml
@@ -0,0 +1,212 @@
+
+
+
+ Diverse onderwerpen<indexterm class="singular">
+ <primary>Diversen</primary>
+ </indexterm>
+
+
+ <application><indexterm class="singular">
+ <primary>OmegaT modus console</primary> <seealso>diversen</seealso>
+ </indexterm>OmegaT</application> modus Console<indexterm class="singular">
+ <primary>Diversen</primary> <secondary>OmegaT modus console</secondary>
+ </indexterm>
+
+
+ Alleen van belang voor gevorderde gebruikers!
+
+
+ Het doel van de modus console (d.i. de opdrachtregel) is om het gebruiken van OmegaT als vertaalprogramma in een scriptomgeving mogelijk te maken. Indien gestart in de modus console, wordt geen GUI geladen (het zal daarom op elke console werken) en het opgegeven project wordt automatisch vertaald. Een voorbeeld zou een softwareproject zijn, waarvan de GUI is gelocaliseerd in een aantal talen. Door gebruik te maken van de modus console kan men het maken van een gelocaliseerde interface deel van het bouwproces laten zijn.
+
+
+ Vooraf vereist
+
+ Een geldig project in OmegaT moet aanwezig zijn om OmegaT uit te kunnen voeren. De locatie maakt niet uit omdat het bij de start toch al moet worden ingevuld in de opdrachtregel.
+
+ Indien u geen standaard instellingen wilt gebruiken, moeten de configuratiebestanden (filters.conf en segmentation.conf) aanwezig zijn. Dat kan op twee manieren worden bereikt:
+
+
+
+ Voer OmegaT normaal uit (met de GUI) en maak de instellingen. Indien u OmegaT in console-modus start, zal het de instellingen gebruiken die u hebt geconfigureerd.
+
+
+
+ Indien u OmegaT niet normaal kunt uitvoeren (geen grafische omgeving beschikbaar): kopieer de instellingen vanaf een andere installatie van OmegaT op een andere machine naar een bepaalde map. De locatie maakt niet uit, omdat u die toch in kunt vullen in de opdrachtregel bij het starten (zie hieronder). De relevante bestanden zijn filters.conf en segmentation.conf en kunnen worden gevonden in de startmap van de gebruiker (Bijv. C:\Documents and Settings\%User%\OmegaT onder Windows, %user%/.omegat/ onder Linux)
+
+
+
+
+
+ OmegaT opstarten in modus console
+
+ Enkele extra parameters moeten bij het starten worden opgegeven om OmegaT in modus console te starten. De meest belangrijke is <project-dir>, en optioneel --config-dir=<config-dir>. Voorbeeld:
+
+ $>java -jar OmegaT.jar /pad/naar/project \
+
+ --config-dir=/pad/naar/config-bestanden/ \
+
+ --mode=console-translate \
+
+ --source-pattern={reguliere uitdrukking}
+
+ Uitleg:
+
+
+
+ <project-dir> vertelt OmegaT waar het project kan worden gevonden dat moet worden vertaald. Indien opgegeven start OmegaT in de modus console en zal het opgegeven project gaan vertalen.
+
+
+
+
+
+ --config-dir=<config-dir> maakt het mogelijk OmegaT te instrueren in welke map de configuratiebestanden zijn opgeslagen. Indien niet opgegeven gaat OmegaT terug naar de standaard waarden (de map OmegaT onder de startmap van de gebruiker, of indien niet beschikbaar: de huidige werkmap).
+
+
+
+
+
+ --mode=console-translate OmegaT start in de modus console en vertaalt het opgegeven project
+
+
+
+ --source-pattern={reguliere uitdrukking} De bestanden die moeten worden vertaald kunnen op deze manier worden gespecificeerd. Hier is een voorbeeld van de reguliere uitdrukking: test\.html
+
+
+
+
+
+ optie Quiet
+
+ Een extra parameter voor de opdrachtregel, specifiek voor de console-modus: --quiet.In de modus quiet, wordt er minder informatie gelogd op het scherm. De berichten die u normaal gesproken zou vinden in de statusbalk worden niet weergegeven.
+
+ Gebruik: java -jar OmegaT.jar /pad/naar/project --mode=console-translate --quiet
+
+
+
+ Optie Tags valideren
+
+ Een andere parameter voor de opdrachtregel, specifiek voor de console-modus: --tag-validation=[abort|warn]. Als deze parameter wordt toegevoegd, wordt het valideren van tags toegepast voorafgaande aan vertalen/uitlijnen. Als de waarde abort is dan worden bij tagfouten de fouten afgedrukt en het programma stopt. Als de waarde warn is dan worden fouten afgedrukt maar OmegaT gaat door.
+
+ Gebruik: java -jar OmegaT.jar /pad/naar/project --mode=console-translate --tag-validation=abort
+
+
+
+
+ Automatisch vergelijken van Java-eigenschappen<indexterm class="singular">
+ <primary>Diversen</primary> <secondary>Automatisch vergelijken van Java-eigenschappen</secondary> <seealso>diversen</seealso>
+ </indexterm>
+
+ OmegaT kan Java .properties vergelijken in modus console. Indien u de Properties-bestanden voor bron en doel voor één en dezelfde inhoud in uw taalpaar hebt, zal deze procedure een overeenkomend tmx-bestand maken voor deze inhoud. Gebruik:
+
+ java -jar OmegaT.jar --mode=console-align /my-project-dir
+ --alignDir=/translatedFiles/
+
+ alignDir moet een vertaling bevatten in de doeltaal van het project. (bijvoorbeeld: als het project EN->FR is, moet alignDir een bundle bevatten die eindigt op _fr). De resulterende TMX wordt opgeslagen in de map omegat onder de naam align.tmx.
+
+
+
+ Lettertype-instellingen<indexterm class="singular">
+ <primary>Diversen</primary> <secondary>Lettertype-instellingen</secondary>
+ </indexterm>
+
+ In dit dialoogvenster kan het lettertype worden gedefinieerd dat door OmegaT in de volgende vensters wordt gebruikt:
+
+
+
+ OmegaT hoofdvenster (Bewerken, venster Overeenkomsten, venster Woordenlijst)
+
+
+
+
+
+ venster Zoeken
+
+
+
+
+
+ venster Tags valideren
+
+
+
+ Het dialoogvenster kan worden aangeroepen door het item in het hoofdmenu
+ menu OptiesLettertype...
+ OptiesLettertype.... Het dialoogvenster bevat:
+
+
+
+ Lettertype: keuzelijst om één van de beschikbare lettertypen op uw machine te selecteren
+
+
+
+
+
+ Grootte: bewerken om de grootte van het lettertype te wijzigen
+
+
+
+
+
+ Voorbeeldtekst: veld voor direct voorbeeld van het geselecteerde lettertype
+
+
+
+ Opmerking: In sommige gevallen kan het behoorlijk wat tijd vergen voordat OmegaT de weergave heeft bijgewerkt nadat de lettertype-instelling werd gewijzigd. In het bijzonder wanneer een groot bestand met veel segmenten in de bewerker is geopend en/of trage hardware wordt gebruikt. Merk ook op dat sommige lettertypen zich beter lenen voor bepaalde taalparen dan andere. In het bijzonder, als u vertaalt tussen twee talen met verschillende alfabet/schrijfsystemen (zoals Russisch en Japans), selecteer een lettertype dat voor beide gebruikt kan worden.
+
+
+
+ Gegevensverlies voorkomen<indexterm class="singular">
+ <primary>Diversen</primary> <secondary>Gegevensverlies voorkomen</secondary>
+ </indexterm>
+
+ OmegaT is een robuuste toepassing. U zou echter toch voorzorgen moeten nemen tegen gegevensverlies als u OmegaT gebruikt, net als met elke andere toepassing. Bij het vertalen van uw bestanden slaat OmegaT al uw voortgang op in het vertaalgeheugen project_save.tmx in de submap /omegat van het project.
+
+ OmegaT slaat ook, elke keer als een project wordt geopend of herladen, een kopie van het vertaalgeheugen op in project_save.tmx.JAARMMDDUUMM.bak in dezelfde submap. JAAR is 4-getallen jaar, MM is de maand, DD de dag van de maand, en UU en MM zijn de uren en minuten van wanneer het vorige vertaalgeheugen werd opgeslagen.
+
+ Als u denkt dat u vertaalde gegevens kwijt bent, kunt u de volgende procedure gebruiken om het project te herstellen naar de meest recent opgeslagen status, in de meeste gevallen niet ouder dan ongeveer 10 minuten:
+
+
+
+ sluit het project
+
+
+
+ hernoem het huidige project_save.tmx-bestand naar iets dat u zult onthouden (zoals bijvoorbeeld project_save.tmx.tijdelijk)
+
+
+
+ selecteer de back-up van het vertaalgeheugen dat meest waarschijnlijk de gegevens bevat die u nodig hebt
+
+
+
+ hernoem dat naar project_save.tmx
+
+
+
+ open het project
+
+
+
+ Voorkomen van verlies van belangrijke gegevens:
+
+
+
+ Maak regelmatig kopieën van het bestand /omegat/project_save.tmx naar back-upmedia, zoals CD of DVD.
+
+
+
+ Maak met regelmatige tussenpozen de vertaalde bestanden en controleer of dat vertaalde bestand de laatste versie van uw vertaling bevat, totdat u zich OmegaT eigen hebt gemaakt.
+
+
+
+ Wees in het bijzonder voorzichtig met het maken van wijzigingen in de bestanden in /source terwijl u midden in een project zit. Als het bronbestand wordt gewijzigd nadat u de vertaling bent begonnen, kan het zijn dat OmegaT een segment dat u al vertaald had niet meer kan vinden.
+
+
+
+
+
+ Gebruik om te beginnen deze Helpteksten. Als u tegen problemen aanloopt, post dan een bericht in de OmegaT-gebruikersgroep. Maak er geen probleem van om in uw eigen taal te posten.
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/OmegaT.css b/OmegaT/doc_src/nl/OmegaT.css
new file mode 100644
index 0000000..1893c29
--- /dev/null
+++ b/OmegaT/doc_src/nl/OmegaT.css
@@ -0,0 +1,78 @@
+body {
+ font-family: sans-serif;
+ margin: 1em;
+}
+
+h1, h2, table, dt {
+ color: navy;
+}
+
+h3, h4, ul a {
+ color: green;
+}
+
+code, .code {
+ color: black;
+ background: #ffffcc;
+ border-style: solid;
+ border-width: 1px;
+ border-color: #ffff66;
+ vertical-align: top;
+}
+
+.new {
+ font-size: x-small;
+ color: red;
+ background: yellow;
+}
+
+.updated {
+ font-size: x-small;
+ color: orange;
+}
+
+.note {
+ font-size: small;
+ color: black;
+ background: silver;
+}
+
+.warning {
+ color: red;
+ background: yellow;
+}
+
+.chapter {
+ color: black;
+}
+
+.navbar-top, .navbar-bottom {
+ margin-top: 1em;
+ margin-bottom: 1em;
+}
+
+.rel-p {
+ width: 9%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.rel-n {
+ width: 6%;
+ align: left;
+ valign: center;
+ font-weight: bold;
+}
+
+.nav-link {
+ width: 39%;
+ align: left;
+ valign: center;
+}
+
+.toc-link {
+ width: 7%;
+ align: left;
+ valign: center;
+}
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/OmegaTUsersManual_xinclude full.xml b/OmegaT/doc_src/nl/OmegaTUsersManual_xinclude full.xml
new file mode 100644
index 0000000..3f933ac
--- /dev/null
+++ b/OmegaT/doc_src/nl/OmegaTUsersManual_xinclude full.xml
@@ -0,0 +1,77 @@
+
+
+
+
+ OmegaT - Gebruikershandleiding
+
+ vs
+ Vito
+Smolej
+
+
+
+
+
+ Dit document is de officiële gebruikershandleiding voor OmegaT, het gratis Computer Aided Translation-programma. Het bevat ook instructies voor de installatie.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/PlainText.xml b/OmegaT/doc_src/nl/PlainText.xml
new file mode 100644
index 0000000..6f5ff00
--- /dev/null
+++ b/OmegaT/doc_src/nl/PlainText.xml
@@ -0,0 +1,113 @@
+
+
+
+ Werken met platte tekst<indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>Platte tekst-bestanden</secondary>
+ </indexterm>
+
+
+ Standaard codering<indexterm class="singular">
+ <primary>Standaard codering</primary> <secondary>'platte tekst'-bestanden</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>Standaard codering</secondary>
+ </indexterm>
+
+ 'Platte-tekst'-bestanden - meestal met de extensie .txt - bevatten slechts tekstuele informatie en bieden geen helder gedefinieerde manier om de computer te vertellen welke taal zij bevatten. Het beste dat OmegaT in zo'n geval kan doen, is er van uitgaan dat de tekst is geschreven in de taal die de computer zelf gebruikt. Dit is geen probleem voor bestanden die zijn gecodeerd in Unicode met behulp van een 16-bit tekenset voor codering. Al de tekst echter werd gecodeerd in 8-bit, kan men worden geconfronteerd met de volgende vervelende situatie: in plaats van de tekst weer te geven voor Japanse tekens...
+
+
+
+
+
+
+
+
+
+
+
+ ...zal het systeem het bijvoorbeeld als volgt weergeven:
+
+
+
+
+
+
+
+
+
+
+
+ De computer waarop OmegaT wordt uitgevoerd heeft Russisch als de standaard taal en dus worden de tekens in het Cyrillisch alfabet weergegeven en niet in Kanji.
+
+
+
+ De <application>OmegaT</application>-oplossing<indexterm class="singular">
+ <primary>Standaard codering</primary> <secondary>OmegaT oplossing</secondary>
+ </indexterm>
+
+ Er bestaan in principe drie manieren om dit op te lossen in OmegaT. Zij behelzen allemaal het gebruik van de bestandsfilters in het menu Opties.
+
+
+
+ Wijzig de codering van uw bestanden naar Unicode
+
+
+ open uw bronbestand in een tekstverwerker die zijn codering juist interpreteert en sla het bestand op met de codering "UTF-8". Wijzig de bestandsextensie van .txt naar .utf8. OmegaT zal het bestand automatisch interpreteren als een UTF8-bestand. Dit is de beste algemene alternatief, het bespaart u problemen op de langere termijn.
+
+
+
+
+
+
+ Specificeer de codering voor uw 'platte tekst'-bestanden
+
+
+ - d.i. bestanden met de extensie .txt - : wijzig, in de sectie Tekstbestanden van het dialoogvenster Bestandsfilters, de Codering van bronbestand van <auto> naar de codering die overeenkomt met uw bron .txt-bestand, bijvoorbeeld .jp voor het bovenstaande voorbeeld.
+
+
+
+
+
+
+ Wijzig de extensies van uw 'platte tekst'-bestanden
+
+
+ bijvoorbeeld van .txt naar .jp voor Japanse platte teksten: voeg, in de sectie Tekstbestanden van het dialoogvenster Bestandsfilters, een nieuw Patroon voor bronbestanden toe (*.jp voor dit voorbeeld) en selecteer de toepasselijke parameters voor de bron- en doelcodering.
+
+
+
+
+ OmegaT heeft standaard het volgende lijstje beschikbaar om het voor u eenvoudiger te maken om sommige 'platte tekst'-bestanden te behandelen.
+
+
+
+ .txt-bestanden worden automatisch (<auto>) door OmegaT geïnterpreteerd als zijnde gecodeerd in de standaard codering van de computer.
+
+
+
+
+
+ .txt1-bestanden zijn bestanden in ISO-8859-1, geschikt voor de meeste West-Europese talen.
+ Standaard coderingWesters
+
+
+
+
+
+
+ .txt2-bestanden zijn bestanden in ISO-8859-2, die de meeste Centraal- en Oost-Europese talen ondervangt)
+ Standaard coderingCentraal- en Oost-Europees
+
+
+
+
+
+
+ .utf8 bestanden worden door OmegaT geïnterpreteerd als zijnde gecodeerd in UTF-8 (een codering die bijna alle talen in de wereld ondervangt).
+ Standaard coderingUnicode
+
+
+
+
+ U kunt dat zelf controleren door het item Bestandsfilters te selecteren in het menu Opties. Als u bijvoorbeeld een Tsjechisch tekstbestand (zeer waarschijnlijk geschreven in de code ISO-8859-2) hebt, hoeft u alleen maar de extensie te wijzigen van .txt naar .txt2 en OmegaT zal de inhoud juist interpreteren. Indien u echter op zeker wilt spelen kunt u overwegen om dit soort bestanden te converteren naar Unicode, d.i. naar de bestandsindeling .utf8.
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/ProjectProperties.xml b/OmegaT/doc_src/nl/ProjectProperties.xml
new file mode 100644
index 0000000..aadb6d1
--- /dev/null
+++ b/OmegaT/doc_src/nl/ProjectProperties.xml
@@ -0,0 +1,95 @@
+
+
+
+ Projecteigenschappen<indexterm class="singular">
+ <primary>Project</primary><secondary>eigenschappen</secondary>
+ </indexterm>
+
+
+
+
+ dialoogvenster Eigenschappen
+
+ Het dialoogvenster CtrlEProjecteigenschappen... wordt gebruikt om de projectmappen en talen te definiëren en aan te passen.
+
+
+ venster Projecteigenschappen
+
+
+
+
+
+
+
+
+
+
+
+
+ Het bevat:
+
+
+
+ Een gebied om de bron- en doeltalen van het project met keuzelijsten in te stellen
+
+
+
+
+
+ Een vlag voor de instellingen van de segmentatie
+
+
+
+
+
+ Een gebied voor het instellen van de projectmappen
+
+
+
+ Alle velden zijn te bewerken. U kunt de talen handmatig instellen of het menu met de keuzelijst gebruiken. Indien u namen voor mappen invoert die nog niet bestaan, zal OmegaT ze voor u maken.
+
+
+
+ Projecteigenschappen aanpassen
+
+ Onthoud dat wijzigen van de instellingen voor het project consequenties kan hebben, in het bijzonder als het project al is opgestart.
+
+
+
+ Wijzigen van bron- en doeltalen:
+ ProjectBron- en doeltalen
+
+
+ Onthoud goed dat het wijzigen van de talen er voor kan zorgen dat het de huidige gebruikte vertaalgeheugens onbruikbaar kan maken omdat hun taal niet meer overeenkomt met de nieuwe talen.
+
+
+
+ Aanpassen van segmentatie:
+ ProjectSegmentatie aanpassen
+
+
+ De instellingen voor segmentatie hebben alleen betrekking op de manier waarop de bronbestanden door OmegaT worden afgehandeld. Zij passen niet de segmentatie van de reeds bestaande vertaalgeheugens aan.
+
+ Wijzigingen aan de instellingen voor segmentatie kunnen er voor zorgen dat sommige reeds vertaalde segmenten opgedeeld of samengevoegd worden. Zij zullen dan effectief terugkeren naar de status "niet vertaald" omdat zij niet overeenkomen met de opgenomen segmenten in het projectgeheugen, zelfs als de originele vertaling daar nog steeds in staat.
+
+ OmegaT kan oude vertaalgeheugens bijwerken die geen gebruik maakten van zin-segmentatie, maar niet andersom. Indien u gedurende de vertaling besluit om te schakelen van zin- naar alinea-vertaling, zal het interne vertaalgeheugen van het project niet worden gewijzigd.
+
+
+
+ Wijzigen van de mappenstructuur:
+ ProjectWijzigen van de mappenstructuur
+
+
+ Voor het geval u van plan bent de projectmappen aan te passen, onthoudt dan dat daarmee niet de bestanden uit oude mappen naar de nieuwe worden verplaatst.
+
+
+
+ Aanpassen van projecteigenschappen tijdens de sessie
+ ProjectAanpassen tijdens de sessie
+
+
+ Het is mogelijk om de projecteigenschappen gedurende een vertaalsessie aan te passen. De veiligste manier is echter om, totdat u wat meer ervaring hebt met OmegaT, alle instellingen als vast te beschouwen als de vertaling eenmaal is begonnen - tenzij u zich natuurlijk realiseert dat er een grote vergissing is gemaakt. Zie het gedeelte Gegevensverlies voorkomen voor manieren om uw werk te beveiligen.
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/Regexp.xml b/OmegaT/doc_src/nl/Regexp.xml
new file mode 100644
index 0000000..3a0af14
--- /dev/null
+++ b/OmegaT/doc_src/nl/Regexp.xml
@@ -0,0 +1,565 @@
+
+
+
+ Reguliere uitdrukkingen<indexterm class="singular">
+ <primary>Reguliere uitdrukkingen</primary> <seealso>segmentatie</seealso> <seealso>zoeken</seealso>
+ </indexterm>
+
+ De reguliere uitdrukkingen (of afgekort regex) die worden gebruikt in zoekacties en segmentatieregels zijn die welke worden ondersteund door Java. Als u meer specifieke informatie nodig heeft raadpleeg dan documentatie voor Java Regex. Bekijk de aanvullende verwijzingen en voorbeelden hieronder.
+
+
+ Dit hoofdstuk is bedoeld voor gevorderde gebruikers, die hun eigen varianten van segmentatieregels moeten kunnen definiëren of meer complexe en krachtigere zoeksleutels moeten kunnen opdelen.
+
+
+
+ Regex - Vlaggen
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ (?i)
+
+ Schakelt overeenkomen van hoofd-/kleine letters in (standaard is het patroon hoofdletter-gevoelig).
+
+
+
+
+
+
+ Regex - Teken
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ x
+
+ Het teken x, met uitzondering van het volgende...
+
+
+
+ \uhhhh
+
+ Het teken met de hexadecimale waarde 0xhhhh
+
+
+
+ \t
+
+ Het Tab-teken ('\u0009')
+
+
+
+ \n
+
+ Het teken voor een nieuwe regel (line feed) ('\u000A')
+
+
+
+ \r
+
+ Het teken voor een carriage-return ('\u000D')
+
+
+
+ \f
+
+ Het teken voor form-feed ('\u000C')
+
+
+
+ \a
+
+ Het waarschuwingsteken (bel) ('\u0007')
+
+
+
+ \e
+
+ Het escape-teken ('\u001B')
+
+
+
+ \cx
+
+ Het besturingsteken dat overeenkomt met x
+
+
+
+ \0n
+
+ Het teken met de octale waarde 0n (0 <= n <= 7)
+
+
+
+ \0nn
+
+ Het teken met de octale waarde 0nn (0 <= n <= 7)
+
+
+
+ \0mnn
+
+ Het teken met de octale waarde (0 <= m <= 3, 0 <= n <= 7)
+
+
+
+ \xhh
+
+ Het teken met de hexadecimale waarde 0xhh
+
+
+
+
+
+
+ Regex - Aanhalingen
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ \
+
+ Niets, maar quote het volgende teken. Dit is vereist als u een van de metatekens !$()*+.<>?[\]^{|} zou willen invoeren om overeen te komen als hetzelfde teken.
+
+
+
+ \\
+
+ Dit is bijvoorbeeld het teken voor een backslash
+
+
+
+ \Q
+
+ Niets, maar quote alle tekens tot \E
+
+
+
+ \E
+
+ Niets, maar beëindigt quoten dat werd gestart door \Q
+
+
+
+
+
+
+ Regex - Klassen voor Unicode-blokken en categorieën
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ \p{InGreek}
+
+ Een teken in het Griekse blok (eenvoudig blok)
+
+
+
+ \p{Lu}
+
+ Een hoofdletter (eenvoudige categorie)
+
+
+
+ \p{Sc}
+
+ Een valutasymbool
+
+
+
+ \P{InGreek}
+
+ Elk teken met uitzondering van die in het Griekse blok (negatie)
+
+
+
+ [\p{L}&&[^\p{Lu}]]
+
+ Elke letter met uitzondering van hoofdletters (subtractie)
+
+
+
+
+
+
+ Regex - Tekenklassen
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ [abc]
+
+ a, b, of c (eenvoudige klasse)
+
+
+
+ [^abc]
+
+ Elk teken met uitzondering van a, b, of c (negatie)
+
+
+
+ [a-zA-Z]
+
+ a tot en met z of A tot en met Z inclusief (bereik)
+
+
+
+
+
+
+ Regex - Voorgedefinieerde tekenklassen
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ .
+
+ Elk teken (met uitzondering van regeleinden)
+
+
+
+ \d
+
+ Een getal: [0-9]
+
+
+
+ \D
+
+ Geen getal: [^0-9]
+
+
+
+ \s
+
+ Een teken voor witruimte: [ \t\n\x0B\f\r]
+
+
+
+ \S
+
+ Een teken niet zijnde witruimte: [^\s]
+
+
+
+ \w
+
+ Een woordteken: [a-zA-Z_0-9]
+
+
+
+ \W
+
+ Een teken voor geen-woord: [^\w]
+
+
+
+
+
+
+ Regex - Overeenkomsten voor begrenzingen
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ ^
+
+ Het begin van een regel
+
+
+
+ $
+
+ Het einde van een regel
+
+
+
+ \b
+
+ Een woordgrens
+
+
+
+ \B
+
+ Grens voor geen-woord
+
+
+
+
+
+
+ Regex - Gulzige parameters
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ X?
+
+ X, één maal of helemaal niet
+
+
+
+ X*
+
+ X, nul of meer keren
+
+
+
+ X+
+
+ X, één of meer keren
+
+
+
+
+
+
+ Gulzige parameters zullen overeenkomen met zoveel als voor hen mogelijk is. Bijvoorbeeld: a+? zal overeenkomen met de aaa in aaabbb
+
+
+
+ Regex - Weigerachtige (niet-gulzige) parameters
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ X??
+
+ X, één maal of helemaal niet
+
+
+
+ X*?
+
+ X, nul of meer keren
+
+
+
+ X+?
+
+ X, één of meer keren
+
+
+
+
+
+
+ Weigerachtige (niet-gulzige) parameters zullen overeenkomen met zo weinig als voor hen mogelijk is. a+? zal bijvoorbeeld overeen komen met de eerste a in aaabbb
+
+
+
+ Regex - Logische operatoren
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ XY
+
+ X gevolgd door Y
+
+
+
+ X|Y
+
+ Of X óf Y
+
+
+
+ (XY)
+
+ XY als een enkele groep
+
+
+
+
+
+
+ <indexterm class="singular">
+ <primary>Reguliere uitdrukkingen</primary> <secondary>programma's</secondary>
+ </indexterm>Regex-programma's en voorbeelden van gebruik<indexterm class="singular">
+ <primary>Reguliere uitdrukkingen</primary> <secondary>voorbeelden van gebruik</secondary>
+ </indexterm>
+
+ Er zijn een aantal interactieve programma's beschikbaar om reguliere uitdrukkingen te ontwikkelen en te testen. Zij volgen in het algemeen allemaal hetzelfde patroon (zie hieronder voor een voorbeeld van de Regular Expression Tester): de reguliere uitdrukking (bovenste item) analyseert de zoektekst (tekstvak in het midden), wat de hits oplevert, weergegeven in het tekstvak met het resultaat.
+
+
+ Regex Tester
+
+
+
+
+
+
+
+
+
+
+
+
+ Zie The Regex Coach voor Windows, Linux, Mac, FreeBSD versies van een zelfstandig programma. Dat is vrijwel identiek aan het bovenstaande voorbeeld.
+
+ Een fijne collectie van handige gevallen van reguliere uitdrukkingen kan worden gevonden in OmegaT zelf (zie Opties > Segmentatie). De volgende lijst bevat uitdrukkingen die u misschien handig vindt bij het doorzoeken van het vertaalgeheugen:
+
+
+ Regex - Voorbeelden van reguliere uitdrukkingen in vertalingen
+
+
+
+
+
+
+ Reguliere uitdrukking
+
+ Vindt het volgende:
+
+
+
+
+
+ (\b\w+\b)\s\1\b
+
+ dubbele woorden
+
+
+
+ [\.,]\s*[\.,]+
+
+ komma of een punt, gevolgd door spaties en weer een andere komma of punt
+
+
+
+ \. \s+$
+
+ extra spaties na de punt aan het einde van de regel
+
+
+
+ \s+a\s+[aeiou]
+
+ Engels: woorden, beginnend met een klinker, zouden moeten worden voorafgegaan door "an", niet "a"
+
+
+
+ \s+an\s+[^aeiou]
+
+ Engels: dezelfde controle als hierboven, maar met betrekking tot medeklinkers ("a", niet "an")
+
+
+
+ \s\s+
+
+ meer dan één spatie
+
+
+
+ \.[A-Z]
+
+ Punt, gevolgd door een hoofdletter - mogelijk ontbreekt er een spatie tussen de punt en het begin van een nieuwe regel?
+
+
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/Searches.xml b/OmegaT/doc_src/nl/Searches.xml
new file mode 100644
index 0000000..0e1c23f
--- /dev/null
+++ b/OmegaT/doc_src/nl/Searches.xml
@@ -0,0 +1,141 @@
+
+
+
+ Zoeken<indexterm class="singular">
+ <primary>Zoeken</primary>
+ </indexterm>
+
+
+ venster Zoeken
+
+
+ venster Tekst zoeken<indexterm class="singular">
+ <primary>venster Zoeken</primary> <secondary>voorbeeld</secondary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+
+ De bovenstaande zoekactie vindt alle doelsegmenten waarin twee of meer witruimten - \s\s+ - voorkomen.
+
+
+
+ Zoeken<indexterm class="singular">
+ <primary>Sneltoetsen</primary> <secondary>Ctrl+F - Zoeken</secondary>
+ </indexterm>
+
+ OmegaT verschaft een groot scala aan zoekfuncties. Open het venster Zoeken met CtrlF en voer het woord of de frase waarnaar u wilt zoeken in het vak "Zoeken naar" in. Als alternatief: selecteer een woord of frase ergens in het bewerkingsveld en druk op CtrlF. Het woord of de frase wordt automatisch ingevoegd in het vak "Zoeken naar". U kunt verschillende vensters Zoeken tegelijkertijd geopend hebben, maar sluit ze als u ze niet langer nodig hebt zodat zij uw bureaublad niet vol zetten.
+
+
+
+ Zoeklocatie
+
+ Zoekacties worden standaard uitgevoerd in zowel de bron- als de doelgedeelten van het project, maar u kunt uw zoekactie beperken tot de bron- of het de doeltekst. U kunt zoeken in
+
+
+
+ alleen het project (standaardinstelling)
+
+
+
+
+
+ zowel het project en in de vertaalgeheugens waarnaar wordt verwezen in /tm/ (kies Zoeken in TM's)
+
+
+
+
+
+ één enkel bestand of een map die een aantal bestanden bevat (kies Bestanden zoeken)
+
+
+
+ Bij het zoeken in bestanden (in tegenstelling tot in vertaalgeheugens) zal OmegaT zich beperken tot de bestanden in de indelingen van bronbestanden. Als consequentie daarvan zal OmegaT, hoewel het in staat is om tmx-bestanden te behandelen, die niet opnemen bij zoekacties met Zoeken in bestanden. Indien u
+ Zoekengevorderde opties
+ Gevorderde opties inschakelt, kunt u de zoekactie combineren met de naam van de auteur van de vertaling en het tijdstip waarop de laatste wijziging is gemaakt.
+
+
+
+
+ Jokertekens gebruiken<indexterm class="singular">
+ <primary>Zoeken</primary> <secondary>Jokertekens gebruiken</secondary>
+ </indexterm>
+
+ In zowel exact zoeken als zoeken naar sleutelwoorden kunnen de jokertekens '*' en '?' worden gebruikt. Zorg ervoor dat de optie reguliere uitdrukkingen niet is geselecteerd om jokertekens te gebruiken, omdat '*' en '?' een speciale betekenis hebben in reguliere uitdrukkingen.
+
+
+
+ '*' komt overeen met nul of meer tekens, vanaf de huidige positie in een opgegeven woord tot het einde ervan. De zoekterm 'run*' zal bijvoorbeeld overeenkomen met 'run', 'runs' en 'running'.
+
+
+
+
+
+ '?' komt overeen met exact één teken. 'run?' zal bijvoorbeeld overeenkomen met 'runs' en 'runn' in het woord 'running'.
+
+
+
+ De overeenkomsten zullen in vet blauw worden weergegeven.
+
+
+
+ Zoeken methodes<indexterm class="singular">
+ <primary>Zoeken</primary> <secondary>methoden</secondary>
+ </indexterm>
+
+ Selecteer de methode met behulp van de optieknoppen. U kunt kiezen uit twee methodes om te zoeken:
+
+
+
+ Exact zoeken
+
+
+ Zoekt naar segmenten die de exacte tekenreeks bevatten die u heeft opgegeven. Exact zoeken zoekt naar een frase, d.i. als er meerdere woorden zijn ingevoerd, zullen zij slechts worden gevonden als zij in exact dezelfde volgorde voorkomen. Zoeken naar geopend bestand zal dus alle entiteiten van de tekenreeks geopend bestand vinden, maar niet bestand geopend of geopend invoerbestand.
+
+
+
+
+ Sleutelwoorden zoeken
+
+
+ Zoekt naar segmenten die alle sleutelwoorden bevatten die u heeft opgegeven, in willekeurige volgorde. Selecteer Sleutelwoorden zoeken om te zoeken naar een willekeurig aantal individuele woorden, in willekeurige volgorde. OmegaT zal een lijst weergeven waarin alle segmenten staan waarin alle gespecificeerde woorden voorkomen. Zoeken met sleutelwoord is hetzelfde als zoekacties "met alle woorden" in een internetzoekmachine zoals Google (logische EN). Zoeken met sleutelwoorden naar geopend bestand zal dus alle entiteiten van de tekenreeks open file vinden, en ook bestand geopend, geopend invoer bestand, bestand kan gevaarlijk zijn als geopend, etc..
+
+
+
+
+ Voor elk van deze twee methoden kunt u de volgende drie opties kiezen:
+
+
+
+ hoofdletter gevoelig: het zoeken zal worden uitgevoerd voor de exact opgegeven tekenreeks, d.i. met hoofdletters wordt rekening gehouden.
+
+
+
+ reguliere uitdrukkingen: de tekenreeks zal worden behandeld als een reguliere uitdrukking. Een zoekactie met reguliere uitdrukkingen is een krachtig middel om te zoeken naar tekenreeksen. Het komt overeen met zoeken met jokertekens, maar is veel meer flexibel. De reguliere uitdrukkingen die worden gebruikt in zoekacties zijn die welke worden ondersteund door Java. Zie verder het hoofdstuk over Reguliere uitdrukkingen.
+
+
+
+ zoeken in TM's: vertaalgeheugens in de map tm worden opgenomen in de zoekactie.
+
+
+
+
+
+ Zoekresultaten weergeven
+
+ Door op de knop Zoeken te drukken na het invoeren van een tekenreeks in het zoekveld zullen alle segmenten in het project, die de gezochte tekenreeks bevatten, worden weergegeven. Omdat OmegaT identieke segmenten behandelt als één entiteit wordt alleen het eerste unieke segment getoond.
+
+ De segmenten worden weergegeven in de volgorde waarin zij in het project voorkomen. Vertaalde segmenten worden weergegeven met de originele tekst boven en de vertaalde tekst eronder, niet-vertaalde segmenten worden alleen als bron weergegeven.
+
+ Klikken op een segment opent het in het venster Bewerken om het aan te kunnen passen. Daarna kunt u teruggaan naar het venster Zoeken en naar het volgende gevonden segment gaan, bijvoorbeeld om het te controleren en, indien nodig, de terminologie aan te passen.
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/Segmentation.xml b/OmegaT/doc_src/nl/Segmentation.xml
new file mode 100644
index 0000000..2831fc1
--- /dev/null
+++ b/OmegaT/doc_src/nl/Segmentation.xml
@@ -0,0 +1,171 @@
+
+
+
+ Bronsegmentatie
+
+ Programma's met vertaalgeheugens werken met teksteenheden die segmenten worden genoemd. OmegaT heeft 2 manieren om een tekst te segmenteren: alineasegmentatie en zinsegmentatie (waarnaar ook wel wordt verwezen als “op regels gebaseerde-segmentatie”). Selecteer
+ Projecteigenschappen
+ Projecteigenschappen... uit het hoofdmenu en selecteer het aanwezig keuzevak, of niet, om het type segmentatie te kiezen. Alinea-segmentatie heeft in bepaalde gevallen voordelen, zoals bij bijzonder creatieve of stilistische vertalingen waarin de vertaler de volgorde van gehele zinnen zou willen wijzigen; voor het merendeel van de projecten is echter zin- segmentatie de keuze die wordt geprefereerd, omdat het betere overeenkomsten oplevert vanuit eerdere vertalingen. Als zinsegmentatie is geselecteerd kunt u de regels instellen door
+ ProjectOpties
+ OptiesSegmentatie...te selecteren uit het hoofdmenu.
+
+ Betrouwbare segmentatieregels zijn al beschikbaar voor veel talen, dus is het onwaarschijnlijk dat het voor u nodig is om uw eigen segmentatieregels te schrijven. Aan de andere kant kan deze functionaliteit in speciale gevallen bijzonder handig zijn, waarbij u uw productiviteit kunt verhogen door de segmentatieregels af te stemmen op de tekst die vertaald moet worden.
+
+ Waarschuwing: omdat de tekst afwijkend zal segmenteren nadat filteropties zijn gewijzigd, zult u misschien geheel opnieuw moeten beginnen met vertalen. Tegelijkertijd zullen de eerder gevalideerde segmenten in het vertaalgeheugen van het project worden omgezet naar wezen-segmenten. Als u de segmentatie-opties wijzigt als een project geopend is moet u het project herladen vóórdat de wijzigingen effect hebben.
+
+ OmegaT gebruikt de volgende reeks stappen:
+
+
+
+
+ Segmentatiesegmentatie op niveau van de bron
+ Segmentatie op niveau van de structuur
+
+
+ OmegaT parst eerst de tekst voor segmentatie op niveau van de structuur. Gedurende dit proces wordt alleen de structuur van het brondocument gebruikt om segmenten te maken.
+
+ Tekstbestanden kunnen bijvoorbeeld gesegmenteerd worden op regeleinden, lege regels of helemaal niet gesegmenteerd worden. Bestanden die opmaak bevatten (OpenOffice.org-documenten, HTML-documenten, etc.) worden gesegmenteerd op het blokniveau (alinea)tags. Vertaalbare object-attributen in XHTML of HTML-bestanden kunnen als afzonderlijke segmenten worden geëxtraheerd.
+
+
+
+
+
+ Segmentatiesegmentatie op niveau van zin
+ Segmentatie op niveau van de zin
+
+
+ Nadat het bronbestand in structurele eenheden is gesegmenteerd, zal OmegaT deze blokken verder segmenteren in zinnen.
+
+
+
+
+
+ Segmentatieregels<indexterm class="singular">
+ <primary>Segmentatie</primary> <secondary>regels</secondary>
+ </indexterm>
+
+ Het proces van segmentering kan als volgt worden voorgesteld: de cursor verplaatst zich langs de tekst, één teken per keer. Voor elke cursorpositie wordt elke regel, bestaande uit een Voor- en Na -patroon, in de opgegeven volgorde toegepast en probeert of een van de Voor-patronen geldig is voor alle tekst die links van de cursor staat en het overeenkomende Na-patroon op de tekst rechts van de cursor. Als de regel overeenkomt gaat de cursor ofwel door zonder een einde voor het segment in te voegen (voor de uitzonderingsregel) of er wordt een nieuw einde voor het segment ingevoegd op de cursorpositie (voor de afbreekregels).
+
+ De twee typen regels gedragen zich als volgt:
+
+
+
+
+ Segmentatieregelsafbreekregel
+ Afbreekregel
+
+
+ Verdeelt de brontekst in segmenten. Voorbeeld: "Begrijpt u dat? Ik was er niet zeker van." zou moeten worden gescheiden in twee segmenten. Wat betekent dat er een afbreekregel zou moeten zijn voor "?", indien die wordt gevolgd door spaties en een woord met een hoofdletter. Selecteer het keuzevak Afbreken/Uitzondering om een regel te definiëren als een Afbreekregel.
+
+
+
+
+
+
+
+ Segmentatieregelsuitzonderingsregel
+ Uitzonderingsregel
+
+
+ specificeer welke gedeelten van de tekst NIET zouden moeten worden gescheiden. Niettegenstaande de punt zou "Mrs. Dalloway " niet moeten worden gesplitst in twee segmenten, dus zou een uitzonderingsregel gemaakt moeten worden voor Mrs (en voor Mr, voor Dr, voor prof etc), gevolgd door een punt. Selecteer NIET het keuzevak Afbreken/Uitzondering om een regel te definiëren als een Uitzonderingsregel.
+
+
+
+
+ De voorgedefinieerde afbreekregels zouden voldoende moeten zijn voor de meeste Europese talen en Japans. Gelet op de flexibiliteit kunt u overwegen om meer uitzonderingsregels te definiëren voor de taal waaruit u vertaald om u meer betekenisvolle en samenhangende segmenten te geven.
+
+
+
+ Prioriteit van regels<indexterm class="singular">
+ <primary>Segmentatie</primary> <secondary>prioriteit van regels</secondary>
+ </indexterm>
+
+ Alle segmentatieregels die zijn ingesteld voor een overeenkomend taalpatroon zijn actief en worden toegepast in de opgegeven volgorde van prioriteit, dus regels voor een specifieke taal zouden hoger moeten staan dan de standaardregels. Regels voor Canadees Frans (FR-CA) zouden bijvoorbeeld hoger moeten staan dan de regels voor Frans (FR.*) en hoger dan de standaardregels (.*). Dus, bij het vertalen vanuit Canadees Frans worden de regels voor Canadees Frans - indien aanwezig - eerst worden toegepast, gevolgd door de regels voor Frans en tenslotte de standaard regels.
+
+
+
+ Een nieuwe regel maken<indexterm class="singular">
+ <primary>Segmentatie</primary> <secondary>een nieuwe regel maken</secondary> <seealso>reguliere uitdrukkingen</seealso>
+ </indexterm>
+
+ Grote wijzigingen aan de segmentatieregels zouden in het algemeen moeten wordne vermeden, speciaal na het voltooien van een eerste gang, maar kleinere wijzigingen, zoals het toevoegen van een herkende afkorting, kan voordelen bieden.
+
+ Klik eenvoudigweg op een verzameling van regels in de bovenste tabel om die te bewerken of uit te breiden. De regels voor die verzameling zullen in het onderste gedeelte van het venster verschijnen.
+
+ Klik op Toevoegen in het bovenste gedeelte van het dialoogvenster, om een lege verzameling van regels te maken voor een nieuw taalpatroon. Een lege regel zal aan de onderzijde van de bovenste tabel verschijnen (u moet misschien naar beneden scrollen om die te zien). Wijzig de naam van de regelverzameling en het taalpatroon naar die van de betrokken taal en de code daarvan (zie voor een lijst van taalcodes). De syntaxis van het taalpatroon komt overeen met de syntaxis voor reguliere uitdrukkingen. Als uw regelverzameling een taal/land-paar betreft raden wij u aan om het naar boven te verplaatsen met de knop Naar boven.
+
+ Voeg de patronen Voor en Na toe. Het wordt aangeraden om programma's te gebruiken die het mogelijk maken de effecten direct te zien om de syntaxis en de toepasbaarheid te controleren. Zie het hoofdstuk over Reguliere uitdrukkingen. Een goed startpunt zullen altijd de bestaande regels zijn.
+
+
+
+ <indexterm class="singular">
+ <primary>Segmentatie</primary> <secondary>voorbeelden</secondary>
+ </indexterm>Een paar eenvoudige voorbeelden
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Bedoeling
+
+ Vóór
+
+ Na
+
+ Opmerking
+
+
+
+
+
+ Stel een segment in na een punt ('.') en vóór een spatie
+
+ \.
+
+ \s
+
+ "\." betekent het teken "." "\s" betekent elk teken voor witruimte ((spatie, tab, nieuw pagina etc.)
+
+
+
+ Niet segmenteren na Mr.
+
+ Mr\.
+
+ \s
+
+ Dit is een uitzonderingsregel, dus het keuzevak voor de regel moet niet zijn geselecteerd
+
+
+
+ Stel een segment in na "。" (Japanse punt)
+
+ 。
+
+
+
+ Let er op dat Na leeg is
+
+
+
+ Niet segmenteren na M. Mr. Mrs. en Ms.
+
+ Mr??s??\.
+
+ \s
+
+ Uitzonderingsregel - zie het gebruik van ? in reguliere uitdrukkingen
+
+
+
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/Spellchecker.xml b/OmegaT/doc_src/nl/Spellchecker.xml
new file mode 100644
index 0000000..8757b8e
--- /dev/null
+++ b/OmegaT/doc_src/nl/Spellchecker.xml
@@ -0,0 +1,95 @@
+
+
+
+ Spellingscontrole<indexterm class="singular">
+ <primary>Spellingscontrole</primary>
+ </indexterm>
+
+ OmegaT heeft een ingebouwde spellingscontrole die is gebaseerd op de spellingscontrole die wordt gebruikt in OpenOffice.org, Firefox en Thunderbird. Als consequentie daarvan is het in staat om het grote aantal gratis woordenboeken voor spelling te gebruiken die beschikbaar is voor die toepassingen.
+
+
+ Installeren van woordenboeken voor spelling
+
+ Voordat de functie Spellingscontrole kan worden gebruikt moet een geschikt woordenboek of woordenboeken (voor uw doeltaal) zijn geïnstalleerd. Volg deze procedure om woordenboeken te installeren:
+
+
+
+ Maak, in uw bestandsbeheerder, een nieuwe map op een geschikte locatie waarin uw woordenboeken voor de spelling kunnen worden opgeslagen.
+
+
+
+
+
+ Selecteer, in OmegaT,
+ menu Optiesspellingscontrole...
+ Opties > Spellingscontrole, en klik dan op Kiezen naast het veld map Woordenboek-bestand. Navigeer naar en selecteer de map die u hebt gemaakt voor de woordenboeken.
+
+
+
+
+
+ Plaats de bestanden voor de woordenboeken die u wilt gebruiken in deze map. Er bestaan in essentie twee manieren waarop u dit kunt doen. U kunt ofwel de bestanden handmatig kopiëren, d.i. van elders op uw systeem, met behulp van uw bestandsbeheerder; of u kunt de functie "Installeren" van OmegaT gebruiken om een lijst te verschaffen met beschikbare woordenboeken, waaruit kan worden gekozen. Onthoud dat de functie "Installeren" een internetverbinding nodig heeft. De geselecteerde talen zullen dan worden geïnstalleerd en verschijnen uiteindelijk in het venster Instellen spellingscontrole (dit kan even duren).
+
+
+
+ Handmatig kopiëren van de bestanden is handig als u al geschikte bestanden voor de woordenboeken op uw systeem heeft staan, bijvoorbeeld als deel van uw installatie van OpenOffice.org of Thunderbird. De bestanden die u nodig heeft hebben de extensies .aff en .dic, en u hebt beide bestanden nodig om het betrokken woordenboek te kunnen laten werken. U kunt die bestandsextensies gebruiken om op uw computer te zoeken naar geschikte woordenboeken. In het geval hieronder is geen extra map gemaakt en was het kopiëren van bestanden niet nodig, omdat in plaats daarvan de map van het woordenboek van OpenOffice.org is gebruikt:
+
+
+ Opties voor spellingscontrole
+
+
+
+
+
+
+
+
+ Onthoud dat u in het geval hierboven de woordenboeken voor de spelling kunt verliezen als de installatie van OpenOffice.org van uw systeem wordt verwijderd. Maken van uw eigen map en het kopiëren van de bestanden kan wat extra werk betekenen, maar het is misschien de moeite waard.
+
+ Meer recente woordenboeken voor de spelling van OpenOffice.org worden geleverd als "OpenOffice.org extensies", met de bestandsnaamextensie .oxt. Dit zijn echter ziparchieven: indien u het bestand hernoemt met de extensie .zip, kunt u de inhoud extraheren in een zip-programma, en u zult de .aff- en .dic-bestanden vinden die u nodig hebt, die u dan kunt plaatsen in de map die u ervoor hebt gemaakt.
+
+ Onthoud alstublieft dat de toepassing achter de knop "Installeren" afhankelijk is van de lijst met woordenboeken op het internet. Indien die gedateerd is of de gewenste taal niet beschikbaar is zult u zelf moeten zoeken naar de toepasselijke woordenboeken. OpenOffice.org bevat waarschijnlijk de grootste collectie woordenboeken op de site OpenOffice.org Extensions. Nadat de extensie met het woordenboek is gedownload en geïnstalleerd, zullen de corresponderende aff en dic beschikbaar komen. Hetzelfde kan worden bereikt door een extensie voor spellingscontrole toe te voegen aan Firefox of Thunderbird; in dit geval zullen de bestanden van de spellingscontrole worden opgeslagen in uw profiel (Firefox of Thunderbird).
+
+ Zorg er voor dat de taalcode van de doelbestanden correspondeert met de taalcode van het woordenboek: een FR-FR woordenboek zal niet werken met de instelling FR voor het doel. U zult de instelling naar FR-FR moeten wijzigen om de spellingscontrole het juiste woordenboek voor uw doel te laten herkennen. Zoek naar bestanden met de naam, verwijzend naar de gebruikte taal en die de extensies aff en dic. hebben.
+
+
+
+ Woordenboeken voor spelling gebruiken
+
+ Het is niet nodig om OmegaT te instrueren om een bepaald woordenboek voor de spellingscontrole te gebruiken; OmegaT zal het juiste taalwoordenboek gebruiken gebaseerd op de taalcodes van uw project. Controleer echter dat de taalcodes exact hetzelfde zijn: een FR-FR woordenboek zal bijvoorbeeld niet werken met de instelling FR voor het doel. Bewerk, indien nodig, de bestandsnamen van het woordenboek of wijzig de taalinstellingen van uw project.
+
+ Selecteer Opties > Spellingscontrole en selecteer het keuzevak Automatische spellingscontrole (zie boven) om de spellingscontrole in te schakelen.
+
+
+ <indexterm class="singular">
+ <primary>Spellingscontrole</primary> <secondary>Spellingscontrole - afbeelding</secondary>
+ </indexterm>Spellingscontrole in actie
+
+
+
+
+
+
+
+
+
+
+
+
+ Klikken met rechts op een onderstreept woord (distriberen in de afbeelding hierboven) opent een menu met keuzelijst met suggesties voor de correctie (distribueren). U kunt de spellingscontrole instrueren om, alle keren dat het woord verkeerd gespeld voorkomt, alles te negeren of het aan het woordenboek toe te voegen.
+
+
+
+ Hints<indexterm class="singular">
+ <primary>Spellingscontrole</primary> <secondary>hints</secondary>
+ </indexterm>
+
+ Als de spellingscontrole niet werkt, zorg er dan eerst voor dat het keuzevak "Automatische spellingscontrole" in het dialoogvenster van de spellingscontrole (Opties > Spellingscontrole...) is geslecteerd.
+
+ Controleer de taalcode van uw doel met de beschikbare woordenboeken in het venster Instellen spellingscontrole. De spellingscontrole bepaalt de taal die het moet gebruiken uit de taalcode van het doel: als de taalcode voor het doel Braziliaans Portugees (PT_BR) is, moet de submap met woordenboeken de twee bestanden voor het woordenboek, genaamd pt_br.aff en pt_br.dic, bevatten.
+
+ In het geval dat u al een groot gedeelte van de tekst heeft vertaald, maar zich dan realiseert dat de taalcode van het project niet overeenkomt met de taalcode van de spellingscontrole (u specificeerde pt_BR als de taal, maar er zijn geen pt_BR-woordenboeken) kunt u eenvoudigweg de twee corresponderende bestanden kopiëren en die hernoemen (bijvoorbeeld van pt_PT.arr en pt_PT.dic naar pt._BR.arr en pt_BR.dic). Natuurlijk is het veel verstandiger om een korte pauze te nemen en de juiste versies van de spellingscontrole te downloaden.
+
+ Merk op dat Verwijderen de geselecteerde woordenboeken fysiek verwijdert. Als zij, zoals in het bovenstaande geval, deel uitmaken van OpenOffice.org zullen zij ook uit die toepassing verdwijnen. Indien u dat, om welke reden dan ook, zo nu en dan moet doen, kan het daarom verstandiger zijn om de betrokken bestanden te kopiëren naar een andere map, alleen gereserveerd voor gebruik door OmegaT.
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/TranslationMemories.xml b/OmegaT/doc_src/nl/TranslationMemories.xml
new file mode 100644
index 0000000..cd53201
--- /dev/null
+++ b/OmegaT/doc_src/nl/TranslationMemories.xml
@@ -0,0 +1,245 @@
+
+
+
+ Vertaalgeheugens<indexterm class="singular">
+ <primary>Vertaalgeheugens</primary>
+ </indexterm>
+
+
+ Vertaalgeheugens in OmegaT
+
+
+ mappen tmx - locatie en doel
+
+ Projecten van OmegaT kunnen bestanden voor vertaalgeheugens bevatten - dit zijn bestanden met de extensie tmx - op vier verschillende plaatsen:
+
+
+
+
+ Vertaalgeheugenssubmap omegatprojectbestanden
+ map omegat
+
+
+ De map omegat bevat project_save.tmx en mogelijk een aantal back-ups van TMX-bestanden. Het bestand project_save.tmx bevat alle segmenten die in het geheugen zijn opgenomen sinds u het project startte. Dit bestand bestaat altijd in een project. De inhoud ervan zal altijd alfabetisch worden gesorteerd op het bronsegment.
+
+
+
+
+
+ Vertaalgeheugenshoofdmap project
+ hoofdmap project
+
+
+ De hoofdmap van het project bevat 3 tmx-bestanden, project_naam-omegat.tmx, project_naam-level1.tmx en project_naam-level2.tmx (waarin project_naam de naam is van uw project).
+
+
+
+ Het bestand level1 bevat alleen tekstuele informatie.
+
+
+
+ Het bestand level2 kapselt specifieke tags van OmegaT in binnen correcte TMX-tags zodat het bestand met zijn opmaakinformatie kan worden gebruikt in een vertaalprogramma dat TMX niveau 2-geheugens ondersteund of OmegaT zelf.
+
+
+
+ Het bestand OmegaT is inclusief OmegaT specifieke opmaaktags zodat het bestand kan worden gebruikt in andere OmegaT-projecten
+
+
+
+ Deze bestanden zijn kopieën van het bestand project_save.tmx, d.i. van het belangrijkste vertaalgeheugen van het project, exclusief de zogenaamde wezen-segmenten. Zij dragen toepasselijk gewijzigde namen, zodat de inhoud ervan steeds kan worden geïdentificeerd, indien elders gebruikt, bijvoorbeeld in de submap tm van een ander project (zie hieronder).
+
+
+
+
+ map
+ Vertaalgeheugenssubmap tmprojectbestanden
+ tm
+
+
+ De map /tm/ kan een willekeurig aantal aanvullende vertaalgeheugens bevatten - d.i. tmx-bestanden. Zulke bestanden kunnen worden gemaakt in elk van de drie hierboven aangegeven variëteiten. Onthoud dat andere CAT-programma's tmx-bestanden kunnen exporteren (en ook importeren), gewoonlijk in alle drie vormen. Het beste is natuurlijk om OmegaT-specifieke TMX-bestanden te gebruiken (zie hierboven), zodat de in-regelige opmaak binnen het segment wordt behouden.
+
+ De inhoud van vertaalgeheugens in de submap tm dienen om suggesties te genereren voor de tekst(en) om te worden vertaald. Elke tekst, reeds vertaald en opgeslagen in deze bestanden, zal tussen de overeenkomsten verschijnen, indien het voldoende overeenkomt met de tekst die momenteel wordt vertaald.
+
+ Indien het bronsegment in één van de aanvullende TM's identiek is aan de tekst die wordt vertaald, gedraagt OmegaT zich zoals gedefinieerd is in het dialoogvenster OptiesBewerken (gedrag).... Bijvoorbeeld (als de standaard is geaccepteerd) zal de vertaling vanuit de aanvullende TM worden geaccepteerd en worden vooraf gegaan door [fuzzy], zodat de vertaler de vertalingen op een later tijdstip kan nakijken en controleren of segmenten die op deze manier zijn getagd, juist zijn vertaald (zie het hoofdstuk Bewerken (gedrag)) .
+
+
+
+
+
+ Vertaalgeheugenssubmap tm/autoprojectbestanden
+ map tm/auto
+ Projectvooraf vertalen
+
+
+
+ Als het vanaf het begin duidelijk is dat de vertalingen in een bepaald TM (of TM's) allemaal juist zijn, kan één van hen in de map tm/auto worden geplaatst en heel veel van de gevallen van bevestiging met [fuzzy] worden voorkomen. Dit zal de brontekst effectief vooraf vertalen : alle segmenten in de brontekst, waarvoor vertalingen kunnen worden gevonden in deze "auto"-TM's, zullen zonder interventie van de gebruiker belanden in de belangrijkste TM van het project.
+
+
+
+
+ Optioneel kunt u OmegaT een aanvullend tmx-bestand laten hebben (OmegaT-opmaak) waar u dat maar wilt, dat alle te vertaalbare segmenten van het project bevat. Zie pseudo-vertaald geheugen hieronder.
+
+ Onthoud dat alle vertaalgeheugens in het geheugen worden geladen bij het openen van het project. Back-ups worden regelmatig van het vertaalgeheugen van het project gemaakt (zie het volgende hoofdstuk) en project_save.tmx wordt ook opgeslagen/bijgewerkt als het project wordt gesloten of opnieuw geladen. Dit betekent bijvoorbeeld dat u het project waarin u momenteel werkt niet behoeft te verlaten als u besluit om er een andere aanvullende TM aan toe te voegen: u kunt eenvoudigweg het project opnieuw laden, en de wijzigingen die u hebt gemaakt zullen daarin worden opgenomen.
+
+ De locaties van de verschillende vertaalgeheugens voor een bepaald project zijn door de gebruiker gedefinieerd (zie dialoogvenster Project in gids Snel starten)
+
+ Afhankelijk van de situatie zijn dus verschillende strategieën mogelijk, bijvoorbeeld:
+
+ diverse projecten over hetzelfde onderwerp: behoud de projectstructuur en wijzig mappen voor bron en doel (Bron = bron/volgorde1, doel = doel/volgorde1 etc). Onthoud dat u segmenten uit volgorde1, die niet aanwezig zijn in volgorde2 en andere opvolgende taken, zullen worden getagd als wezen-segmenten; echter, zij zullen nog steeds handig zijn om overeenkomsten te verkrijgen.
+
+ verschillende vertalers werken aan hetzelfde project: splits de bronbestanden in bron/Alice, bron/Bob... en geef ze uit aan de leden van het team (Alice, Bob ...). Zij kunnen dan hun eigen projecten maken en hun eigen project_save.tmx, inleveren indien voltooid of wanneer een bepaalde mijlpaal is bereikt. De bestanden project_save.tmx worden dan verzameld en mogelijke conflicten met betrekking tot bijvoorbeeld terminologie worden opgelost. Een nieuwe versie van de hoofd-TM wordt dan gemaakt, ofwel om in de submappen tm/auto van de teamleden te worden geplaatst of om hun bestanden project_save.tmx in hun projecten te vervangen. Het team kan ook dezelfde structuur voor de submappen gebruiken voor de doelbestanden. Dit maakt het voor hen bijvoorbeeld mogelijk om op elk moment te controleren, of de doelversie voor het gehele project nog steeds OK is.
+
+
+
+ TMX back-up<indexterm class="singular">
+ <primary>Vertaalgeheugens</primary> <secondary>back-up</secondary>
+ </indexterm>
+
+ Tijdens het vertalen van uw bestanden slaat OmegaT uw werk op in project_save.tmx in de submap /omegat van het project.
+
+ OmegaT maakt ook, elke keer als een project wordt geopend of herladen, een back-up van het vertaalgeheugen in project_save.tmx.JAARMMDDUUMM.bak in dezelfde submap. JAAR is 4-getallen jaar, MM is een maand, DD dag van de maand, UU en MM zijn uren en minuten van wanneer het vorige vertaalgeheugen werd opgeslagen.
+
+ Als u denkt dat u vertaalde gegevens kwijt bent, volg dan de volgende procedure:
+
+
+
+ Sluit het project
+
+
+
+ Hernoem het huidige project_save.tmx-bestand naar iets dat u zult onthouden (zoals bijvoorbeeld project_save.tmx.tijdelijk)
+
+
+
+ Selecteer de back-up van het vertaalgeheugen dat meest waarschijnlijk (bijv. de meest recente of de laatste versie van de dag ervoor) de gegevens bevat die u nodig hebt
+
+
+
+ Kopieer het als project_save.tmx
+
+
+
+ Open het project
+
+
+
+
+
+ TMX-bestanden en taal<indexterm class="singular">
+ <primary>Vertaalgeheugens</primary> <secondary>taal</secondary>
+ </indexterm>
+
+ TMX-bestanden bevatten vertaaleenheden die zijn gemaakt van een aantal equivalente segmenten in verschillende talen. Een vertaaleenheid bestaat uit ten minste twee variaties van een vertaaleenheid (tuv). Beide kunnen als bron of doel worden gebruikt.
+
+ De instellingen in uw project geven aan wat de bron- en wat de doeltaal is. OmegaT neemt dus de tuv-segmenten die overeenkomen met de taalcodes van de bron en het doel in het project en gebruiken ze respectievelijk als de bron- en doelsegmenten. OmegaT herkent de taalcodes met behulp van de twee volgende standaard conventies:
+
+
+
+ 2 letters (bijv. JA voor Japans), of
+
+
+
+ 2- of 3-letter taalcode gevolgd door de 2-letter landcode (bijv. EN-US - Zie voor een gedeeltelijke lijst van taal- en landcodes).
+
+
+
+ Als de taalcodes en de TMX-taalcodes voor het project volledig overeenkomen worden de segmenten in het geheugen geladen. Als de taal overeenkomt, maar niet de landcode worden de segmenten toch geladen. Als de taalcode, noch de landcode overeenkomen zullen de segmenten worden genegeerd.
+
+
+
+ Wezen-segmenten<indexterm class="singular">
+ <primary>Vertaalgeheugens</primary> <secondary>wezen-segmenten</secondary>
+ </indexterm>
+
+ Het bestand project_save.tmx bevat alle segmenten die zijn vertaald sinds u het project startte. Als u de segmentatie van het project aanpast of bestanden uit de bron verwijdert, zullen sommige overeenkomsten in het venster Overeenkomsten kunnen verschijnen als wezen-tekenreeksen: zulke overeenkomsten verwijzen niet langer naar segmenten die voorkomen in de brondocumenten, omdat zij overeenkomen met segmenten die werden vertaald en opgenomen vóór de aanpassingen plaats vonden.
+
+
+
+
+ Vertaalgeheugens opnieuw gebruiken<indexterm class="singular">
+ <primary>Vertaalgeheugens</primary> <secondary>importeren en exporteren</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Vertaalgeheugens</primary> <secondary>vertaalgeheugens opnieuw gebruiken</secondary>
+ </indexterm>
+
+ In het begin, dat is als het project wordt gemaakt, is de hoofd-TM van het project, project_save.tmx, leeg. Deze TM wordt gedurende de vertaling gevuld. Bestaande vertalingen kunnen worden gebruikt om dit proces te versnellen. Indien een bepaalde zin al eens is vertaald, en juist is vertaald, bestaat er geen reden om die opnieuw te gaan vertalen. Vertaalgeheugens kunnen ook vertaalgeheugens als verwijzingen bevatten: meertalige wetgeving, zoals van de Europese Gemeenschap is daarvan een typisch voorbeeld.
+
+ Wanneer u de doeldocumenten maakt in een project van OmegaT, wordt het vertaalgeheugen van het project uitgevoerd in de vorm van drie bestanden in de hoofdmap van uw project van OmegaT (zie de bovenstaande beschrijving). U kunt deze drie TMX-bestanden, (-omegat.tmx", "-level1.tmx" en "-level2.tmx"), beschouwen als een "exporteerbaar vertaalgeheugen", dat is: een export van de inhoud van uw huidige project in tweetalige vorm.
+
+ Indien u een vertaalgeheugen uit een vorig project zou willen gebruiken (bijvoorbeeld omdat het nieuwe project overeenkomt met het eerdere project, of terminologie gebruikt die eerder gebruikt is), kunt u deze vertaalgeheugens gebruiken als "invoer vertaalgeheugens", dat is: om in uw nieuwe project te importeren. In dit geval plaats u de vertaalgeheugens die u wilt gebruiken in de mappen \tm of \tm\auto van uw nieuwe project: in het eerste geval zult u hits van deze vertaalgeheugens in het venster Overeenkomsten krijgen en in het laatste geval zullen deze TM's worden gebruikt om uw brontekst vooraf te vertalen.
+
+ Standaard staat de map \tm onder de hoofdmap van het project (bijvoorbeeld ...\MijnProject\tm), maar u kunt een andere map kiezen in het dialoogvenster Projecteigenschappen als u dat wilt. Dit is handig als u regelmatig eerder gemaakte vertaalgeheugens gebruikt, bijvoorbeeld omdat zij over hetzelfde onderwerp gaan of voor dezelfde klant zijn. In dit geval zou een handige procedure zijn:
+
+
+
+ Maak een map (een "voorraadmap") op een handige locatie op uw harde schijf voor de vertaalgeheugens voor een bepaalde klant of onderwerp.
+
+
+
+
+
+ Elke keer als u een project voltooid, kopieert u één van de drie "exporteerbare" bestanden van vertaalgeheugens vanuit de map van het project naar de voorraadmap.
+
+
+
+
+
+ Als u een nieuw project begint voor hetzelfde onderwerp of voor dezelfde klant, navigeer naar de voorraadmap in het dialoogvenster Project > Eigenschappen > Project bewerken en selecteer het als de map voor het vertaalgeheugen.
+
+
+
+ Onthoud wel dat alle TMX-bestanden in de voorraadmap /tm worden geparset als het project wordt geopend, dus door daarin alle verschillende vertaalgeheugens die u voorhanden hebt te plaatsen, kan OmegaT onnodig langzamer maken. U zou zelfs kunnen overwegen om die, welke u niet meer nodig hebt, te verwijderen, als u eenmaal hun inhoud hebt gebruikt om het bestand project-save.tmx te vullen.
+
+
+ Importeren en exporteren van vertaalgeheugens
+
+ OmegaT ondersteunt geïmporteerde tmx-versies 1.1-1.4b (zowel niveau 1 als niveau 2). Dit maakt het mogelijk dat vertaalgeheugens die zijn gemaakt door andere programma's kunnen worden gelezen door OmegaT. OmegaT ondersteunt echter niet volledig geïmporteerde TMX-bestanden van niveau 2 (die niet alleen de vertaling opslaan, maar ook de opmaak). TMX-bestanden van niveau 2 kunnen nog steeds worden geïmporteerd en hun tekstuele inhoud kan worden bekeken in OmegaT, maar de kwaliteit van de overeenkomsten zal wat lager zijn.
+
+ OmegaT volgt zeer strikte procedures bij het laden van bestanden van vertaalgeheugens (TMX-bestanden). Als een fout in een dergelijk bestand wordt gevonden zal OmegaT de positie aangeven binnen het defecte bestand waarin de fout zich bevindt.
+
+ Sommige programma's staan er om bekend dat zij onder bepaalde omstandigheden ongeldige TMX-bestanden maken. Als u dergelijke bestanden als verwijzingen voor vertalingen in OmegaT wilt gebruiken, moeten zij worden gerepareerd of OmegaT zal een fout rapporteren en het weigeren te laden. Reparaties zijn kleine bewerkingen en OmegaT assisteert bij het oplossen van problemen met het gerelateerde foutbericht. U kunt advies aan de gebruikersgroep vragen als u problemen ondervindt.
+
+ OmegaT exporteert versie 1.4 TMX-bestanden (zowel niveau 1 en niveau 2). De export van niveau 2 komt niet volledig overeen met de standaard van niveau 2 maar is goed genoeg en zal correcte overeenkomsten genereren in andere programma's met vertaalgeheugens die TMX niveau 2 ondersteunen. Als u alleen tekstuele informatie wilt (en geen opmaakinformatie) gebruik dan het bestand van niveau 1 dat OmegaT heeft gemaakt.
+
+
+
+
+ Pseudo-vertaald geheugen<indexterm class="singular">
+ <primary>Vertaalgeheugens</primary> <secondary>pseudo-vertaling</secondary>
+ </indexterm>
+
+
+ Alleen van belang voor gevorderde gebruikers!
+
+
+ Voordat segmenten worden vertaald wilt u ze misschien vooraf verwerken of op een andere manier behandelen dan met OmegaT mogelijk is. Als u bijvoorbeeld een pseudo-vertaling wilt maken om te testen, maakt OmegaT het u mogelijk om een aanvullend TMX-bestand te maken file dat alle segmenten van het project bevat. De vertaling in die tmx kan zijn
+
+
+
+ vertaling komt overeen met bron (standaard)
+
+
+
+
+
+ vertaalde segment is leeg
+
+
+
+ Het TMX-bestand mag elke naam hebben die u op wil geven. Een pseudo-vertaald geheugen kan worden gegenereerd met de volgende parameters voor de opdrachtregel:
+
+ java -jar omegat.jar --pseudotranslatetmx=<bestandsnaam> [pseudotranslatetype=[equal|empty]]
+
+ Vervang <bestandsnaam> door de naam van het bestand dat u wilt maken, ofwel absoluut of relatief naar de werkmap (de map van waaruit u OmegaT start). Het tweede argument --pseudotranslatetype is optioneel. De waarde ervan is ofwel equal (standaard waarde, voor bron=doel) of empty (doelsegment is leeg). U kunt de gemaakte tmx verwerken met elk programma dat u wilt. Hernoem het naar project_save.tmx en plaats het in de map omegat van uw project om het opnieuw in OmegaT te gebruiken.
+
+
+
+ Vertaalgeheugens bijwerken<indexterm class="singular">
+ <primary>Vertaalgeheugens</primary> <secondary>bijwerken naar zinsegmentatie</secondary>
+ </indexterm>
+
+ Hele vroege versies van OmegaT waren slechts in staat bronbestanden in alinea's te segmenteren en nummerden de opmaaktags in HTML- en Open Document-bestanden niet consistent. OmegaT 2.5 kan dergelijke TMX-bestanden herkennen en direct bijwerken om de kwaliteit van de fuzzy overeenkomsten te vergroten en uw vertaling op peil te brengen, zodat u dat werk niet handmatig hoeft te doen.
+
+ De TMX van een project wordt maar één keer bijgewerkt en zal in de bijgewerkte vorm worden weggeschreven in project-save.tmx; eerder gemaakte TMX-bestanden worden, elke keer als het project wordt geladen, direct bijgewerkt. Wees er attent op dat sommige wijzigingen in bestandsfilters in OmegaT 2.5 zouden kunnen leiden tot totaal afwijkende segmentatie; als resultaat daarvan moet u in zulke zeer uitzonderlijke gevallen uw vertaling handmatig bijwerken.
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/UserInterface.xml b/OmegaT/doc_src/nl/UserInterface.xml
new file mode 100644
index 0000000..41bb590
--- /dev/null
+++ b/OmegaT/doc_src/nl/UserInterface.xml
@@ -0,0 +1,654 @@
+
+
+
+ De gebruikersinterface
+
+
+ Items in de gebruikersinterface
+
+
+ Veel gebruikte vensters<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary>
+ </indexterm>
+
+
+
+ OmegaT hoofdvenster
+
+
+ bevat het hoofdmenu, statusbalk en verschillende vensters:
+
+
+
+ Bewerken - waar u uw vertaling typt en bewerkt
+
+
+
+ Overeenkomsten - geeft de meest overeenkomende segmenten vanuit vertaalgeheugens weer
+
+
+
+ Woordenlijst - geeft terminologie weer
+
+
+
+ Woordenboek - geeft informatie weer die verschaft wordt door woordenboeken
+
+
+
+ Machinevertaling - geeft de vertaling weer zoals die wordt verschaft door services voor machinevertaling zolas Google Translate
+
+
+
+ Meerdere vertalingen - geeft alternatieve vertalingen weer - indien enige zijn ingevoerd - voor het huidige segment
+
+
+
+ Notities - opmerkingen van de vertaler met betrekking tot huidige segment
+
+
+
+ Opmerkingen - opmerkingen van de vertaler met betrekking tot huidige segment
+
+
+
+
+
+
+
+
+ SneltoetsenCtrl+L - venster Projectbestanden
+ venster Projectbestanden
+
+
+ De lijst van uw te vertalen bestanden (openen met CtrlL, sluiten met Esc)
+
+
+
+
+
+ SneltoetsenCtrl+F - venster Zoeken
+ venster Zoeken
+
+
+ Gebruikt om te zoeken naar specifieke segmenten in het project (openen met CtrlF, sluiten met Esc)
+
+
+
+
+
+
+ Minder frequent gebruikt
+
+
+
+
+ SneltoetsenCtrl+T - venster Tags valideren
+ venster Tags valideren
+
+
+ Gebruikt om te controleren of er tagfouten in vertalingen staan (openen met CtrlT sluiten met Esc)
+
+
+
+
+
+ SneltoetsenF1 - Help
+ Help-browser
+
+
+ gebruikt om de gebruikershandleiding te lezen (openen met F1, sluiten met Esc)
+
+
+
+
+ venster Statistieken
+
+
+ Gebruikt om het venster met de statistieken van het project te openen, geef het weer met behulp van
+ menu ExtraStatistieken
+ ExtraStatistieken.
+
+
+
+
+ venster Statistieken voor overeenkomsten
+
+
+ Gebruikt om de statistieken voor overeenkomsten in het project weer te geven, selecteer
+ menu ExtraStatistieken voor overeenkomsten
+ ExtraStatistieken voor overeenkomstenom het te openen.
+
+
+
+
+
+
+ dialoogvenster Projectinstellingen<indexterm class="singular">
+ <primary>Project</primary> <secondary>Projectinstellingen</secondary>
+ </indexterm>
+
+ De dialoogvensters hieronder worden gebruikt om de projectinstellingen voor OmegaT project te wijzigen. Elk wordt in detail beschreven in een afzonderlijk gedeelte; de informatie hieronder somt hun gebruik op en hoe zij worden geactiveerd:
+
+
+
+
+ SneltoetsenCtrl+E - Projecteigenschappen
+
+ menu ProjectEigenschappen
+ Projecteigenschappen
+
+
+ Gebruikt om de projectmappen en talen aan te passen, (openen met CtrlEProjecteigenschappen..., sluiten met Esc)
+
+
+
+
+
+ Projectinstellingenlettertype
+ Lettertype
+ menu Optieslettertype
+
+
+
+ Gebruikt om het lettertype aan te passen dat door OmegaT wordt gebruikt voor het weergeven van bron, vertaling, overeenkomsten en de termen uit de woordenlijst, (openen met OptiesLettertype..., sluiten met Esc)
+
+
+
+
+
+ Projectinstellingenbestandsfilters
+ Bestandsfilters
+ menu Optiesbestandsfilters
+
+
+
+ Gebruikt om de afhandeling van ondersteunde bestandsformaten aan te passen (openen met OptiesBestandsfilters..., sluiten met Esc)
+
+
+
+
+
+ Projectinstellingensegmentatie
+ Segmentatie
+ menu OptiesSegmentatie
+
+
+
+ Gebruikt om de manier waarop uw tekst wordt opgedeeld in zinnen te wijzigen (openen met OptiesSegmentatie, sluiten met Esc)
+
+
+
+
+
+ Projectinstellingenbewerken (gedrag)
+ Bewerken (gedrag)
+ menu Optiesbewerken (gedrag)
+
+
+
+ Gebruikt om te wijzigen hoe OmegaT zich gedraagt bij het doorlopen van de segmenten, (openen met OptiesBewerken (gedrag)..., sluiten met Esc)
+
+
+
+
+
+
+
+ <application>OmegaT</application> hoofdvenster<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>hoofdvenster</secondary> <tertiary>- afbeelding</tertiary>
+ </indexterm><indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>hoofdvenster</secondary>
+ </indexterm>
+
+
+ OmegaT-vensters
+
+
+
+
+
+
+
+
+
+
+
+
+ Het hoofdvenster bestaat uit verschillende vensters, het hoofdmenu en een statusbalk. U kunt de positie van elk venster wijzigen of het zelfs losmaken en er een zelfstandig venster van maken door het venster te slepen aan zijn naam. Afhankelijk van de status van het venster kunnen verschillende tekens verschijnen in de rechterbovenhoek ervan.
+
+
+ pictogrammen voor vensters<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>pictogrammen voor vensters</secondary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ minimaliseert het venster zodat alleen de naam wordt weergegeven aan de onderzijde van het venster.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ maximaliseert het venster.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ maakt het venster los van het hoofdvenster.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ zet het venster weer vast in het hoofdvenster.
+
+
+
+
+
+ U kunt de vensters elkaar laten overlappen als u dat wilt. Als dat gedaan wordt zullen de vensters aan de bovenzijde een tab weergeven. De scheidingen tussen de vensters kunnen worden gesleept om de afmetingen van vensters te wijzigen. Indien u niet meer weet welke wijzigingen u aan de gebruikersinterface heeft aangebracht, kunt u op elk moment
+ Vensters van OmegaTvensters in OmegaT
+
+ Vensters van OmegaTterugzetten naar fabrieksinstellingen
+ Opties → Hoofdvenster herstellen gebruiken om terug te keren naar de originele lay-out.
+
+ De tellers in de rechter benedenhoek houden de voortgang van de vertaling bij (getallen in de linkerkolom verwijzen naar de afbeelding hierboven):
+
+
+ Hoofdvenster - tellers<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>tellers</secondary>
+ </indexterm>
+
+
+
+
+
+
+ 33/33
+
+ aantal segmenten - vertaald / totaal van huidig bestand
+
+
+
+ 2780/2780
+
+ aantal unieke segmenten - vertaald / totaal in het project
+
+
+
+ 3760
+
+ totaal aantal segmenten (inclusief herhalingen) in het project
+
+
+
+ 126/127
+
+ aantal tekens in het bron- en in het doelsegment
+
+
+
+
+
+ Vanuit praktisch oogpunt is het meest belangrijkste paar het tweede paar getallen: het vertelt hoeveel u tot op dit moment hebt gedaan, in relatie tot het totaal van het tweede getal. Het project in het voorbeeld is zeker voltooid, omdat alle unieke segmenten zijn vertaald.
+
+
+ venster Bewerken<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Bewerken</secondary>
+ </indexterm>
+
+ Hier typt en bewerkt u uw vertaling. Het venster Bewerken geeft de tekst van het gedeeltelijk vertaalde document weer: de tekst die al vertaald is wordt vertaald weergegeven en de tekst die nog niet vertaald is wordt weergegeven in de originele taal. De weergegeven tekst is gesplitst in segmenten en u kunt door het document scrollen en op een willekeurig segment dubbelklikken om het te bewerken. In het bovenstaande geval zijn de reeds vertaalde segmenten weergegeven in geel, maar u kunt de instelling wijzigen om aan uw voorkeuren te voldoen (zie ).
+
+ Eén van de bovenstaande segmenten is het huidige segment. Het is het segment dat wordt weergegeven in twee gedeelten. Het bovenste gedeelte is weergegeven in de brontaal, in vette tekens met een groene achtergrondkleur, het onderste gedeelte is het bewerkingsveld, gescheiden door een markering:
+ Segment markering
+ de markering is <segment nnnn> waarbij nnnn het getal is van het segment in het project. Gebruik het bovenste gedeelte als een verwijzing en vervang of pas de inhoud van het bewerkingsveld aan door/met uw vertaling.
+
+ Afhankelijk van het gedrag van uw voorkeur tijdens het bewerken kan het bewerkingsveld voor het niet-vertaalde segment leeg zijn, de brontekst bevatten of de vertaling bevatten van de tekenreeks die het meeste lijkt op die welke u gaat vertalen. Als u verder gaat naar een ander segment wordt de vertaling gevalideerd en opgeslagen. Als u wilt dat het segment niet vertaald wordt, maakt u eenvoudigweg het bewerkingsveld leeg door alle tekst te verwijderen (selecteer alles met Ctrl+A en verwijder het met Del). OmegaT is in staat om vertalingen op te slaan die identiek aan de bron zijn. Het is handig voor documenten die handelsmerken, (bedrijfs-)namen of andere woorden met hoofdletters bevatten of delen in een derde taal die niet vertaald behoeven te worden. Zie Vertaling bewerken voor meer details.
+
+ Als u met rechts klikt op het venster bewerken opent een pop-upmenu waarin Knippen, Kopiëren, Plakken (d.i. dezelfde functies als CtrlX, CtrlC en CtrlV) en de functies Ga naar segment.
+
+
+
+ venster Overeenkomsten<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Overeenkomsten</secondary>
+ </indexterm>
+
+
+ <indexterm class="singular">
+ <primary>Overeenkomsten</primary> <secondary>venster Overeenkomsten - afbeelding</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Overeenkomsten - afbeelding</secondary>
+ </indexterm>venster Overeenkomsten
+
+
+
+
+
+
+
+
+
+
+
+
+ Het venster Overeenkomsten toont de meest overeenkomende segmenten uit de vertaalgeheugens, zowel uit het interne vertaalgeheugen dat werd gemaakt terwijl u uw project vertaalde als uit aanvullende vertaalgeheugens die u importeerde uit eerder werk of die u heeft gekregen van uw cliënt of vertaalbureau.
+
+ Als u doorgaat naar het volgende segment wordt de eerste overeenkomst (die met het hoogste percentage van overeenkomst) automatisch geselecteerd. U kunt een andere overeenkomst selecteren door te drukken op Ctrl+2, 3, 4 of 5.
+ SneltoetsenCtrl+N - Selecteren van de overeenkomst
+ Uiteraard zal het drukken op Ctrl5 geen effect hebben als er geen overeenkomst #5 is. Gebruik Ctrl+R
+ SneltoetsenCtrl+R - Tekst vervangen
+ om het doelveld te vervangen door die overeenkomst of Ctrl+I
+ SneltoetsenCtrl+I - Tekst invoegen
+ om die in te voegen op de cursorpositie, om de geselecteerde overeenkomst in uw vertaling te gebruiken.
+
+ Het percentage voor de overeenkomst is ruwweg het equivalent van het aantal meest voorkomende woorden in het vergeleken en het overeenkomende segment, gedeeld door het aantal woorden in de langste van de twee. De geselecteerde overeenkomst zal worden geaccentueerd in vet, woorden die ontbreken in het segment dat u vertaald zullen blauw gekleurd zijn en woorden die aansluiten aan ontbrekende gedeelten zullen groen zijn. In het bovenstaande voorbeeld is het bronsegment Context menu command. De bovenste overeenkomst is 100%, omdat alle woorden overeenkomen. Hetzelfde geldt voor de twee volgende overeenkomsten en de overeenkomst #4 is soortgelijk, maar verschilt. De regel met het percentage van overeenkomst bevat ook de naam van het vertaalgeheugen
+ Vertaalgeheugensovereenkomsten
+ dat de overeenkomst bevat. Indien er geen naam vermeld is, is de bron het interne vertaalgeheugen van het project. Wezen-segmenten
+ Vertaalgeheugenswezen-segmenten
+ (de overeenkomst #2) beschrijven segmenten in het standaard vertaalgeheugen van het project die geen overeenkomend bronsegment hebben.
+
+ Er zijn feitelijk drie berekende overeenkomsten beschikbaar (66/66/30 in het geval van overeenkomst #4 hierboven). Zij worden als volgt gedefinieerd:
+
+
+
+ percentage van overeenkomst als de plugin tokenizer wordt gebruikt
+
+
+
+
+
+ standaard overeenkomst OmegaT - aantal overeenkomende woorden - getallen en tags worden genegeerd - gedeeld door het totale aantal woorden
+
+
+
+
+
+ overeenkomst OmegaT, inclusief getallen en tags
+
+
+
+
+
+ venster Woordenlijst<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Woordenlijst</secondary>
+ </indexterm>
+
+ Het venster Woordenlijst maakt het u mogelijk om uw eigen collectie uitdrukkingen en speciale terminologie, die u heeft verzameld in uw bestanden voor de woordenlijst, te gebruiken. Het geeft de vertalingen weer van termen die zijn gevonden in het huidige segment. Het bronsegment in het voorbeeld hieronder was “Context menu command”, zoals het voorbeeld voor Overeenkomsten hierboven, en de weergegeven termen werden gevonden in de beschikbare woordenlijsten (Microsoft's Term collection en de woordenlijst voor de Sloveense Linux gebruikersgroep.
+
+
+ <indexterm class="singular">
+ <primary>Woordenlijsten</primary> <secondary>item met meerdere woorden in de woordenlijst - afbeelding</secondary>
+ </indexterm>item met meerdere woorden in de woordenlijst
+
+
+
+
+
+
+
+
+
+
+
+
+ Als u de optie TransTips hebt geactiveerd Opties → Transtips), kunt u met rechts klikken op het geaccentueerde woord om een keuzelijst te openen met de voorgestelde vertalingen, zoals die worden aangeboden door uw woordenlijst. Selecteren van een er van zal het invoegen op de huidige positie in het doelsegment. U kunt ook uw geprefereerde alternatief accentueren in het venster Woordenlijst en het invoegen in het doel door met rechts op de selectie te klikken.
+
+
+
+ venster Woordenboek<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Woordenboek</secondary>
+ </indexterm>
+
+ Woordenboeken zijn de elektronische versies van gedrukte woordenboeken zoals MerriamWebster, Duden, Larousse etc., die u op uw bureau zou hebben kunnen staan. Bekijk er meer over in het hoofdstuk over Woordenboeken
+
+
+
+ venster Meerdere vertalingen<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Meerdere vertalingen</secondary>
+ </indexterm>
+
+ Een bepaald bronsegment kan verschillende vertalingen vereisen, afhankelijk van de context. Als de huidige vertaling van het segment niet past, kan de gebruiker Bewerken → Alternatieve vertaling maken selecteren. De doeltekst die daarna wordt ingevoerd zal wordne behandeld als een alternatieve vertaling van het bronsegment. U kunt één van de alternatieven - bijvoorbeeld die welke het meest waarschijnlijk is - als de standaard vertaling instellen door te selecteren Bewerken → Als standaard vertaling gebruiken
+
+
+
+ venster Notities
+
+ De vertaler kan notities toevoegen aan het geopende segment, bijvoorbeeld om later terug te kunnen keren naar het segment en de vertaling opnieuw te doen, te controleren dat alternatieve vertalingen juist zijn of om collega's om hun mening te vragen. U kunt door de notities bladeren met behulp van Ga naar → Volgende notitie en Ga naar → Vorige notitie.
+
+
+
+ venster Opmerkingen
+
+ Sommige bestandsindelingen, gespecialiseerd voor vertaalwerk, bijvoorbeeld PO, maken het opnemen van opmerkingen mogelijk. Op deze manier kan de vertaler de context voor het segment dat moet worden vertaald worden verschaft. In het voorbeeld hieronder heeft de auteur van het PO-bestand een waarschuwing voor de vertaler opgenomen om de lengte van de vertaling te controleren:
+
+
+
+
+
+
+
+
+
+
+
+
+
+ venster Machinevertaling<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Machinevertaling</secondary>
+ </indexterm>
+
+ Het venster Machinevertaling, indien geopend, bevat de suggesties van programma's voor machinevertaling voor het huidige segment. Druk op Ctrl+M om de vertaling van het huidige segment te vervangen door de voorgestelde vertaling. Meer in het hoofdstuk Machinevertaling
+
+
+
+ Hoofdmenu
+
+ Het hoofdmenu geeft toegang tot alle functies van OmegaT. Zie de appendix Hoofdmenu voor een volledige beschrijving van alle menu's en menu-items. De meestgebruikte functies zijn te benaderen met sneltoetsen voor het toetsenbord, dus als u daar eenmaal aan gewend bent, zal er geen reden meer zijn om door de menu's te bladeren tijdens het vertalen. Bekijk hoofdstuk Sneltoetsen voor menu en het toetsenbord voor details.
+
+
+
+ Statusbalk
+
+ De statusbalk geeft berichten met betrekking tot de werkzaamheden weer aan de onderzijde van het hoofdvenster. Deze balk geeft de gebruiker berichten met terugkoppeling over specifieke bewerkingen die worden uitgevoerd. Het geeft ook het aantal overeenkomsten en overeenkomsten in de woordenlijst aan voor het huidige segment.
+
+
+
+
+ Andere vensters
+
+
+ Projectbestanden<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>Projectbestanden</secondary>
+ </indexterm>
+
+ Het venster Projectbestanden somt de projectbestanden op en geeft andere informatie over het project weer. Het wordt automatisch weergegeven als OmegaT een project laadt. Gebruik Ctrl+L
+ SneltoetsenCtrl+L - lijst projectbestanden
+ om het te openen en Esc om het te sluiten. Het venster Projectbestanden geeft de volgende informatie weer:
+
+
+
+ de lijst met alle vertaalbare bestanden in het project. Dit zijn de bestanden die aanwezig zijn in de map met bronbestanden in een formaat dat OmegaT kan afhandelen. Klikken op een bestand zal het openen voor vertaling
+
+
+
+
+
+ het bestand dat momenteel beschikbaar is in het venster Bewerken is geaccentueerd met een blauwe achtergrond. Drukken op Enter zal het venster Bewerken verplaatsen naar het begin van het geselecteerde bestand
+
+
+
+
+
+ het aantal segmenten in elk bestand wordt naast de naam van het bestand weergegeven
+
+
+
+
+
+ het totale aantal segmenten, het aantal unieke segmenten in het gehele project en het aantal reeds vertaalde unieke segmenten worden weergegeven aan de onderzijde
+
+
+
+ De verzameling Unieke segmenten wordt berekend door alle segmenten te nemen en daaruit de duplicaten te verwijderen. (De definitie van “uniek” is gevoelig voor hoofdletters: "Run" en "run" worden als verschillend behandeld)
+
+ Het verschil tussen "Aantal segmenten" en "Aantal unieke segmenten" geeft een ruwe benadering van het aantal herhalingen in een tekst. Merk echter op dat de aantallen niet vertellen hoe relevant de herhalingen zijn: zij zouden kunnen betekenen dat relatief lange zinnen een aantal keren worden herhaald (in welk geval u gul hebt) of het zou een tabel met sleutelwoorden kunnen beschrijven (niet zo gelukkig). Het bestand project_stats.txt dat is geplaatst in de map omegat van uw project bevat meer gedetailleerde informatie over elk segment per bestand.
+
+ Aanpassen van de segmentatieregels kan effect hebben op het aanpassen van het aantal segmenten/unieke segmenten. Zoiets zou echter in het algemeen moeten worden vermeden nadat u eenmaal met de vertaling van het project bent begonnen. Zie het hoofdstuk Segmentatieregels voor meer informatie.
+
+
+ Bronbestandenbestanden toevoegen aan het project
+ bestanden toevoegen aan het project: U kunt bronbestanden toevoegen aan het project door te klikken op de knop "Bronbestanden importeren...". Dit kopieert de geselecteerde bestanden naar de map /source en herlaadt het project om de nieuwe bestanden te importeren. U kunt ook bronbestanden toevoegen vanaf internetpagina's, geschreven in MediaWiki, door te klikken op de knop "Importeren vanuit MediaWiki" en de corresponderende URL op te geven.
+
+
+
+ venster Zoeken<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Zoeken</secondary>
+ </indexterm>
+
+ U kunt het venster Zoeken gebruiken om specifieke segmenten in het project te vinden. U kunt meerdere vensters tegelijkertijd geopend hebben. Gebruik CtrlF in het hoofdvenster om een nieuw venster te openen. Het venster Zoeken bestaat uit een tekstvak voor tekenreeksen of sleutelwoorden om te zoeken, vlaggen en keuzeknoppen voor het instellen van het zoek- en weergavegebied dat de resultaten van de zoekactie bevat. Zie het hoofdstuk Zoeken voor meer informatie over het zoekvenster.
+
+
+
+ Tags valideren<indexterm class="singular">
+ <primary>Tags valideren</primary> <seealso>sneltoetsen, tags</seealso>
+ </indexterm><indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>tags valideren</secondary> <seealso>tags</seealso>
+ </indexterm>
+
+ Het venster Tags valideren detecteert de tagfouten en niet-consistente vertalingen in de vertaling en somt ze op. Open het venster met Ctrl+T. Het venster heeft een kolom met 3 tabellen met een koppeling naar het segment en de inhoud van diens bron en doel:
+
+
+ <indexterm class="singular">
+ <primary>Tags valideren</primary> <secondary>venster - afbeelding</secondary> <seealso>tags</seealso>
+ </indexterm>venster Tags valideren
+
+
+
+
+
+
+
+
+
+
+
+
+ De tags worden vet blauw geaccentueerd voor eenvoudige vergelijking tussen de originele en de vertaalde inhoud. Klik op de koppeling om naar het segment in het venster Bewerken te springen. Verbeter, indien nodig, de fout en druk op Ctrl+T om terug te keren naar het venster Tags valideren om andere fouten te corrigeren. In het eerste en derde geval hierboven waren tags niet correct gepaard en in het tweede geval ontbreekt bij de openingstag het <-teken.
+
+ Tagfouten zijn gevallen waarin de tags in de vertaling niet overeenkomen in volgorde en aantal in vergelijking met het originele segment. Sommige scenario's met betrekking tot tags die worden gevlagd in het venster Tag valideren zijn noodzakelijk en zijn goedaardig, terwijl andere problemen zullen veroorzaken als het vertaalde document wordt gemaakt. Tags vertegenwoordigen meestal enige vorm van opmaak in de originele tekst. Vereenvoudigen van de opmaak van de originele tekst in het bronbestand voordat de vertaling wordt begonnen draagt enorm bij aan het verminderen van het aantal tags.
+
+
+
+ Statistieken<indexterm class="singular">
+ <primary>Statistieken</primary> <seealso>menu Extra</seealso>
+ </indexterm>
+
+ Het venster Statistieken - te benaderen via Extra > Statistieken - geeft de statistieken voor het huidige project van OmegaT weer, zowel in de vorm van een overzicht als in detail voor elk bestand dat moet worden vertaald. De weergegeven statistieken zijn beschikbaar als een tab-gescheiden bestand project_stats.txt (submap omegat), klaar om te worden geladen in een programma met rekenbladen dat de gebruiker wil gebruiken. U kunt Ctrl+A
+ SneltoetsenCtrl+A - alles selecteren
+ , Ctrl+C
+ SneltoetsenCtrl+C - tekst kopiëren
+ , Ctrl+V
+ SneltoetsenCtrl+V - tekst plakken
+ gebruiken om de inhoud te kopiëren en te plakken.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Statistieken voor overeenkomsten<indexterm class="singular">
+ <primary>Statistieken voor overeenkomsten</primary> <seealso>menu Extra</seealso>
+ </indexterm>
+
+ Toegang tot de statistieken voor overeenkomsten gaat viaExtra > Statistieken voor overeenkomsten. De evaluatie vergt nogal wat gebruik van de CPU en kan nogal wat tijd vergen, dus wordt er een voortgangsbalk weergegevn gedurende de berekening. Voorzover het categorieën betreft, de de facto industriestandaard voor het classificeren van overeenkomsten in de volgende groepen wordt gebruikt: Exacte overeenkomst, 95%-100%, 85%-94%, 75%-84%, 50%-74% en Geen overeenkomst. De tellingen van woorden, identiek aan tellingen in het venster Projectbestanden, are strikt gebaseerd op de methode van tellen van OmegaT, met een aantal verschillen in terminologie om rekening te houden met conceptuele verschillen. Deze informatie wordt berekend voor zowel segmenten als voor woorden en voor tekens (zonder en met spaties).
+
+ Onthoud dat deze totalen een goede (of zo-goed-als-maar-kan-zijn) benadering zijn van het betrokken werk in het project en dus kan dienen als een basis voor uw berekeningen van kosten en prijzen.
+
+
+ statistieken voor overeenkomsten
+
+
+
+
+
+
+
+
+
+
+
+
+ Met spaties tussen segmenten wordt geen rekening gehouden in de laatste kolom. Herhalingen staan voor identieke segmenten die meerdere malen aanwezig zijn in de tekst. Het eerste segment en de inhoud daarvan zullen worden geclassificeerd als "geen overeenkomst", en de rest van hen als een herhaling van de eerste. Als de vertaling voor verschillende identieke bronsegmenten al bestaat in het vertaalgeheugen van het project, zullen deze segmenten, samen met andere, reeds vertaalde unieke segmenten, worden geclassificeerd als een "Exacte overeenkomst". Het aantal unieke segmenten die, indien nodig, worden verschaft in het standaard venster met statistieken, ongeacht of zij zijn vertaald of niet.
+
+ De rest van de categorieën (50-100%) behelst niet-vertaalde segmenten met een fuzzy overeenkomst. Fuzzy overeenkomsten kunnen ook vanuit de map /tm komen - en niet alleen vanuit het interne vertaalgeheugen in /omegaT, zoals het geval is voor herhalingen en exacte overeenkomsten. Het enige verschil met overeenkomsten vanuit het vertaalgeheugen project_save is dat externe TM's geen exacte overeenkomsten kunnen geven, alleen 100%. Indien men geen externe TM's wil gebruiken voor het tellen, moet men de map /tm leeg maken of de instelling van het project wijzigen (tijdelijk) zodat de waarde voor /tm naar een andere locatie verwijst.
+
+ De overeenkomsten voor statistieken zijn tab-gescheiden en u kunt Ctrl+A
+ SneltoetsenCtrl+A - alles selecteren
+ , Ctrl+C
+ SneltoetsenCtrl+C - tekst kopiëren
+ , Ctrl+V
+ SneltoetsenCtrl+V - tekst plakken
+ gebruiken om ze te kopiëren/plakken, bijvoorbeeld in een werkblad of in uw toepassing voor kostenberekening. Eenmaal berekend zijn de gegevens ook beschikbaar in omegat/project_stats_match.txt. Onthoud dat het bestand voorzien is van een tijdstempel, omdat de berekening (in tegenstelling tot de standaard statistieken) is niet onmiddellijk wordt uitgevoerd en dus snel niet meer van toepassing is.
+
+
+
+ Help-browser<indexterm class="singular">
+ <primary>menu Help</primary> <secondary>Help-browser</secondary>
+ </indexterm>
+
+ De Help-browser (die deze handleiding weergeeft) kan worden opgeroepen door op
+ SneltoetsenF1 - Help
+ F1 te drukken of door te navigeren naar
+ menu HelpGebruikershandleiding...
+ Help → Gebruikershandleiding... in het hoofdmenu. In het venster worden de handleiding en twee knoppen weergegeven: Terug en Inhoud. De gebruikershandleiding is een HTML-document met koppelingen naar de verschillende hoofdstukken. Klikken op een koppeling, zoals u in een webbrowser zou doen, brengt de gewenste pagina op de voorgrond.
+
+ De gebruikershandleiding is geplaatst in de submap docs onder de installatiemap van OmegaT, dus u kunt bijvoorbeeld de Engelse documentatie bekijken door het bestand docs/en/index.html in uw browser te openen. Openen van de gebruikershandleiding op deze manier stelt u ook in staat om externe koppelingen te volgen, omdat de ingebouwde help-browser geen externe koppelingen naar internet accepteert.
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/nl/images/AppleKey.gif b/OmegaT/doc_src/nl/images/AppleKey.gif
new file mode 100644
index 0000000..dabdac4
Binary files /dev/null and b/OmegaT/doc_src/nl/images/AppleKey.gif differ
diff --git a/OmegaT/doc_src/nl/images/Comments_25.png b/OmegaT/doc_src/nl/images/Comments_25.png
new file mode 100644
index 0000000..2040603
Binary files /dev/null and b/OmegaT/doc_src/nl/images/Comments_25.png differ
diff --git a/OmegaT/doc_src/nl/images/DictMerriamWebster.png b/OmegaT/doc_src/nl/images/DictMerriamWebster.png
new file mode 100644
index 0000000..f0515b6
Binary files /dev/null and b/OmegaT/doc_src/nl/images/DictMerriamWebster.png differ
diff --git a/OmegaT/doc_src/nl/images/Dock.gif b/OmegaT/doc_src/nl/images/Dock.gif
new file mode 100644
index 0000000..4a6487c
Binary files /dev/null and b/OmegaT/doc_src/nl/images/Dock.gif differ
diff --git a/OmegaT/doc_src/nl/images/EditingBehaviourOptions.png b/OmegaT/doc_src/nl/images/EditingBehaviourOptions.png
new file mode 100644
index 0000000..370aae4
Binary files /dev/null and b/OmegaT/doc_src/nl/images/EditingBehaviourOptions.png differ
diff --git a/OmegaT/doc_src/nl/images/GlossaryEntry_25.png b/OmegaT/doc_src/nl/images/GlossaryEntry_25.png
new file mode 100644
index 0000000..6c614b7
Binary files /dev/null and b/OmegaT/doc_src/nl/images/GlossaryEntry_25.png differ
diff --git a/OmegaT/doc_src/nl/images/GlossaryPane_25.png b/OmegaT/doc_src/nl/images/GlossaryPane_25.png
new file mode 100644
index 0000000..1c02dc9
Binary files /dev/null and b/OmegaT/doc_src/nl/images/GlossaryPane_25.png differ
diff --git a/OmegaT/doc_src/nl/images/InstantGuide_1.png b/OmegaT/doc_src/nl/images/InstantGuide_1.png
new file mode 100644
index 0000000..700879e
Binary files /dev/null and b/OmegaT/doc_src/nl/images/InstantGuide_1.png differ
diff --git a/OmegaT/doc_src/nl/images/InstantGuide_2.png b/OmegaT/doc_src/nl/images/InstantGuide_2.png
new file mode 100644
index 0000000..006ce2c
Binary files /dev/null and b/OmegaT/doc_src/nl/images/InstantGuide_2.png differ
diff --git a/OmegaT/doc_src/nl/images/Main_pane_counters.png b/OmegaT/doc_src/nl/images/Main_pane_counters.png
new file mode 100644
index 0000000..8844e41
Binary files /dev/null and b/OmegaT/doc_src/nl/images/Main_pane_counters.png differ
diff --git a/OmegaT/doc_src/nl/images/MatchStatistics.png b/OmegaT/doc_src/nl/images/MatchStatistics.png
new file mode 100644
index 0000000..bcb6fbc
Binary files /dev/null and b/OmegaT/doc_src/nl/images/MatchStatistics.png differ
diff --git a/OmegaT/doc_src/nl/images/MatchesPane_25.png b/OmegaT/doc_src/nl/images/MatchesPane_25.png
new file mode 100644
index 0000000..ea6409d
Binary files /dev/null and b/OmegaT/doc_src/nl/images/MatchesPane_25.png differ
diff --git a/OmegaT/doc_src/nl/images/Maximize.gif b/OmegaT/doc_src/nl/images/Maximize.gif
new file mode 100644
index 0000000..24e1b0a
Binary files /dev/null and b/OmegaT/doc_src/nl/images/Maximize.gif differ
diff --git a/OmegaT/doc_src/nl/images/Minimize.gif b/OmegaT/doc_src/nl/images/Minimize.gif
new file mode 100644
index 0000000..f41fac5
Binary files /dev/null and b/OmegaT/doc_src/nl/images/Minimize.gif differ
diff --git a/OmegaT/doc_src/nl/images/MobyDick.png b/OmegaT/doc_src/nl/images/MobyDick.png
new file mode 100644
index 0000000..94ca2f6
Binary files /dev/null and b/OmegaT/doc_src/nl/images/MobyDick.png differ
diff --git a/OmegaT/doc_src/nl/images/MultiTerm_Glossary_25.png b/OmegaT/doc_src/nl/images/MultiTerm_Glossary_25.png
new file mode 100644
index 0000000..fa5c256
Binary files /dev/null and b/OmegaT/doc_src/nl/images/MultiTerm_Glossary_25.png differ
diff --git a/OmegaT/doc_src/nl/images/NewProject_25.png b/OmegaT/doc_src/nl/images/NewProject_25.png
new file mode 100644
index 0000000..79d7a08
Binary files /dev/null and b/OmegaT/doc_src/nl/images/NewProject_25.png differ
diff --git a/OmegaT/doc_src/nl/images/OmT_Cyrillic.png b/OmegaT/doc_src/nl/images/OmT_Cyrillic.png
new file mode 100644
index 0000000..fd74105
Binary files /dev/null and b/OmegaT/doc_src/nl/images/OmT_Cyrillic.png differ
diff --git a/OmegaT/doc_src/nl/images/OmT_Japanese.png b/OmegaT/doc_src/nl/images/OmT_Japanese.png
new file mode 100644
index 0000000..b760d89
Binary files /dev/null and b/OmegaT/doc_src/nl/images/OmT_Japanese.png differ
diff --git a/OmegaT/doc_src/nl/images/OmegaT projects_and_subdirectories.png b/OmegaT/doc_src/nl/images/OmegaT projects_and_subdirectories.png
new file mode 100644
index 0000000..646a2e2
Binary files /dev/null and b/OmegaT/doc_src/nl/images/OmegaT projects_and_subdirectories.png differ
diff --git a/OmegaT/doc_src/nl/images/OmegaT_icon.png b/OmegaT/doc_src/nl/images/OmegaT_icon.png
new file mode 100644
index 0000000..5e8762b
Binary files /dev/null and b/OmegaT/doc_src/nl/images/OmegaT_icon.png differ
diff --git a/OmegaT/doc_src/nl/images/OmegaT_panes.png b/OmegaT/doc_src/nl/images/OmegaT_panes.png
new file mode 100644
index 0000000..a93fdc3
Binary files /dev/null and b/OmegaT/doc_src/nl/images/OmegaT_panes.png differ
diff --git a/OmegaT/doc_src/nl/images/OmegaT_panes_25.png b/OmegaT/doc_src/nl/images/OmegaT_panes_25.png
new file mode 100644
index 0000000..bfd04ce
Binary files /dev/null and b/OmegaT/doc_src/nl/images/OmegaT_panes_25.png differ
diff --git a/OmegaT/doc_src/nl/images/OmegaT_projects_and_subdirectories.png b/OmegaT/doc_src/nl/images/OmegaT_projects_and_subdirectories.png
new file mode 100644
index 0000000..e277b5c
Binary files /dev/null and b/OmegaT/doc_src/nl/images/OmegaT_projects_and_subdirectories.png differ
diff --git a/OmegaT/doc_src/nl/images/Omegatproject.png b/OmegaT/doc_src/nl/images/Omegatproject.png
new file mode 100644
index 0000000..8942d78
Binary files /dev/null and b/OmegaT/doc_src/nl/images/Omegatproject.png differ
diff --git a/OmegaT/doc_src/nl/images/OptionsTabValidation_25.png b/OmegaT/doc_src/nl/images/OptionsTabValidation_25.png
new file mode 100644
index 0000000..40c1429
Binary files /dev/null and b/OmegaT/doc_src/nl/images/OptionsTabValidation_25.png differ
diff --git a/OmegaT/doc_src/nl/images/RegexTester.png b/OmegaT/doc_src/nl/images/RegexTester.png
new file mode 100644
index 0000000..0876eb6
Binary files /dev/null and b/OmegaT/doc_src/nl/images/RegexTester.png differ
diff --git a/OmegaT/doc_src/nl/images/Restore.gif b/OmegaT/doc_src/nl/images/Restore.gif
new file mode 100644
index 0000000..4099595
Binary files /dev/null and b/OmegaT/doc_src/nl/images/Restore.gif differ
diff --git a/OmegaT/doc_src/nl/images/SpellcheckerSetup2.png b/OmegaT/doc_src/nl/images/SpellcheckerSetup2.png
new file mode 100644
index 0000000..bb21407
Binary files /dev/null and b/OmegaT/doc_src/nl/images/SpellcheckerSetup2.png differ
diff --git a/OmegaT/doc_src/nl/images/SpellcheckingText.png b/OmegaT/doc_src/nl/images/SpellcheckingText.png
new file mode 100644
index 0000000..b95b3d3
Binary files /dev/null and b/OmegaT/doc_src/nl/images/SpellcheckingText.png differ
diff --git a/OmegaT/doc_src/nl/images/StatisticsWindow_25.png b/OmegaT/doc_src/nl/images/StatisticsWindow_25.png
new file mode 100644
index 0000000..d50c8fe
Binary files /dev/null and b/OmegaT/doc_src/nl/images/StatisticsWindow_25.png differ
diff --git a/OmegaT/doc_src/nl/images/TagValidation.png b/OmegaT/doc_src/nl/images/TagValidation.png
new file mode 100644
index 0000000..e109554
Binary files /dev/null and b/OmegaT/doc_src/nl/images/TagValidation.png differ
diff --git a/OmegaT/doc_src/nl/images/TagValidator.png b/OmegaT/doc_src/nl/images/TagValidator.png
new file mode 100644
index 0000000..74cb768
Binary files /dev/null and b/OmegaT/doc_src/nl/images/TagValidator.png differ
diff --git a/OmegaT/doc_src/nl/images/TextSearch.png b/OmegaT/doc_src/nl/images/TextSearch.png
new file mode 100644
index 0000000..f1ebc5b
Binary files /dev/null and b/OmegaT/doc_src/nl/images/TextSearch.png differ
diff --git a/OmegaT/doc_src/nl/images/Undock.gif b/OmegaT/doc_src/nl/images/Undock.gif
new file mode 100644
index 0000000..6680e9c
Binary files /dev/null and b/OmegaT/doc_src/nl/images/Undock.gif differ
diff --git a/OmegaT/doc_src/nl/images/saveglossary.png b/OmegaT/doc_src/nl/images/saveglossary.png
new file mode 100644
index 0000000..7026a3d
Binary files /dev/null and b/OmegaT/doc_src/nl/images/saveglossary.png differ
diff --git a/OmegaT/doc_src/nl/images/tagged_segment.png b/OmegaT/doc_src/nl/images/tagged_segment.png
new file mode 100644
index 0000000..9d4d87f
Binary files /dev/null and b/OmegaT/doc_src/nl/images/tagged_segment.png differ
diff --git a/OmegaT/doc_src/nl/images/tagged_segment_target.png b/OmegaT/doc_src/nl/images/tagged_segment_target.png
new file mode 100644
index 0000000..ddbd1c6
Binary files /dev/null and b/OmegaT/doc_src/nl/images/tagged_segment_target.png differ
diff --git a/OmegaT/doc_src/nl/index.xml b/OmegaT/doc_src/nl/index.xml
new file mode 100644
index 0000000..2463479
--- /dev/null
+++ b/OmegaT/doc_src/nl/index.xml
@@ -0,0 +1,8111 @@
+
+
+
+
+ OmegaT - Gebruikershandleiding
+
+ vs
+ Vito
+Smolej
+
+
+
+
+
+ Dit document is de officiële gebruikershandleiding voor OmegaT, het gratis Computer Aided Translation-programma. Het bevat ook instructies voor de installatie.
+
+
+
+
+
+ Over <application>OmegaT</application> - introductie
+
+
+ OmegaT pluspunten
+
+ OmegaT is een vrij, multiplatform Computer Aided Translation programma met de volgende pluspunten.
+
+
+
+ Vertaalgeheugen:OmegaT slaat uw vertalingen op in een vertaalgeheugen. Tegelijkertijd kan het vertaalgeheugens van eerdere vertalingen als verwijzingen gebruiken. Vertaalgeheugens kunnen zeer handig zijn bij het vertalen van veel voorkomende herhalingen of tekstsegmenten die redelijk met elkaar overeen komen. OmegaT gebruikt vertaalgeheugens om uw eerdere vertalingen op te slaan en toont u dan de meest waarschijnlijke vertalingen voor de tekst waaraan u momenteel werkt.
+
+ Deze vertaalgeheugens kunnen zeer handig zijn als een, reeds vertaald, document moet worden bijgewerkt. Ongewijzigde zinnen worden automatisch vertaald, terwijl bijgewerkte zinnen worden getoond met de vertaling van de meest gelijkende oudere versie van dezelfde zin. Wijzigingen in het originele document worden dus gemakkelijker afgehandeld. Als u eerder gemaakte vertaalgeheugens gebruikt, bijvoorbeeld geleverd door uw vertaalbureau of uw cliënt, is OmegaT in staat om ze te gebruiken als referentie-geheugens.
+
+ OmegaT gebruikt de standaard bestandsindeling TMX om vertaalgeheugens op te slaan en om daar toegang toe te krijgen, hetgeen garandeert dat u uw vertalingsmateriaal kunt uitwisselen met andere CAT-toepassingen die deze bestandsindeling ondersteunen.
+
+
+
+
+
+ Terminologiebeheer: Terminologiebeheer is belangrijk voor consistentie in de vertalingen. OmegaT gebruikt woordenlijsten die vertalingen van woorden of korte frasen bevatten, een soort vereenvoudigd tweetalig woordenboek op een bepaald terrein. Voor uw verwijzing toont OmegaT de vertaling van woorden als die aanwezig zijn in het segment dat op dit moment de focus heeft.
+
+
+
+
+
+ Proces van vertalingen: Veronderstel dat u iets moet vertalen, van één enkel bestand tot een map die submappen bevat met meerdere bestanden in verschillende indelingen. Als u OmegaT laat weten welke bestanden u moet vertalen, zal het kijken naar de bestanden die het begrijpt, gebaseerd op regels voor bestandsfiltering, de tekstdelen daarin herkennen, de tekstgroepen opsplitsen op basis van segmentatieregels, en de segmenten één voor één tonen zodat u door kunt gaan met de vertaling. OmegaT slaat uw vertalingen op en stelt mogelijke vertalingen voor vanuit overeenkomende segmenten in eerdere vertaalgeheugens. Als u klaar bent om het uiteindelijke product te bekijken, kunt u de vertaalde bestanden exporteren, ze openen in het gewenste programma en zien hoe de vertaling er in de uiteindelijke indeling uitziet.
+
+
+
+
+
+ Overzicht van hoofdstukken
+
+ Deze documentatie is zowel bedoeld als handleiding als als gids met verwijzingen. Hier is een kort overzicht van de hoofdstukken en hun inhoud.
+
+
+
+ gids Snel starten: dit hoofdstuk is bedoeld als een gids Snel starten voor beginners en “ongeduldige types”, die de complete procedure weergeeft vanaf het openen van een nieuw project voor vertalingen tot en met het voltooien van die vertaling.
+
+
+
+
+
+ Installeren en uitvoeren van OmegaT: dit hoofdstuk is handig als u voor het eerst begint met het werken met OmegaT. Het bevat de specifieke instructies over hoe OmegaT te installeren en het uit te voeren op Windows, Mac OS X en Linux. Voor gevorderde gebruikers beschrijft dit hoofdstuk de opdrachten voor de modus met de opdrachtregel en de mogelijkheden daarvan.
+
+
+
+
+
+ De gebruikersinterface,Hoofdmenu en Sneltoetsen voor het toetsenbord: deze twee hoofdstukken zullen waarschijnlijk veelvuldig geraadpleegd worden, omdat zij de gebruikersinterface van OmegaT uitleggen en de via het hoofdmenu en de sneltoetsen voor het toetsenbord beschikbare functies.
+
+
+
+
+
+ Projecteigenschappen, OmegaT bestanden en mappen: een project in de context van OmegaT is het gedeelte werk dat OmegaT in staat is als CAT-gereedschap af te handelen. Dit hoofdstuk beschrijft de projecteigenschappen, zoals de bron- en doeltalen. Het tweede hoofdstuk beschrijft de verschillende submappen en bestanden in een vertaalproject en hun rol als ook andere gebruikers- en toepassingsbestanden die zijn geassocieerd met OmegaT.
+
+
+
+
+
+ Gedrag bewerkingsveld: een kort hoofdstuk dat beschrijft hoe het gedrag met betrekking tot bewerking van het segment dat wordt vertaald wordt ingesteld.
+
+
+
+
+
+ Werken met platte tekst en Werken met opgemaakte tekst: deze twee hoofdstukken beschrijven bepaalde belangrijke punten met betrekking tot te vertalen teksten, zoals de codering (in het geval van "platte tekst"-bestanden) en de afhandeling van tags (in het geval van opgemaakte tekst).
+
+
+
+
+
+ Vertaalgeheugens: beschrijft de rol van de verschillende submappen die vertaalgeheugens bevatten, en verschaft informatie over andere belangrijke aspecten met betrekking tot vertaalgeheugens.
+
+
+
+ Segmentatie: programma's met vertaalgeheugens werken met teksteenheden die segmenten worden genoemd. In OmegaT kunnen segmenten worden gebaseerd op alinea's of op segmentatieregels. Segmentatie op basis van alinea's wordt minder frequent gebruikt, maar kan handig zijn in het geval van zogenaamde "creatieve" teksten. De op regels gebaseerde segmentatie is gewoonlijk synoniem aan de op zinnen gebaseerde segmentatie. Een aantal verzamelingen van regels worden meegeleverd, terwijl aanvullende regels door de gebruiker kunnen worden gedefinieerd, zoals beschreven in dit hoofdstuk.
+
+
+
+ Zoeken enReguliere uitdrukkingen: Zoeken in OmegaT kan zo eenvoudig zijn als "som de segmenten op met het woord 'kangoeroe'". Zij mogen ook complex zijn, om het bijvoorbeeld mogelijk te maken te zoeken naar segmenten met twee of meer opeenvolgende spaties. In dat geval zou de reguliere uitdrukking ^s^s+ worden gebruikt te zoeken en de betrokken segmenten op te sommen. Reguliere uitdrukkingen worden ook uitgebreid in de segmentatieregels gebruikt.
+
+
+
+ Woordenboeken, Woordenlijsten, Machinevertaling en Spellingscontrole: in OmegaT kunnen woordenboeken en woordenlijsten worden uitgebreid. Als een internetverbinding beschikbaar is, kunnen diverse services voor machinevertaling zoals Google Translate worden gebruikt vanuit OmegaT. Indien spellingscontrole is geactiveerd, worden spelfouten en typefouten herkend en kunnen die gecorrigeerd worden tijdens de vertaling.
+
+
+
+ Diversen: behandelt andere interessante punten zoals het vermijden van het verliezen van gegevens.
+
+
+
+ Appendices bevat de volgende informatie
+
+
+
+ OmegaT op het web: informatie met betrekking tot on-line bronnen voor OmegaT
+
+
+
+
+
+ Talen: bevat de ISO-lijst van talen en taalcodes
+
+
+
+
+
+ Sneltoetsen toetsenbord: de lijst met sneltoetsen die worden gebruikt bij het bewerken
+
+
+
+ Aanpassen van sneltoetsen: sneltoetsen kunnen worden aangepast om te voldoen aan uw persoonlijke voorkeuren
+
+
+
+
+
+ Auteursrechten
+
+
+
+
+
+ Index sleutelwoorden: een uitgebreide index van sleutelwoorden wordt verschaft om de lezer te helpen de relevante informatie te vinden.
+
+
+
+
+
+
+ Leren om OmegaT te gebruiken in 5 minuten!
+
+
+ Stel een nieuw project in<indexterm class="singular">
+ <primary>Project</primary> <secondary>Maak / open nieuw</secondary>
+ </indexterm>
+
+ Opmerking: Op een Apple Mac, gebruik de toets Cmd of Apple in plaats van de toets Ctrl
+
+ Maak eerst een project dat al uw bestanden zal bevatten, zoals uw bronbestanden, vertaalgeheugens, woordenlijsten en uiteindelijk uw vertaalde bestand, om te beginnen met het gebruiken van OmegaT. Selecteer, in het menu Project, Nieuw...
+ menu ProjectNieuw...
+ typ een naam voor uw project. Onthoud waar u het project maakte, omdat u er later naar terug moet keren.
+
+ Nadat u het project een naam hebt gegeven, zal het dialoogvenster Nieuw project maken openen. Selecteer, aan het begin van dat dialoogvenster, uw taal voor de bronbestanden en de taal waarin uw vertaalde bestand moet zijn, en klik op OK om door te gaan.
+
+ Indien u geïnteresseerd bent in andere instellingen van dit dialoogvenster, kunt u er op elk moment naar terugkeren door te drukken op Ctrl+E.
+
+ Vervolgens opent het dialoogvenster Projectbestanden. Klik op de knop Bronbestanden importeren... om uw bronbestand te selecteren. OmegaT zal dan het geselecteerde bestand kopiëren naar de submap /source/ van uw nieuw gemaakte project. Nadat het bronbestand is geladen in het venster Bewerken kunt u het dialoogvenster Projectbestanden sluiten.
+
+
+
+ Vertaal het bestand
+
+ OmegaT zal één segment per keer presenteren om door u te worden vertaald. Nadat u elk segment hebt vertaald, druk op Ctrl+U om naar het volgende niet-vertaalde segment te gaan. Wanneer u wilt zien hoe uw vertaling eruit zal zien in zijn uiteindelijke opmaak, druk op Ctrl+D om het vertaalde document te genereren, dat zal worden gemaakt in de submap /target/ van uw projectmap. Gebruik, gedurende het vertalen, de menu's Bewerken en Ga naar om verschillende handige functies uit te voeren.
+
+
+
+ Valideren van uw tags
+
+ Als uw bronbestand een opgemaakt bestand is, bijv. Microsoft Word, LibreOffice Writer of HTML, zal OmegaT de opmaak converteren naar tags die de tekst die u vertaalt omsluiten. Documenten hebben ook vaak tags die niets te maken hebben met opmaak, maar die ook belangrijk zijn. In het bronbestand (en in het vertaalde bestand), zou een bronzin eruit kunnen zien als
+
+
+
+
+
+
+
+
+
+
+
+ OmegaT zal deze zin echter op de volgende manier presenteren:
+
+
+
+
+
+
+
+
+
+
+
+ De tags in OmegaT zijn grijs, zodat zij eenvoudig te herkennen zijn. Zij zijn niet beveiligd, zodat u ze kunt verwijderen, ze handmatig kunt invoeren of ze kunt verplaatsen in de doelzin. Indien u echter fouten maakte bij het typen van de tags voor de opmaak, kan het zijn dat uw vertaalde bestand niet wil openen. Druk daarom op Ctrl+T vóórdat uw uw vertaalde document genereert, om te valideren dat uw tags juist zijn.
+
+
+
+ Genereren van het vertaalde bestand
+
+ Als u zich er eenmaal van overtuigd hebt dat er geen tagfouten meer in uw vertaling staan, druk dan op Ctrl+D om het doelbestand te genereren, dat zal worden gemaakt in de submap /target/ van uw projectmap.
+
+
+
+ Enkele andere dingen om te onthouden
+
+
+
+ Indien een bestand niet wordt geladen in het venster Bewerken, dan zou het kunnen zijn dat uw bronbestand in een indeling is die niet werkt in OmegaT. Zie hoofdstuk 7: Bestandsfilters in de Gebruikershandleiding voor een lijst van bestandsindelingen die OmegaT kan afhandelen.
+
+
+
+
+
+ U kunt een nieuw project maken voor elke nieuwe taak en u kunt verschillende bronbestanden tegelijkertijd aan een project toevoegen.
+
+
+
+
+
+ Open het dialoogvenster Projecteigenschappen door te drukken op Ctrl+E om uzelf te herinneren aan de initiële instellingen van het project. Open het dialoogvenster Projectbestanden door te drukken op Ctrl+L om een lijst van bestanden in het project te zien.
+
+
+
+
+
+ Aan het einde van uw vertaling exporteert OmegaT drie vertaalgeheugens, genaamd "level1", "level2" en "omegat" naar uw projectmap. De geheugens "level1" en "level2" kunnen worden gedeeld met gebruikers van andere vertaalprogramma's. Het geheugen genaamd "omegat" kan worden gebruikt in OmegaT zelf, in toekomstige projecten die u maakt. Als u bestanden van vertaalgeheugens plaats in de submap /tm/ van uw projectmap, zal OmegaT automatisch daarin zoeken naar overeenkomstige segmenten, genaamd "fuzzy overeenkomsten".
+
+
+
+
+
+ U kunt een woordenlijst maken door te drukken op Ctrl+Shift+G, of bestaande woordenlijsten kopiëren naar de submap /glossary/ van uw projectmap en OmegaT zal automatisch daarin woorden opzoeken.
+
+
+
+
+
+ Het is vaak handig om te zoeken naar woorden en frasen in de brontekst en in uw vertaling, dus druk op elk moment op Ctrl+F voor het dialoogvenster "Tekst zoeken".
+
+
+
+
+
+ Voor een meer uitgebreide introductie, bekijk OmegaT for Beginners op de OmegaT website. Als u ondersteuning nodig hebt met enig aspect van OmegaT, neem dan vrijblijvend deel aan de OmegaT gebruikersgroep.
+
+
+
+
+
+
+ Installeren en uitvoeren van <application>OmegaT</application>
+
+
+ Windows-gebruikers<indexterm class="singular">
+ <primary>Installeren van OmegaT</primary> <secondary>Windows</secondary>
+ </indexterm>
+
+
+ Downloaden van het pakket
+
+ Heeft u een Java-implementatie die compatibel is met Oracle's Java 1.5 JRE?
+
+
+
+ Ja: download OmegaT_2.5.x_Windows_without_JRE.exe.
+
+
+
+ Nee / Ik weet het niet: download OmegaT_2.5.x_Windows.exe.
+
+ Dit pakket is gebundeld met Oracle's Java Runtime Environment. Deze JRE zal geen problemen veroorzaken met andere Java-implementaties die misschien al op uw systeem geïnstalleerd zijn.
+
+
+
+
+
+ <application>Installeren van OmegaT</application>
+
+ Dubbelklik op het programma dat u hebt gedownload en volg de instructies om OmegaT te installeren.
+
+
+
+ <application>OmegaT</application> toevoegen aan het menu Start of bureaublad<indexterm class="singular">
+ <primary>OmegaT aanpassen</primary> <secondary>Windows</secondary>
+ </indexterm>
+
+ Gedurende de installatie zal het programma u vragen of u een map in het menu Start wilt maken en of u een snelkoppeling op het bureaublad en in het systeemvak wilt maken.
+
+ U kunt daarna nog steeds een snelkoppeling maken door OmegaT.exe naar het bureaublad of menu Start te slepen om het van daaruit te koppelen.
+
+
+
+ <application>OmegaT<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>Windows</secondary>
+ </indexterm></application> uitvoeren
+
+ Als OmegaT eenmaal is geïnstalleerd, kunt u klikken op OmegaT.jar om het direct te starten, of u kunt het direct vanaf de opdrachtregel starten.
+
+ De eenvoudigste manier om OmegaT te starten is echter om het programmaOmegaT.exe uit te voeren.
+ OmegaT uitvoerenWindowsINI-bestand
+ De opties voor het opstarten van het programma zullen in dit geval worden gelezen uit het OmegaT.l4J.ini-bestand, dat zich bevindt in dezelfde map als het exe-bestand en wat u kunt bewerken om uw instellingen weer te geven. Het volgende voorbeeld voor het INI-bestand reserveert 1GB aan geheugen, zal Frans als taal van de gebruiker instellen en Portugal als het land:
+
+ # OmegaT.exe runtime configuration
+# To use a parameter, remove the '#' before the '-'
+# Memory
+-Xmx1024M
+# Language
+-Duser.language=FR
+# Country
+-Duser.country=CA
+
+
+
+ Upgraden van OmegaT<indexterm class="singular">
+ <primary>Upgraden van OmegaT</primary> <secondary>Windows</secondary>
+ </indexterm>
+
+ Deze informatie is alleen van toepassing op de "traditionele" Windows-versies van OmegaT. Het is niet van toepassing op de Web Start-versies, die automatisch worden geüpgraded, noch op de versies voor meerdere platformen die zijn geïnstalleerd op Windows.
+
+ Als u al een versie van OmegaT hebt geïnstalleerd op uw PC en wilt upgraden naar een meer recente versie, heeft u twee opties:
+
+
+
+ Installeren over de bestaande installatie heen. Selecteer eenvoudigweg dezelfde installatiemap als de bestaande installatie bij het installeren van de nieuw versie om dit te doen. De "oude" versie van OmegaT zal worden overschreven, maar alle instellingen ervan zullen worden behouden. Dit omvat ook de voorkeuren die zijn ingesteld binnen OmegaT, alle wijzigingen die u hebt gemaakt aan uw OmegaT.l4J.ini-bestand, en ook uw script om op te starten (.bat-bestand), als u er een gebruikt.
+
+
+
+ Met deze methode kunt u ook de versie "Windows without JRE" downloaden, omdat de nieuwe installatie uw bestaande JRE zal gebruiken.
+
+
+
+ Installeren in een nieuwe map. Hiermee zult u beide versies naast elkaar hebben staan, wat u zou kunnen doen totdat u zich op uw gemak voelt met de nieuwe versie. Deze methode zal ook de voorkeuren en instellingen gebruiken die u hebt gemaakt binnen OmegaT. In dit geval echter:
+
+
+
+ Als u wijzigingen hebt gemaakt in uw OmegaT.l4J.ini-bestand en/of een .bat-bestand gebruikt, moet u die kopiëren naar de nieuwe installatie.
+
+
+
+
+
+ Als uw bestaande installatie van OmegaT een "Windows with JRE"-versie is, moet de nieuwe versie ook een "Windows with JRE"-versie zijn.
+
+
+
+
+
+
+
+
+ Linux (Intel)-gebruikers<indexterm class="singular">
+ <primary>Installeren van OmegaT</primary> <secondary>Linux</secondary>
+ </indexterm>
+
+
+ Downloaden van het juiste pakket
+
+ Heeft u een Java-implementatie die compatibel is met Oracle's Java 1.5 JRE?
+
+
+
+ Ja: download OmegaT_2.5.x_Without_JRE.zip.
+
+
+
+ Nee / Ik weet het niet: download OmegaT_2.5.x_Linux.tar.bz2.
+
+ Dit pakket is gebundeld met Oracle's Java Runtime Environment. Deze JRE zal geen problemen veroorzaken met andere Java-implementaties die misschien al op uw systeem geïnstalleerd zijn.
+
+
+
+
+
+ <application>Installeren van OmegaT</application>
+
+ Uitpakken/untarren van het gedownloade bestand. Dit zal een map omegat/ maken in de werkmap waarin u alle nodige bestanden vindt om OmegaT uit te voeren. Uitpakken van het .tar.gz bestand:
+
+ $ tar xf downloaded_file.tar.gz
+
+
+
+ <application>OmegaT</application> toevoegen aan uw menu's (KDE) of panelen (Gnome)
+
+
+ KDE 4-gebruikers<indexterm class="singular">
+ <primary>OmegaT aanpassen</primary> <secondary>KDE 4</secondary>
+ </indexterm>
+
+ U kunt OmegaT als volgt aan uw menu's toevoegen:
+
+
+
+ Druk op Alt+F2 om KRunner weer te geven. Typ kmenuedit+enter om de opdracht uit te voeren. De KMenuEditor verschijnt. Selecteer in KMenuEditor Bestand -> Nieuw item.
+
+
+
+ Dan, na het selecteren van een passend menu, voeg een submenu/item toe met Bestand - Nieuw submenu en Bestand - Nieuw item. Voer OmegaT in als de naam van het nieuwe item.
+
+
+
+ Gebruik, in het veld "Commando", de navigatieknop om uw OmegaT startscript te vinden (het bestand genaamd OmegaT in de uitgepakte map) en selecteer dat.
+
+
+
+ Klik op de pictogramknop (rechts van de velden Naam/Beschrijving/Commentaar)
+
+
+
+ Andere pictogrammen - Bladeren en navigeer naar de submap /images in de OmegaT-toepassingsmap. Selecteer het pictogram OmegaT.png.
+
+
+
+ Sla tenslotte de wijzigingen op met Bestand - Opslaan.
+
+
+
+
+
+ Gnome-gebruikers<indexterm class="singular">
+ <primary>OmegaT aanpassen</primary> <secondary>GNOME</secondary>
+ </indexterm>
+
+ U kunt OmegaT als volgt aan uw menu's toevoegen:
+
+
+
+ Klik met rechts op het paneel - Nieuwe starter.
+
+
+
+ Voer "OmegaT" in in het veld "Naam"; gebruik, in het veld "Commando", de navigatieknop om uw startscript voor OmegaT te vinden (het bestand genaamd OmegaT in de uitgepakte map). Selecteer dat en bevestig met OK.
+
+
+
+ Klik op de pictogramknop, en druk dan op Bladeren... en navigeer naar de submap /images in de toepassingenmap OmegaT. Selecteer het pictogram OmegaT.png. GNOME kan weigeren om de pictogrambestanden weer te geven in de beschikbare indelingen en in het begin een SVGbestand verwachten, maar als de map wordt geselecteerd, zouden de bestanden moeten verschijnen en kan OmegaT.png worden geselecteerd.
+
+
+
+
+
+
+ <application>OmegaT<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>Linux</secondary>
+ </indexterm></application> uitvoeren
+
+ U kunt OmegaT opstarten vanaf de opdrachtregel met een script dat de opties voor opstarten bevat of u kunt klikken op OmegaT.jar om het direct op te starten. Methoden verschillen, afhankelijk van de distributie. Zorg ervoor dat de instellingen van uw PATH juist zijn en dat .jar-bestanden juist zijn gekoppeld aan een Java-starter. Bekijk "Starten vanaf de opdrachtregel" hieronder voor meer informatie.
+
+
+
+
+ Mac OS X-gebruikers<indexterm class="singular">
+ <primary>OS X</primary> <secondary>Installeren van OmegaT</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Installeren van OmegaT</primary> <secondary>OS X</secondary>
+ </indexterm>
+
+
+ Downloaden van het pakket
+
+ OmegaT 2.5 vereist Java 1.5 om te kunnen worden uitgevoerd. Gebruik "Software Update..." uit het menu Apple om uw versie van Java bij te werken.
+
+ Download OmegaT_2.5.x_Mac.zip.
+
+
+
+ <application>Installeren van OmegaT</application>
+
+ Dubbelklik op OmegaT_2.5.x_Mac.zip om het uit te pakken. Dit zal een map maken dieOmegaTheet. De map bevat 2 bestanden: index.html en OmegaT.app. Kopieer de map naar een toepasselijke map (bijv. Toepassingen). Als u dit gedaan heeft kunt u het bestand OmegaT_2.5.x_Mac.zip verwijderen, het is niet langer nodig.
+
+
+
+ <application>OmegaT</application> toevoegen aan het dock<indexterm class="singular">
+ <primary>OS X</primary> <secondary>OmegaT toevoegen aan het dock</secondary> <seealso>OmegaT aanpassen</seealso>
+ </indexterm>
+
+ Sleep en zet OmegaT.app op het Dock neer.
+
+
+
+ <application>OmegaT<indexterm class="singular">
+ <primary>OS X</primary> <secondary>OmegaT uitvoeren</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>OS X</secondary>
+ </indexterm></application> uitvoeren
+
+ Dubbelklik opOmegaT.app of klik op zijn locatie in het dock
+
+ Klik met rechts op OmegaT.app en selecteer "Pakketinhoud weergeven" om toegang te krijgen tot Info.plist, en open het bestand door er met rechts op te klikken en selecteer uw tekstverwerker van uw keuze. U kunt ook met "cd" daar rechtstreeks naartoe gaan vanaf de opdrachtregel en Info.plist openen in een verwerker voor de opdrachtregel zoals emacs of vi.
+ OS XOmegaT aanpassenStartparameters
+
+ OS XOmegaT aanpassen
+
+
+ U kunt het gedeelte Properties en ook het gedeelte VMOptions aanpassen.
+
+ Indien u waarden wilt toevoegen aan VMOptions, plaatst u er een spatie tussen. Bijvoorbeeld: -Xmx1024M -Duser.language=ja zal OmegaT opstarten met 1024MB aan geheugen en de gebruikersinterface in het Japans.
+
+ Als u meerdere instanties van OmegaT.app moet uitvoeren, gebruik dan in plaats daarvan het bestand JavaApplicationStub dat zich bevind in OmegaT.app/ Contents/MacOS/.
+
+ Gebruik het bestand OmegaT.jar dat zich bevindt in OmegaT.app/Contents/Resources/Java/ om OmegaT vanaf de opdrachtregel te starten. Bekijk "Starten vanaf de opdrachtregel" hieronder voor meer informatie.
+
+
+
+ Mac OS X goede dingen
+
+ OmegaT.app kan worden bereikt vanuit Mac OS X Services. U kunt dus ergens in OmegaT een woord selecteren en de Services gebruiken om het te controleren, bijvoorbeeld in Spotlight of in Google. U kunt ook AppleScript of Automator gebruiken om Services of scripts te maken die acties die veel voorkomen te automatiseren.
+
+
+
+
+ Andere systemen<indexterm class="singular">
+ <primary>Installeren van OmegaT</primary> <secondary>Andere systemen</secondary>
+ </indexterm>
+
+ Deze informatie is van toepassing op systemen zoals Solaris SPARC/x86/x64, Linux x64/PowerPC, Windows x64
+
+
+ Downloaden van het juiste pakket
+
+ OmegaT is beschikbaar, gebundeld met een Oracle Java JRE voor Linux (Intel x86)- en Windows-platformen. Gebruikers van andere platformen (Linux PowerPC, Linux x64, Solaris SPARC/x86/x64, Windows x64 etc) moeten een werkende compatibele Java JRE op hun systeem hebben om OmegaT te kunnen gebruiken.
+
+ Heeft u een Java-implementatie die compatibel is met Oracle's Java 1.5 JRE?
+
+
+
+ Ja: download OmegaT_2.5.x_Windows_without_JRE.zip. Dit pakket kan worden gebruikt op elk platform waar een Java 1.5 JRE compatibele JRE is geïnstalleerd.
+
+
+
+ Ik weet het niet: open een terminal en type "java -version". Als een "command not found" of soortgelijk bericht wordt teruggegeven, is het waarschijnlijk dat Java niet is geïnstalleerd op uw systeem.
+
+
+
+ Nee: Zorg voor een Java JRE voor uw systeem (zie hieronder) en download OmegaT_2.5.x_Without_JRE.zip.
+
+ Oracle levert JRE's voor Solaris SPARC/x86 (Java 1.5) en voor Linux x64, Solaris x64, Windows x64 (Java 1.5) op http://www.oracle.com/technetwork/java/archive-139210.html.
+
+ IBM levert JRE's voor Linux PowerPC op http://www.ibm.com/developerworks/java/jdk/linux/download.htm
+
+ Volg de installatie-instructies voor het pakket dat u nodig hebt.
+
+
+
+
+
+ <application>Installeren van OmegaT</application><indexterm class="singular">
+ <primary>Installeren van OmegaT</primary> <secondary>Andere systemen</secondary>
+ </indexterm>
+
+ Pak eenvoudigweg het bestand OmegaT_2.5.x_Without_JRE.zip uit om OmegaT te installeren. Dit maakt een map ./OmegaT_2.5.x_Without_JRE/ in de werkmap waarin u alle benodigde bestanden zult vinden om OmegaT uit te voeren.
+
+
+
+ Installeren van handige sneltoetsen
+
+ Volg de instructies voor uw systeem om sneltoetsen voor OmegaT op handige plaatsen te installeren.
+
+
+
+ <application>OmegaT<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>Andere systemen</secondary>
+ </indexterm></application> uitvoeren
+
+ Als OmegaT eenmaal is geïnstalleerd, kunt u het direct vanaf de opdrachtregel starten, u kunt een script maken dat de startparameters voor de opdrachtregel bevat of u kunt op OmegaT.jar klikken om het direct uit te voeren. Methoden verschillen, afhankelijk van de distributie. Zorg ervoor dat de instellingen van uw PATH juist zijn en dat .jar-bestanden juist zijn gekoppeld aan een Java-starter. Bekijk "Starten vanaf de opdrachtregel" hieronder voor meer informatie.
+
+
+
+
+ Java Web Start gebruiken<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>Java Web Start gebruiken</secondary>
+ </indexterm>
+
+ Java Web Start-technologie (onderdeel van Java 1.5 en hoger) kan worden gebruikt om met één enkele klik zelfstandige Java softwaretoepassingen uit te voeren over het netwerk. Java Web Start zorgt er voor dat de meest recente versie van de toepassing zal worden uitgevoerd, evenals de juiste versie van de Java Runtime Environment (JRE). Laad de volgende URL in uw browser om OmegaT voor de eerste keer te starten met Java Web Start:
+
+ http://omegat.sourceforge.net/webstart/OmegaT.jnlp
+
+ Download het bestandOmegaT.jnlp en klik er dan op. Gedurende de installatie, afhankelijk van uw besturingssysteem, zou u verschillende beveiligingswaarschuwingen kunnen ontvangen. De rechten die u aan deze versie geeft (welke kunnen lijken op "onbeperkte toegang tot de computer") zijn identiek aan de rechten die u geeft voor de locale versie, d.i. zij geven toegang tot de harde schijf van de computer. Opvolgende klikken op OmegaT.jnlp zal leiden tot het controleren op upgrades, ze installeren als ze er zijn, en dan OmegaT starten. Na de initiële installatie kunt u natuurlijk OmegaT.jnlp ook gebruiken als u offline bent.
+
+ Privacy: OmegaT Java Web Start slaat geen informatie van u op buiten de computer waarop het wordt uitgevoerd. De toepassing wordt slechts uitgevoerd op uw machine. Uw documenten en vertaalgeheugens blijven op uw computer, en het OmegaTproject zal geen toegang hebben tot uw werk of informatie.
+
+ Merk op dat als u argumenten voor het opstarten wilt gebruiken (zie boven), u de normale installatie moet gebruiken.
+
+
+
+ OmegaT starten vanaf de opdrachtregel<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>Starten vanaf de opdrachtregel</secondary>
+ </indexterm>
+
+ Normaal gesproken is het niet nodig om OmegaT te starten vanaf de opdrachtregel. Het alternatief van de opdrachtregel stelt echter de gebruiker in staat om het gedrag van het programma te beheren en aan te passen. Er zijn twee manieren om OmegaT te starten met behulp van de opdrachtregel.
+
+
+ Openen van een venster voor de opdrachtregel
+
+ Een venster voor de opdrachtregel wordt ook wel een "terminalvenster" genoemd. Op Windows wordt het een "MS-DOSvenster" genoemd en is het beschikbaar via het menu Start, in Alle programma's → Bureau-accessoires, via het item "Opdrachtprompt". Het equivalent voor Mac OS X is de toepassing Terminal die zich bevind in Programma's → Hulpprogramma's.
+
+ U moet normaal gesproken twee opdrachten typen om OmegaT te starten. De eerste hiervan is:
+
+ cd {map}
+
+ waar {map} de naam is van de map, met het complete pad, waarin uw OmegaT-programma - specifiek het bestand OmegaT.jar - is geplaatst. In de praktijk zal deze opdracht er ongeveer zo uitzien:
+
+ Op Windows
+
+ cd C:\Program
+ Files\OmegaT
+
+ Op Mac OS X
+
+ cd <locatie OmegaT.app>/OmegaT.app/Contents/Resources/Java/
+
+
+ Op Linux
+
+ cd /usr/local/omegat
+
+ Deze opdracht wijzigt de map naar de map die het uitvoerbare OmegaT-bestand bevat. De tweede opdracht is de opdracht die OmegaT echt start. In zijn meest basale vorm is deze opdracht:
+
+ java -jar
+ OmegaT.jar
+
+ Let op de hoofdletters - het programma zal niet starten als u invoert omegat in plaats van OmegaT !
+
+ Deze methode heeft het bijzondere voordeel dat het geschikt is om oorzaken voor problemen op te sporen: als een fout optreedt gedurende het gebruiken van het programma wordt een foutbericht weergegeven in het terminalvenster dat bruikbare informatie kan bevatten over de oorzaak.
+
+ De bovenstaande methode is een niet zo praktische manier om een programma routinematig te starten. Om deze reden zijn de twee hierboven beschreven opdrachten opgenomen in een bestand (een "script", ook wel een ".bat-bestand" genoemd op Windows-systemen).
+
+ Als dit bestand wordt uitgevoerd worden de daarin opgenomen opdrachten automatisch uitgevoerd. Derhalve is het voldoende om dit bestand aan te passen om wijzigingen aan te brengen in de startopdracht.
+
+
+
+ Argumenten voor de startopdracht<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>Argumenten voor bestand om op te starten</secondary>
+ </indexterm>
+
+ De basisopdracht is hierboven al genoemd. Wijzigingen voor deze opdracht behelzen het daaraan toevoegen van "argumenten". Argumenten worden toegevoegd ná het initiële "java" en vóór het gedeelte "-jar OmegaT.jar". Onthoud dat u in Windows het bestand OmegaT.l4J.ini kunt wijzigen om uw voorkeuren weer te geven. Op Mac OSX kunt u Info.plist wijzigen, dat zich bevindt in OmegaT.app/Contents/, om hetzelfde te doen.
+
+ Een lijst van mogelijke argumenten wordt hieronder weergegeven. Gevorderde gebruikers kunnen meer informatie over de argumenten vinden door man java in het terminalvenster te typen.
+
+
+
+ Taal van de gebruikersinterface
+
+ -Duser.language=XX
+ OmegaT uitvoerenArgumenten voor bestand om op te startenUser.language
+ Normaal gesproken, d.i. als OmegaT wordt gestart zonder enig argument, detecteert het programma eerst de taal van het besturingssysteem van de gebruiker. Als een gebruikersinterface in deze taal beschikbaar is gebruikt OmegaT die. Dus, als het besturingssysteem van de gebruiker Russisch is en OmegaT is vertaald in het Russisch, wordt OmegaT weergegeven met een Russische gebruikersinterface, Russische menu's, etc. Als de taal van het besturingssysteem van de gebruiker niet beschikbaar is gebruikt OmegaT standaard Engels. Dit is het standaard gedrag.
+
+ Het argument "-Duser.language=XX" zorgt ervoor dat OmegaT de gespecificeerde taal gebruikt, in plaats van de taal van het besturingssysteem van de gebruiker. "XX" in de opdracht staat voor de code van twee letters van de gewenste taal. De opdracht, om OmegaT te starten met een Franse interface (bijvoorbeeld op een Russisch besturingssysteem), zou daarom zijn:
+
+ java -Duser.language=fr -jar
+ OmegaT.jar
+
+
+
+
+
+ Instellen land gebruiker
+
+ -Duser.country=XX
+ OmegaT uitvoerenArgumenten voor bestand om op te startenUser.country
+ Naast de taal kunt u ook het land specificeren, bijvoorbeeld CN of TW in geval van de Chinese taal. U moet zowel de taal als het land specificeren om de gids Snel starten in de gewenste taal weer te geven. Dit is zelfs nodig als er slechts één combinatie beschikbaar is, zoals pt_BR in geval van Portugees / Braziliaans.
+
+
+
+
+
+ Antialiasing lettertype - (alleen Java 1.5)
+
+ -Dswing.aatext=true
+ OmegaT uitvoerenArgumenten voor bestand om op te startenAntialiasing lettertype
+ Dit argument beïnvloedt de anti-aliasing van de lettertypen, waarbij hun weergave wordt verbeterd.
+
+
+
+ Toewijzen van geheugen
+
+ -XmxZZM
+ OmegaT uitvoerenArgumenten voor bestand om op te startenToewijzen van geheugen
+ Deze opdracht wijst meer geheugen toe aan OmegaT. Standaard wordt 256 Mb toegewezen, dus er is geen voordeel te behalen door minder dan dit getal toe te wijzen. "ZZ" staat voor de toegewezen geheugenruimte in megabytes. De opdracht om OmegaT te starten met toewijzing van 1024 Mb (1 gigabyte) aan geheugen luidt dan ook:
+
+ java -Xmx1024M -jar
+ OmegaT.jar
+
+
+
+ Proxy host IP-adres
+
+ -Dhttp.proxyHost=nnn.nnn.nnn.nnn
+ OmegaT uitvoerenArgumenten voor bestand om op te startenProxyserver IP-adres
+ Het IP-adres van uw proxyserver, als uw systeem een proxy gebruikt
+
+
+
+ Proxyserver poortnummer
+
+ Dhttp.proxyPort=NNNN
+ OmegaT uitvoerenArgumenten voor bestand om op te startenProxyserver - Poortnummer
+ Het poortnummer dat uw systeem gebruikt om toegang te krijgen tot de proxyserver.
+
+
+
+ Google Translate V2
+
+ -Dgoogle.api.key=A123456789B123456789C123456789D12345678
+ OmegaT uitvoerenArgumenten voor bestand om op te startenGoogle Translate V2
+ Indien u bent geabonneerd op de services van Google Translate, dient u hier uw eigen private Google API-sleutel in te voeren. Onthoud dat de sleutel 38 tekens lang is.
+
+
+
+ Argumenten mogen worden gecombineerd: Voor het starten van OmegaT met alle hierboven genoemde voorbeelden zou de opdracht zijn:
+
+ java -Dswing.aatext=true -Duser.language=pt
+ -Duser.country=BR -Xmx1024M -DDhttp.proxyHost=192.168.1.1
+ -Dhttp.proxyport=3128 -jar
+ -OmegaT.jar
+
+
+
+ OmegaT in de modus Opdrachtregel<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>modus Opdrachtregel</secondary>
+ </indexterm>
+
+ Het doel van de console-modus is om OmegaT als vertaalgereedschap te gebruiken in een script-omgeving. Indien wordt begonnen in de console-modus, wordt geen GUI geladen (dus het zal werken op elke console) en het opgegeven project wordt automatisch verwerkt zoals verzocht.
+
+
+ Vooraf vereist
+
+ Een geldig OmegaT-project moet aanwezig zijn om OmegaT uit te kunnen voeren in de modus Opdrachtregel. De locatie maakt niet uit omdat het bij de start toch al moet worden ingevuld in de opdrachtregel.
+
+ Indien u gewijzigde instellingen nodig hebt, moeten de configuratiebestanden beschikbaar zijn. Dat kan op twee manieren worden bereikt:
+
+
+
+ Voer OmegaT normaal uit (met de GUI) en maak de instellingen. Indien u OmegaT in console-modus start, zal het dezelfde instellingen gebruiken.
+
+
+
+ Indien u OmegaT niet normaal kunt uitvoeren (geen grafische omgeving beschikbaar): kopieer de instellingen vanaf een andere installatie van OmegaT op een andere machine naar een bepaalde map. De locatie maakt niet uit, omdat u die toch in kunt vullen in de opdrachtregel bij het starten. De relevante bestanden zijn filters.conf en segmentation.conf en kunnen worden gevonden in de startmap van de gebruiker (bijv. C:\Documents and Settings\%User%\OmegaT onder Windows, %user%/.omegat/ onder Linux).
+
+
+
+
+
+ Beginnen in console-modus
+
+ Enkele extra parameters moeten bij het starten worden opgegeven om OmegaT in console-modus te starten. De meest belangrijke is <project-dir>, en optioneel --config-dir=<config-dir>. Voorbeeld:
+
+ java -jar OmegaT.jar /pad/naar/project \
+
+ --config-dir=/pad/naar/config-bestanden/ \
+
+
+ --mode=console-translate|console-createpseudotranslatetmx|console-align
+
+ --source-pattern={reguliere uitdrukking}
+
+ Merk op dat alle parameters beginnen met een dubbel "-"-teken.
+
+ Uitleg:
+
+
+
+ <project-dir> vertelt OmegaT waar het project kan worden gevonden dat moet worden vertaald. Indien opgegeven start OmegaT in de console-modus en zal het opgegeven project gaan vertalen.
+
+
+
+
+
+ --config-dir=<config-dir> vertelt OmegaT in welke map de configuratiebestanden zijn opgeslagen. Indien niet opgegeven gaat OmegaT terug naar de standaard waarden (OmegaT-dir onder beginmap van de gebruiker, of indien niet beschikbaar: de huidige werkmap). Onthoud het dubbele "-"-teken
+
+
+
+
+
+ --mode=...-OmegaT begint in de console-modus om één van de volgende services automatisch uit te voeren
+
+
+
+ --mode=console-translate
+
+ In deze modus zal OmegaT proberen om de bestanden in /source/ te vertalen met de beschikbare vertaalgeheugens. Dit is handig om OmegaT uit te voeren op een server waarmee TMX-bestanden automatisch worden toegevoegd aan het project.
+
+
+
+ --mode=console-createpseudotranslatetmx
+
+ In deze modus zal OmegaT een TMX voor het gehele project maken, alleen gebaseerd op de bronbestanden. U specificeert dat het TMX/bestand moet worden gemaakt met
+
+ --pseudotranslatetmx=allsegments.tmx
+ --pseudotranslatetype=[equal|empty]
+
+ Het argument pseudotranslatetype specificeert, of de doelsegmenten gelijk moeten zijn aan de bron of leeg moeten worden gelaten.
+
+
+
+ --mode=console-align
+
+ In deze modus zal OmegaT het bestand met de Java-eigenschappen die zijn gevonden in de map /source/ van het project vergelijken met de inhoud op de opgegeven locatie. De resulterende TMX wordt opgeslagen in de map /omegat/ onder de naam align.tmx.
+
+ Een aanvullende parameter, die de locatie van de doelgegevens specificeert, is in dit geval vereist:
+
+ --alignDir={locatie van vertaalde bestanden}
+
+ alignDir moet een vertaling bevatten in de doeltaal van het project. Als, bijvoorbeeld, het project EN->FR is, moet alignDir een bundle bevatten die eindigt op _fr. De resulterende TMX wordt opgeslagen in de map omegat onder de naam align.tmx.
+
+
+
+
+
+ --source-pattern={reguliere uitdrukking}
+
+ Als deze modus werd gebruikt, zal deze optie de bestanden specificeren die automatisch moeten worden verwerkt. Als de parameter niet is gespecificeerd, zullen alle bestanden worden verwerkt. Hier zijn een paar typische voorbeelden om uw keuze te beperken:
+
+
+
+ .*\.html
+
+ Alle HTML-bestanden zullen worden vertaald - merk op dat de punt in het gebruikelijke *.html moet worden vooraf gegaan door een backslash (\.) zoals gespecificeerd door de regels voor reguliere uitdrukkingen
+
+
+
+ test\.html
+
+ Alleen het bestand test.html aan het begin van de map source zal worden vertaald. Indien er andere bestanden, genaamd test.html, in andere mappen staan, worden die genegeerd.
+
+
+
+ dir-10\\test\.html
+
+ Alleen het bestand test.html in de map dir-10 zal worden verwerkt. Merk opnieuw op dat ook de backslash moet worden voorafgegaan door een backslash.
+
+
+
+
+
+
+
+ optie Quiet
+
+ Een extra parameter voor de opdrachtregel, specifiek voor de console-modus: --quiet.In de modus quiet, wordt er minder informatie gelogd op het scherm. De berichten die u normaal gesproken zou vinden in de statusbalk worden niet weergegeven.
+
+ Gebruik: java -jar OmegaT.jar /pad/naar/project --mode=console-translate --quiet
+
+
+
+ Optie Tags valideren
+
+ Een andere parameter voor de opdrachtregel, specifiek voor de console-modus: --tag-validation=[abort|warn]. Als deze parameter wordt toegevoegd, wordt het valideren van tags toegepast voorafgaande aan vertalen/uitlijnen. Als de waarde abort is dan worden bij tagfouten de fouten afgedrukt en het programma stopt. Als de waarde warn is dan worden fouten afgedrukt maar OmegaT gaat door.
+
+ Gebruik: java -jar OmegaT.jar /pad/naar/project --mode=console-translate --tag-validation=abort
+
+
+
+
+
+ <application>OmegaT</application> bouwen vanuit de bron<indexterm class="singular">
+ <primary>OmegaT uitvoeren</primary> <secondary>OmegaT bouwen vanuit de bron</secondary>
+ </indexterm>
+
+ Onthoud dat u ook het programma ant (http://ant.apache.org/bindownload.cgi) nodig hebt om uw eigen versie van OmegaT te bouwen. Pak het bestand OmegaT_2.5.x_Source.zip uit en geef de map OmegaT_2.5.x_Source op of voer de map ./omegat/ in voor de checkout-code van SVN. Controleer of een bestand build.xml in die map aanwezig is. Typ dan op de opdrachtregel:
+
+ $ ant jar release
+
+ Dit zal een volledige distributie van OmegaT maken in de map ./dist/, waarin u alle benodigde bestanden zult vinden om OmegaT uit te voeren.
+
+
+
+
+ De gebruikersinterface
+
+
+ Items in de gebruikersinterface
+
+
+ Veel gebruikte vensters<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary>
+ </indexterm>
+
+
+
+ OmegaT hoofdvenster
+
+
+ bevat het hoofdmenu, statusbalk en verschillende vensters:
+
+
+
+ Bewerken - waar u uw vertaling typt en bewerkt
+
+
+
+ Overeenkomsten - geeft de meest overeenkomende segmenten vanuit vertaalgeheugens weer
+
+
+
+ Woordenlijst - geeft terminologie weer
+
+
+
+ Woordenboek - geeft informatie weer die verschaft wordt door woordenboeken
+
+
+
+ Machinevertaling - geeft de vertaling weer zoals die wordt verschaft door services voor machinevertaling zolas Google Translate
+
+
+
+ Meerdere vertalingen - geeft alternatieve vertalingen weer - indien enige zijn ingevoerd - voor het huidige segment
+
+
+
+ Notities - opmerkingen van de vertaler met betrekking tot huidige segment
+
+
+
+ Opmerkingen - opmerkingen van de vertaler met betrekking tot huidige segment
+
+
+
+
+
+
+
+
+ SneltoetsenCtrl+L - venster Projectbestanden
+ venster Projectbestanden
+
+
+ De lijst van uw te vertalen bestanden (openen met CtrlL, sluiten met Esc)
+
+
+
+
+
+ SneltoetsenCtrl+F - venster Zoeken
+ venster Zoeken
+
+
+ Gebruikt om te zoeken naar specifieke segmenten in het project (openen met CtrlF, sluiten met Esc)
+
+
+
+
+
+
+ Minder frequent gebruikt
+
+
+
+
+ SneltoetsenCtrl+T - venster Tags valideren
+ venster Tags valideren
+
+
+ Gebruikt om te controleren of er tagfouten in vertalingen staan (openen met CtrlT sluiten met Esc)
+
+
+
+
+
+ SneltoetsenF1 - Help
+ Help-browser
+
+
+ gebruikt om de gebruikershandleiding te lezen (openen met F1, sluiten met Esc)
+
+
+
+
+ venster Statistieken
+
+
+ Gebruikt om het venster met de statistieken van het project te openen, geef het weer met behulp van
+ menu ExtraStatistieken
+ ExtraStatistieken.
+
+
+
+
+ venster Statistieken voor overeenkomsten
+
+
+ Gebruikt om de statistieken voor overeenkomsten in het project weer te geven, selecteer
+ menu ExtraStatistieken voor overeenkomsten
+ ExtraStatistieken voor overeenkomstenom het te openen.
+
+
+
+
+
+
+ dialoogvenster Projectinstellingen<indexterm class="singular">
+ <primary>Project</primary> <secondary>Projectinstellingen</secondary>
+ </indexterm>
+
+ De dialoogvensters hieronder worden gebruikt om de projectinstellingen voor OmegaT project te wijzigen. Elk wordt in detail beschreven in een afzonderlijk gedeelte; de informatie hieronder somt hun gebruik op en hoe zij worden geactiveerd:
+
+
+
+
+ SneltoetsenCtrl+E - Projecteigenschappen
+
+ menu ProjectEigenschappen
+ Projecteigenschappen
+
+
+ Gebruikt om de projectmappen en talen aan te passen, (openen met CtrlEProjecteigenschappen..., sluiten met Esc)
+
+
+
+
+
+ Projectinstellingenlettertype
+ Lettertype
+ menu Optieslettertype
+
+
+
+ Gebruikt om het lettertype aan te passen dat door OmegaT wordt gebruikt voor het weergeven van bron, vertaling, overeenkomsten en de termen uit de woordenlijst, (openen met OptiesLettertype..., sluiten met Esc)
+
+
+
+
+
+ Projectinstellingenbestandsfilters
+ Bestandsfilters
+ menu Optiesbestandsfilters
+
+
+
+ Gebruikt om de afhandeling van ondersteunde bestandsformaten aan te passen (openen met OptiesBestandsfilters..., sluiten met Esc)
+
+
+
+
+
+ Projectinstellingensegmentatie
+ Segmentatie
+ menu OptiesSegmentatie
+
+
+
+ Gebruikt om de manier waarop uw tekst wordt opgedeeld in zinnen te wijzigen (openen met OptiesSegmentatie, sluiten met Esc)
+
+
+
+
+
+ Projectinstellingenbewerken (gedrag)
+ Bewerken (gedrag)
+ menu Optiesbewerken (gedrag)
+
+
+
+ Gebruikt om te wijzigen hoe OmegaT zich gedraagt bij het doorlopen van de segmenten, (openen met OptiesBewerken (gedrag)..., sluiten met Esc)
+
+
+
+
+
+
+
+ <application>OmegaT</application> hoofdvenster<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>hoofdvenster</secondary> <tertiary>- afbeelding</tertiary>
+ </indexterm><indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>hoofdvenster</secondary>
+ </indexterm>
+
+
+ OmegaT-vensters
+
+
+
+
+
+
+
+
+
+
+
+
+ Het hoofdvenster bestaat uit verschillende vensters, het hoofdmenu en een statusbalk. U kunt de positie van elk venster wijzigen of het zelfs losmaken en er een zelfstandig venster van maken door het venster te slepen aan zijn naam. Afhankelijk van de status van het venster kunnen verschillende tekens verschijnen in de rechterbovenhoek ervan.
+
+
+ pictogrammen voor vensters<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>pictogrammen voor vensters</secondary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ minimaliseert het venster zodat alleen de naam wordt weergegeven aan de onderzijde van het venster.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ maximaliseert het venster.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ maakt het venster los van het hoofdvenster.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ zet het venster weer vast in het hoofdvenster.
+
+
+
+
+
+ U kunt de vensters elkaar laten overlappen als u dat wilt. Als dat gedaan wordt zullen de vensters aan de bovenzijde een tab weergeven. De scheidingen tussen de vensters kunnen worden gesleept om de afmetingen van vensters te wijzigen. Indien u niet meer weet welke wijzigingen u aan de gebruikersinterface heeft aangebracht, kunt u op elk moment
+ Vensters van OmegaTvensters in OmegaT
+
+ Vensters van OmegaTterugzetten naar fabrieksinstellingen
+ Opties → Hoofdvenster herstellen gebruiken om terug te keren naar de originele lay-out.
+
+ De tellers in de rechter benedenhoek houden de voortgang van de vertaling bij (getallen in de linkerkolom verwijzen naar de afbeelding hierboven):
+
+
+ Hoofdvenster - tellers<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>tellers</secondary>
+ </indexterm>
+
+
+
+
+
+
+ 33/33
+
+ aantal segmenten - vertaald / totaal van huidig bestand
+
+
+
+ 2780/2780
+
+ aantal unieke segmenten - vertaald / totaal in het project
+
+
+
+ 3760
+
+ totaal aantal segmenten (inclusief herhalingen) in het project
+
+
+
+ 126/127
+
+ aantal tekens in het bron- en in het doelsegment
+
+
+
+
+
+ Vanuit praktisch oogpunt is het meest belangrijkste paar het tweede paar getallen: het vertelt hoeveel u tot op dit moment hebt gedaan, in relatie tot het totaal van het tweede getal. Het project in het voorbeeld is zeker voltooid, omdat alle unieke segmenten zijn vertaald.
+
+
+ venster Bewerken<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Bewerken</secondary>
+ </indexterm>
+
+ Hier typt en bewerkt u uw vertaling. Het venster Bewerken geeft de tekst van het gedeeltelijk vertaalde document weer: de tekst die al vertaald is wordt vertaald weergegeven en de tekst die nog niet vertaald is wordt weergegeven in de originele taal. De weergegeven tekst is gesplitst in segmenten en u kunt door het document scrollen en op een willekeurig segment dubbelklikken om het te bewerken. In het bovenstaande geval zijn de reeds vertaalde segmenten weergegeven in geel, maar u kunt de instelling wijzigen om aan uw voorkeuren te voldoen (zie ).
+
+ Eén van de bovenstaande segmenten is het huidige segment. Het is het segment dat wordt weergegeven in twee gedeelten. Het bovenste gedeelte is weergegeven in de brontaal, in vette tekens met een groene achtergrondkleur, het onderste gedeelte is het bewerkingsveld, gescheiden door een markering:
+ Segment markering
+ de markering is <segment nnnn> waarbij nnnn het getal is van het segment in het project. Gebruik het bovenste gedeelte als een verwijzing en vervang of pas de inhoud van het bewerkingsveld aan door/met uw vertaling.
+
+ Afhankelijk van het gedrag van uw voorkeur tijdens het bewerken kan het bewerkingsveld voor het niet-vertaalde segment leeg zijn, de brontekst bevatten of de vertaling bevatten van de tekenreeks die het meeste lijkt op die welke u gaat vertalen. Als u verder gaat naar een ander segment wordt de vertaling gevalideerd en opgeslagen. Als u wilt dat het segment niet vertaald wordt, maakt u eenvoudigweg het bewerkingsveld leeg door alle tekst te verwijderen (selecteer alles met Ctrl+A en verwijder het met Del). OmegaT is in staat om vertalingen op te slaan die identiek aan de bron zijn. Het is handig voor documenten die handelsmerken, (bedrijfs-)namen of andere woorden met hoofdletters bevatten of delen in een derde taal die niet vertaald behoeven te worden. Zie Vertaling bewerken voor meer details.
+
+ Als u met rechts klikt op het venster bewerken opent een pop-upmenu waarin Knippen, Kopiëren, Plakken (d.i. dezelfde functies als CtrlX, CtrlC en CtrlV) en de functies Ga naar segment.
+
+
+
+ venster Overeenkomsten<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Overeenkomsten</secondary>
+ </indexterm>
+
+
+ <indexterm class="singular">
+ <primary>Overeenkomsten</primary> <secondary>venster Overeenkomsten - afbeelding</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Overeenkomsten - afbeelding</secondary>
+ </indexterm>venster Overeenkomsten
+
+
+
+
+
+
+
+
+
+
+
+
+ Het venster Overeenkomsten toont de meest overeenkomende segmenten uit de vertaalgeheugens, zowel uit het interne vertaalgeheugen dat werd gemaakt terwijl u uw project vertaalde als uit aanvullende vertaalgeheugens die u importeerde uit eerder werk of die u heeft gekregen van uw cliënt of vertaalbureau.
+
+ Als u doorgaat naar het volgende segment wordt de eerste overeenkomst (die met het hoogste percentage van overeenkomst) automatisch geselecteerd. U kunt een andere overeenkomst selecteren door te drukken op Ctrl+2, 3, 4 of 5.
+ SneltoetsenCtrl+N - Selecteren van de overeenkomst
+ Uiteraard zal het drukken op Ctrl5 geen effect hebben als er geen overeenkomst #5 is. Gebruik Ctrl+R
+ SneltoetsenCtrl+R - Tekst vervangen
+ om het doelveld te vervangen door die overeenkomst of Ctrl+I
+ SneltoetsenCtrl+I - Tekst invoegen
+ om die in te voegen op de cursorpositie, om de geselecteerde overeenkomst in uw vertaling te gebruiken.
+
+ Het percentage voor de overeenkomst is ruwweg het equivalent van het aantal meest voorkomende woorden in het vergeleken en het overeenkomende segment, gedeeld door het aantal woorden in de langste van de twee. De geselecteerde overeenkomst zal worden geaccentueerd in vet, woorden die ontbreken in het segment dat u vertaald zullen blauw gekleurd zijn en woorden die aansluiten aan ontbrekende gedeelten zullen groen zijn. In het bovenstaande voorbeeld is het bronsegment Context menu command. De bovenste overeenkomst is 100%, omdat alle woorden overeenkomen. Hetzelfde geldt voor de twee volgende overeenkomsten en de overeenkomst #4 is soortgelijk, maar verschilt. De regel met het percentage van overeenkomst bevat ook de naam van het vertaalgeheugen
+ Vertaalgeheugensovereenkomsten
+ dat de overeenkomst bevat. Indien er geen naam vermeld is, is de bron het interne vertaalgeheugen van het project. Wezen-segmenten
+ Vertaalgeheugenswezen-segmenten
+ (de overeenkomst #2) beschrijven segmenten in het standaard vertaalgeheugen van het project die geen overeenkomend bronsegment hebben.
+
+ Er zijn feitelijk drie berekende overeenkomsten beschikbaar (66/66/30 in het geval van overeenkomst #4 hierboven). Zij worden als volgt gedefinieerd:
+
+
+
+ percentage van overeenkomst als de plugin tokenizer wordt gebruikt
+
+
+
+
+
+ standaard overeenkomst OmegaT - aantal overeenkomende woorden - getallen en tags worden genegeerd - gedeeld door het totale aantal woorden
+
+
+
+
+
+ overeenkomst OmegaT, inclusief getallen en tags
+
+
+
+
+
+ venster Woordenlijst<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Woordenlijst</secondary>
+ </indexterm>
+
+ Het venster Woordenlijst maakt het u mogelijk om uw eigen collectie uitdrukkingen en speciale terminologie, die u heeft verzameld in uw bestanden voor de woordenlijst, te gebruiken. Het geeft de vertalingen weer van termen die zijn gevonden in het huidige segment. Het bronsegment in het voorbeeld hieronder was “Context menu command”, zoals het voorbeeld voor Overeenkomsten hierboven, en de weergegeven termen werden gevonden in de beschikbare woordenlijsten (Microsoft's Term collection en de woordenlijst voor de Sloveense Linux gebruikersgroep.
+
+
+ <indexterm class="singular">
+ <primary>Woordenlijsten</primary> <secondary>item met meerdere woorden in de woordenlijst - afbeelding</secondary>
+ </indexterm>item met meerdere woorden in de woordenlijst
+
+
+
+
+
+
+
+
+
+
+
+
+ Als u de optie TransTips hebt geactiveerd Opties → Transtips), kunt u met rechts klikken op het geaccentueerde woord om een keuzelijst te openen met de voorgestelde vertalingen, zoals die worden aangeboden door uw woordenlijst. Selecteren van een er van zal het invoegen op de huidige positie in het doelsegment. U kunt ook uw geprefereerde alternatief accentueren in het venster Woordenlijst en het invoegen in het doel door met rechts op de selectie te klikken.
+
+
+
+ venster Woordenboek<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Woordenboek</secondary>
+ </indexterm>
+
+ Woordenboeken zijn de elektronische versies van gedrukte woordenboeken zoals MerriamWebster, Duden, Larousse etc., die u op uw bureau zou hebben kunnen staan. Bekijk er meer over in het hoofdstuk over Woordenboeken
+
+
+
+ venster Meerdere vertalingen<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Meerdere vertalingen</secondary>
+ </indexterm>
+
+ Een bepaald bronsegment kan verschillende vertalingen vereisen, afhankelijk van de context. Als de huidige vertaling van het segment niet past, kan de gebruiker Bewerken → Alternatieve vertaling maken selecteren. De doeltekst die daarna wordt ingevoerd zal wordne behandeld als een alternatieve vertaling van het bronsegment. U kunt één van de alternatieven - bijvoorbeeld die welke het meest waarschijnlijk is - als de standaard vertaling instellen door te selecteren Bewerken → Als standaard vertaling gebruiken
+
+
+
+ venster Notities
+
+ De vertaler kan notities toevoegen aan het geopende segment, bijvoorbeeld om later terug te kunnen keren naar het segment en de vertaling opnieuw te doen, te controleren dat alternatieve vertalingen juist zijn of om collega's om hun mening te vragen. U kunt door de notities bladeren met behulp van Ga naar → Volgende notitie en Ga naar → Vorige notitie.
+
+
+
+ venster Opmerkingen
+
+ Sommige bestandsindelingen, gespecialiseerd voor vertaalwerk, bijvoorbeeld PO, maken het opnemen van opmerkingen mogelijk. Op deze manier kan de vertaler de context voor het segment dat moet worden vertaald worden verschaft. In het voorbeeld hieronder heeft de auteur van het PO-bestand een waarschuwing voor de vertaler opgenomen om de lengte van de vertaling te controleren:
+
+
+
+
+
+
+
+
+
+
+
+
+
+ venster Machinevertaling<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Machinevertaling</secondary>
+ </indexterm>
+
+ Het venster Machinevertaling, indien geopend, bevat de suggesties van programma's voor machinevertaling voor het huidige segment. Druk op Ctrl+M om de vertaling van het huidige segment te vervangen door de voorgestelde vertaling. Meer in het hoofdstuk Machinevertaling
+
+
+
+ Hoofdmenu
+
+ Het hoofdmenu geeft toegang tot alle functies van OmegaT. Zie de appendix Hoofdmenu voor een volledige beschrijving van alle menu's en menu-items. De meestgebruikte functies zijn te benaderen met sneltoetsen voor het toetsenbord, dus als u daar eenmaal aan gewend bent, zal er geen reden meer zijn om door de menu's te bladeren tijdens het vertalen. Bekijk hoofdstuk Sneltoetsen voor menu en het toetsenbord voor details.
+
+
+
+ Statusbalk
+
+ De statusbalk geeft berichten met betrekking tot de werkzaamheden weer aan de onderzijde van het hoofdvenster. Deze balk geeft de gebruiker berichten met terugkoppeling over specifieke bewerkingen die worden uitgevoerd. Het geeft ook het aantal overeenkomsten en overeenkomsten in de woordenlijst aan voor het huidige segment.
+
+
+
+
+ Andere vensters
+
+
+ Projectbestanden<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>Projectbestanden</secondary>
+ </indexterm>
+
+ Het venster Projectbestanden somt de projectbestanden op en geeft andere informatie over het project weer. Het wordt automatisch weergegeven als OmegaT een project laadt. Gebruik Ctrl+L
+ SneltoetsenCtrl+L - lijst projectbestanden
+ om het te openen en Esc om het te sluiten. Het venster Projectbestanden geeft de volgende informatie weer:
+
+
+
+ de lijst met alle vertaalbare bestanden in het project. Dit zijn de bestanden die aanwezig zijn in de map met bronbestanden in een formaat dat OmegaT kan afhandelen. Klikken op een bestand zal het openen voor vertaling
+
+
+
+
+
+ het bestand dat momenteel beschikbaar is in het venster Bewerken is geaccentueerd met een blauwe achtergrond. Drukken op Enter zal het venster Bewerken verplaatsen naar het begin van het geselecteerde bestand
+
+
+
+
+
+ het aantal segmenten in elk bestand wordt naast de naam van het bestand weergegeven
+
+
+
+
+
+ het totale aantal segmenten, het aantal unieke segmenten in het gehele project en het aantal reeds vertaalde unieke segmenten worden weergegeven aan de onderzijde
+
+
+
+ De verzameling Unieke segmenten wordt berekend door alle segmenten te nemen en daaruit de duplicaten te verwijderen. (De definitie van “uniek” is gevoelig voor hoofdletters: "Run" en "run" worden als verschillend behandeld)
+
+ Het verschil tussen "Aantal segmenten" en "Aantal unieke segmenten" geeft een ruwe benadering van het aantal herhalingen in een tekst. Merk echter op dat de aantallen niet vertellen hoe relevant de herhalingen zijn: zij zouden kunnen betekenen dat relatief lange zinnen een aantal keren worden herhaald (in welk geval u gul hebt) of het zou een tabel met sleutelwoorden kunnen beschrijven (niet zo gelukkig). Het bestand project_stats.txt dat is geplaatst in de map omegat van uw project bevat meer gedetailleerde informatie over elk segment per bestand.
+
+ Aanpassen van de segmentatieregels kan effect hebben op het aanpassen van het aantal segmenten/unieke segmenten. Zoiets zou echter in het algemeen moeten worden vermeden nadat u eenmaal met de vertaling van het project bent begonnen. Zie het hoofdstuk Segmentatieregels voor meer informatie.
+
+
+ Bronbestandenbestanden toevoegen aan het project
+ bestanden toevoegen aan het project: U kunt bronbestanden toevoegen aan het project door te klikken op de knop "Bronbestanden importeren...". Dit kopieert de geselecteerde bestanden naar de map /source en herlaadt het project om de nieuwe bestanden te importeren. U kunt ook bronbestanden toevoegen vanaf internetpagina's, geschreven in MediaWiki, door te klikken op de knop "Importeren vanuit MediaWiki" en de corresponderende URL op te geven.
+
+
+
+ venster Zoeken<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Zoeken</secondary>
+ </indexterm>
+
+ U kunt het venster Zoeken gebruiken om specifieke segmenten in het project te vinden. U kunt meerdere vensters tegelijkertijd geopend hebben. Gebruik CtrlF in het hoofdvenster om een nieuw venster te openen. Het venster Zoeken bestaat uit een tekstvak voor tekenreeksen of sleutelwoorden om te zoeken, vlaggen en keuzeknoppen voor het instellen van het zoek- en weergavegebied dat de resultaten van de zoekactie bevat. Zie het hoofdstuk Zoeken voor meer informatie over het zoekvenster.
+
+
+
+ Tags valideren<indexterm class="singular">
+ <primary>Tags valideren</primary> <seealso>sneltoetsen, tags</seealso>
+ </indexterm><indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>tags valideren</secondary> <seealso>tags</seealso>
+ </indexterm>
+
+ Het venster Tags valideren detecteert de tagfouten en niet-consistente vertalingen in de vertaling en somt ze op. Open het venster met Ctrl+T. Het venster heeft een kolom met 3 tabellen met een koppeling naar het segment en de inhoud van diens bron en doel:
+
+
+ <indexterm class="singular">
+ <primary>Tags valideren</primary> <secondary>venster - afbeelding</secondary> <seealso>tags</seealso>
+ </indexterm>venster Tags valideren
+
+
+
+
+
+
+
+
+
+
+
+
+ De tags worden vet blauw geaccentueerd voor eenvoudige vergelijking tussen de originele en de vertaalde inhoud. Klik op de koppeling om naar het segment in het venster Bewerken te springen. Verbeter, indien nodig, de fout en druk op Ctrl+T om terug te keren naar het venster Tags valideren om andere fouten te corrigeren. In het eerste en derde geval hierboven waren tags niet correct gepaard en in het tweede geval ontbreekt bij de openingstag het <-teken.
+
+ Tagfouten zijn gevallen waarin de tags in de vertaling niet overeenkomen in volgorde en aantal in vergelijking met het originele segment. Sommige scenario's met betrekking tot tags die worden gevlagd in het venster Tag valideren zijn noodzakelijk en zijn goedaardig, terwijl andere problemen zullen veroorzaken als het vertaalde document wordt gemaakt. Tags vertegenwoordigen meestal enige vorm van opmaak in de originele tekst. Vereenvoudigen van de opmaak van de originele tekst in het bronbestand voordat de vertaling wordt begonnen draagt enorm bij aan het verminderen van het aantal tags.
+
+
+
+ Statistieken<indexterm class="singular">
+ <primary>Statistieken</primary> <seealso>menu Extra</seealso>
+ </indexterm>
+
+ Het venster Statistieken - te benaderen via Extra > Statistieken - geeft de statistieken voor het huidige project van OmegaT weer, zowel in de vorm van een overzicht als in detail voor elk bestand dat moet worden vertaald. De weergegeven statistieken zijn beschikbaar als een tab-gescheiden bestand project_stats.txt (submap omegat), klaar om te worden geladen in een programma met rekenbladen dat de gebruiker wil gebruiken. U kunt Ctrl+A
+ SneltoetsenCtrl+A - alles selecteren
+ , Ctrl+C
+ SneltoetsenCtrl+C - tekst kopiëren
+ , Ctrl+V
+ SneltoetsenCtrl+V - tekst plakken
+ gebruiken om de inhoud te kopiëren en te plakken.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Statistieken voor overeenkomsten<indexterm class="singular">
+ <primary>Statistieken voor overeenkomsten</primary> <seealso>menu Extra</seealso>
+ </indexterm>
+
+ Toegang tot de statistieken voor overeenkomsten gaat viaExtra > Statistieken voor overeenkomsten. De evaluatie vergt nogal wat gebruik van de CPU en kan nogal wat tijd vergen, dus wordt er een voortgangsbalk weergegevn gedurende de berekening. Voorzover het categorieën betreft, de de facto industriestandaard voor het classificeren van overeenkomsten in de volgende groepen wordt gebruikt: Exacte overeenkomst, 95%-100%, 85%-94%, 75%-84%, 50%-74% en Geen overeenkomst. De tellingen van woorden, identiek aan tellingen in het venster Projectbestanden, are strikt gebaseerd op de methode van tellen van OmegaT, met een aantal verschillen in terminologie om rekening te houden met conceptuele verschillen. Deze informatie wordt berekend voor zowel segmenten als voor woorden en voor tekens (zonder en met spaties).
+
+ Onthoud dat deze totalen een goede (of zo-goed-als-maar-kan-zijn) benadering zijn van het betrokken werk in het project en dus kan dienen als een basis voor uw berekeningen van kosten en prijzen.
+
+
+ statistieken voor overeenkomsten
+
+
+
+
+
+
+
+
+
+
+
+
+ Met spaties tussen segmenten wordt geen rekening gehouden in de laatste kolom. Herhalingen staan voor identieke segmenten die meerdere malen aanwezig zijn in de tekst. Het eerste segment en de inhoud daarvan zullen worden geclassificeerd als "geen overeenkomst", en de rest van hen als een herhaling van de eerste. Als de vertaling voor verschillende identieke bronsegmenten al bestaat in het vertaalgeheugen van het project, zullen deze segmenten, samen met andere, reeds vertaalde unieke segmenten, worden geclassificeerd als een "Exacte overeenkomst". Het aantal unieke segmenten die, indien nodig, worden verschaft in het standaard venster met statistieken, ongeacht of zij zijn vertaald of niet.
+
+ De rest van de categorieën (50-100%) behelst niet-vertaalde segmenten met een fuzzy overeenkomst. Fuzzy overeenkomsten kunnen ook vanuit de map /tm komen - en niet alleen vanuit het interne vertaalgeheugen in /omegaT, zoals het geval is voor herhalingen en exacte overeenkomsten. Het enige verschil met overeenkomsten vanuit het vertaalgeheugen project_save is dat externe TM's geen exacte overeenkomsten kunnen geven, alleen 100%. Indien men geen externe TM's wil gebruiken voor het tellen, moet men de map /tm leeg maken of de instelling van het project wijzigen (tijdelijk) zodat de waarde voor /tm naar een andere locatie verwijst.
+
+ De overeenkomsten voor statistieken zijn tab-gescheiden en u kunt Ctrl+A
+ SneltoetsenCtrl+A - alles selecteren
+ , Ctrl+C
+ SneltoetsenCtrl+C - tekst kopiëren
+ , Ctrl+V
+ SneltoetsenCtrl+V - tekst plakken
+ gebruiken om ze te kopiëren/plakken, bijvoorbeeld in een werkblad of in uw toepassing voor kostenberekening. Eenmaal berekend zijn de gegevens ook beschikbaar in omegat/project_stats_match.txt. Onthoud dat het bestand voorzien is van een tijdstempel, omdat de berekening (in tegenstelling tot de standaard statistieken) is niet onmiddellijk wordt uitgevoerd en dus snel niet meer van toepassing is.
+
+
+
+ Help-browser<indexterm class="singular">
+ <primary>menu Help</primary> <secondary>Help-browser</secondary>
+ </indexterm>
+
+ De Help-browser (die deze handleiding weergeeft) kan worden opgeroepen door op
+ SneltoetsenF1 - Help
+ F1 te drukken of door te navigeren naar
+ menu HelpGebruikershandleiding...
+ Help → Gebruikershandleiding... in het hoofdmenu. In het venster worden de handleiding en twee knoppen weergegeven: Terug en Inhoud. De gebruikershandleiding is een HTML-document met koppelingen naar de verschillende hoofdstukken. Klikken op een koppeling, zoals u in een webbrowser zou doen, brengt de gewenste pagina op de voorgrond.
+
+ De gebruikershandleiding is geplaatst in de submap docs onder de installatiemap van OmegaT, dus u kunt bijvoorbeeld de Engelse documentatie bekijken door het bestand docs/en/index.html in uw browser te openen. Openen van de gebruikershandleiding op deze manier stelt u ook in staat om externe koppelingen te volgen, omdat de ingebouwde help-browser geen externe koppelingen naar internet accepteert.
+
+
+
+
+
+ Sneltoetsen voor menu en het toetsenbord
+
+
+ <indexterm class="singular">
+ <primary>Hoofdmenu</primary>
+ </indexterm>Hoofdmenu
+
+
+ SneltoetsenHoofdmenu
+
+
+ Alle functionaliteiten van OmegaT zijn beschikbaar via de menubalk boven het venster Bewerken. De meeste functies zijn ook beschikbaar via sneltoetsen voor het toetsenbord. Sneltoetsen worden geactiveerd door te drukken op Ctrl en een letter. Sommige sneltoetsen gebruiken ook andere toetsen. Voor de leesbaarheid worden letters hier geschreven als hoofdletters. Ctrl wordt gebruikt op Windows, UNIX en UNIX-achtige besturingssystemen die een toetsenbord hebben met de Ctrl- of Control-toets. Mac-gebruikers moeten in plaats daarvan de cmd-toets gebruiken. De "Cmd"-toets heeft ofwel een label "command" of een Apple-merkteken op toetsenborden van Apple.
+
+ U kunt bestaande sneltoetsen aanpassen of nieuwe, naar uw behoeften, toevoegen. Zie Appendix - Sneltoetsen aanpassen
+
+
+ Hoofdmenu
+
+
+
+
+ Project
+
+ Bewerken
+
+ Ga naar
+
+ Weergave
+
+ Extra
+
+ Opties
+
+ Help
+
+
+
+
+ menu Project
+
+
+
+
+
+
+
+
+ Nieuw
+
+
+
+ Maakt en opent een nieuw project. Het dialoogvenster om een project te maken is hetzelfde als voor het bewerken van het project. Zie
+
+
+
+ Openen
+
+
+ Ctrl
+
+ O
+
+
+ Opent een eerder gemaakt project.
+
+
+
+ Bronbestanden importeren...
+
+
+
+ Kopieert de geselecteerde bestanden naar de map /source en herlaadt het project om de nieuwe bestanden te laden.
+
+
+
+ Importeren vanuit MediaWiki...
+
+
+
+ Importeert eenheden vanaf pagina's van MediaWiki, gebaseerd op de ingevoerde URL.
+
+
+
+ Herladen
+
+ F5
+
+ Herlaadt het project om externe wijzigingen in bronbestanden, gebruikte vertaalgeheugens, woordenlijsten en instellingen voor het project te verwerken.
+
+
+
+ Sluiten
+
+
+ Ctrl
+
+ Shift
+
+ W
+
+
+ Slaat de vertaling op en sluit het project.
+
+
+
+ Opslaan
+
+
+ Ctrl
+
+ S
+
+
+ Slaat het interne vertaalgeheugen op de harde schijf op. OmegaT slaat automatisch elke 10 minuten de vertaalgeheugens op en ook als u het project sluit of OmegaT afsluit.
+
+
+
+ Vertaalde documenten maken
+
+
+ Ctrl
+
+ D
+
+
+ Maakt de doeldocumenten op basis van uw vertaling van de tekst in de documenten. De gemaakte doeldocumenten zijn geplaatst in de map /target.
+
+
+
+ Eigenschappen...
+
+
+ Ctrl
+
+ E
+
+
+ Geeft het dialoogvenster Projecteigenschappen weer om de projecttalen en maplocaties te kunnen bewerken.
+
+
+
+ Projectbestanden...
+
+
+ Ctrl
+
+ L
+
+
+ Sluit of opent het venster Projectbestanden (afhankelijk van het feit of het geopend of gesloten is).
+
+
+
+ Afsluiten
+
+
+ Ctrl
+
+ Q
+
+
+ Slaat het project op en sluit OmegaT af. Als u het project nog niet hebt opgeslagen wordt hier handmatig bevestiging gevraagd of u werkelijk af wilt sluiten.
+
+
+
+
+
+
+
+ Bewerken<indexterm class="singular">
+ <primary>Hoofdmenu</primary> <secondary>Bewerken</secondary>
+ </indexterm>
+
+ Opmerking: Items die in de meeste toepassingen aanwezig zijn (kopiëren/knippen/plakken) worden in dit menu niet weergegeven maar zijn beschikbaar met de sneltoetsen van uw systeem. Bijvoorbeeld:
+
+
+ Sneltoetsen kopiëren/knippen/plakken
+
+
+
+
+
+
+
+
+ Kopiëren
+
+
+ Ctrl
+
+ C
+
+
+ Kopieert de geselecteerde tekst naar het klembord.
+
+
+
+ Knippen
+
+
+ Ctrl
+
+ X
+
+
+ Kopieert de geselecteerde tekst naar het klembord en verwijdert de geselecteerde tekst.
+
+
+
+ Plakken
+
+
+ Ctrl
+
+ V
+
+
+ Plakt de tekst van het klembord op de cursorpositie.
+
+
+
+
+
+ Het menu Bewerken zelf bevat de volgende sneltoetsen:
+
+
+ menu Bewerken
+
+
+
+
+
+
+
+
+ Laatste actie ongedaan maken
+
+
+ Ctrl
+
+ Z
+
+
+ Herstelt de status naar vóórdat de laatste actie werd uitgevoerd. Deze opdracht werkt niet als het gewijzigde segment al is gevalideerd.
+
+
+
+ Laatste actie opnieuw
+
+
+ Ctrl
+
+ Y
+
+
+ Herstelt de status naar vóórdat de laatste actie werd geannuleerd. Deze opdracht werkt niet als het gewijzigde segment al is gevalideerd.
+
+
+
+ Vervangen door overeenkomst
+
+
+ Ctrl
+
+ R
+
+
+ Vervangt het gehele doelsegment door de huidige geselecteerde overeenkomst (de eerste overeenkomst is standaard geselecteerd)
+
+
+
+ Overeenkomst invoegen
+
+
+ Ctrl
+
+ I
+
+
+ Voegt de huidige geselecteerde overeenkomst in op de cursorpositie. Indien een gedeelte van het doelsegment is geselecteerd, overschrijft deze functie het geselecteerde gedeelte.
+
+
+
+ Vervangen door machinevertaling
+
+
+ Ctrl
+
+ M
+
+
+ Vervangt het doelsegment door de vertaling die wordt verschaft door de service van de machinevertaling. Geen actie wordt ondernomen indien er geen service voor machinevertaling is geactiveerd (zie Menu > Opties hieronder).
+
+
+
+ Vervangen door bron
+
+
+ Shift
+
+ Ctrl
+
+ R
+
+
+ Vervangt het huidige doelsegment door de brontekst.
+
+
+
+ Bron invoegen
+
+
+ Shift
+
+ Ctrl
+
+ I
+
+
+ Voegt de brontekst in op de cursorpositie.
+
+
+
+ Brontags invoegen
+
+
+ Shift
+
+ Ctrl
+
+ T
+
+
+
+ TagsBrontags invoegen
+ Voegt de brontags in op de cursorpositie. Alle tags in de brontekst zullen worden ingevoegd in het huidige segment, ongeacht of ze daar al staan of niet. Tekst, omsloten door tags, wordt vervangen door spaties: <f0><f1>Dit is tekst</f0></f1> dus zal worden gekopieerd als <f0><f1>één_spatie</f0></f1>
+
+
+
+ Selectie exporteren
+
+
+ Shift
+
+ Ctrl
+
+ C
+
+
+ Exporteert de huidige selectie naar een tekstbestand voor verwerking. Indien geen tekst is geselecteerd, wordt het huidige bronsegment naar dit bestand geschreven. Wanneer de gebruiker OmegaT afsluit, wordt dit bestand niet geleegd, om consistent te zijn aan het gebruikelijke gedrag van het klembord. De geëxporteerde inhoud wordt gekopieerd naar het bestand selection.txt dat is geplaatst in de voorkeursmap van de gebruiker (zie ).
+
+
+
+ Item voor woordenlijst maken
+
+
+ Shift
+
+ Ctrl
+
+ G
+
+
+ Laat de gebruiker een item maken in het standaard bestand voor de woordenlijst.
+
+
+
+ Zoeken in project...
+
+
+ Ctrl
+
+ F
+
+
+ Opent een nieuw venster Zoeken.
+
+
+
+ Schakel Hoofd-/kleine letters naar...
+
+ ShiftF3 (zie tekst)
+
+ Wijzigt hoofd-/kleine letters van de geaccentueerde tekst in het doelsegment naar de geselecteerde optie (Kleine letters, Hoofdletters of Alle woorden hoofdletters). Gebruik Shift+F3
+ SneltoetsenShift+F3 - Selectie Hoofd-/kleine letters
+ om tussen de drie keuzes te schakelen. Indien geen tekst is geselecteerd, selecteert OmegaT het woord dat de letter bevat direct rechts naast de cursor.
+
+
+
+ Overeenkomst #N selecteren
+
+
+ Ctrl
+
+ #N
+
+
+ (#N is een getal van 1 tot en met 5) - Selecteert de Ne overeenkomst die is weergegeven in het venster Overeenkomsten om het segment te vervangen of het daar in te voegen. De beschrijft de codering van de kleuren in detail.
+
+
+
+ Als standaard vertaling gebruiken
+
+
+
+ Indien er meerdere alternatieve vertalingen beschikbaar zijn voor het actieve segment, kunt u het geselecteerde alternatief als de standaard vertaling instellen. Het item zal grijs worden als er slechts één vertaling beschikbaar is.
+
+
+
+ Alternatieve vertaling maken
+
+
+
+ Het ene en hetzelfde segment kan, afhankelijk van de context, verschillende vertalingen vereisen. Selecteer dit menuitem als de huidige vertaling niet van toepassing is en voer de alternatieve vertaling in.
+
+
+
+
+ menu Ga naar
+
+
+
+
+
+
+
+
+ Volgende niet-vertaalde segment
+
+
+ Ctrl
+
+ U
+
+
+ Verplaatst naar het volgende segment dat geen equivalent heeft in het vertaalgeheugen.
+
+
+
+ Volgende segment
+
+ CtrlN of Enter of Tab
+
+ Verplaatst naar het volgende segment. Als het huidige segment het laatste in een bestand is, verplaatst het naar het eerste segment van het volgende bestand.
+
+
+
+ Vorige segment
+
+ CtrlP of CtrlEnter of CtrlTab
+
+ Verplaatst naar het vorige segment. Als het huidige segment het eerste in een bestand is, verplaatst het naar het laatste segment van het vorige bestand.
+
+
+
+ Segmentnummer...
+
+
+ Ctrl
+
+ J
+
+
+ Het segment wordt geopend als zijn segmentnummer wordt ingevoerd.
+
+
+
+ Volgende notitie
+
+
+
+ Het volgende segment waar een notitie aan is verbonden, zal openen.
+
+
+
+ Vorige notitie
+
+
+
+ Het vorige segment met een notitie zal openen.
+
+
+
+ Verder in geschiedenis...
+
+
+ Ctrl
+
+ Shift
+
+ N
+
+
+ OmegaT onthoudt de verwerkte segmenten. Met deze opdracht kunt u vooruit naar het segment dat u eerder verliet met de opdracht Terug in geschiedenis...
+
+
+
+ Terug in geschiedenis...
+
+
+ Ctrl
+
+ Shift
+
+ P
+
+
+ Met deze opdracht kunt u één segment terug in de tijd gaan, om later terug te keren naar het huidige segment met behulp van de opdracht Verder in geschiedenis... hieronder.
+
+
+
+
+ menu Weergave
+
+
+
+
+
+
+ Vertaalde segmenten markeren
+
+ Indien aangevinkt, zullen de vertaalde segmenten in geel worden geaccentueerd.
+
+
+
+ Niet-vertaalde segmenten markeren
+
+ Indien aangevinkt, zullen de niet-vertaalde segmenten in paars worden geaccentueerd.
+
+
+
+ Bronsegmenten weergeven
+
+ Indien aangevinkt, zullen de bronsegmenten in groen worden geaccentueerd. Indien niet aangevinkt, zullen de bronsegmenten niet worden weergegeven.
+
+
+
+ Niet-unieke segmenten markeren
+
+ Indien aangevinkt zullen niet-unieke segmenten bleekgrijs worden gemarkeerd.
+
+
+
+ Segmenten met opmerkingen markeren
+
+ In aangevinkt zullen segmenten met opmerkingen cyaankleurig worden gemarkeerd.
+
+
+
+ Niet-afbreekbare spaties markeren
+
+ Indien aangevinkt worden niet-afbreekbare spaties in het segment met een grijze achtergrond weergegeven.
+
+
+
+ Info over wijzigingen
+
+ Instellen van de optie Info over wijzigingen op Weergave voor huidige segment zal datum en tijd en de auteur weergeven van de laatste wijziging aan het huidige segment. Het instellen op Weergave voor alle segmenten geeft deze informatie weer voor alle segmenten en Niets weergeven schakelt deze optie uit.
+
+
+
+
+ menu Extra
+
+
+ OvereenkomstenStatistieken voor overeenkomsten
+
+
+
+ ProjectStatistieken voor overeenkomsten
+
+
+
+ ProjectStatistieken
+
+
+
+
+
+
+
+ Tags valideren
+
+ Ctrl+T: Controleert op ontbrekende of misplaatste tags in opgemaakte bestanden. Zal een lijst weergeven waarin de segmenten met tagfouten en mogelijke onvolkomenheden staan. Zie Tagvalidatie en .
+
+
+
+ Tags verwijderen
+
+ Indien ingeschakeld worden alle tags voor opmaak verwijderd uit de bronsegmenten. Dit is handig als teksten worden afgehandeld waarin in-regelige opmaak geen echt nut heeft (bijv. ge-OCRde PDF, slecht geconverteerde .odt of .docx, etc.) Alleen in-regelige tags worden verwijderd, dus normaal gesproken zou er geen probleem moeten zijn met het openen van de doeldocumenten. Niet-zichtbare opmaak (d.i. die niet als tags verschijnen in de bewerker van OmegaT) wordt in het doeldocument behouden.
+
+
+
+ Statistieken
+
+ Opent een nieuw venster en geeft de statistieken voor het project weer, d.i. de totalen voor het project en de totalen voor elk bestand in het project.
+
+
+
+ Statistieken voor overeenkomsten
+
+ Geeft de Statistieken voor overeenkomsten weer voor het project: het aantal herhalingen, exacte overeenkomsten, overeenkomsten en geen overeenkomsten, voor segmenten, woorden en in tekens.
+
+
+
+
+ menu Opties
+
+
+
+
+
+
+ Tab gebruiken om door te gaan
+
+ Stelt de toets voor het valideren van het segment in op Tab in plaats van de standaardtoets Enter. Deze optie is handig voor sommige invoersystemen voor Chinese, Japanse of Koreaanse tekens.
+
+
+
+ Afsluiten altijd bevestigen
+
+ Het programma zal u altijd om bevestiging vragen om af te sluiten.
+
+
+
+ Machinevertaling
+
+ Stelt u in staat om de aangeboden programma's voor machinevertaling te activeren/deactiveren. Indien actief, zal CtrlM de suggestie in het doelgedeelte van het huidige segment invoegen.
+
+
+
+ Woordenlijst
+
+
+
+
+
+ TransTips
+
+ Stelt u in staat de mogelijkheid TransTips te activeren/deactiveren en stelt de optie er van in op Exacte overeenkomst. Met de geactiveerde TransTips zal een klik met rechts op een geaccentueerd woord in de brion een pop-upmenu openen met de items van de woordenlijst voor het woord waarop u hebt geklikt. U kunt dan op de geprefereerde vertaling klikken om die in te voegen in het doelsegment op de huidige positie. Met TransTips/Exacte overeenkomst ingeschakeld, zullen alleen volledige woorden worden gecontroleerd, anders zullen ook gedeelten van woorden overeenkomen.
+
+
+
+ Lettertype...
+
+ Toont het dialoogvenster om het lettertype voor de weergave van de tekst aan te passen. Gebruikers van oudere computers die het aanpassen van de venstergrootte heel traag vinden kunnen proberen om het lettertype te wijzigen. Zie .
+
+
+
+ Bestandsfilters...
+
+ Geeft het dialoogvenster Bestandsfilters weer om de bestandsafhandeling en het parsen te configureren.
+
+
+
+ Segmentatie...
+
+ Opent het venster Segmentatie-instellingen om de segmentatie van de tekst te configureren.
+
+
+
+ Spellingscontrole...
+
+ Geeft het venster Spellingscontrole instellen weer om de spellingscontrole te installeren, te configureren en te activeren.
+
+
+
+ Bewerken (gedrag)...
+
+ Geeft het dialoogvenster Vertaling bewerken weer om te configureren.
+
+
+
+ Tags valideren...
+
+ Voor programmeurs: Stelt u in staat om de opties voor Tags valideren te configureren en ook variabelen in het programma (%...) te controleren.
+
+
+
+ Team...
+
+ Voer hier uw naam in en die zal worden gekoppeld aan alle door u vertaalde segmenten.
+
+
+
+ Externe TMXen...
+
+ Laat de gebruiker beslissen hoe tags in vreemde TMX-bestanden (d.i. niet gegenereerd door OmegaT) moeten worden behandeld.
+
+
+
+ Weergave...
+
+ Bevat de optie om alle bronsegmenten in vet weer te geven en het eerste niet-unieke segment te markeren.
+
+
+
+ Inloggen Proxy...
+
+ Voer u gebruikersnaam en uw wachtwoord in, als u een proxy gebruikt om toegang te krijgen tot uw projecten.
+
+
+
+ Hoofdvenster herstellen
+
+ Herstelt de componenten van het hoofdvenster van OmegaT naar hun standaard status. Gebruik deze mogelijkheid in de gevallen dat u één of meer componenten heeft losgemaakt, verplaatst of verborgen en u ze niet terug kan krijgen op de manier die u wilt. Het kan ook worden gebruikt als vensters er niet uitzien zoals u verwachtte na een upgrade van OmegaT.
+
+
+
+
+ menu Help
+
+
+
+
+
+
+ Gebruikershandleiding...
+
+ F1: Opent de Help-browser met deze handleiding in een afzonderlijk venster.
+
+
+
+ Over...
+
+ Geeft auteursrechten, dankwoorden en licentie-informatie weer.
+
+
+
+
+
+
+
+
+ Toetsenbord sneltoetsen<indexterm class="singular">
+ <primary>Toetsenbord sneltoetsen</primary>
+ </indexterm>
+
+ De volgende sneltoetsen zijn beschikbaar in het hoofdvenster. Als een ander venster op de voorgrond staat, klik dan op het hoofdvenster om het weer op de voorgrond te plaatsen of druk op Esc om dat venster te sluiten.
+
+ Sneltoetsen worden geactiveerd door te drukken op Ctrl en een letter. Sommige sneltoetsen gebruiken ook andere toetsen. Voor de leesbaarheid worden letters hier geschreven als hoofdletters.
+
+ Ctrl wordt gebruikt op Windows, UNIX en UNIX-achtige besturingssystemen die een toetsenbord hebben met de Ctrl / Control-toets. Mac-gebrukers zouden in plaats daarvan de cmd+toets moeten gebruiken. Op toetsenborden van Apple heeft de cmd-toets een label "command" of een Apple-merkteken er op.
+
+
+
+ Projectbeheer
+
+
+
+
+
+ Bewerken
+
+
+
+
+
+ Verplaatsen
+
+
+
+
+
+ Verwijzingsvensters
+
+
+
+
+
+ Andere
+
+
+
+
+ <indexterm class="singular">
+ <primary>Toetsenbord sneltoetsen</primary> <secondary>Project</secondary>
+ </indexterm>Projectbeheer<indexterm class="singular">
+ <primary>Project</primary> <secondary>Sneltoetsen voor projectbeheer</secondary>
+ </indexterm>
+
+
+ Sneltoetsen voor projectbeheer
+
+
+
+
+
+
+
+
+ Project openen
+
+
+ Ctrl
+
+ O
+
+
+ Geeft een dialoogvenster weer om een reeds bestaand project te zoeken.
+
+
+
+ Opslaan
+
+
+ Ctrl
+
+ S
+
+
+ Slaat het huidige werk op in het interne vertaalgeheugen (bestand project_save.tmx dat staat in de map omegat van het project).
+
+
+
+ Project sluiten
+
+
+ Shift
+
+ Ctrl
+
+ W
+
+
+ Sluit het huidige project.
+
+
+
+ Vertaalde documenten maken
+
+
+ Ctrl
+
+ D
+
+
+ Maakt de vertaalde documenten in de map Target van het project en maakt de bestanden voor het vertaalgeheugen (level1, level2 en omegat tmx-bestanden) in de hoofdmap van het project.
+
+
+
+ Projecteigenschappen
+
+
+ Ctrl
+
+ E
+
+
+ Geeft de instellingen voor het project weer om die aan te passen, indien gewenst.
+
+
+
+
+ Sneltoetsen Bewerken
+
+
+
+
+
+
+
+
+ Laatste actie ongedaan maken
+
+
+ Ctrl
+
+ Z
+
+
+ Maakt de laatste actie in het huidige doelsegment ongedaan
+
+
+
+ Laatste actie opnieuw
+
+
+ Ctrl
+
+ Y
+
+
+ Voert opnieuw de laatste bewerking uit die zojuist in het huidige doelsegment ongedaan werd gemaakt
+
+
+
+ Overeenkomst #N selecteren
+
+
+ Ctrl
+
+ #N
+
+
+ #N is een getal van 1 tot en met 5. De sneltoets selecteert de Ne overeenkomst die wordt weergegeven in het venster Overeenkomsten (de eerste overeenkomst wordt standaard geselecteerd)
+
+
+
+ Vervangen door overeenkomst
+
+
+ Ctrl
+
+ R
+
+
+ Vervangt de inhoud van het huidige doelsegment door de geselecteerde overeenkomst (de eerste overeenkomst wordt standaard geselecteerd)
+
+
+
+ Overeenkomst invoegen
+
+
+ Ctrl
+
+ I
+
+
+ Voegt de geselecteerde overeenkomst in op de cursorpositie in het huidige doelsegment (de eerste overeenkomst wordt standaard geselecteerd)
+
+
+
+ Vervangen door bron
+
+
+ Ctrl
+
+ Shift+R
+
+
+ Vervangt de inhoud van het huidige doelsegment door de inhoud van de brontekst
+
+
+
+ Bron invoegen
+
+
+ Ctrl
+
+ Shift+I
+
+
+ Voegt de inhoud van de brontekst in op de cursorpositie in het huidige doelsegment
+
+
+
+ Brontags invoegen
+
+
+ Ctrl
+
+ Shift+T
+
+
+ Voegt de brontags in op de cursorpositie in het huidige doelsegment.
+
+
+
+ Zoeken in project
+
+
+ Ctrl
+
+ F
+
+
+ Geeft een dialoogvenster weer waarmee zoekacties kunnen worden uitgevoerd binnen het project
+
+
+
+ Vervangen door machinevertaling
+
+
+ Ctrl
+
+ M
+
+
+ Vervangt het doelsegment door de machinevertaling van de bron. Geen actie indien machinevertaling is gedeactiveerd (zie Menu > Opties > Machinevertaling).
+
+
+
+ Selectie exporteren
+
+
+ Shift
+
+ Ctrl
+
+ C
+
+
+ Exporteert de huidige selectie naar een tekstbestand voor verwerking.
+
+
+
+ Item voor woordenlijst maken
+
+
+ Shift
+
+ Ctrl
+
+ G
+
+
+ Laat de gebruiker een item maken in het standaard bestand voor de woordenlijst.
+
+
+
+
+ Sneltoetsen Verplaatsen
+
+
+
+
+
+
+
+
+ Volgende niet-vertaalde segment
+
+
+ Ctrl
+
+ U
+
+
+ Verplaatst het bewerkingsveld naar het volgende segment dat nog niet geregistreerd is in het vertaalgeheugen van het project
+
+
+
+ Volgende segment
+
+ CtrlN, Enter of Return
+
+ Verplaatst het bewerkingsveld naar het volgende segment
+
+
+
+ Vorige segment
+
+
+ Ctrl
+
+ P
+
+
+ Verplaatst het bewerkingsveld naar het vorige segment
+
+
+
+ Segmentnummer...
+
+
+ Ctrl
+
+ J
+
+
+ Verplaatst naar het ingevoerde segmentnummer
+
+
+
+ Terug in geschiedenis...
+
+
+ Ctrl
+
+ Shift+P
+
+
+ Verplaats één segment terug in de geschiedenis.
+
+
+
+ Verder in geschiedenis...
+
+
+ Ctrl
+
+ Shift+N
+
+
+ Verplaatst één segment naar voren in de geschiedenis.
+
+
+
+
+ Diverse sneltoetsen
+
+
+
+
+
+
+
+
+ Lijst projectbestanden
+
+
+ Ctrl
+
+ L
+
+
+ Geeft de lijst met projectbestanden weer
+
+
+
+ Tags valideren
+
+
+ Ctrl
+
+ T
+
+
+ Opent het venster Tags valideren.
+
+
+
+ Selectie exporteren
+
+
+ Shift
+
+ Ctrl+C
+
+
+ Exporteert de huidige selectie of de huidige bron, als er geen tekst is geselecteerd. De tekst wordt geëxporteerd naar een bestand met platte tekst.
+
+
+
+ Zoeken in project
+
+
+ Ctrl
+
+ F
+
+
+ Opent een nieuw venster Zoeken.
+
+
+
+ Helpbestanden
+
+ F1
+
+ Geeft de OmegaT helpbestanden weer in een afzonderlijk venster
+
+
+
+
+
+
+
+
+
+ Projecteigenschappen<indexterm class="singular">
+ <primary>Project</primary><secondary>eigenschappen</secondary>
+ </indexterm>
+
+
+
+
+ dialoogvenster Eigenschappen
+
+ Het dialoogvenster CtrlEProjecteigenschappen... wordt gebruikt om de projectmappen en talen te definiëren en aan te passen.
+
+
+ venster Projecteigenschappen
+
+
+
+
+
+
+
+
+
+
+
+
+ Het bevat:
+
+
+
+ Een gebied om de bron- en doeltalen van het project met keuzelijsten in te stellen
+
+
+
+
+
+ Een vlag voor de instellingen van de segmentatie
+
+
+
+
+
+ Een gebied voor het instellen van de projectmappen
+
+
+
+ Alle velden zijn te bewerken. U kunt de talen handmatig instellen of het menu met de keuzelijst gebruiken. Indien u namen voor mappen invoert die nog niet bestaan, zal OmegaT ze voor u maken.
+
+
+
+ Projecteigenschappen aanpassen
+
+ Onthoud dat wijzigen van de instellingen voor het project consequenties kan hebben, in het bijzonder als het project al is opgestart.
+
+
+
+ Wijzigen van bron- en doeltalen:
+ ProjectBron- en doeltalen
+
+
+ Onthoud goed dat het wijzigen van de talen er voor kan zorgen dat het de huidige gebruikte vertaalgeheugens onbruikbaar kan maken omdat hun taal niet meer overeenkomt met de nieuwe talen.
+
+
+
+ Aanpassen van segmentatie:
+ ProjectSegmentatie aanpassen
+
+
+ De instellingen voor segmentatie hebben alleen betrekking op de manier waarop de bronbestanden door OmegaT worden afgehandeld. Zij passen niet de segmentatie van de reeds bestaande vertaalgeheugens aan.
+
+ Wijzigingen aan de instellingen voor segmentatie kunnen er voor zorgen dat sommige reeds vertaalde segmenten opgedeeld of samengevoegd worden. Zij zullen dan effectief terugkeren naar de status "niet vertaald" omdat zij niet overeenkomen met de opgenomen segmenten in het projectgeheugen, zelfs als de originele vertaling daar nog steeds in staat.
+
+ OmegaT kan oude vertaalgeheugens bijwerken die geen gebruik maakten van zin-segmentatie, maar niet andersom. Indien u gedurende de vertaling besluit om te schakelen van zin- naar alinea-vertaling, zal het interne vertaalgeheugen van het project niet worden gewijzigd.
+
+
+
+ Wijzigen van de mappenstructuur:
+ ProjectWijzigen van de mappenstructuur
+
+
+ Voor het geval u van plan bent de projectmappen aan te passen, onthoudt dan dat daarmee niet de bestanden uit oude mappen naar de nieuwe worden verplaatst.
+
+
+
+ Aanpassen van projecteigenschappen tijdens de sessie
+ ProjectAanpassen tijdens de sessie
+
+
+ Het is mogelijk om de projecteigenschappen gedurende een vertaalsessie aan te passen. De veiligste manier is echter om, totdat u wat meer ervaring hebt met OmegaT, alle instellingen als vast te beschouwen als de vertaling eenmaal is begonnen - tenzij u zich natuurlijk realiseert dat er een grote vergissing is gemaakt. Zie het gedeelte Gegevensverlies voorkomen voor manieren om uw werk te beveiligen.
+
+
+
+
+
+
+ Bestandsfilters
+
+ OmegaT omvat zeer aanpasbare filters die u in staat stellen verschillende aspecten in te stellen. Bestandsfilters zijn gedeelten van code die in staat zijn om:
+
+
+
+ Het document in enkele specifieke bestandsformaten te lezen. Bijvoorbeeld platte tekst-bestanden.
+
+
+
+
+
+ De te vertalen inhoud uit het bestand te halen.
+
+
+
+
+
+ Automatische wijzigingen in de vertaalde bestandsnamen van de documenten te maken door de te vertalen inhoud te vervangen door de vertaling.
+
+
+
+ De meeste gebruikers zullen tevreden zijn met de standaard ingestelde opties. Als u dat niet bent opent u het hoofd dialoogvenster door in het hoofdmenu Opties → Bestandsfilters... te selecteren. U kunt ook project-specifieke bestandsfilters inschakelen, die alleen zullen worden gebruikt voor het huidige project, door de optie Bestandsfilters... in Project → Eigenschappen te selecteren.
+
+ Waarschuwing! Als u de segmentatie-opties wijzigt als een project geopend is moet u het project herladen vóórdat de wijzigingen effect hebben.
+
+
+ dialoogvenster Bestandsfilters<indexterm class="singular">
+ <secondary>dialoogvenster</secondary> <primary>Bestandsfilters</primary>
+ </indexterm>
+
+ Dit dialoogvenster toont de beschikbare bestandsfilters. Als u OmegaT niet wilt gebruiken om bestanden van een bepaald type te vertalen, kunt u het betreffende filter uitschakelen door het keuzevak naast de naam niet te selecteren. OmegaT zal dan de betreffende bestanden weglaten bij het laden van projecten en zal ze ongewijzigd kopiëren bij het maken van de doeldocumenten. Als u het filter opnieuw wilt gebruiken, selecteer dan het keuzevak. Klik op Standaardinstellingen om de bestandsfilters terug te zetten naar de standaard instellingen. Selecteer het filter uit de lijst en klik op Bewerken om aan te geven welke bestanden in welke coderingen het filter moet verwerken.
+
+
+
+ Filteropties<indexterm class="singular">
+ <primary>Bestandsfilters</primary> <secondary>Opties</secondary>
+ </indexterm>
+
+ Vijf filters (Tekstbestanden, XHTML-bestanden, HTML- en XHTML-bestanden, OpenDocument/OpenOffice.org-bestanden en Microsoft Open XML-bestanden) hebben één of meer specifieke opties. Selecteer, om de opties aan te passen, het filter uit de lijst en klik op Opties. De beschikbare opties zijn:
+
+ Tekstbestanden
+
+
+
+ Alineasegmentatie op regeleinden, lege regels of nooit:
+
+ als regels voor zinsegmentatie actief zijn, zal de tekst verder worden gesegmenteerd overeenkomstig de hier geselecteerde optie.
+
+
+
+ PO-bestanden
+
+
+
+ Blanco vertalingen in het doelbestand toestaan:
+
+ Indien ingeschakeld zal, wanneer een PO-segment (wat een gehele alinea kan zijn) niet is vertaald, de vertaling leeg zijn in het doelbestand. Technisch gesproken zal het segment msgstr in het PO-doelbestand, indien gemaakt, leeg zijn. Het staat standaard aan, omdat dit het standaard gedrag is voor PO-bestanden. Indien de optie is uitgeschakeld, zal de brontekst worden gekopieerd naar het doelsegment.
+
+
+
+ XHTML-bestanden
+
+
+
+ Vertaal de volgende attributen- de geselecteerde attributen zullen als segmenten in het venster Bewerken verschijnen.
+
+
+
+
+
+ Start een nieuwe alinea bij: De <br> HTML-tag zal een alinea voor segmentatiedoeleinden maken.
+
+
+
+
+
+ Tekst die overeenkomt met reguliere uitdrukking overslaan: De tekst die overeenkomt met de reguliere uitdrukking zal worden overgeslagen.
+
+
+
+
+
+ Vertaal het attribuut 'content' van metatags niet: ... : de 'sleutel-waarden'-paren van het attribuut, gescheiden door komma's, zullen niet vertaald worden
+
+
+
+ Microsoft Office Open XML-bestanden
+
+ U kunt selecteren welke elementen vertaald moeten worden. Zij zullen als afzonderlijke segmenten in de vertaling verschijnen.
+
+
+
+ Word: Niet-zichtbare tekst met instructies, Notities, Voetnoten, Eindnoten, Voetteksten
+
+
+
+
+
+ Excel: Notities, Werkbladnamen
+
+
+
+
+
+ Powerpoint: Dianotities, Diamodellen, Dia-lay-outs
+
+
+
+
+
+ Globaal: Grafieken, Diagrammen, Tekeningen, WordArt
+
+
+
+
+
+ Andere opties:
+
+
+
+ Hoeveelheid tags: Indien geselecteerd zullen tags, zonder vertaalbare tekst er tussen, worden samengevoegd tot enkele tags.
+
+
+
+ Spaties voor alle tags behouden: Indien geselecteerd zal "witruimte" (d.i. spaties en nieuwe regels) worden behouden, zelfs als dat niet technisch is ingesteld in het document.
+
+
+
+
+
+ HTML- en XHTML-bestanden
+
+
+
+ Codering-declaratie aan HTML- en XHTML-bestanden toevoegen of herschrijven: Altijd (standaard), Alleen als (X)HTML-bestand een kop heeft, Alleen als (X)HTML-bestand een codering-declaratie heeft, Nooit
+
+
+
+
+
+ Vertaal de volgende attributen: De geselecteerde attributen zullen als segmenten in het venster Bewerken verschijnen.
+
+
+
+
+
+ Start een nieuwe alinea bij: De <br> HTML-tag zal een alinea voor segmentatiedoeleinden maken.
+
+
+
+
+
+ Tekst die overeenkomt met reguliere uitdrukking overslaan: De tekst die overeenkomt met de reguliere uitdrukking zal worden overgeslagen.
+
+
+
+
+
+ Vertaal het attribuut 'content' van metatags niet ...: de 'sleutel-waarden'-paren van het attribuut, gescheiden door komma's, zullen niet vertaald worden
+
+
+
+ Tekstbestanden
+
+
+
+ Alineasegmentatie op regeleinden, lege regels of nooit:
+
+ als regels voor zinsegmentatie actief zijn, zal de tekst verder worden gesegmenteerd overeenkomstig de hier geselecteerde optie.
+
+
+
+ OpenDocument/OpenOffice.org bestanden
+
+
+
+ U kunt selecteren welke van de volgende elementen vertaald moeten worden.
+
+ Indexitems, bladwijzers, verwijzingen naar bladwijzers, notities, opmerkingen, notities in presentaties, koppelingen (URL), werkbladnamen
+
+
+
+
+
+ dialoogvenster Filter bewerken<indexterm class="singular">
+ <primary>Bestandsfilters</primary> <secondary>Bewerken</secondary>
+ </indexterm>
+
+ Het dialoogvenster stelt u in staat om de patronen van de bronbestandsnaam te bewerken van de bestanden die het filter zal verwerken, de bestandsnamen van vertaalde bestanden aan te passen en te selecteren welke coderingen het zal gebruiken bij het laden van het bestand en zijn vertaalde tegenhanger. Pas de velden direct aan of klik op Bewerken om een patroon voor het bestandsfilter aan te passen. Klik op Toevoegen om een nieuw patroon voor een bestandsfilter toe te voegen. Hetzelfde dialoogvenster wordt gebruikt om een patroon toe te voegen of een bepaald patroon te bewerken. Het dialoogvenster is handig omdat het een speciale bewerker voor het patroon van de doelbestandsnaam heeft waarmee u de namen van de te maken bestanden aan kunt passen.
+
+
+ <indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>Bestandstype, patroon bestandsnaam</secondary>
+ </indexterm>Type bronbestand, patroon voor bestandsnaam<indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>Bestandstype bron, bestandsnaam</secondary>
+ </indexterm>
+
+ Als OmegaT een bestand tegenkomt in zijn bronmap, probeert dat het filter te selecteren gebaseerd op de extensie van het bestand. Meer precies: OmegaT probeert of van elk filter het patroon van de bestandsnaam overeenkomt met de bestandsnaam. Het *.xhtml-patroon zal bijvoorbeeld overeenkomen met elk bestand met de extensie .xhtml. Als het juiste filter is gevonden wordt dat voor verdere verwerking toegepast op het betreffende bestand. Standaard zal bijvoorbeeld het XHTML-filter worden gebruikt bij het verwerken van bestanden met de extensie .xhtml. U kunt bestandsnaam-patronen toevoegen of wijzigen voor bestanden die door elk filter worden afgehandeld. Patronen voor bronbestandsnamen gebruiken jokertekens die overeenkomen met die in Zoeken. Het teken '*' komt overeen met nul of meer tekens. Het teken '?' komt overeen met exact één teken. Alle andere tekens vertegenwoordigen zichzelf. Als u bijvoorbeeld wilt dat het tekstfilter readme-bestanden (readme, read.me en readme.txt) afhandelt, zou u het patroon read* moeten gebruiken.
+
+
+
+ Coderen van bron- en doelbestanden
+
+
+ Bronbestandencoderen
+
+
+
+ Doelbestandencoderen
+
+
+
+ Bestandsfilterscoderen bron, doel
+
+
+ Slechts een beperkt aantal bestandsformaten specificeren een voorgeschreven codering. Bestandsformaten die hun codering niet specificeren zullen de codering gebruiken die u instelt voor de extensie die overeenkomt met hun naam. Standaard zullen bijvoorbeeld .txt-bestanden worden geladen met behulp van de standaard codering van uw besturingssysteem. U kunt de broncodering voor elk verschillend bronbestandsnaam-patroon wijzigen. Zulke bestanden kunnen ook in elke codering worden weggeschreven. Als standaard heeft het vertaalde bestand dezelfde codering als de codering van het bronbestand. Velden voor bron- en doelcodering gebruiken combinatievakken waarin alle ondersteunde coderingen zijn opgenomen. <auto> laat de keuze van de codering aan OmegaT over. Zo werkt het:
+
+
+
+ OmegaT identificeert de codering van het bronbestand door de declaratie van de codering te gebruiken, indien aanwezig (HTML-bestanden, op XML gebaseerde bestanden).
+
+
+
+
+
+ OmegaT is geïnstrueerd om een voorgeschreven codering te gebruiken voor bepaalde bestandsformaten ( Java-properties etc)
+
+
+
+
+
+ OmegaT gebruikt de standaard codering van het besturingssysteem voor tekstbestanden.
+
+
+
+
+
+ Doelbestandsnaam<indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>bestandsnamen</secondary>
+ </indexterm>
+
+ Soms wilt u misschien de bestanden die u vertaalde automatisch hernoemen, bijvoorbeeld door een taalcode achter de bestandsnaam te zetten. Doelbestandsnaam-patronen gebruiken een speciale syntaxis, dus als u dit veld zou willen bewerken, moet u op Bewerken... klikken en het dialoogvenster
+ dialoogvensterBestandsfilters
+ Patroon bewerken gebruiken. Klik op Standaardinstellingen als u terug wilt keren naar de standaard configuratie van het filter. U kunt de naam ook direct aanpassen in het veld voor het patroon van het doelbestand of het dialoogvenster Bestandsfilters. Het dialoogvenster Patroon bewerken biedt de volgende opties:
+
+
+
+ Standaard is ${filename} - volledige bestandsnaam van het bronbestand met extensie: in dit geval is de naam van het vertaalde bestand hetzelfde als dat van het bronbestand.
+
+
+
+
+
+ ${nameOnly} - laat u alleen de naam van het bronbestand invoegen zonder de extensie.
+
+
+
+
+
+ ${targetLocale} - locale-code voor doel (in de vorm "xx_YY").
+
+
+
+
+
+ ${targetLanguage} - de doeltaal en landcode samen (in de vorm "XX-YY").
+
+
+
+
+
+ ${targetLanguageCode} - alleen de doeltaal ("XX").
+
+
+
+
+
+ ${targetCoutryCode} - alleen de doel-landcode ("YY").
+
+
+
+
+
+
+
+ <application>OmegaT</application> bestanden en mappen
+
+ OmegaT werkt met drie bestandstypen.
+
+
+
+ Projectbestanden vertaling: Deze vormen een vertaalproject. Verlies van deze bestanden kan de integriteit van het project beïnvloeden alsmede de mogelijkheid van het voltooien van uw werk. Projectbestanden zijn de meest belangrijke bestanden in OmegaT. Het zijn de bestanden waarmee u dagelijks hebt te maken bij het vertalen.
+
+
+
+
+
+ Bestanden voor gebruikersinstellingen: Deze worden gemaakt als het gedrag van OmegaT wordt gewijzigd met voorkeursinstellingen voor de gebruiker. Verlies van deze bestanden zorgt er meestal voor dat OmegaT terugkeert naar de "fabrieksinstellingen". Dit kan soms enige problemen geven als u midden in een vertaling bent.
+
+
+
+
+
+ Toepassingsbestanden: Zij zijn opgenomen in het pakket dat u hebt gedownload. De meeste er van zijn nodig om OmegaT juist te laten functioneren. Als door enige oorzaak deze bestanden verloren gaan of beschadigd worden, download en herinstalleer OmegaT dan om ze allemaal terug te zetten.
+
+
+
+
+ Projectbestanden vertaling
+
+ Een OmegaT vertaalproject bestaat uit een aantal bestanden en mappen.
+
+
+ <indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>locatie</secondary>
+ </indexterm>Locatie van projectbestanden van de vertaling
+
+ Als u een vertaalproject maakt, maakt OmegaT automatisch een lijst van mappen aan die later zullen dienen als opslagplaatsen voor de bestanden, alsook een aantal bestanden die zullen worden gebruikt om enkele voorkeuren voor het project in te stellen en om het vertaalgeheugen van het project op te slaan. Standaard worden de mappen van een vertaalproject gegroepeerd onder de hoofdmap van het project. Alternatieve locaties voor sommige mappen kunnen worden gekozen bij het maken van het project of tijdens de vertaling. Het is daarom mogelijk om bestaande mappen te kiezen of mappen te maken op locaties die passen bij uw eigen werkwijze en projectbeheer. Open Project > Eigenschappen... of met Ctrl+E en maak de nodige aanpassingen om de locaties van de mappen te wijzigen nadat een project is gemaakt.
+
+
+
+ <indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>lijst</secondary>
+ </indexterm>Lijst van bestanden van het vertaalproject
+
+ In een met OmegaT geopend dialoogvenster ziet een vertaalproject er uit als een bestand met een pictogram van OmegaT er aan verbonden. In een bestandsbeheerder ziet een vertaalproject er echter uit als elke andere map en gedraagt zich ook zo.
+
+
+ OmegaT projecten en mappen
+
+
+
+
+
+
+
+
+ Dubbelklikken op het item met het pictogram van OmegaT is voldoende om het project te openen. Een vertaalproject Voorbeeld_Project, gemaakt met de standaard instellingen, zal worden gemaakt als een nieuwe submap met de volgende structuur:
+
+
+ OmegaT project
+
+
+
+
+
+
+
+
+ Alle submappen zullen bij aanvang leeg zijn.
+
+
+
+ Omegat<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>Submap omegat</secondary>
+ </indexterm>
+
+ De submap omegat bevat ten minste één en mogelijk meerdere andere bestanden. Het meest belangrijke bestand is het bestand van het vertaalgeheugen, project_save.tmx (...). Het bestand project_save.tmx is het werkende vertaalgeheugen voor het project. Met de geactiveerde functie Automatisch opslaan wordt het automatisch bijgewerkt als u stopt. Het is het vertaalgeheugen dat wordt gebruikt om de vertaalde bestanden te maken. Een aantal bestanden met namen in de vorm project_save.tmx.<datum en tijd>.bak (...) zullen later aan deze submap worden toegevoegd. Zij dienen als back-up voor het vertaalgeheugen van het project. Een nieuw exemplaar wordt, iedere keer als u een project opnieuw opent, gemaakt om de inhoud van het project weer te geven, voordat de huidige sessie die heeft veranderd.
+
+ Het projectbestand
+ Projectbestandenbestand Statistieken
+ stats.txt (...) bevat de statistieken over het huidige project en kan worden geopend in een werkbladtoepassing om segment- en informatie over de telling van woorden weer te geven. Het bestand bevat het aantal segmenten voor elk te vertalen bestand - Totaal en Resterend - het aantal unieke segmenten per bestand, het aantal unieke woorden en het aantal unieke tekens met / zonder spaties per bestand.
+
+ Merk op dat Unieke segmenten per bestand het aantal unieke segmenten in een opgegeven bestand vermeld die niet ergens anders in het project voorkomen. De unieke woorden of tekens per bestand hebben een soortgelijke definitie. Merk op dat in een project met meerdere bestanden de som van de unieke segmenten per bestand niet noodzakelijkerwijze gelijk zal zijn aan het totale aantal unieke segmenten in het project.
+
+ De bestanden
+ Projectbestandenignored_words en learned_words
+ ignored_words.txt en learned_words.txt worden gebruikt door de spellingscontrole. Onthoud dat zij specifiek zijn voor een bepaald project, dus als u al een verzameling woorden hebt waarvan u wilt dat de spellingscontrole die negeert / accepteert, moet u de corresponderende twee bestanden naar de submap omegat van uw huidige project kopiëren.
+
+
+
+ Bronbestanden<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>submap Source</secondary>
+ </indexterm>
+
+ De submap source is de locatie voor projectbestanden die moeten worden vertaald. U kunt een nieuwe submap maken en later de bestanden er aan toevoegen. Houdt er wel rekening mee dat de structuur van de submap source elke vorm mag hebben die u wilt. Indien de bestanden die vertaald moeten worden deel uitmaken van een boomstructuur (zoals op een website), hoeft u slechts de bovenste submap op te geven en zal OmegaT de gehele inhoud behouden, waarbij de boomstructuur intact blijft.
+
+
+
+ Doelbestanden<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>submap Target</secondary>
+ </indexterm>
+
+ Als CtrlDProjectVertaalde documenten maken wordt geselecteerd, worden alle bestanden in de map source, of zij zijn vertaald of niet, gereproduceerd in de doelmap met dezelfde hiërarchie van mappen om de huidige status van de vertaling weer te geven. Met andere woorden: OmegaT voegt de informatie voor de vertaling, die is opgeslagen in /omegat/project_save,tmx, samen met de brondocumenten om de inhoud voor het doel te produceren.
+
+
+
+ omegat.project<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>bestand omegat.project</secondary>
+ </indexterm>
+
+ OmegaT maakt dit bestand automatisch als het project wordt gemaakt en het bevat de parameters voor het project. De parameters die zijn opgenomen in dit bestand kunnen worden aangepast in het venster Projecteigenschappen.
+
+ project_naam-omegat.tmx (...)
+
+ project_naam-level1.tmx
+
+ project_naam-level2.tmx
+
+
+ Projectbestandenbestanden project_name....tmx
+
+
+ Deze bestanden bevatten de bron- en doelsegmenten die overeenkomen met de inhoud van de map source op het moment dat ze gemaakt werden (gewoonlijk is dat als de vertaalde documenten worden gemaakt). Zij vormen de geëxporteerde vertaalgeheugens die u kunt gebruiken in toekomstige projecten.
+
+
+
+
+ Gebruikersbestanden<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>gebruikersbestanden</secondary>
+ </indexterm>
+
+
+ Locatie van gebruikersbestanden<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>gebruikersbestanden</secondary> <tertiary>locatie</tertiary>
+ </indexterm>
+
+ Gebruikersbestanden worden opgeslagen op een afzonderlijke locatie waar door elke versie van OmegaT toegang toe kan worden verkregen. De locatie is afhankelijk van het platform dat u gebruikt:
+
+
+
+
+
+
+
+ Windows 2000 en XP
+
+ Documents and Settings\<gebruikersnaam>\Application Data\OmegaT
+
+
+
+ Windows Vista en 7
+
+ Users\<gebruikersnaam>\AppData\Roaming\OmegaT
+
+
+
+ andere Windows
+
+ <Iets>\OmegaT (<Iets> komt overeen met de locatie van de map "home" zoals die wordt vastgesteld door Java.)
+
+
+
+ Linux/Solaris/FreeBSD
+
+ <User Home>/.omegat (.omegat is een map, de punt die voor de naam staat maakt die onzichtbaar tenzij u typt ls -a of een overeenkomende opdracht.)
+
+
+
+ MAC OSX
+
+ <gebruiker Home>/Library/Preferences/OmegaT
+
+
+
+ Andere
+
+ <gebruiker Home>
+
+
+
+
+
+
+
+ Lijst van gebruikersbestanden<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>lijst gebruikersbestanden</secondary>
+ </indexterm>
+
+
+
+
+
+
+
+ logs/OmegaT.log
+
+ Dit bestand slaat foutberichten van Java op terwijl OmegaT wordt uitgevoerd. Als OmegaT zich niet goed lijkt te gedragen is het belangrijk om dit bestand of het relevante gedeelte daarvan op te nemen in een foutenrapport.
+
+
+
+ omegat.prefs
+
+ Een xml-bestand met alle toegankelijke optie-instellingen voor de GUI.
+
+
+
+ uiLayout.xml
+
+ Een xml-bestand met gegevens voor vensterposities.
+
+
+
+ filters.xml
+
+ Een xml-bestand met alle gegevens die zijn ingesteld door de voorkeuren voor het filter.
+
+
+
+ segmentation.conf
+
+ Een xml-bestand dat segmentatieregels bevat.
+
+
+
+
+
+
+
+
+ <indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>toepassingsmappen</secondary>
+ </indexterm>Toepassingsbestanden<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>toepassingsbestanden</secondary>
+ </indexterm>
+
+ OmegaT wordt uitgegeven als een pakket dat u kunt downloaden vanaf SourceForge. In dit hoofdstuk gaan we uit van het platform onafhankelijke pakket dat de toepassing in een standaard Java-vorm bevat. Andere pakketten bevatten een Linux .tar-pakket, een Windows-installatieprogramma - met of zonder een Java Runtime Environment -, een MacOSX-installatieprogramma en een broncodepakket voor ontwikkelaars. Het platform onafhankelijke pakket kan worden gebruikt op elk platform met een werkende Java 1.5 runtime omgeving, inclusief de platforms waarvoor een specifiek pakket bestaat. Het platform onafhankelijke pakket bestaat uit een gecomprimeerd bestand (zip- of tar-archief) dat u in de map van uw keuze moet uitpakken om te installeren. Het bestand kan gewoonlijk worden uitgepakt door op het gedownloade pakket te dubbelklikken. Als het archief is uitgepakt zal een map zijn gemaakt met de volgende inhoud:
+
+
+
+
+
+
+
+ Bestand/ submap
+
+ Inhoud
+
+
+
+ /docs/
+
+ Alle bestanden van de gebruikershandleiding staan in deze map. U kunt ze in een internetbrowser openen om toegang te krijgen tot externe koppelingen.
+
+
+
+ /images/
+
+ Pictogrammen en logo-afbeeldingen zijn hierin opgenomen.
+
+
+
+ /lib/
+
+ Bevat Java-bestanden die nodig zijn om OmegaT uit te voeren.
+
+
+
+ join.html
+
+ Dit is een normaal html-bestand dat, eenmaal geopend in uw internetbrowser, u naar de OmegaT gebruikersgroep brengt die wordt gehost op Yahoo Groups. Abonneren is niet noodzakelijk maar geeft u toegang tot aanvullende services, zoals bestanden en onregelmatige polls, daarnaast kunt u deelnemen aan discussies die zijn gerelateerd aan OmegaT. De groepsarchieven zijn publiek en het raadplegen daarvan vereist geen abonnement op de groep.
+
+
+
+ changes.txt
+
+ Een relatief gedetailleerde lijst van aanpassingen tussen deze versie en de voorafgaande versies.
+
+
+
+ license.txt
+
+ De GNU GENERAL PUBLIC LICENSE. Deze licentie staat u toe om bepaalde dingen met OmegaT te doen, inclusief het aanpassen en distribueren ervan. Indien u bent geïnteresseerd in het aanpassen of distribueren van OmegaT, lees dit document dan zorgvuldig door en zorg er voor dat u bekend bent met alle implicaties vóórdat u iets anders doet. Als u twijfelt, aarzel dan niet om de projectleden direct te benaderen ofwel door hen een mail te sturen vanaf de pagina van SourceForge of door een publieke mail te sturen aan de gebruikersgroep.
+
+
+
+ doc-license.txt
+
+ De GNU GENERAL PUBLIC LICENSE. Deze licentie behandelt de documentatie. Zie boven.
+
+
+
+ readme.txt
+
+ Dit bestand is heel belangrijk en u zou het gelezen moeten hebben voordat u met OmegaT begon. Het bevat algemene informatie over OmegaT, waar meer informatie te vinden is, hoe mee te doen etc. Het is vertaald in een aantal talen.
+
+
+
+ Omegat
+
+ Een tekstbestand dat twee regels bevat:
+
+
+
+
+
+ #!/bin/bash java
+
+
+
+
+
+ java -jar
+ OmegaT.jar $*
+
+
+
+
+
+ Linux- en OSX-gebruikers zouden dit handig kunnen vinden. Maak het uitvoerbaar (chmod +x OmegaT) vanaf de opdrachtregel nadat u zich er van overtuigd hebt dat u in de map /OmegaT_2.5/ bent. U kunt dan OmegaT starten door dit bestand vanaf de opdrachtregel uit te voeren.
+
+
+
+ OmegaT.bat
+
+ Een batch-bestand gebruikt om OmegaT te starten vanaf de opdrachtregel van Windows. Het bevat slechts de volgende regel:
+
+
+
+
+
+ java -jar OmegaT.jar
+ %*
+
+
+
+ OmegaT.jar
+
+ De hoofdtoepassing OmegaT. U moet dit bestand aanroepen vanaf de opdrachtregel of starten vanuit uw bestandsbeheerder, gewoonlijk door er op te dubbelklikken, om OmegaT te starten.
+
+
+
+
+
+
+
+
+ Te vertalen bestanden
+
+
+ Bestandsformaten<indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>bestandsformaten</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>bestandsformaten</secondary>
+ </indexterm>
+
+ U kunt OmegaT gebruiken om bestanden te vertalen in een aantal bestandsformaten. Er zijn twee basale typen bestandsformaten, platte tekst en opgemaakte tekst.
+
+
+ Platte-tekst bestanden<indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>Platte tekst-bestanden</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>Platte tekst-bestanden</secondary>
+ </indexterm>
+
+ Platte tekst-bestanden bevatten alleen maar tekst, zodat hun vertaling zo eenvoudig is als het typen van die vertaling. Er zijn meerdere methoden om de codering van een bestand te specificeren zodat de inhoud niet door elkaar wordt gegooid bij het openen in OmegaT. Zulke bestanden hebben geen informatie over opmaak naast de "witte ruimte" die wordt gebruikt om tekst uit te lijnen, alinea's aan te geven of paginaeinden in te voegen. Zij zijn niet in staat informatie te bevatten / te behouden met betrekking tot de kleur, lettertype etc. van de tekst. Momenteel ondersteunt OmegaT de volgende platte tekst-formaten:
+ Bestandsformatenniet opgemaaktebronbestanden
+
+
+
+
+ ASCII tekst (.txt, etc.)
+
+
+
+
+
+ Gecodeerde tekst (*.UTF8)
+
+
+
+
+
+ Java bronbundels (*.properties)
+
+
+
+
+
+ PO-bestanden (*.po)
+
+
+
+
+
+ INI (sleutel=waarde) bestanden (*.ini)
+
+
+
+
+
+ DTD-bestanden (*.DTD)
+
+
+
+ DocuWiki-bestanden (*.txt)
+
+
+
+
+
+ SubRip titelbestanden (*.srt)
+
+
+
+
+
+ Magento CE Locale CSV-bestanden (*.csv)
+
+
+
+ Andere platte-tekst bestanden kunnen worden behandeld door OmegaT door hun bestandstype te koppelen aan een ondersteund bestandstype (bijvoorbeeld .pod-bestanden zouden kunnen worden gekoppeld aan het ASCII tekstfilter) en ze voor te bewerken met specifieke segmentatieregels.
+
+
+
+ Opgemaakte tekstbestanden<indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>opgemaakte tekstbestanden</secondary> <seealso>getagde tekst</seealso>
+ </indexterm><indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>opgemaakte tekstbestanden</secondary>
+ </indexterm>
+
+ Opgemaakte tekstbestanden bevatten zowel tekst als informatie, zoals lettertype, afmeting, kleur etc. Zij worden normaal gesproken gemaakt met tekst- of HTML-verwerkingsprogramma's. Zulke bestanden zijn ontworpen om hun informatie over de opmaak te behouden. Zulke informatie over de opmaak kan eenvoudig zijn zoals "dit is vet" of zo complex als tabelgegevens met verschillende lettertype-afmetingen, kleuren, posities etc. In de meeste vertalingen wordt het belangrijk geacht dat het vertaalde document er uitziet zoals het origineel. OmegaT stelt u in staat om dit te doen door het markeren van de tekens/woorden die een speciale opmaak hebben met eenvoudig te bewerken tags. Vereenvoudigen van de opmaak van de originele tekst draagt enorm bij aan het verminderen van het aantal tags. Indien mogelijk zou het gelijk maken van gebruikte lettertypen, lettertype-afmetingen, kleuren etc. het vertalen vereenvoudigen en het aantal mogelijke fouten in tags verminderen. Elk bestandstype wordt verschillend behandeld in OmegaT. Specifiek gedrag kan worden ingesteld in de bestandsfilters. Momenteel ondersteunt OmegaT de volgende opgemaakte tekst-formaten:
+ Bestandsformatenopgemaaktebronbestanden
+
+
+
+
+ OpenOffice.org / OpenDocument (*.ods, *.ots, *.odt, *.ott,
+ *.odp, *.otp)
+
+
+
+ Microsoft Office Open XML (*.docx, *.dotx, *.xlsx, *.xltx,
+ *.pptx)
+
+
+
+ (X)HTML (*.html, *.xhtml,*.xht)
+
+
+
+ HTML Help Compiler (*.hhc, *.hhk)
+
+
+
+ DocBook (*.xml)
+
+
+
+ XLIFF (*.xlf, *.xliff, *.sdlxliff) - eentalig, d.i. één taalcombinatie mogelijk voor een bepaald project
+
+
+
+ QuarkXPress CopyFlowGold (*.tag, *.xtg)
+
+
+
+ ResX-bestanden (*.resx)
+
+
+
+ Android-bronbestanden (*.xml)
+
+
+
+ LaTex (*.tex, *.latex)
+
+
+
+ Help- (*.xml) en Manual- (*.hmxp) bestanden
+
+
+
+ Typo3 LocManager (*.xml)
+
+
+
+ WiX Localization (*.wxl)
+
+
+
+ Iceni Infix (*.xml)
+
+
+
+ Flash XML exporteren (*.xml)
+
+
+ Wordfast TXML (*.txml)
+
+
+ Camtasia voor Windows (*.camproj)
+
+
+
+
+ Andere opgemaakte tekst-bestanden kunnen worden afgehandeld door OmegaT door hun bestandstype te koppelen aan een ondersteund bestandstype, er van uitgaande dat de overeenkomende segmentatieregels ze juist zullen segmenteren.
+
+
+
+
+ Andere bestandsformaten<indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>andere bestandsformaten</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>andere bestandsformaten</secondary>
+ </indexterm>
+
+ Andere platte tekst- of opgemaakte tekst-bestandsformaten die mogelijk door OmegaT kunnen worden verwerkt zouden ook kunnen bestaan.
+
+
+ Doelbestandenprogramma's voor bestandsconversie
+ Externe programma's kunnen worden gebruikt om bestanden te converteren naar ondersteunde formaten. De vertaalde bestanden moeten daarna weer terug worden geconverteerd naar het originele formaat. Als u bijvoorbeeld een verouderde versie van Microsoft Word hebt, die niet het ODT-formaat kan afhandelen, is hier een manier voor Word-bestanden met de extensie DOC:
+
+
+
+ importeer het bestand in OpenOffice.org Writer
+
+
+
+
+
+ sla het bestand op in de indeling ODT
+
+
+
+
+
+ vertaal het in het doel-ODT-bestand
+
+
+
+
+
+ laad het doelbestand in OpenOffice.org Writer
+
+
+
+
+
+ sla het bestand op als een DOC-bestand
+
+
+
+ De kwaliteit van het vertaalde bestand zal afhankelijk zijn van de kwaliteit van het heen-en-weer converteren. Voor het uitvoeren van dergelijke conversies: zorg er voor dat alle opties zijn uitgeprobeerd. Controleer de OmegaT homepage voor een bijgewerkte lijst van hulpprogramma's voor vertalingen.
+
+
+
+ Van rechts naar links talen<indexterm class="singular">
+ <primary>Van rechts naar links talen</primary>
+ </indexterm><indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>talen van rechts naar links</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>talen van rechts naar links</secondary>
+ </indexterm>
+
+ Uitvulling van de bron- en doelsegmenten is afhankelijk van de projecttalen. Ze worden standaard links uitgevuld voor talen van Left-To-Right (LTR) en rechts uitgevuld voor talen van Right-To-Left (RTL). U kunt schakelen tussen de verschillende weergavemodi door in te drukken ShiftCtrlO (dit is de letter O en niet de numerieke 0). De schakeling met ShiftCtrlO heeft drie statussen:
+
+
+
+ standaard uitvulling, die wordt gedefinieerd door de taal
+
+
+
+
+
+ links uitvullen
+
+
+
+
+
+ rechts uitvullen
+
+
+
+ Gebruiken van de modus RTL in OmegaT heeft geen enkele invloed op de modus weergeven van de vertaalde documenten die werden gemaakt in OmegaT. De modus weergeven van de vertaalde documenten zal moeten worden aangepast binnen de gewoonlijk gebruikte toepassing (zoals Microsoft Word) om ze weer te geven of te wijzigen (bekijk de relevante handleidingen voor de details). Gebruiken van ShiftCtrlO zorgt er voor dat zowel de tekstinvoer als de weergave in OmegaT worden gewijzigd. Door te klikken op het venster en te schakelen met de weergavemodus kan het afzonderlijk worden gebruikt voor alle drie vensters (Bewerken, Overeenkomsten en Woordenlijst). Het kan ook worden gebruikt in alle aanwezige invoervelden in OmegaT - in het zoekvenster, voor de segmentatieregels etc.
+
+ Opmerking voor Mac OS X-gebruikers: gebruik de sneltoets ShiftCtrlO en niet cmd+Ctrl+O.
+
+
+ LTR- en RTL-tekenreeksen in segmenten mixen<indexterm class="singular">
+ <primary>Van rechts naar links talen</primary> <secondary>mixen van RTL- en LTR-tekenreeksen</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>mixen van RTL- en LTR-tekenreeksen</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>mixen van RTL- en LTR-tekenreeksen</secondary>
+ </indexterm>
+
+ Bij het schrijven van pure RTL-tekst, kan de standaard (LTR) weergave worden gebruikt. In veel gevallen is het echter noodzakelijk om LTR-tekst in RTL-tekst in te bedden. Bijvoorbeeld in OmegaT-tags, productnamen die moeten worden behouden in de LTR-brontaal, tijdelijke plaatsaanduidingen in lokalisatie-bestanden en getallen in tekst. In dit soort gevallen is het noodzakelijk om te schakelen naar de modus RTL, zodat de RTL- (in feite twee richtingen) tekst correct wordt weergegeven. Waarbij dient te worden opgemerkt dat als OmegaT in de modus RTL staat, zowel de bron als het doel worden weergegeven in de modus RTL. Dit betekent dat als de brontaal in LTR is en de doeltaal is RTL, of vice versa, het nodig zou kunnen zijn om heen en weer te schakelen tussen de modi RTL en LTR om de bron te bekijken en eenvoudiger het doel in te voeren in hun respectievelijke modus.
+
+
+
+ <application>OmegaT</application>-tags in RTL-segmenten<indexterm class="singular">
+ <primary>Van rechts naar links talen</primary> <secondary>OmegaT-tags in RTL-talen</secondary>
+ </indexterm>
+
+ Zoals hierboven vermeld zijn OmegaT-tags LTR-tekenreeksen. Bij het vertalen tussen RTL- en LTR-talen kan het nodig zijn dat de vertaler, om de tags juist te lezen uit de bron en om ze dan juist in te voeren in het doel, vele malen moet schakelen tussen de modi LTR en RTL.
+
+ Indien het document het toelaat wordt het de vertaler sterk aangeraden om informatie over de opmaak uit het originele document te verwijderen zodat er zo weinig mogelijk tags als nodig is in de OmegaT-interface verschijnen. Volg de aanwijzingen die worden gegeven in Hints voor tagbeheer. Valideer de tags regelmatig (zie Tag-validatie) en maak met regelmatige tussenpozen vertaalde documenten (zie hieronder en Menu) om het eenvoudiger te maken om problemen te zien die opkomen. Een hint: vertalen van een 'platte tekst'-versie van de tekst en het op een later moment toevoegen van het noodzakelijke opmaakprofiel in de relevante toepassing zou misschien minder problematisch blijken te zijn.
+
+
+
+ Vertaalde RTL-documenten maken<indexterm class="singular">
+ <primary>Van rechts naar links talen</primary> <secondary>RTL-doelbestanden maken</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Van rechts naar links talen</primary> <secondary>doelbestanden</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Van rechts naar links talen</primary> <secondary>RTL-doeltekst maken</secondary>
+ </indexterm>
+
+ Als het vertaalde document wordt gemaakt zal de weergaverichting hetzelfde zijn als die van het originele document. Als het originele document LTR was, moet de weergaverichting van het doeldocument handmatig worden gewijzigd naar RTL in de toepassing waarin het wordt weergegeven. Elke indeling voor de uitvoer heeft specifieke manieren om om te gaan met RTL-weergave, controleer de relevante handleidingen voor de toepassing voor details.
+
+ Het is soms mogelijk om de parameters voor weergave voor het bronbestand te wijzigen zodat dergelijke parameters worden geërfd door de doelbestanden, om te vermijden dat de parameters voor weergave voor de doelbestanden elke keer moeten worden gewijzigd als de bestanden worden geopend. Dergelijke aanpassingen zijn bijvoorbeeld mogelijk in bestanden van OpenOffice.org.
+
+
+
+
+
+ Bewerken (gedrag)<indexterm class="singular">
+ <primary>menu Opties</primary> <secondary>Bewerken (gedrag)...</secondary>
+ </indexterm>
+
+ Het dialoogvenster in OptiesBewerken (gedrag)... laat de gebruiker bepalen hoe het huidige segment wordt geïnitialiseerd en afgehandeld.
+
+
+ Bewerken (gedrag) opties
+
+
+
+
+
+
+
+
+
+ Automatisch invoegen van overeenkomst<indexterm class="singular">
+ <primary>Automatisch invoegen van overeenkomst</primary>
+ </indexterm>
+
+ U vertaalt uw bestanden door van segment naar segment te gaan, waarbij elk segment op zijn beurt wordt bewerkt. Bij het verplaatsen tussen segmenten kunt u bepalen of het bewerkingsveld moet worden gevuld met een bestaande vertaling uit het venster Overeenkomsten of met de brontekst. In OptiesBewerken (gedrag)... biedt OmegaT u de volgende alternatieven:
+
+
+
+ De brontekst
+
+
+ U kunt de brontekst automatisch ingevoegd hebben in het bewerkingsveld. Dit is handig als teksten veel handelsnamen en andere woorden met hoofdletters bevat die intact gelaten moeten worden.
+
+
+
+
+ Segment leeg laten
+
+
+ OmegaT laat het bewerkingsveld leeg. Deze optie stelt u in staat om de vertaling in te voeren zonder de brontekst te hoeven verwijderen, hetgeen u een aantal toetsaanslagen scheelt (Ctrl+A en Del).
+
+
+
+
+ Beste overeenkomst invoegen
+
+
+ OmegaT voegt de vertaling van de tekenreeks in die het meeste lijkt op de huidige bron, indien die boven de drempel van het percentage van overeenkomst komt dat in het dialoogvenster is ingesteld. Het voorvoegsel (is standaard leeg) kan worden gebruikt om vertalingen te taggen, wat wordt gedaan via fuzzy overeenkomsten. Indien u een voorvoegsel toevoegt (bijvoorbeeld [fuzzy]), kunt u deze vertalingen later traceren om te zien of zij juist zijn.
+
+
+
+
+
+
+ Vertaling mag gelijk zijn aan brontekst<indexterm class="singular">
+ <primary>Vertaling gelijk aan brontekst</primary>
+ </indexterm>
+
+ Te vertalen documenten kunnen handelsnamen, namen of andere woorden met hoofdletters bevatten die hetzelfde moeten blijven in vertaalde documenten. Er zijn twee strategieën voor segmenten die slechts zulke onveranderlijke tekst bevatten.
+
+ U zou kunnen besluiten om zulke segmenten niet te vertalen. OmegaT zal deze segmenten dan aanmerken als niet-vertaald. Dit is de standaard. Het alternatief is om een vertaling in te voeren die identiek is aan de brontekst. OmegaT is in staat om te herkennen dat u dit gedaan hebt. Ga naar OptiesBewerken (gedrag)... en selecteer het vak Vertaling mag gelijk zijn aan brontekst, om dit mogelijk te maken.
+
+
+
+ Segment naar tekstbestanden exporteren<indexterm class="singular">
+ <primary>Het huidige segment exporteren</primary>
+ </indexterm>
+
+ De functie Tekst exporteren exporteert gegevens vanuit het huidige OmegaTproject naar platte tekst-bestanden. De gegevens worden geëxporteerd als het segment wordt geopend. De bestanden verschijnen in de submap /script in de map met gebruikersbestanden van OmegaT, en bevatten:
+
+
+
+ De inhoud van de brontekst van het segment (source.txt).
+
+
+
+ De inhoud van de brontekst van het segment (target.txt).
+
+
+
+ De tekst die door de gebruiker werd geaccentueerd, als Ctrl-Shift-C werd ingedrukt of als Bewerken > Selectie exporteren is geselecteerd (selection.txt).
+
+
+
+ De inhoud van de bestanden wordt overschreven als een nieuw segment wordt geopend (source.txt en target.txt) of als een nieuwe selectie wordt geëxporteerd (selection.txt). De bestanden zijn niet-opgemaakte platte tekst-bestanden. Het gehele proces kan worden gestuurd en beheerd via op Tck/Tcl-gebaseerde scripts. Bekijk De functie Tekst exporteren in OmegaT gebruiken voor specificaties, voorbeelden en suggesties.
+
+
+
+
+ Lettertype-instellingen
+
+
+ Lettertype-instellingen
+
+ Lettertype-instellingen
+
+
+ In dit dialoogvenster kan het lettertype worden gedefinieerd dat door OmegaT in de volgende vensters wordt gebruikt:
+
+
+
+ OmegaT hoofdvenster (zonder het venster Woordenboek)
+
+
+ venster Zoeken
+
+
+ venster Tags valideren
+
+
+
+ Het dialoogvenster kan worden benaderd via het item in het menu van de toepassing. Het dialoogvenster bevat: OptiesLettertype...
+
+ menu OptiesLettertype...
+
+
+
+
+
+
+ Lettertype
+ Gebruik de keuzelijst om één van de beschikbare lettertypen op uw machine te selecteren.
+
+
+
+
+ Grootte
+ Bewerken om de grootte van het lettertype te wijzigen.
+
+
+
+
+
+
+
+ Voorbeeldtekst
+ Direct voorbeeld van het geselecteerde lettertype.
+
+
+
+
+
+ Opmerking
+ Het bijwerken van de weergave kan meer tijd vergen als het aantal weergegeven segmenten van belang is. Ook kunnen sommige lettertypen een betere dekking geven voor uw taalpaar.
+
+
+
+
+
+ Werken met opgemaakte tekst<indexterm class="singular">
+ <primary>Doelbestanden</primary> <secondary>opgemaakte tekst</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>opgemaakte tekst</secondary>
+ </indexterm>
+
+ Informatie over opmaak die aanwezig is in het bronbestand moet meestal worden gereproduceerd in het doelbestand. De in-regelige informatie over opmaak van ondersteunde formaten (momenteel DocBook, HTML, XHTML, Open Document (OpenOffice.org) en Office Open XML (MS Office 2007 en later) wordt door OmegaT weergegeven als tags. Normaal gesproken worden tags genegeerd bij het bepalen van de gelijkheid tussen de verschillende teksten ten behoeve van overeenkomsten. Tags die zijn gereproduceerd in het vertaalde segment zullen aanwezig zijn in het vertaalde document.
+
+
+ Tags voor opmaak<indexterm class="singular">
+ <primary>Tags</primary>
+ </indexterm>
+
+
+ Tagsnamen
+ Namen van tags:
+
+ De tags bestaan uit één tot drie tekens en een getal. Met unieke nummers kunnen de tags die met elkaar overeenkomen worden gegroepeerd en onderscheiden zich van de tags die dezelfde tekencombinatie hebben, maar in feite verschillend zijn. De gebruikte tekens in de tags proberen de onderliggende betekenis van de tag weer te geven (bijv. b voor vet, i voor cursief, etc.)
+
+
+ Tagsnummering
+ Nummering van tags:
+
+ Tags worden oplopend genummerd per groep van tags. "Taggroepen" in deze context zijn één enkele tag (zoals <i0> en </i0>). Binnen een segment krijgt de eerste groep (paar of enkele) het nummer 0, de tweede het nummer 1, etc. Het eerste voorbeeld hieronder heeft 3 tag-groepen (een paar, een enkele en dan nog een ander paar), het tweede voorbeeld heeft slechts één groep (een paar).
+
+
+ Tagsparen en enkele
+ Paren en enkele:
+
+ Tags zijn altijd óf enkel óf gepaard. Enkele tags geven informatie over de opmaak aan die niet van invloed is op de tekst er omheen (een extra spatie of regeleinde bijvoorbeeld).
+
+ <b0><Ctr+N></b0>,
+ <br1><b2><Enter></b2><segment 2132>
+
+
+ <br1> is een enkele tag en heeft geen effect op de omringende tekst. Tagparen geven gewoonlijk informatie over de stijl weer die van toepassing is op de tekst tussen de openingstag en de sluitingstag van een paar. <b0> en </b0> hieronder zijn gepaard en beïnvloeden de tekst log.txt. Onthoud dat de openingstag altijd vóór de bijbehorende sluitingstag moet komen:
+
+ <Logbestand (<b0>log.txt</b0>) voor het bijhouden van bewerkingen en fouten.<segment 3167>
+
+ OmegaT maakt zijn tags voordat het proces van segmentatie van zinnen wordt uitgevoerd. Afhankelijk van de segmentatieregels kan het paar tags worden gescheiden naar twee opeenvolgende segmenten en zal de tagvalidatie een fout aangeven en de twee segmenten markeren.
+
+
+
+ Tag-bewerkingen<indexterm class="singular">
+ <primary>Tags</primary> <secondary>bewerkingen</secondary>
+ </indexterm>
+
+ Voorzichtigheid is geboden met tags. Als zij per ongeluk worden gewijzigd kan de opmaak van het uiteindelijke document corrupt worden. De basisregel is dat de volgorde van de tags in dezelfde volgorde moet worden behouden. Het is echter mogelijk, als bepaalde regels strikt worden gevolgd, om van deze basisregel af te wijken.
+
+
+ Tagsdupliceren
+ Tags dupliceren:
+
+ Kopieer ze eenvoudigweg naar de positie van uw keuze om tags te dupliceren. Onthoud dat in een paar de openingstag vóór de sluitingstag moet komen. De opmaak die wordt vertegenwoordigd door de groep die u dupliceerde zal op beide gedeelten worden toegepast.
+
+ Voorbeeld:
+
+ <b0>Deze opmaak</b0> zal hier worden gedupliceerd.<segment 0001>
+
+ Na het dupliceren:
+
+ <b0>Deze opmaak</b0> is <b0>hier gedupliceerd</b0>.<segment 0001>
+
+
+ Tagsverwijderen van groepen
+ Verwijderen van taggroepen:
+
+ Verwijder ze eenvoudigweg uit het segment om taggroepen te verwijderen. Onthoud dat van een paar zowel de openings- als de sluitingstag moet worden verwijderd om er voor te zorgen dat alle sporen van de opmaak correct worden uitgewist, anders zou het vertaalde bestand mogelijk beschadigd kunnen raken. Door een taggroep te verwijderen verwijdert u de gerelateerde opmaak uit het vertaalde document.
+
+ Voorbeeld:
+
+ <b0>Deze opmaak</b0> zal worden verwijderd.<segment 0001>
+
+ Na het verwijderen:
+
+ Deze opmaak is verwijderd.<segment 0001>
+
+
+
+ Taggroep nesten<indexterm class="singular">
+ <primary>Tags</primary> <secondary>nesten van groepen</secondary>
+ </indexterm>
+
+ Wijzigen van de volgorde van een taggroep kan resulteren in het nesten van een taggroep binnen een andere taggroep. Dit is acceptabel zolang de omsluitende groep in zijn geheel de omsloten groep bevat. Met andere woorden, zorg er bij het verplaatsen van tagparen voor dat zowel de openings- als de sluitingstag ofwel binnen of buiten andere tagparen staan, anders zou het vertaalde bestand mogelijk beschadigd kunnen zijn en niet willen openen.
+
+ Voorbeeld:
+
+ <b0>Opmaak</b0> <b1>een</b1> zal worden genest binnen opmaak nul.<segment 0001>
+
+ Na het nesten:
+
+ <b0>Opmaak <b1>een</b1></b0> is genest binnen opmaak nul.<segment 0001>
+
+
+
+ Taggroep overlappen<indexterm class="singular">
+ <primary>Tags</primary> <secondary>overlappen van groepen</secondary>
+ </indexterm>
+
+ Overlappen is het resultaat van slechte bewerkingen van tagparen en zal gegarandeerd leiden tot beschadiging van de opmaak en soms tot het helemaal niet openen van het vertaalde document.
+
+ Voorbeeld:
+
+ <b0>Opmaak</b0> <b1>one</b1> zal worden verminkt.<segment 0001>
+
+ Na een slechte bewerking:
+
+ <b0>Opmaak <b1>een</b0> </b1>is nu zeer verminkt.<end segment 0001>
+
+
+
+ Taggroep validatie<indexterm class="singular">
+ <primary>Tags</primary> <secondary>groep valideren</secondary>
+ </indexterm>
+
+ De functie Tags valideren detecteert gewijzigde tags (of dat met opzet is gedaan of per ongeluk) en toont de betrokken segmenten. Het activeren van deze functie – Ctrl+T
+ SneltoetsenCtrl+T - Tagvalidatie
+ - zal een venster openen dat alle segmenten uit het bestand, waarvan wordt vermoed dat ze zijn verbroken of slechte tags zijn, bevat. Repareren van de tags en het opnieuw samenstellen van de doeldocumenten is eenvoudig met de functie Tags valideren. Het venster, dat wordt geopend door te drukken op Ctrl+T, heeft een kolom met 3 tabellen met een koppeling naar het segment, het originele segment en het doelsegment
+
+
+ Invoer bij tagvalidatie
+
+
+
+
+
+
+
+
+
+
+
+
+ De tags worden vet blauw geaccentueerd voor eenvoudige vergelijking tussen de originele en de vertaalde inhoud. Klik op de koppeling om het segment in het venster Bewerken te activeren. Verbeter, indien nodig, de fout (in het geval hierboven is dat het ontbrekende paar <i2></i2>) en druk op Ctrl+T om terug te keren naar het venster Tags valideren om andere fouten te corrigeren. Tagfouten zijn volgordes van tags in de vertaling die niet dezelfde volgorde en nummering van tags produceren als die in het originele segment. Sommige tagbewerkingen zijn noodzakelijk en zijn goedaardig, sommige zullen problemen veroorzaken als het vertaalde document wordt gemaakt.
+
+
+
+ Hints voor tagbeheer<indexterm class="singular">
+ <primary>Tags</primary> <secondary>hints</secondary>
+ </indexterm>
+
+ Vereenvoudig de originele tekst
+
+ Tags vertegenwoordigen over het algemeen een bepaalde vorm van opmaak van de originele tekst. Vereenvoudigen van de originele opmaak draagt bij aan het verminderen van het aantal tags. Waar de omstandigheden dat toestaan, zou het gelijk maken van gebruikte lettertypen, lettertype-afmetingen, kleuren etc. moeten worden overwogen, omdat het het vertalen vereenvoudigt en mogelijke fouten in tags vermindert. Lees het gedeelte Tagbewerkingen om te zien wat er met tags gedaan kan worden. Onthoud dat als u tags een probleem vindt in OmegaT en de opmaak niet buitengewoon relevant is voor de huidige vertaling, het verwijderen van tags de eenvoudigste manier kan zijn om uit de problemen te geraken.
+
+ Wees extra voorzichtig met tagparen.
+
+ Als u de tags moet zien in OmegaT maar de meeste opmaak niet behoeft te behouden in het vertaalde document staat het u vrij om de tags niet op te nemen in het vertaalde document. Let in dit geval extra op de tagparen omdat het verwijderen van één deel van het paar, maar het vergeten te verwijderen van het andere, gegarandeerd de opmaak van uw document zal beschadigen. Omdat tags in de tekst zelf zijn opgenomen, is het mogelijk om segmentatieregels te gebruiken om segmenten te maken met minder tags. Dit is een geavanceerde voorziening en enige ervaring is vereist om die juist toe te passen.
+
+ OmegaT is nog niet in staat om fouten in de opmaak volautomatisch te detecteren, dus het zal geen signaal geven als u een fout maakt of de opmaak wijzigt zodat die beter bij uw doeltaal past. Soms kan uw vertaalde document er echter vervormd uitzien en, - in het ergste geval-, zou zelfs misschien weigeren te openen.
+
+
+
+
+ Werken met platte tekst<indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>Platte tekst-bestanden</secondary>
+ </indexterm>
+
+
+ Standaard codering<indexterm class="singular">
+ <primary>Standaard codering</primary> <secondary>'platte tekst'-bestanden</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Bronbestanden</primary> <secondary>Standaard codering</secondary>
+ </indexterm>
+
+ 'Platte-tekst'-bestanden - meestal met de extensie .txt - bevatten slechts tekstuele informatie en bieden geen helder gedefinieerde manier om de computer te vertellen welke taal zij bevatten. Het beste dat OmegaT in zo'n geval kan doen, is er van uitgaan dat de tekst is geschreven in de taal die de computer zelf gebruikt. Dit is geen probleem voor bestanden die zijn gecodeerd in Unicode met behulp van een 16-bit tekenset voor codering. Al de tekst echter werd gecodeerd in 8-bit, kan men worden geconfronteerd met de volgende vervelende situatie: in plaats van de tekst weer te geven voor Japanse tekens...
+
+
+
+
+
+
+
+
+
+
+
+ ...zal het systeem het bijvoorbeeld als volgt weergeven:
+
+
+
+
+
+
+
+
+
+
+
+ De computer waarop OmegaT wordt uitgevoerd heeft Russisch als de standaard taal en dus worden de tekens in het Cyrillisch alfabet weergegeven en niet in Kanji.
+
+
+
+ De <application>OmegaT</application>-oplossing<indexterm class="singular">
+ <primary>Standaard codering</primary> <secondary>OmegaT oplossing</secondary>
+ </indexterm>
+
+ Er bestaan in principe drie manieren om dit op te lossen in OmegaT. Zij behelzen allemaal het gebruik van de bestandsfilters in het menu Opties.
+
+
+
+ Wijzig de codering van uw bestanden naar Unicode
+
+
+ open uw bronbestand in een tekstverwerker die zijn codering juist interpreteert en sla het bestand op met de codering "UTF-8". Wijzig de bestandsextensie van .txt naar .utf8. OmegaT zal het bestand automatisch interpreteren als een UTF8-bestand. Dit is de beste algemene alternatief, het bespaart u problemen op de langere termijn.
+
+
+
+
+
+
+ Specificeer de codering voor uw 'platte tekst'-bestanden
+
+
+ - d.i. bestanden met de extensie .txt - : wijzig, in de sectie Tekstbestanden van het dialoogvenster Bestandsfilters, de Codering van bronbestand van <auto> naar de codering die overeenkomt met uw bron .txt-bestand, bijvoorbeeld .jp voor het bovenstaande voorbeeld.
+
+
+
+
+
+
+ Wijzig de extensies van uw 'platte tekst'-bestanden
+
+
+ bijvoorbeeld van .txt naar .jp voor Japanse platte teksten: voeg, in de sectie Tekstbestanden van het dialoogvenster Bestandsfilters, een nieuw Patroon voor bronbestanden toe (*.jp voor dit voorbeeld) en selecteer de toepasselijke parameters voor de bron- en doelcodering.
+
+
+
+
+ OmegaT heeft standaard het volgende lijstje beschikbaar om het voor u eenvoudiger te maken om sommige 'platte tekst'-bestanden te behandelen.
+
+
+
+ .txt-bestanden worden automatisch (<auto>) door OmegaT geïnterpreteerd als zijnde gecodeerd in de standaard codering van de computer.
+
+
+
+
+
+ .txt1-bestanden zijn bestanden in ISO-8859-1, geschikt voor de meeste West-Europese talen.
+ Standaard coderingWesters
+
+
+
+
+
+
+ .txt2-bestanden zijn bestanden in ISO-8859-2, die de meeste Centraal- en Oost-Europese talen ondervangt)
+ Standaard coderingCentraal- en Oost-Europees
+
+
+
+
+
+
+ .utf8 bestanden worden door OmegaT geïnterpreteerd als zijnde gecodeerd in UTF-8 (een codering die bijna alle talen in de wereld ondervangt).
+ Standaard coderingUnicode
+
+
+
+
+ U kunt dat zelf controleren door het item Bestandsfilters te selecteren in het menu Opties. Als u bijvoorbeeld een Tsjechisch tekstbestand (zeer waarschijnlijk geschreven in de code ISO-8859-2) hebt, hoeft u alleen maar de extensie te wijzigen van .txt naar .txt2 en OmegaT zal de inhoud juist interpreteren. Indien u echter op zeker wilt spelen kunt u overwegen om dit soort bestanden te converteren naar Unicode, d.i. naar de bestandsindeling .utf8.
+
+
+
+
+ Vertaalgeheugens<indexterm class="singular">
+ <primary>Vertaalgeheugens</primary>
+ </indexterm>
+
+
+ Vertaalgeheugens in OmegaT
+
+
+ mappen tmx - locatie en doel
+
+ Projecten van OmegaT kunnen bestanden voor vertaalgeheugens bevatten - dit zijn bestanden met de extensie tmx - op vier verschillende plaatsen:
+
+
+
+
+ Vertaalgeheugenssubmap omegatprojectbestanden
+ map omegat
+
+
+ De map omegat bevat project_save.tmx en mogelijk een aantal back-ups van TMX-bestanden. Het bestand project_save.tmx bevat alle segmenten die in het geheugen zijn opgenomen sinds u het project startte. Dit bestand bestaat altijd in een project. De inhoud ervan zal altijd alfabetisch worden gesorteerd op het bronsegment.
+
+
+
+
+
+ Vertaalgeheugenshoofdmap project
+ hoofdmap project
+
+
+ De hoofdmap van het project bevat 3 tmx-bestanden, project_naam-omegat.tmx, project_naam-level1.tmx en project_naam-level2.tmx (waarin project_naam de naam is van uw project).
+
+
+
+ Het bestand level1 bevat alleen tekstuele informatie.
+
+
+
+ Het bestand level2 kapselt specifieke tags van OmegaT in binnen correcte TMX-tags zodat het bestand met zijn opmaakinformatie kan worden gebruikt in een vertaalprogramma dat TMX niveau 2-geheugens ondersteund of OmegaT zelf.
+
+
+
+ Het bestand OmegaT is inclusief OmegaT specifieke opmaaktags zodat het bestand kan worden gebruikt in andere OmegaT-projecten
+
+
+
+ Deze bestanden zijn kopieën van het bestand project_save.tmx, d.i. van het belangrijkste vertaalgeheugen van het project, exclusief de zogenaamde wezen-segmenten. Zij dragen toepasselijk gewijzigde namen, zodat de inhoud ervan steeds kan worden geïdentificeerd, indien elders gebruikt, bijvoorbeeld in de submap tm van een ander project (zie hieronder).
+
+
+
+
+ map
+ Vertaalgeheugenssubmap tmprojectbestanden
+ tm
+
+
+ De map /tm/ kan een willekeurig aantal aanvullende vertaalgeheugens bevatten - d.i. tmx-bestanden. Zulke bestanden kunnen worden gemaakt in elk van de drie hierboven aangegeven variëteiten. Onthoud dat andere CAT-programma's tmx-bestanden kunnen exporteren (en ook importeren), gewoonlijk in alle drie vormen. Het beste is natuurlijk om OmegaT-specifieke TMX-bestanden te gebruiken (zie hierboven), zodat de in-regelige opmaak binnen het segment wordt behouden.
+
+ De inhoud van vertaalgeheugens in de submap tm dienen om suggesties te genereren voor de tekst(en) om te worden vertaald. Elke tekst, reeds vertaald en opgeslagen in deze bestanden, zal tussen de overeenkomsten verschijnen, indien het voldoende overeenkomt met de tekst die momenteel wordt vertaald.
+
+ Indien het bronsegment in één van de aanvullende TM's identiek is aan de tekst die wordt vertaald, gedraagt OmegaT zich zoals gedefinieerd is in het dialoogvenster OptiesBewerken (gedrag).... Bijvoorbeeld (als de standaard is geaccepteerd) zal de vertaling vanuit de aanvullende TM worden geaccepteerd en worden vooraf gegaan door [fuzzy], zodat de vertaler de vertalingen op een later tijdstip kan nakijken en controleren of segmenten die op deze manier zijn getagd, juist zijn vertaald (zie het hoofdstuk Bewerken (gedrag)) .
+
+
+
+
+
+ Vertaalgeheugenssubmap tm/autoprojectbestanden
+ map tm/auto
+ Projectvooraf vertalen
+
+
+
+ Als het vanaf het begin duidelijk is dat de vertalingen in een bepaald TM (of TM's) allemaal juist zijn, kan één van hen in de map tm/auto worden geplaatst en heel veel van de gevallen van bevestiging met [fuzzy] worden voorkomen. Dit zal de brontekst effectief vooraf vertalen : alle segmenten in de brontekst, waarvoor vertalingen kunnen worden gevonden in deze "auto"-TM's, zullen zonder interventie van de gebruiker belanden in de belangrijkste TM van het project.
+
+
+
+
+ Optioneel kunt u OmegaT een aanvullend tmx-bestand laten hebben (OmegaT-opmaak) waar u dat maar wilt, dat alle te vertaalbare segmenten van het project bevat. Zie pseudo-vertaald geheugen hieronder.
+
+ Onthoud dat alle vertaalgeheugens in het geheugen worden geladen bij het openen van het project. Back-ups worden regelmatig van het vertaalgeheugen van het project gemaakt (zie het volgende hoofdstuk) en project_save.tmx wordt ook opgeslagen/bijgewerkt als het project wordt gesloten of opnieuw geladen. Dit betekent bijvoorbeeld dat u het project waarin u momenteel werkt niet behoeft te verlaten als u besluit om er een andere aanvullende TM aan toe te voegen: u kunt eenvoudigweg het project opnieuw laden, en de wijzigingen die u hebt gemaakt zullen daarin worden opgenomen.
+
+ De locaties van de verschillende vertaalgeheugens voor een bepaald project zijn door de gebruiker gedefinieerd (zie dialoogvenster Project in gids Snel starten)
+
+ Afhankelijk van de situatie zijn dus verschillende strategieën mogelijk, bijvoorbeeld:
+
+ diverse projecten over hetzelfde onderwerp: behoud de projectstructuur en wijzig mappen voor bron en doel (Bron = bron/volgorde1, doel = doel/volgorde1 etc). Onthoud dat u segmenten uit volgorde1, die niet aanwezig zijn in volgorde2 en andere opvolgende taken, zullen worden getagd als wezen-segmenten; echter, zij zullen nog steeds handig zijn om overeenkomsten te verkrijgen.
+
+ verschillende vertalers werken aan hetzelfde project: splits de bronbestanden in bron/Alice, bron/Bob... en geef ze uit aan de leden van het team (Alice, Bob ...). Zij kunnen dan hun eigen projecten maken en hun eigen project_save.tmx, inleveren indien voltooid of wanneer een bepaalde mijlpaal is bereikt. De bestanden project_save.tmx worden dan verzameld en mogelijke conflicten met betrekking tot bijvoorbeeld terminologie worden opgelost. Een nieuwe versie van de hoofd-TM wordt dan gemaakt, ofwel om in de submappen tm/auto van de teamleden te worden geplaatst of om hun bestanden project_save.tmx in hun projecten te vervangen. Het team kan ook dezelfde structuur voor de submappen gebruiken voor de doelbestanden. Dit maakt het voor hen bijvoorbeeld mogelijk om op elk moment te controleren, of de doelversie voor het gehele project nog steeds OK is.
+
+
+
+ TMX back-up<indexterm class="singular">
+ <primary>Vertaalgeheugens</primary> <secondary>back-up</secondary>
+ </indexterm>
+
+ Tijdens het vertalen van uw bestanden slaat OmegaT uw werk op in project_save.tmx in de submap /omegat van het project.
+
+ OmegaT maakt ook, elke keer als een project wordt geopend of herladen, een back-up van het vertaalgeheugen in project_save.tmx.JAARMMDDUUMM.bak in dezelfde submap. JAAR is 4-getallen jaar, MM is een maand, DD dag van de maand, UU en MM zijn uren en minuten van wanneer het vorige vertaalgeheugen werd opgeslagen.
+
+ Als u denkt dat u vertaalde gegevens kwijt bent, volg dan de volgende procedure:
+
+
+
+ Sluit het project
+
+
+
+ Hernoem het huidige project_save.tmx-bestand naar iets dat u zult onthouden (zoals bijvoorbeeld project_save.tmx.tijdelijk)
+
+
+
+ Selecteer de back-up van het vertaalgeheugen dat meest waarschijnlijk (bijv. de meest recente of de laatste versie van de dag ervoor) de gegevens bevat die u nodig hebt
+
+
+
+ Kopieer het als project_save.tmx
+
+
+
+ Open het project
+
+
+
+
+
+ TMX-bestanden en taal<indexterm class="singular">
+ <primary>Vertaalgeheugens</primary> <secondary>taal</secondary>
+ </indexterm>
+
+ TMX-bestanden bevatten vertaaleenheden die zijn gemaakt van een aantal equivalente segmenten in verschillende talen. Een vertaaleenheid bestaat uit ten minste twee variaties van een vertaaleenheid (tuv). Beide kunnen als bron of doel worden gebruikt.
+
+ De instellingen in uw project geven aan wat de bron- en wat de doeltaal is. OmegaT neemt dus de tuv-segmenten die overeenkomen met de taalcodes van de bron en het doel in het project en gebruiken ze respectievelijk als de bron- en doelsegmenten. OmegaT herkent de taalcodes met behulp van de twee volgende standaard conventies:
+
+
+
+ 2 letters (bijv. JA voor Japans), of
+
+
+
+ 2- of 3-letter taalcode gevolgd door de 2-letter landcode (bijv. EN-US - Zie voor een gedeeltelijke lijst van taal- en landcodes).
+
+
+
+ Als de taalcodes en de TMX-taalcodes voor het project volledig overeenkomen worden de segmenten in het geheugen geladen. Als de taal overeenkomt, maar niet de landcode worden de segmenten toch geladen. Als de taalcode, noch de landcode overeenkomen zullen de segmenten worden genegeerd.
+
+
+
+ Wezen-segmenten<indexterm class="singular">
+ <primary>Vertaalgeheugens</primary> <secondary>wezen-segmenten</secondary>
+ </indexterm>
+
+ Het bestand project_save.tmx bevat alle segmenten die zijn vertaald sinds u het project startte. Als u de segmentatie van het project aanpast of bestanden uit de bron verwijdert, zullen sommige overeenkomsten in het venster Overeenkomsten kunnen verschijnen als wezen-tekenreeksen: zulke overeenkomsten verwijzen niet langer naar segmenten die voorkomen in de brondocumenten, omdat zij overeenkomen met segmenten die werden vertaald en opgenomen vóór de aanpassingen plaats vonden.
+
+
+
+
+ Vertaalgeheugens opnieuw gebruiken<indexterm class="singular">
+ <primary>Vertaalgeheugens</primary> <secondary>importeren en exporteren</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Vertaalgeheugens</primary> <secondary>vertaalgeheugens opnieuw gebruiken</secondary>
+ </indexterm>
+
+ In het begin, dat is als het project wordt gemaakt, is de hoofd-TM van het project, project_save.tmx, leeg. Deze TM wordt gedurende de vertaling gevuld. Bestaande vertalingen kunnen worden gebruikt om dit proces te versnellen. Indien een bepaalde zin al eens is vertaald, en juist is vertaald, bestaat er geen reden om die opnieuw te gaan vertalen. Vertaalgeheugens kunnen ook vertaalgeheugens als verwijzingen bevatten: meertalige wetgeving, zoals van de Europese Gemeenschap is daarvan een typisch voorbeeld.
+
+ Wanneer u de doeldocumenten maakt in een project van OmegaT, wordt het vertaalgeheugen van het project uitgevoerd in de vorm van drie bestanden in de hoofdmap van uw project van OmegaT (zie de bovenstaande beschrijving). U kunt deze drie TMX-bestanden, (-omegat.tmx", "-level1.tmx" en "-level2.tmx"), beschouwen als een "exporteerbaar vertaalgeheugen", dat is: een export van de inhoud van uw huidige project in tweetalige vorm.
+
+ Indien u een vertaalgeheugen uit een vorig project zou willen gebruiken (bijvoorbeeld omdat het nieuwe project overeenkomt met het eerdere project, of terminologie gebruikt die eerder gebruikt is), kunt u deze vertaalgeheugens gebruiken als "invoer vertaalgeheugens", dat is: om in uw nieuwe project te importeren. In dit geval plaats u de vertaalgeheugens die u wilt gebruiken in de mappen \tm of \tm\auto van uw nieuwe project: in het eerste geval zult u hits van deze vertaalgeheugens in het venster Overeenkomsten krijgen en in het laatste geval zullen deze TM's worden gebruikt om uw brontekst vooraf te vertalen.
+
+ Standaard staat de map \tm onder de hoofdmap van het project (bijvoorbeeld ...\MijnProject\tm), maar u kunt een andere map kiezen in het dialoogvenster Projecteigenschappen als u dat wilt. Dit is handig als u regelmatig eerder gemaakte vertaalgeheugens gebruikt, bijvoorbeeld omdat zij over hetzelfde onderwerp gaan of voor dezelfde klant zijn. In dit geval zou een handige procedure zijn:
+
+
+
+ Maak een map (een "voorraadmap") op een handige locatie op uw harde schijf voor de vertaalgeheugens voor een bepaalde klant of onderwerp.
+
+
+
+
+
+ Elke keer als u een project voltooid, kopieert u één van de drie "exporteerbare" bestanden van vertaalgeheugens vanuit de map van het project naar de voorraadmap.
+
+
+
+
+
+ Als u een nieuw project begint voor hetzelfde onderwerp of voor dezelfde klant, navigeer naar de voorraadmap in het dialoogvenster Project > Eigenschappen > Project bewerken en selecteer het als de map voor het vertaalgeheugen.
+
+
+
+ Onthoud wel dat alle TMX-bestanden in de voorraadmap /tm worden geparset als het project wordt geopend, dus door daarin alle verschillende vertaalgeheugens die u voorhanden hebt te plaatsen, kan OmegaT onnodig langzamer maken. U zou zelfs kunnen overwegen om die, welke u niet meer nodig hebt, te verwijderen, als u eenmaal hun inhoud hebt gebruikt om het bestand project-save.tmx te vullen.
+
+
+ Importeren en exporteren van vertaalgeheugens
+
+ OmegaT ondersteunt geïmporteerde tmx-versies 1.1-1.4b (zowel niveau 1 als niveau 2). Dit maakt het mogelijk dat vertaalgeheugens die zijn gemaakt door andere programma's kunnen worden gelezen door OmegaT. OmegaT ondersteunt echter niet volledig geïmporteerde TMX-bestanden van niveau 2 (die niet alleen de vertaling opslaan, maar ook de opmaak). TMX-bestanden van niveau 2 kunnen nog steeds worden geïmporteerd en hun tekstuele inhoud kan worden bekeken in OmegaT, maar de kwaliteit van de overeenkomsten zal wat lager zijn.
+
+ OmegaT volgt zeer strikte procedures bij het laden van bestanden van vertaalgeheugens (TMX-bestanden). Als een fout in een dergelijk bestand wordt gevonden zal OmegaT de positie aangeven binnen het defecte bestand waarin de fout zich bevindt.
+
+ Sommige programma's staan er om bekend dat zij onder bepaalde omstandigheden ongeldige TMX-bestanden maken. Als u dergelijke bestanden als verwijzingen voor vertalingen in OmegaT wilt gebruiken, moeten zij worden gerepareerd of OmegaT zal een fout rapporteren en het weigeren te laden. Reparaties zijn kleine bewerkingen en OmegaT assisteert bij het oplossen van problemen met het gerelateerde foutbericht. U kunt advies aan de gebruikersgroep vragen als u problemen ondervindt.
+
+ OmegaT exporteert versie 1.4 TMX-bestanden (zowel niveau 1 en niveau 2). De export van niveau 2 komt niet volledig overeen met de standaard van niveau 2 maar is goed genoeg en zal correcte overeenkomsten genereren in andere programma's met vertaalgeheugens die TMX niveau 2 ondersteunen. Als u alleen tekstuele informatie wilt (en geen opmaakinformatie) gebruik dan het bestand van niveau 1 dat OmegaT heeft gemaakt.
+
+
+
+
+ Pseudo-vertaald geheugen<indexterm class="singular">
+ <primary>Vertaalgeheugens</primary> <secondary>pseudo-vertaling</secondary>
+ </indexterm>
+
+
+ Alleen van belang voor gevorderde gebruikers!
+
+
+ Voordat segmenten worden vertaald wilt u ze misschien vooraf verwerken of op een andere manier behandelen dan met OmegaT mogelijk is. Als u bijvoorbeeld een pseudo-vertaling wilt maken om te testen, maakt OmegaT het u mogelijk om een aanvullend TMX-bestand te maken file dat alle segmenten van het project bevat. De vertaling in die tmx kan zijn
+
+
+
+ vertaling komt overeen met bron (standaard)
+
+
+
+
+
+ vertaalde segment is leeg
+
+
+
+ Het TMX-bestand mag elke naam hebben die u op wil geven. Een pseudo-vertaald geheugen kan worden gegenereerd met de volgende parameters voor de opdrachtregel:
+
+ java -jar omegat.jar --pseudotranslatetmx=<bestandsnaam> [pseudotranslatetype=[equal|empty]]
+
+ Vervang <bestandsnaam> door de naam van het bestand dat u wilt maken, ofwel absoluut of relatief naar de werkmap (de map van waaruit u OmegaT start). Het tweede argument --pseudotranslatetype is optioneel. De waarde ervan is ofwel equal (standaard waarde, voor bron=doel) of empty (doelsegment is leeg). U kunt de gemaakte tmx verwerken met elk programma dat u wilt. Hernoem het naar project_save.tmx en plaats het in de map omegat van uw project om het opnieuw in OmegaT te gebruiken.
+
+
+
+ Vertaalgeheugens bijwerken<indexterm class="singular">
+ <primary>Vertaalgeheugens</primary> <secondary>bijwerken naar zinsegmentatie</secondary>
+ </indexterm>
+
+ Hele vroege versies van OmegaT waren slechts in staat bronbestanden in alinea's te segmenteren en nummerden de opmaaktags in HTML- en Open Document-bestanden niet consistent. OmegaT 2.5 kan dergelijke TMX-bestanden herkennen en direct bijwerken om de kwaliteit van de fuzzy overeenkomsten te vergroten en uw vertaling op peil te brengen, zodat u dat werk niet handmatig hoeft te doen.
+
+ De TMX van een project wordt maar één keer bijgewerkt en zal in de bijgewerkte vorm worden weggeschreven in project-save.tmx; eerder gemaakte TMX-bestanden worden, elke keer als het project wordt geladen, direct bijgewerkt. Wees er attent op dat sommige wijzigingen in bestandsfilters in OmegaT 2.5 zouden kunnen leiden tot totaal afwijkende segmentatie; als resultaat daarvan moet u in zulke zeer uitzonderlijke gevallen uw vertaling handmatig bijwerken.
+
+
+
+
+ Bronsegmentatie
+
+ Programma's met vertaalgeheugens werken met teksteenheden die segmenten worden genoemd. OmegaT heeft 2 manieren om een tekst te segmenteren: alineasegmentatie en zinsegmentatie (waarnaar ook wel wordt verwezen als “op regels gebaseerde-segmentatie”). Selecteer
+ Projecteigenschappen
+ Projecteigenschappen... uit het hoofdmenu en selecteer het aanwezig keuzevak, of niet, om het type segmentatie te kiezen. Alinea-segmentatie heeft in bepaalde gevallen voordelen, zoals bij bijzonder creatieve of stilistische vertalingen waarin de vertaler de volgorde van gehele zinnen zou willen wijzigen; voor het merendeel van de projecten is echter zin- segmentatie de keuze die wordt geprefereerd, omdat het betere overeenkomsten oplevert vanuit eerdere vertalingen. Als zinsegmentatie is geselecteerd kunt u de regels instellen door
+ ProjectOpties
+ OptiesSegmentatie...te selecteren uit het hoofdmenu.
+
+ Betrouwbare segmentatieregels zijn al beschikbaar voor veel talen, dus is het onwaarschijnlijk dat het voor u nodig is om uw eigen segmentatieregels te schrijven. Aan de andere kant kan deze functionaliteit in speciale gevallen bijzonder handig zijn, waarbij u uw productiviteit kunt verhogen door de segmentatieregels af te stemmen op de tekst die vertaald moet worden.
+
+ Waarschuwing: omdat de tekst afwijkend zal segmenteren nadat filteropties zijn gewijzigd, zult u misschien geheel opnieuw moeten beginnen met vertalen. Tegelijkertijd zullen de eerder gevalideerde segmenten in het vertaalgeheugen van het project worden omgezet naar wezen-segmenten. Als u de segmentatie-opties wijzigt als een project geopend is moet u het project herladen vóórdat de wijzigingen effect hebben.
+
+ OmegaT gebruikt de volgende reeks stappen:
+
+
+
+
+ Segmentatiesegmentatie op niveau van de bron
+ Segmentatie op niveau van de structuur
+
+
+ OmegaT parst eerst de tekst voor segmentatie op niveau van de structuur. Gedurende dit proces wordt alleen de structuur van het brondocument gebruikt om segmenten te maken.
+
+ Tekstbestanden kunnen bijvoorbeeld gesegmenteerd worden op regeleinden, lege regels of helemaal niet gesegmenteerd worden. Bestanden die opmaak bevatten (OpenOffice.org-documenten, HTML-documenten, etc.) worden gesegmenteerd op het blokniveau (alinea)tags. Vertaalbare object-attributen in XHTML of HTML-bestanden kunnen als afzonderlijke segmenten worden geëxtraheerd.
+
+
+
+
+
+ Segmentatiesegmentatie op niveau van zin
+ Segmentatie op niveau van de zin
+
+
+ Nadat het bronbestand in structurele eenheden is gesegmenteerd, zal OmegaT deze blokken verder segmenteren in zinnen.
+
+
+
+
+
+ Segmentatieregels<indexterm class="singular">
+ <primary>Segmentatie</primary> <secondary>regels</secondary>
+ </indexterm>
+
+ Het proces van segmentering kan als volgt worden voorgesteld: de cursor verplaatst zich langs de tekst, één teken per keer. Voor elke cursorpositie wordt elke regel, bestaande uit een Voor- en Na -patroon, in de opgegeven volgorde toegepast en probeert of een van de Voor-patronen geldig is voor alle tekst die links van de cursor staat en het overeenkomende Na-patroon op de tekst rechts van de cursor. Als de regel overeenkomt gaat de cursor ofwel door zonder een einde voor het segment in te voegen (voor de uitzonderingsregel) of er wordt een nieuw einde voor het segment ingevoegd op de cursorpositie (voor de afbreekregels).
+
+ De twee typen regels gedragen zich als volgt:
+
+
+
+
+ Segmentatieregelsafbreekregel
+ Afbreekregel
+
+
+ Verdeelt de brontekst in segmenten. Voorbeeld: "Begrijpt u dat? Ik was er niet zeker van." zou moeten worden gescheiden in twee segmenten. Wat betekent dat er een afbreekregel zou moeten zijn voor "?", indien die wordt gevolgd door spaties en een woord met een hoofdletter. Selecteer het keuzevak Afbreken/Uitzondering om een regel te definiëren als een Afbreekregel.
+
+
+
+
+
+
+
+ Segmentatieregelsuitzonderingsregel
+ Uitzonderingsregel
+
+
+ specificeer welke gedeelten van de tekst NIET zouden moeten worden gescheiden. Niettegenstaande de punt zou "Mrs. Dalloway " niet moeten worden gesplitst in twee segmenten, dus zou een uitzonderingsregel gemaakt moeten worden voor Mrs (en voor Mr, voor Dr, voor prof etc), gevolgd door een punt. Selecteer NIET het keuzevak Afbreken/Uitzondering om een regel te definiëren als een Uitzonderingsregel.
+
+
+
+
+ De voorgedefinieerde afbreekregels zouden voldoende moeten zijn voor de meeste Europese talen en Japans. Gelet op de flexibiliteit kunt u overwegen om meer uitzonderingsregels te definiëren voor de taal waaruit u vertaald om u meer betekenisvolle en samenhangende segmenten te geven.
+
+
+
+ Prioriteit van regels<indexterm class="singular">
+ <primary>Segmentatie</primary> <secondary>prioriteit van regels</secondary>
+ </indexterm>
+
+ Alle segmentatieregels die zijn ingesteld voor een overeenkomend taalpatroon zijn actief en worden toegepast in de opgegeven volgorde van prioriteit, dus regels voor een specifieke taal zouden hoger moeten staan dan de standaardregels. Regels voor Canadees Frans (FR-CA) zouden bijvoorbeeld hoger moeten staan dan de regels voor Frans (FR.*) en hoger dan de standaardregels (.*). Dus, bij het vertalen vanuit Canadees Frans worden de regels voor Canadees Frans - indien aanwezig - eerst worden toegepast, gevolgd door de regels voor Frans en tenslotte de standaard regels.
+
+
+
+ Een nieuwe regel maken<indexterm class="singular">
+ <primary>Segmentatie</primary> <secondary>een nieuwe regel maken</secondary> <seealso>reguliere uitdrukkingen</seealso>
+ </indexterm>
+
+ Grote wijzigingen aan de segmentatieregels zouden in het algemeen moeten wordne vermeden, speciaal na het voltooien van een eerste gang, maar kleinere wijzigingen, zoals het toevoegen van een herkende afkorting, kan voordelen bieden.
+
+ Klik eenvoudigweg op een verzameling van regels in de bovenste tabel om die te bewerken of uit te breiden. De regels voor die verzameling zullen in het onderste gedeelte van het venster verschijnen.
+
+ Klik op Toevoegen in het bovenste gedeelte van het dialoogvenster, om een lege verzameling van regels te maken voor een nieuw taalpatroon. Een lege regel zal aan de onderzijde van de bovenste tabel verschijnen (u moet misschien naar beneden scrollen om die te zien). Wijzig de naam van de regelverzameling en het taalpatroon naar die van de betrokken taal en de code daarvan (zie voor een lijst van taalcodes). De syntaxis van het taalpatroon komt overeen met de syntaxis voor reguliere uitdrukkingen. Als uw regelverzameling een taal/land-paar betreft raden wij u aan om het naar boven te verplaatsen met de knop Naar boven.
+
+ Voeg de patronen Voor en Na toe. Het wordt aangeraden om programma's te gebruiken die het mogelijk maken de effecten direct te zien om de syntaxis en de toepasbaarheid te controleren. Zie het hoofdstuk over Reguliere uitdrukkingen. Een goed startpunt zullen altijd de bestaande regels zijn.
+
+
+
+ <indexterm class="singular">
+ <primary>Segmentatie</primary> <secondary>voorbeelden</secondary>
+ </indexterm>Een paar eenvoudige voorbeelden
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Bedoeling
+
+ Vóór
+
+ Na
+
+ Opmerking
+
+
+
+
+
+ Stel een segment in na een punt ('.') en vóór een spatie
+
+ \.
+
+ \s
+
+ "\." betekent het teken "." "\s" betekent elk teken voor witruimte ((spatie, tab, nieuw pagina etc.)
+
+
+
+ Niet segmenteren na Mr.
+
+ Mr\.
+
+ \s
+
+ Dit is een uitzonderingsregel, dus het keuzevak voor de regel moet niet zijn geselecteerd
+
+
+
+ Stel een segment in na "。" (Japanse punt)
+
+ 。
+
+
+
+ Let er op dat Na leeg is
+
+
+
+ Niet segmenteren na M. Mr. Mrs. en Ms.
+
+ Mr??s??\.
+
+ \s
+
+ Uitzonderingsregel - zie het gebruik van ? in reguliere uitdrukkingen
+
+
+
+
+
+
+
+
+ Reguliere uitdrukkingen<indexterm class="singular">
+ <primary>Reguliere uitdrukkingen</primary> <seealso>segmentatie</seealso> <seealso>zoeken</seealso>
+ </indexterm>
+
+ De reguliere uitdrukkingen (of afgekort regex) die worden gebruikt in zoekacties en segmentatieregels zijn die welke worden ondersteund door Java. Als u meer specifieke informatie nodig heeft raadpleeg dan documentatie voor Java Regex. Bekijk de aanvullende verwijzingen en voorbeelden hieronder.
+
+
+ Dit hoofdstuk is bedoeld voor gevorderde gebruikers, die hun eigen varianten van segmentatieregels moeten kunnen definiëren of meer complexe en krachtigere zoeksleutels moeten kunnen opdelen.
+
+
+
+ Regex - Vlaggen
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ (?i)
+
+ Schakelt overeenkomen van hoofd-/kleine letters in (standaard is het patroon hoofdletter-gevoelig).
+
+
+
+
+
+
+ Regex - Teken
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ x
+
+ Het teken x, met uitzondering van het volgende...
+
+
+
+ \uhhhh
+
+ Het teken met de hexadecimale waarde 0xhhhh
+
+
+
+ \t
+
+ Het Tab-teken ('\u0009')
+
+
+
+ \n
+
+ Het teken voor een nieuwe regel (line feed) ('\u000A')
+
+
+
+ \r
+
+ Het teken voor een carriage-return ('\u000D')
+
+
+
+ \f
+
+ Het teken voor form-feed ('\u000C')
+
+
+
+ \a
+
+ Het waarschuwingsteken (bel) ('\u0007')
+
+
+
+ \e
+
+ Het escape-teken ('\u001B')
+
+
+
+ \cx
+
+ Het besturingsteken dat overeenkomt met x
+
+
+
+ \0n
+
+ Het teken met de octale waarde 0n (0 <= n <= 7)
+
+
+
+ \0nn
+
+ Het teken met de octale waarde 0nn (0 <= n <= 7)
+
+
+
+ \0mnn
+
+ Het teken met de octale waarde (0 <= m <= 3, 0 <= n <= 7)
+
+
+
+ \xhh
+
+ Het teken met de hexadecimale waarde 0xhh
+
+
+
+
+
+
+ Regex - Aanhalingen
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ \
+
+ Niets, maar quote het volgende teken. Dit is vereist als u een van de metatekens !$()*+.<>?[\]^{|} zou willen invoeren om overeen te komen als hetzelfde teken.
+
+
+
+ \\
+
+ Dit is bijvoorbeeld het teken voor een backslash
+
+
+
+ \Q
+
+ Niets, maar quote alle tekens tot \E
+
+
+
+ \E
+
+ Niets, maar beëindigt quoten dat werd gestart door \Q
+
+
+
+
+
+
+ Regex - Klassen voor Unicode-blokken en categorieën
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ \p{InGreek}
+
+ Een teken in het Griekse blok (eenvoudig blok)
+
+
+
+ \p{Lu}
+
+ Een hoofdletter (eenvoudige categorie)
+
+
+
+ \p{Sc}
+
+ Een valutasymbool
+
+
+
+ \P{InGreek}
+
+ Elk teken met uitzondering van die in het Griekse blok (negatie)
+
+
+
+ [\p{L}&&[^\p{Lu}]]
+
+ Elke letter met uitzondering van hoofdletters (subtractie)
+
+
+
+
+
+
+ Regex - Tekenklassen
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ [abc]
+
+ a, b, of c (eenvoudige klasse)
+
+
+
+ [^abc]
+
+ Elk teken met uitzondering van a, b, of c (negatie)
+
+
+
+ [a-zA-Z]
+
+ a tot en met z of A tot en met Z inclusief (bereik)
+
+
+
+
+
+
+ Regex - Voorgedefinieerde tekenklassen
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ .
+
+ Elk teken (met uitzondering van regeleinden)
+
+
+
+ \d
+
+ Een getal: [0-9]
+
+
+
+ \D
+
+ Geen getal: [^0-9]
+
+
+
+ \s
+
+ Een teken voor witruimte: [ \t\n\x0B\f\r]
+
+
+
+ \S
+
+ Een teken niet zijnde witruimte: [^\s]
+
+
+
+ \w
+
+ Een woordteken: [a-zA-Z_0-9]
+
+
+
+ \W
+
+ Een teken voor geen-woord: [^\w]
+
+
+
+
+
+
+ Regex - Overeenkomsten voor begrenzingen
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ ^
+
+ Het begin van een regel
+
+
+
+ $
+
+ Het einde van een regel
+
+
+
+ \b
+
+ Een woordgrens
+
+
+
+ \B
+
+ Grens voor geen-woord
+
+
+
+
+
+
+ Regex - Gulzige parameters
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ X?
+
+ X, één maal of helemaal niet
+
+
+
+ X*
+
+ X, nul of meer keren
+
+
+
+ X+
+
+ X, één of meer keren
+
+
+
+
+
+
+ Gulzige parameters zullen overeenkomen met zoveel als voor hen mogelijk is. Bijvoorbeeld: a+? zal overeenkomen met de aaa in aaabbb
+
+
+
+ Regex - Weigerachtige (niet-gulzige) parameters
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ X??
+
+ X, één maal of helemaal niet
+
+
+
+ X*?
+
+ X, nul of meer keren
+
+
+
+ X+?
+
+ X, één of meer keren
+
+
+
+
+
+
+ Weigerachtige (niet-gulzige) parameters zullen overeenkomen met zo weinig als voor hen mogelijk is. a+? zal bijvoorbeeld overeen komen met de eerste a in aaabbb
+
+
+
+ Regex - Logische operatoren
+
+
+
+
+
+
+ De constructie...
+
+ ...komt overeen met het volgende
+
+
+
+
+
+ XY
+
+ X gevolgd door Y
+
+
+
+ X|Y
+
+ Of X óf Y
+
+
+
+ (XY)
+
+ XY als een enkele groep
+
+
+
+
+
+
+ <indexterm class="singular">
+ <primary>Reguliere uitdrukkingen</primary> <secondary>programma's</secondary>
+ </indexterm>Regex-programma's en voorbeelden van gebruik<indexterm class="singular">
+ <primary>Reguliere uitdrukkingen</primary> <secondary>voorbeelden van gebruik</secondary>
+ </indexterm>
+
+ Er zijn een aantal interactieve programma's beschikbaar om reguliere uitdrukkingen te ontwikkelen en te testen. Zij volgen in het algemeen allemaal hetzelfde patroon (zie hieronder voor een voorbeeld van de Regular Expression Tester): de reguliere uitdrukking (bovenste item) analyseert de zoektekst (tekstvak in het midden), wat de hits oplevert, weergegeven in het tekstvak met het resultaat.
+
+
+ Regex Tester
+
+
+
+
+
+
+
+
+
+
+
+
+ Zie The Regex Coach voor Windows, Linux, Mac, FreeBSD versies van een zelfstandig programma. Dat is vrijwel identiek aan het bovenstaande voorbeeld.
+
+ Een fijne collectie van handige gevallen van reguliere uitdrukkingen kan worden gevonden in OmegaT zelf (zie Opties > Segmentatie). De volgende lijst bevat uitdrukkingen die u misschien handig vindt bij het doorzoeken van het vertaalgeheugen:
+
+
+ Regex - Voorbeelden van reguliere uitdrukkingen in vertalingen
+
+
+
+
+
+
+ Reguliere uitdrukking
+
+ Vindt het volgende:
+
+
+
+
+
+ (\b\w+\b)\s\1\b
+
+ dubbele woorden
+
+
+
+ [\.,]\s*[\.,]+
+
+ komma of een punt, gevolgd door spaties en weer een andere komma of punt
+
+
+
+ \. \s+$
+
+ extra spaties na de punt aan het einde van de regel
+
+
+
+ \s+a\s+[aeiou]
+
+ Engels: woorden, beginnend met een klinker, zouden moeten worden voorafgegaan door "an", niet "a"
+
+
+
+ \s+an\s+[^aeiou]
+
+ Engels: dezelfde controle als hierboven, maar met betrekking tot medeklinkers ("a", niet "an")
+
+
+
+ \s\s+
+
+ meer dan één spatie
+
+
+
+ \.[A-Z]
+
+ Punt, gevolgd door een hoofdletter - mogelijk ontbreekt er een spatie tussen de punt en het begin van een nieuwe regel?
+
+
+
+
+
+
+
+
+ Zoeken<indexterm class="singular">
+ <primary>Zoeken</primary>
+ </indexterm>
+
+
+ venster Zoeken
+
+
+ venster Tekst zoeken<indexterm class="singular">
+ <primary>venster Zoeken</primary> <secondary>voorbeeld</secondary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+
+ De bovenstaande zoekactie vindt alle doelsegmenten waarin twee of meer witruimten - \s\s+ - voorkomen.
+
+
+
+ Zoeken<indexterm class="singular">
+ <primary>Sneltoetsen</primary> <secondary>Ctrl+F - Zoeken</secondary>
+ </indexterm>
+
+ OmegaT verschaft een groot scala aan zoekfuncties. Open het venster Zoeken met CtrlF en voer het woord of de frase waarnaar u wilt zoeken in het vak "Zoeken naar" in. Als alternatief: selecteer een woord of frase ergens in het bewerkingsveld en druk op CtrlF. Het woord of de frase wordt automatisch ingevoegd in het vak "Zoeken naar". U kunt verschillende vensters Zoeken tegelijkertijd geopend hebben, maar sluit ze als u ze niet langer nodig hebt zodat zij uw bureaublad niet vol zetten.
+
+
+
+ Zoeklocatie
+
+ Zoekacties worden standaard uitgevoerd in zowel de bron- als de doelgedeelten van het project, maar u kunt uw zoekactie beperken tot de bron- of het de doeltekst. U kunt zoeken in
+
+
+
+ alleen het project (standaardinstelling)
+
+
+
+
+
+ zowel het project en in de vertaalgeheugens waarnaar wordt verwezen in /tm/ (kies Zoeken in TM's)
+
+
+
+
+
+ één enkel bestand of een map die een aantal bestanden bevat (kies Bestanden zoeken)
+
+
+
+ Bij het zoeken in bestanden (in tegenstelling tot in vertaalgeheugens) zal OmegaT zich beperken tot de bestanden in de indelingen van bronbestanden. Als consequentie daarvan zal OmegaT, hoewel het in staat is om tmx-bestanden te behandelen, die niet opnemen bij zoekacties met Zoeken in bestanden. Indien u
+ Zoekengevorderde opties
+ Gevorderde opties inschakelt, kunt u de zoekactie combineren met de naam van de auteur van de vertaling en het tijdstip waarop de laatste wijziging is gemaakt.
+
+
+
+
+ Jokertekens gebruiken<indexterm class="singular">
+ <primary>Zoeken</primary> <secondary>Jokertekens gebruiken</secondary>
+ </indexterm>
+
+ In zowel exact zoeken als zoeken naar sleutelwoorden kunnen de jokertekens '*' en '?' worden gebruikt. Zorg ervoor dat de optie reguliere uitdrukkingen niet is geselecteerd om jokertekens te gebruiken, omdat '*' en '?' een speciale betekenis hebben in reguliere uitdrukkingen.
+
+
+
+ '*' komt overeen met nul of meer tekens, vanaf de huidige positie in een opgegeven woord tot het einde ervan. De zoekterm 'run*' zal bijvoorbeeld overeenkomen met 'run', 'runs' en 'running'.
+
+
+
+
+
+ '?' komt overeen met exact één teken. 'run?' zal bijvoorbeeld overeenkomen met 'runs' en 'runn' in het woord 'running'.
+
+
+
+ De overeenkomsten zullen in vet blauw worden weergegeven.
+
+
+
+ Zoeken methodes<indexterm class="singular">
+ <primary>Zoeken</primary> <secondary>methoden</secondary>
+ </indexterm>
+
+ Selecteer de methode met behulp van de optieknoppen. U kunt kiezen uit twee methodes om te zoeken:
+
+
+
+ Exact zoeken
+
+
+ Zoekt naar segmenten die de exacte tekenreeks bevatten die u heeft opgegeven. Exact zoeken zoekt naar een frase, d.i. als er meerdere woorden zijn ingevoerd, zullen zij slechts worden gevonden als zij in exact dezelfde volgorde voorkomen. Zoeken naar geopend bestand zal dus alle entiteiten van de tekenreeks geopend bestand vinden, maar niet bestand geopend of geopend invoerbestand.
+
+
+
+
+ Sleutelwoorden zoeken
+
+
+ Zoekt naar segmenten die alle sleutelwoorden bevatten die u heeft opgegeven, in willekeurige volgorde. Selecteer Sleutelwoorden zoeken om te zoeken naar een willekeurig aantal individuele woorden, in willekeurige volgorde. OmegaT zal een lijst weergeven waarin alle segmenten staan waarin alle gespecificeerde woorden voorkomen. Zoeken met sleutelwoord is hetzelfde als zoekacties "met alle woorden" in een internetzoekmachine zoals Google (logische EN). Zoeken met sleutelwoorden naar geopend bestand zal dus alle entiteiten van de tekenreeks open file vinden, en ook bestand geopend, geopend invoer bestand, bestand kan gevaarlijk zijn als geopend, etc..
+
+
+
+
+ Voor elk van deze twee methoden kunt u de volgende drie opties kiezen:
+
+
+
+ hoofdletter gevoelig: het zoeken zal worden uitgevoerd voor de exact opgegeven tekenreeks, d.i. met hoofdletters wordt rekening gehouden.
+
+
+
+ reguliere uitdrukkingen: de tekenreeks zal worden behandeld als een reguliere uitdrukking. Een zoekactie met reguliere uitdrukkingen is een krachtig middel om te zoeken naar tekenreeksen. Het komt overeen met zoeken met jokertekens, maar is veel meer flexibel. De reguliere uitdrukkingen die worden gebruikt in zoekacties zijn die welke worden ondersteund door Java. Zie verder het hoofdstuk over Reguliere uitdrukkingen.
+
+
+
+ zoeken in TM's: vertaalgeheugens in de map tm worden opgenomen in de zoekactie.
+
+
+
+
+
+ Zoekresultaten weergeven
+
+ Door op de knop Zoeken te drukken na het invoeren van een tekenreeks in het zoekveld zullen alle segmenten in het project, die de gezochte tekenreeks bevatten, worden weergegeven. Omdat OmegaT identieke segmenten behandelt als één entiteit wordt alleen het eerste unieke segment getoond.
+
+ De segmenten worden weergegeven in de volgorde waarin zij in het project voorkomen. Vertaalde segmenten worden weergegeven met de originele tekst boven en de vertaalde tekst eronder, niet-vertaalde segmenten worden alleen als bron weergegeven.
+
+ Klikken op een segment opent het in het venster Bewerken om het aan te kunnen passen. Daarna kunt u teruggaan naar het venster Zoeken en naar het volgende gevonden segment gaan, bijvoorbeeld om het te controleren en, indien nodig, de terminologie aan te passen.
+
+
+
+
+ <indexterm class="singular">
+ <primary>Woordenboeken</primary>
+ </indexterm>Woordenboeken
+
+
+
+
+ Hoe woordenboeken te downloaden en te installeren<indexterm class="singular">
+ <primary>Woordenboeken</primary> <secondary>Downloaden en installeren</secondary>
+ </indexterm>
+
+ Woordenboeken in OmegaT zijn gebaseerd op het StarDict Platform. Doe het volgende om de benodigde bestanden te installeren:
+
+
+
+ Zoek naar de gewenste taalcombinatie -bijvoorbeeld op het
+ FreeDictwoordenboeken
+ StartDict Platform hierboven of op FreeDict
+ Stardictwoordenboeken
+
+
+
+
+
+
+ Download het bestand - het zou een tarball-archief (extensie tar.bz of tar.bz2) moeten zijn.
+
+
+
+
+
+ Gebruik untar (of iets soortgelijks, bijvoorbeeld winrar in Windows) om de inhoud uit te pakken naar de projectmap "Dictionary". Er zouden drie bestanden moeten zijn, met de extensies dz, idx en ifo.
+
+
+
+ Merk op dat u, aanvullend aan de "bron-doel" woordenboeken, via de mogelijkheid van Dictionary, toegang kunt krijgen tot informatie zoals:
+
+
+
+
+ Websterwoordenboeken
+ Webster's Revised Unabridged Dictionary (1913)
+
+
+
+
+
+
+ Longmanwoordenboeken
+ Longman Dictionary of Contemporary English
+
+
+
+
+
+
+ Britannicawoordenboeken
+ The Britannica Concise Encyclopedia
+
+
+
+
+
+ etc...
+
+
+
+ Sommige woordenboeken verplichten tot niets - dat is zijn "Vrij te gebruiken", en sommige, zoals de selectie hierboven, bevinden zich onder de GPLlicentie. Het volgende voorbeeld toont Merriam Webster 10th dictionary "in actie":
+
+
+ <indexterm class="singular">
+ <primary>woordenboek</primary> <secondary>Merriam Webster - afbeelding</secondary> <seealso>woordenboeken</seealso>
+ </indexterm>Merriam Webster woordenboek - gebruiken
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ <indexterm class="singular">
+ <primary>Woordenboeken</primary> <secondary>problemen met</secondary>
+ </indexterm>Problemen met woordenboeken
+
+
+
+ Controleer of uw bestanden van het woordenboek in de juiste map (of in één van de submappen daarvan) staan. Controleer in
+ SneltoetsenCtrl+E - Projecteigenschappen
+ CtrlEProjecteigenschappen.
+
+
+
+
+
+ Bevat de map drie bestanden met dezelfde naam, met extensies? Indien er slechts één bestand aanwezig is, controleer dan de extensie er van. Als het tar.bz is, dan bent u vergeten het uit te pakken (untar).
+
+
+
+
+
+
+ Woordenlijsten<indexterm class="singular">
+ <primary>Vensters in OmegaT</primary> <secondary>venster Woordenlijst</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>Woordenlijsten</primary>
+ </indexterm>
+
+ Woordenlijsten zijn bestanden die handmatig gemaakt en bijgewerkt worden voor gebruik in OmegaT.
+
+ Als een project in OmegaT één of meer woordenlijsten bevat, worden termen uit de woordenlijst die ook worden gevonden in het huidige segment automatisch weergegeven in het venster Woordenlijst.
+
+ U definieert de locatie ervan in het dialoogvenster Projecteigenschappen. De extensie moet .txt zijn (indien niet zal die worden toegevoegd). De locatie van het bestand moet liggen binnen de map /glossary , maar het mag in een diepere map staan (bijv. glossary/sub/glossary.txt). Het bestand hoeft niet te bestaan als het wordt ingesteld, het zal worden gemaakt (indien nodig) bij het toevoegen van een item voor de woordenlijst. Als het bestand al bestaat, wordt er geen poging gedaan om de indeling of de tekenset van het bestand te verifiëren: de nieuwe items zullen altijd in de indeling tab-gescheiden en UTF-8 zijn. Omdat de bestaande inhoud niet wordt geraakt, zal schade aan een bestaand bestand beperkt zijn.
+
+
+ Gebruik
+
+ Plaats een bestaande woordenlijst eenvoudigweg in de map
+ Projectbestandensubmap Glossary
+ /glossary, na het maken van het project, om die te gebruiken. OmegaT detecteert automatisch woordenlijstbestanden in deze map als een project wordt geopend. Termen in het huidige segment die OmegaT vindt in het/de woordenlijstbestand(en) worden weergegeven in het venster Woordenlijst:
+
+
+ venster Woordenlijst
+
+
+
+ venster Woordenlijst
+
+
+
+
+
+
+
+
+
+
+
+
+ Het woord voor het =-teken is de bronterm en de vertaling is (of zijn) de woorden na =. Het woordenlijst-item kan een opmerking toegevoegd hebben (zie "bedrijvend werkwoord" voor het tweede item). De functie woordenlijst vindt alleen exacte overeenkomsten met het woordenlijst-item (bijv. vindt geen afgeleide vormen etc.). Nieuwe termen kunnen handmatig aan de woordenlijstbestanden worden toegevoegd tijdens het vertalen (bijvoorbeeld in een tekstverwerkingsprogramma), maar nieuw toegevoegde termen worden niet herkend totdat het project opnieuw wordt geladen.
+
+ De bronterm behoeft geen item met één woord te zijn, zoals het volgende voorbeeld laat zien:
+
+
+ items met meerdere woorden in woordenlijsten - voorbeeld<indexterm class="singular">
+ <primary>venster Woordenlijst - items met meerdere woorden</primary>
+ </indexterm>
+
+
+
+
+
+
+
+
+
+
+
+
+ Het onderstreepte item "pop-upmenu" kan worden gevonden in het venster Woordenlijst als "pojavni menu". Door het te accentueren in het venster Woordenlijst en er dan met rechts op te klikken voegt het in op de cursorpositie in het doelsegment.
+ Onthoud dat in het bovenstaande geval, dit slechts het halve verhaal (of zelfs nog minder is) is, omdat de doeltaal (Sloveens) verbuigingen gebruikt. Het ingevoegde "pojavni meni" moet dus worden gewijzigd naar "pojavcnem meniju". Met andere woorden: het typen van de juiste term, zonder te accentueren en met rechts te klikken, is waarschijnlijk sneller.
+
+
+
+
+ <indexterm class="singular">
+ <primary>Woordenlijsten</primary> <secondary>bestandsformaat</secondary>
+ </indexterm>Bestandsformaat<indexterm class="singular">
+ <primary>Projectbestanden</primary> <secondary>gebruikersbestanden</secondary> <seealso>woordenlijsten</seealso>
+ </indexterm>
+
+ Woordenlijstbestanden zijn eenvoudige platte tekst-bestanden die drie-kolommen, tabgescheiden lijsten bevatten met de bron- en doeltermen in respectievelijk de eerste en tweede kolom. De derde kolom kan worden gebruikt voor aanvullende informatie. Woordenlijstbestanden kunnen of in de standaard systeemcodering (en aangegeven door de extensie .tab) zijn of in UTF-8 (de extensie .utf8). De codering Unicode (UTF8) wordt om voor de hand liggende redenen geprefereerd.
+
+ Ook het CSV-formaat wordt ondersteund. Dit formaat is hetzelfde als de tabgescheiden: bronterm, doelterm. Velden met opmerkingen worden gescheiden door een komma ','. Tekenreeksen kunnen worden omsloten door aanhalingstekens ", die het mogelijk maken een komma binnen een tekenreeks te hebben:
+
+ "This is a source term, which contains a comma","Dit is een bronterm, die een komma bevat"
+
+ In aanvulling op het platte tekst-formaat, wordt TBX-formaat
+ WoordenlijstenTBX-formaat
+ ook ondersteund. TBX - Term Base eXchange - is de open, op XML gebaseerde standaard voor de uitwisseling van gestructureerde terminologische gegevens. TBX is goedgekeurd als een internationale standaard door LISA
+ LISA-bestandsformaat
+ en ISO. Als u een bestaand systeem hebt voor de afhandeling van terminologie - MultiTerm bijvoorbeeld - is het zeer wel mogelijk dat het de mogelijkheid biedt om gegevens van terminologie in TBX-formaat te exporteren. Microsoft Terminology Collection
+ WoordenlijstenMicrosoft Terminology collectie
+ kan worden gedownload in bijna 100 talen en kan dienen als hoeksteen IT-woordenlijst.
+
+
+
+ Hoe zijn woordenlijsten te maken<indexterm class="singular">
+ <primary>Woordenlijsten</primary> <secondary>een woordenlijst maken</secondary>
+ </indexterm>
+
+ De projectinstellingen maken het mogelijk een naam in te voeren voor een te beschrijven woordenlijstbestand (zie het begin van dit hoofdstuk). Toevoegen van nieuwe items wordt gedaan met behulp van de sneltoets voor het toetsenbord Ctrl+Shift+G. Een dialoogvenster opent en maakt het u mogelijk maken een bronterm, doelterm en opmerkingen die u zou kunnen hebben in te voeren:
+
+
+
+
+
+
+
+
+
+
+
+ De inhoud van bestanden met woordenlijsten worden in het geheugen bewaard en geladen als het project wordt geopend of opnieuw geladen. Bijwerken van een woordenlijstbestand is dus vrij eenvoudig: druk op Ctrl+Shift+G en voer de nieuwe term in, de vertaling ervan en opmerkingen die u zou kunnen hebben (zorg er voor dat u op 'tab' drukt tussen de velden) en sla het bestand op. De inhoud van het venster Woordenlijst zal overeenkomstig worden bijgewerkt.
+
+ Opmerking: Natuurlijk zijn er andere wegen en manieren om een eenvoudig bestand met tabgescheiden items te maken, en zij zijn allemaal eenvoudiger, en veel er van een heel stuk eenvoudiger dan bovenstaande suggestie. Men kan bijvoorbeeld de inhoud hierboven exporteren als een CSV, in plaats van als een UTF8-tekstbestand. Er is niets tegen het gebruiken van Notepad++ op Windows of GEdit op Linux bijvoorbeeld: elke tekstverwerker die UTF8 kan afhandelen en witruimte weer kan geven (zodat de vereiste TAB-tekens u niet ontgaan) kan worden gebruikt.
+
+
+
+ <indexterm class="singular">
+ <primary>Woordenlijsten</primary> <secondary>Trados MultiTerm</secondary>
+ </indexterm>Gebruik van Trados Multiterm
+
+ Woordenlijsten die zijn geëxporteerd vanuit Trados Multiterm kunnen zonder verdere aanpassingen worden gebruikt als woordenlijsten voor OmegaT, vooropgesteld dat zij de bestandsextensie .tab hebben gekregen en de velden voor bron- en doelterm respectievelijk de eerste twee velden zijn. Indien u exporteert met behulp van de systeemoptie "Tabgescheiden exporteren", moet u de eerste 5 kolommen verwijderen (Seq. Nr, Date created etc). De nieuwere versies van MultiTerm ondersteunen het exporteren naar TBX-formaat.
+
+
+
+ <indexterm class="singular">
+ <primary>Woordenlijsten</primary> <secondary>problemen met woordenlijsten</secondary>
+ </indexterm>Algemene problemen met woordenlijsten
+
+ Probleem: Er worden geen items van de woordenlijst weergegeven - mogelijke oorzaken:
+
+
+
+ Geen bestand met woordenlijst gevonden in de map "glossary".
+
+
+
+
+
+ Het bestand met de woordenlijst is leeg.
+
+
+
+
+
+ De items worden niet gescheiden door een TAB-teken.
+
+
+
+
+
+ Het bestand met de woordenlijst heeft niet de juiste extensie (.tab of .utf8).
+
+
+
+
+
+ Er bestaat geen EXACTE overeenkomst tussen het item in de woordenlijst en de brontekst in uw document - bijvoorbeeld als het item meervoud is.
+
+
+
+
+
+ Het bestand met de woordenlijst heeft niet de juiste codering.
+
+
+
+
+
+ Er staan in het huidige segment geen termen die overeenkomen met enige term in de woordenlijst.
+
+
+
+
+
+ Eén of meer van bovenstaande problemen kan zijn gerepareerd, maar het project werd nog niet herladen.
+
+
+
+ Probleem: In het venster Woordenlijst worden sommige tekens niet juist weergegeven
+
+
+
+ ...maar dezelfde tekens worden wel goed weergegeven in het venster Bewerken: de extensie en de codering van het bestand komen niet overeen.
+
+
+
+
+
+
+ Machinevertaling<indexterm class="singular">
+ <primary>Machinevertaling</primary>
+ </indexterm>
+
+
+ Introductie<indexterm class="singular">
+ <primary>Machinevertaling</primary> <secondary>introductie</secondary>
+ </indexterm>
+
+ Tegengesteld aan de door de gebruiker gegenereerde vertaalgeheugens (zoals in het geval van OmegaT) gebruiken programma's voor machinevertaling (MT) op regels gebaseerde linguïstische programma's om een vertaling van de bron te maken zonder dat een vertaalgeheugen nodig is. Statistische leertechnieken, gebaseerd op bron- en doelteksten, worden gebruikt om een vertaalmodel te bouwen. Services voor machinevertalingen hebben goed en steeds betere resultaten behaald in research evaluaties.
+
+ Ga naar Opties > Machinevertaling... en activeer de gewenste service om een van de services voor machinevertaling te activeren. Onthoud dat zij allemaal op het web gebaseerd zijn: u zult online moeten zijn als u ze wilt gebruiken.
+
+
+
+ Google Translate<indexterm class="singular">
+ <primary>Machinevertaling</primary> <secondary>Google Translate</secondary>
+ </indexterm>
+
+ Google Translate is een service waarvoor betaald moet worden en die wordt aangeboden door Google, voor het vertalen van zinnen, websites en complete teksten tussen een nof steeds groeiend aantal talen. Op het moment van schrijven bevat de lijst meer dan 50 talen, van Albanees tot Jiddisch, inclusief natuurlijk alle grote talen. De huidige versie van de service is, op het moment van schrijven, gebaseerd op het gebruiken ervan, met een prijs van 20 USD per miljoen tekens.
+
+ Belangrijk: Google Translate API v2 vereist rekeninggegevens voor alle accounts vóórdat u de service kunt gebruiken (zie Pricing and Terms of Service voor meer informatie). U gebruikt uw eigen private unieke sleutel, die door Google aan u is verzonden toen u zich registreerde bij de service, om uzelf te identificeren als een geldige gebruiker voor de services van Google. Bekijk hoofdstuk Installeren en uitvoeren van OmegaT, gedeelte OmegaT starten vanaf de opdrachtregel, voor details om deze sleutel aan de omgeving van OmegaT toe te voegen.
+
+ De kwaliteit van de vertaling is aan de ene kant afhankelijk van het reservoir aan teksten in de doeltaal en de beschikbaarheid van hun meertalige versies, aan de andere kant ook van de kwaliteit van de gebouwde modellen. Het is haast wel zeker dat, hoewel de kwaliteit in sommige gevallen onvoldoende kan zijn, het uiteindelijk mettertijd beter zal worden en niet slechter.
+
+
+
+ <application>OmegaT</application>-gebruikers en Google Translate
+
+ De gebruiker van OmegaT is niet gedwongen om Google Translate te gebruiken. Indien het wordt gebruikt zal de beslissing van de gebruiker om de vertaling te accepteren, noch de uiteindelijke vertaling beschikbaar worden gemaakt voor Google. Het volgende venster geeft een voorbeeld weer van a) de Engelse bron b) Spaanse en c) Sloveense vertaling in Google Translate.
+
+
+ Google Translate - voorbeeld
+
+
+
+
+
+
+
+
+
+
+
+
+ De Spaanse vertaling is beter dan de Sloveense. Merk op dat interesar en navegar in het Spaans correct zijn vertaald als respectievelijk de werkwoorden interest en sail. In de Sloveense versie worden beide woorden vertaald als zelfstandige naamwoorden. Het is eigenlijk zeer waarschijnlijk dat de Spaanse vertaling, ten minste gedeeltelijk, is gebaseerd op de actuele vertaling van het boek.
+
+ Vanaf het moment dat de service is geactiveerd zal er een suggestie voor de vertaling verschijnen in het venster Machinevertaling voor elk nieuw bronsegment dat wordt geopend. Indien u de suggestie acceptabel vindt, druk op
+ SneltoetsenCtrl+M - Machinevertaling
+ CtrlM om het doelgedeelte van het geopende segment te vervangen. In het segment hierboven, bijvoorbeeld, zou CtrlM de Spaanse versie overschrijven met de Sloveense suggestie.
+
+ Indien u niet wilt dat OmegaT uw bronsegmenten verstuurt naar Google om te worden vertaald, verwijdert u het vinkje vóór het menuitem Google Translate in Opties.
+
+ Onthoud dat er niets anders dan het bronsegment wordt verzonden naar de service van de machinevertaling. De online versie van Google Translate maakt het de gebruiker mogelijk om de suggestie te corrigeren en het gecorrigeerde segment in te sturen. Deze mogelijkheid is echter niet geïmplementeerd in OmegaT.
+
+
+
+ Belazar<indexterm class="singular">
+ <primary>Machinevertaling</primary> <secondary>Belazar</secondary>
+ </indexterm>
+
+ Belazar is een programma voor machinevertaling voor een Russisch - Wit-Russisch taalpaar.
+
+
+
+ Apertium<indexterm class="singular">
+ <primary>Machinevertaling</primary> <secondary>Apertium</secondary>
+ </indexterm>
+
+ Apertium is een gratis/open-bron platform voor machinevertaling, initieel gericht op gerelateerde taalparen, zoals CA, ES, GA, PT, OC en FR maar recent uitgebreid om ook minder gangbare taalparen (zoals Engels-Catalaans) te behandelen. Controleer op de website voor de laatste lijst van geïmplementeerde taalparen.
+
+ Het platform levert
+
+
+
+ een taal-onafhankelijk programma voor machinevertaling
+
+
+
+ om de linguïstische gegevens te beheren die nodig zijn om een systeem voor machinevertaling te bouwen voor een bepaald taalpaar en
+
+
+
+
+
+ linguïstische gegevens voor een groeiend aantal taalparen
+
+
+
+ Apertium gebruikt een oppervlakkig overdrachtprogramma voor machinevertaling die de invoer in gedeelten verwerkt, zoals in een lopende band: opmaak verwijderen, morfologische analyses, doorverwijzen van spraakgedeelten, oppervlakkige structurele overdracht, lexicografische overdracht, morfologische generatie, en opnieuw opmaken.
+
+ Het is mogelijk om Apertium te gebruiken om systemen voor machinevertalingen te bouwen voor een variëteit aan taalparen; voor dat doel gebruikt Apertium eenvoudige op XML gebaseerde standaard formaten om de benodigde linguïstische gegevens te coderen (ofwel met de hand of door het converteren van bestaande gegevens), die zijn gecompileerd met behulp van de verschafte programma's in de formaten voor hoge snelheid zoals die gebruikt worden door het programma.
+
+
+
+ Machinevertaling - probleemoplossing<indexterm class="singular">
+ <primary>Machinevertaling</primary> <secondary>Probleemoplossing</secondary>
+ </indexterm>
+
+ Indien er niets verschijnt in het venster Machinevertaling, controleer dan het volgende:
+
+
+
+ Bent u online? U moet online zijn om een programma voor machinevertaling te kunnen gebruiken.
+
+
+
+
+
+ Wat is het taalpaar dat u nodig hebt? Controleer of de geselecteerde service het aanbiedt.
+
+
+
+ Google Translate werkt niet: controleer Opties > Machinevertaling: de service Google Translate is gelabeld Google Translate V2. De oudere versie van de service, gelabeld "Google Translate" en beschikbaar in verouderde versies van OmegaT, is vervallen en werkt niet meer.
+
+
+
+ "Google Translate gaf HTTP antwoordcode: 403 terug ...": controleer of de sleutel van 38 tekens, ingevoerd in het bestand pinfo.list, juist is. Controleer of de service Translate API geactiveerd is.
+
+
+
+
+
+
+ Spellingscontrole<indexterm class="singular">
+ <primary>Spellingscontrole</primary>
+ </indexterm>
+
+ OmegaT heeft een ingebouwde spellingscontrole die is gebaseerd op de spellingscontrole die wordt gebruikt in OpenOffice.org, Firefox en Thunderbird. Als consequentie daarvan is het in staat om het grote aantal gratis woordenboeken voor spelling te gebruiken die beschikbaar is voor die toepassingen.
+
+
+ Installeren van woordenboeken voor spelling
+
+ Voordat de functie Spellingscontrole kan worden gebruikt moet een geschikt woordenboek of woordenboeken (voor uw doeltaal) zijn geïnstalleerd. Volg deze procedure om woordenboeken te installeren:
+
+
+
+ Maak, in uw bestandsbeheerder, een nieuwe map op een geschikte locatie waarin uw woordenboeken voor de spelling kunnen worden opgeslagen.
+
+
+
+
+
+ Selecteer, in OmegaT,
+ menu Optiesspellingscontrole...
+ Opties > Spellingscontrole, en klik dan op Kiezen naast het veld map Woordenboek-bestand. Navigeer naar en selecteer de map die u hebt gemaakt voor de woordenboeken.
+
+
+
+
+
+ Plaats de bestanden voor de woordenboeken die u wilt gebruiken in deze map. Er bestaan in essentie twee manieren waarop u dit kunt doen. U kunt ofwel de bestanden handmatig kopiëren, d.i. van elders op uw systeem, met behulp van uw bestandsbeheerder; of u kunt de functie "Installeren" van OmegaT gebruiken om een lijst te verschaffen met beschikbare woordenboeken, waaruit kan worden gekozen. Onthoud dat de functie "Installeren" een internetverbinding nodig heeft. De geselecteerde talen zullen dan worden geïnstalleerd en verschijnen uiteindelijk in het venster Instellen spellingscontrole (dit kan even duren).
+
+
+
+ Handmatig kopiëren van de bestanden is handig als u al geschikte bestanden voor de woordenboeken op uw systeem heeft staan, bijvoorbeeld als deel van uw installatie van OpenOffice.org of Thunderbird. De bestanden die u nodig heeft hebben de extensies .aff en .dic, en u hebt beide bestanden nodig om het betrokken woordenboek te kunnen laten werken. U kunt die bestandsextensies gebruiken om op uw computer te zoeken naar geschikte woordenboeken. In het geval hieronder is geen extra map gemaakt en was het kopiëren van bestanden niet nodig, omdat in plaats daarvan de map van het woordenboek van OpenOffice.org is gebruikt:
+
+
+ Opties voor spellingscontrole
+
+
+
+
+
+
+
+
+ Onthoud dat u in het geval hierboven de woordenboeken voor de spelling kunt verliezen als de installatie van OpenOffice.org van uw systeem wordt verwijderd. Maken van uw eigen map en het kopiëren van de bestanden kan wat extra werk betekenen, maar het is misschien de moeite waard.
+
+ Meer recente woordenboeken voor de spelling van OpenOffice.org worden geleverd als "OpenOffice.org extensies", met de bestandsnaamextensie .oxt. Dit zijn echter ziparchieven: indien u het bestand hernoemt met de extensie .zip, kunt u de inhoud extraheren in een zip-programma, en u zult de .aff- en .dic-bestanden vinden die u nodig hebt, die u dan kunt plaatsen in de map die u ervoor hebt gemaakt.
+
+ Onthoud alstublieft dat de toepassing achter de knop "Installeren" afhankelijk is van de lijst met woordenboeken op het internet. Indien die gedateerd is of de gewenste taal niet beschikbaar is zult u zelf moeten zoeken naar de toepasselijke woordenboeken. OpenOffice.org bevat waarschijnlijk de grootste collectie woordenboeken op de site OpenOffice.org Extensions. Nadat de extensie met het woordenboek is gedownload en geïnstalleerd, zullen de corresponderende aff en dic beschikbaar komen. Hetzelfde kan worden bereikt door een extensie voor spellingscontrole toe te voegen aan Firefox of Thunderbird; in dit geval zullen de bestanden van de spellingscontrole worden opgeslagen in uw profiel (Firefox of Thunderbird).
+
+ Zorg er voor dat de taalcode van de doelbestanden correspondeert met de taalcode van het woordenboek: een FR-FR woordenboek zal niet werken met de instelling FR voor het doel. U zult de instelling naar FR-FR moeten wijzigen om de spellingscontrole het juiste woordenboek voor uw doel te laten herkennen. Zoek naar bestanden met de naam, verwijzend naar de gebruikte taal en die de extensies aff en dic. hebben.
+
+
+
+ Woordenboeken voor spelling gebruiken
+
+ Het is niet nodig om OmegaT te instrueren om een bepaald woordenboek voor de spellingscontrole te gebruiken; OmegaT zal het juiste taalwoordenboek gebruiken gebaseerd op de taalcodes van uw project. Controleer echter dat de taalcodes exact hetzelfde zijn: een FR-FR woordenboek zal bijvoorbeeld niet werken met de instelling FR voor het doel. Bewerk, indien nodig, de bestandsnamen van het woordenboek of wijzig de taalinstellingen van uw project.
+
+ Selecteer Opties > Spellingscontrole en selecteer het keuzevak Automatische spellingscontrole (zie boven) om de spellingscontrole in te schakelen.
+
+
+ <indexterm class="singular">
+ <primary>Spellingscontrole</primary> <secondary>Spellingscontrole - afbeelding</secondary>
+ </indexterm>Spellingscontrole in actie
+
+
+
+
+
+
+
+
+
+
+
+
+ Klikken met rechts op een onderstreept woord (distriberen in de afbeelding hierboven) opent een menu met keuzelijst met suggesties voor de correctie (distribueren). U kunt de spellingscontrole instrueren om, alle keren dat het woord verkeerd gespeld voorkomt, alles te negeren of het aan het woordenboek toe te voegen.
+
+
+
+ Hints<indexterm class="singular">
+ <primary>Spellingscontrole</primary> <secondary>hints</secondary>
+ </indexterm>
+
+ Als de spellingscontrole niet werkt, zorg er dan eerst voor dat het keuzevak "Automatische spellingscontrole" in het dialoogvenster van de spellingscontrole (Opties > Spellingscontrole...) is geslecteerd.
+
+ Controleer de taalcode van uw doel met de beschikbare woordenboeken in het venster Instellen spellingscontrole. De spellingscontrole bepaalt de taal die het moet gebruiken uit de taalcode van het doel: als de taalcode voor het doel Braziliaans Portugees (PT_BR) is, moet de submap met woordenboeken de twee bestanden voor het woordenboek, genaamd pt_br.aff en pt_br.dic, bevatten.
+
+ In het geval dat u al een groot gedeelte van de tekst heeft vertaald, maar zich dan realiseert dat de taalcode van het project niet overeenkomt met de taalcode van de spellingscontrole (u specificeerde pt_BR als de taal, maar er zijn geen pt_BR-woordenboeken) kunt u eenvoudigweg de twee corresponderende bestanden kopiëren en die hernoemen (bijvoorbeeld van pt_PT.arr en pt_PT.dic naar pt._BR.arr en pt_BR.dic). Natuurlijk is het veel verstandiger om een korte pauze te nemen en de juiste versies van de spellingscontrole te downloaden.
+
+ Merk op dat Verwijderen de geselecteerde woordenboeken fysiek verwijdert. Als zij, zoals in het bovenstaande geval, deel uitmaken van OpenOffice.org zullen zij ook uit die toepassing verdwijnen. Indien u dat, om welke reden dan ook, zo nu en dan moet doen, kan het daarom verstandiger zijn om de betrokken bestanden te kopiëren naar een andere map, alleen gereserveerd voor gebruik door OmegaT.
+
+
+
+
+ Diverse onderwerpen<indexterm class="singular">
+ <primary>Diversen</primary>
+ </indexterm>
+
+
+ <application><indexterm class="singular">
+ <primary>OmegaT modus console</primary> <seealso>diversen</seealso>
+ </indexterm>OmegaT</application> modus Console<indexterm class="singular">
+ <primary>Diversen</primary> <secondary>OmegaT modus console</secondary>
+ </indexterm>
+
+
+ Alleen van belang voor gevorderde gebruikers!
+
+
+ Het doel van de modus console (d.i. de opdrachtregel) is om het gebruiken van OmegaT als vertaalprogramma in een scriptomgeving mogelijk te maken. Indien gestart in de modus console, wordt geen GUI geladen (het zal daarom op elke console werken) en het opgegeven project wordt automatisch vertaald. Een voorbeeld zou een softwareproject zijn, waarvan de GUI is gelocaliseerd in een aantal talen. Door gebruik te maken van de modus console kan men het maken van een gelocaliseerde interface deel van het bouwproces laten zijn.
+
+
+ Vooraf vereist
+
+ Een geldig project in OmegaT moet aanwezig zijn om OmegaT uit te kunnen voeren. De locatie maakt niet uit omdat het bij de start toch al moet worden ingevuld in de opdrachtregel.
+
+ Indien u geen standaard instellingen wilt gebruiken, moeten de configuratiebestanden (filters.conf en segmentation.conf) aanwezig zijn. Dat kan op twee manieren worden bereikt:
+
+
+
+ Voer OmegaT normaal uit (met de GUI) en maak de instellingen. Indien u OmegaT in console-modus start, zal het de instellingen gebruiken die u hebt geconfigureerd.
+
+
+
+ Indien u OmegaT niet normaal kunt uitvoeren (geen grafische omgeving beschikbaar): kopieer de instellingen vanaf een andere installatie van OmegaT op een andere machine naar een bepaalde map. De locatie maakt niet uit, omdat u die toch in kunt vullen in de opdrachtregel bij het starten (zie hieronder). De relevante bestanden zijn filters.conf en segmentation.conf en kunnen worden gevonden in de startmap van de gebruiker (Bijv. C:\Documents and Settings\%User%\OmegaT onder Windows, %user%/.omegat/ onder Linux)
+
+
+
+
+
+ OmegaT opstarten in modus console
+
+ Enkele extra parameters moeten bij het starten worden opgegeven om OmegaT in modus console te starten. De meest belangrijke is <project-dir>, en optioneel --config-dir=<config-dir>. Voorbeeld:
+
+ $>java -jar OmegaT.jar /pad/naar/project \
+
+ --config-dir=/pad/naar/config-bestanden/ \
+
+ --mode=console-translate \
+
+ --source-pattern={reguliere uitdrukking}
+
+ Uitleg:
+
+
+
+ <project-dir> vertelt OmegaT waar het project kan worden gevonden dat moet worden vertaald. Indien opgegeven start OmegaT in de modus console en zal het opgegeven project gaan vertalen.
+
+
+
+
+
+ --config-dir=<config-dir> maakt het mogelijk OmegaT te instrueren in welke map de configuratiebestanden zijn opgeslagen. Indien niet opgegeven gaat OmegaT terug naar de standaard waarden (de map OmegaT onder de startmap van de gebruiker, of indien niet beschikbaar: de huidige werkmap).
+
+
+
+
+
+ --mode=console-translate OmegaT start in de modus console en vertaalt het opgegeven project
+
+
+
+ --source-pattern={reguliere uitdrukking} De bestanden die moeten worden vertaald kunnen op deze manier worden gespecificeerd. Hier is een voorbeeld van de reguliere uitdrukking: test\.html
+
+
+
+
+
+ optie Quiet
+
+ Een extra parameter voor de opdrachtregel, specifiek voor de console-modus: --quiet.In de modus quiet, wordt er minder informatie gelogd op het scherm. De berichten die u normaal gesproken zou vinden in de statusbalk worden niet weergegeven.
+
+ Gebruik: java -jar OmegaT.jar /pad/naar/project --mode=console-translate --quiet
+
+
+
+ Optie Tags valideren
+
+ Een andere parameter voor de opdrachtregel, specifiek voor de console-modus: --tag-validation=[abort|warn]. Als deze parameter wordt toegevoegd, wordt het valideren van tags toegepast voorafgaande aan vertalen/uitlijnen. Als de waarde abort is dan worden bij tagfouten de fouten afgedrukt en het programma stopt. Als de waarde warn is dan worden fouten afgedrukt maar OmegaT gaat door.
+
+ Gebruik: java -jar OmegaT.jar /pad/naar/project --mode=console-translate --tag-validation=abort
+
+
+
+
+ Automatisch vergelijken van Java-eigenschappen<indexterm class="singular">
+ <primary>Diversen</primary> <secondary>Automatisch vergelijken van Java-eigenschappen</secondary> <seealso>diversen</seealso>
+ </indexterm>
+
+ OmegaT kan Java .properties vergelijken in modus console. Indien u de Properties-bestanden voor bron en doel voor één en dezelfde inhoud in uw taalpaar hebt, zal deze procedure een overeenkomend tmx-bestand maken voor deze inhoud. Gebruik:
+
+ java -jar OmegaT.jar --mode=console-align /my-project-dir
+ --alignDir=/translatedFiles/
+
+ alignDir moet een vertaling bevatten in de doeltaal van het project. (bijvoorbeeld: als het project EN->FR is, moet alignDir een bundle bevatten die eindigt op _fr). De resulterende TMX wordt opgeslagen in de map omegat onder de naam align.tmx.
+
+
+
+ Lettertype-instellingen<indexterm class="singular">
+ <primary>Diversen</primary> <secondary>Lettertype-instellingen</secondary>
+ </indexterm>
+
+ In dit dialoogvenster kan het lettertype worden gedefinieerd dat door OmegaT in de volgende vensters wordt gebruikt:
+
+
+
+ OmegaT hoofdvenster (Bewerken, venster Overeenkomsten, venster Woordenlijst)
+
+
+
+
+
+ venster Zoeken
+
+
+
+
+
+ venster Tags valideren
+
+
+
+ Het dialoogvenster kan worden aangeroepen door het item in het hoofdmenu
+ menu OptiesLettertype...
+ OptiesLettertype.... Het dialoogvenster bevat:
+
+
+
+ Lettertype: keuzelijst om één van de beschikbare lettertypen op uw machine te selecteren
+
+
+
+
+
+ Grootte: bewerken om de grootte van het lettertype te wijzigen
+
+
+
+
+
+ Voorbeeldtekst: veld voor direct voorbeeld van het geselecteerde lettertype
+
+
+
+ Opmerking: In sommige gevallen kan het behoorlijk wat tijd vergen voordat OmegaT de weergave heeft bijgewerkt nadat de lettertype-instelling werd gewijzigd. In het bijzonder wanneer een groot bestand met veel segmenten in de bewerker is geopend en/of trage hardware wordt gebruikt. Merk ook op dat sommige lettertypen zich beter lenen voor bepaalde taalparen dan andere. In het bijzonder, als u vertaalt tussen twee talen met verschillende alfabet/schrijfsystemen (zoals Russisch en Japans), selecteer een lettertype dat voor beide gebruikt kan worden.
+
+
+
+ Gegevensverlies voorkomen<indexterm class="singular">
+ <primary>Diversen</primary> <secondary>Gegevensverlies voorkomen</secondary>
+ </indexterm>
+
+ OmegaT is een robuuste toepassing. U zou echter toch voorzorgen moeten nemen tegen gegevensverlies als u OmegaT gebruikt, net als met elke andere toepassing. Bij het vertalen van uw bestanden slaat OmegaT al uw voortgang op in het vertaalgeheugen project_save.tmx in de submap /omegat van het project.
+
+ OmegaT slaat ook, elke keer als een project wordt geopend of herladen, een kopie van het vertaalgeheugen op in project_save.tmx.JAARMMDDUUMM.bak in dezelfde submap. JAAR is 4-getallen jaar, MM is de maand, DD de dag van de maand, en UU en MM zijn de uren en minuten van wanneer het vorige vertaalgeheugen werd opgeslagen.
+
+ Als u denkt dat u vertaalde gegevens kwijt bent, kunt u de volgende procedure gebruiken om het project te herstellen naar de meest recent opgeslagen status, in de meeste gevallen niet ouder dan ongeveer 10 minuten:
+
+
+
+ sluit het project
+
+
+
+ hernoem het huidige project_save.tmx-bestand naar iets dat u zult onthouden (zoals bijvoorbeeld project_save.tmx.tijdelijk)
+
+
+
+ selecteer de back-up van het vertaalgeheugen dat meest waarschijnlijk de gegevens bevat die u nodig hebt
+
+
+
+ hernoem dat naar project_save.tmx
+
+
+
+ open het project
+
+
+
+ Voorkomen van verlies van belangrijke gegevens:
+
+
+
+ Maak regelmatig kopieën van het bestand /omegat/project_save.tmx naar back-upmedia, zoals CD of DVD.
+
+
+
+ Maak met regelmatige tussenpozen de vertaalde bestanden en controleer of dat vertaalde bestand de laatste versie van uw vertaling bevat, totdat u zich OmegaT eigen hebt gemaakt.
+
+
+
+ Wees in het bijzonder voorzichtig met het maken van wijzigingen in de bestanden in /source terwijl u midden in een project zit. Als het bronbestand wordt gewijzigd nadat u de vertaling bent begonnen, kan het zijn dat OmegaT een segment dat u al vertaald had niet meer kan vinden.
+
+
+
+
+
+ Gebruik om te beginnen deze Helpteksten. Als u tegen problemen aanloopt, post dan een bericht in de OmegaT-gebruikersgroep. Maak er geen probleem van om in uw eigen taal te posten.
+
+
+
+
+
+
+ <application><indexterm class="singular">
+ <primary>OmegaT op het web</primary>
+ </indexterm>OmegaT</application> op het web
+
+
+ <application>OmegaT</application>-sites en <application>OmegaT</application> SourceForge project<indexterm class="singular">
+ <primary>OmegaT op het web</primary> <secondary>SourceForge Project</secondary>
+ </indexterm>
+
+ DeOmegaT-website bevat koppelingen naar verschillende bronnen voor OmegaT. Ondersteuning voor gebruikers wordt gegeven op vrijwillige basis op de OmegaT Yahoo gebruikersgroep. De FAQ is een goed beginpunt om antwoorden te vinden op vragen die u misschien hebt. Bekijk de downloadpagina op www.omegat.org voor de laatste versie van OmegaT. U kunt ook foutenrapporten en verzoeken voor verbeteringen indienen.
+
+
+
+ Foutenrapporten<indexterm class="singular">
+ <primary>OmegaT op het web</primary> <secondary>Fouten rapporteren</secondary>
+ </indexterm>
+
+ Onthoud dat elk goed foutenrapport precies drie dingen nodig heeft:
+
+
+
+ Stappen om het te reproduceren
+
+
+
+ Wat u verwachtte te zien
+
+
+
+ Wat u in plaats daarvan zag
+
+
+
+ Meer in het artikel Painless Bug Tracking van Joel Spolsky
+
+ U zou kopieën van bestanden, delen uit het logbestand, schermafdrukken of iets waarvan u denkt dat dat de ontwikkelaars zou kunnen helpen bij het oplossen van uw probleem, moeten toevoegen. Merk op dat foutenrapporten en verzoeken voor verbeteringen publiekelijk te zien zijn, dus u zou daar geen vertrouwelijk bestanden aan moeten toevoegen. Als u bij wilt houden wat er gebeurd met het rapport moet u zich registreren als gebruiker van SourceForge, inloggen en een foutenrapport moeten indienen als u ingelogd bent, of eenvoudigweg op Monitor klikken bovenin het rapport.
+
+
+
+ Deelnemen aan het <application>OmegaT</application> project<indexterm class="singular">
+ <primary>OmegaT op het web</primary> <secondary>Deelnemen aan OmegaT</secondary>
+ </indexterm>
+
+ Deelnemen aan OmegaT:
+
+ Wordt eerst lid van de gebruikersgroep (via het web of door een e-mail te sturen naar OmegaT-subscribe@yahoogroups.com). Betrokken raken bij de ontwikkeling van OmegaT kunt u door deel te nemen aan de de ontwikkelingsgroep, via het web of door een e-mail te sturen aan omegat-development-request@lists.sourceforge.net met het onderwerp "subscribe".
+
+ Voor het vertalen van OmegaT's gebruikersinterface, gebruikershandleiding of andere gerelateerde documenten:
+
+ Lees eerst de gids Localizing and Customizing OmegaT en wordt dan lid van de OmegaT vertalersgroep, via het web of door een e-mail te sturen naar omegat-development-request@lists.sourceforge.net met als onderwerp "subscribe".
+
+
+ OmegaT op het webOntwikkeling, Vertalen
+
+
+ Financieel ondersteunen van het OmegaT-project
+ OmegaT op het webFinanciële ondersteuning
+
+
+ Als u de voortgaande ontwikkeling van OmegaT wilt helpen ondersteunen, zou het zeer op prijs worden gesteld - klik op deze koppeling om naar de OmegaT PayPalrekening te gaan.
+
+
+ OmegaT op het webDoneren aan OmegaT
+
+
+
+
+
+ Talen - ISO 639 codelijst<indexterm class="singular">
+ <primary>Talen</primary>
+ </indexterm>
+ <indexterm class="singular">
+ <primary>ISO taalcodes</primary>
+ </indexterm>
+ <indexterm class="singular">
+ <primary>Project</primary> <secondary>Eigenschappen</secondary> <seealso>Talen</seealso>
+ </indexterm>
+
+
+ Controleer alstublieft de ISO 639 Codetabellen voor meer en meest recente informatie over taalcodes.
+
+
+ ISO 639-1/639-2 lijst voor taalcode
+
+
+
+
+
+
+ Naam taal
+ ISO 639-1
+ ISO 639-2
+
+
+
+
+ Abchazisch
+ ab
+ abk
+
+
+ Afar
+ aa
+ aar
+
+
+ Afrikaans
+ af
+ afr
+
+
+ Akan
+ ak
+ aka
+
+
+ Albanees
+ sq
+ sqi
+
+
+ Amharisch
+ am
+ amh
+
+
+ Arabisch
+ ar
+ ara
+
+
+ Aragonees
+ an
+ arg
+
+
+ Armeens
+ hy
+ hye
+
+
+ Assamees
+ as
+ asm
+
+
+ Avarisch
+ av
+ ava
+
+
+ Avestaans
+ ae
+ ave
+
+
+ Aymarees
+ ay
+ aym
+
+
+ Azerbeidzjaans
+ az
+ aze
+
+
+ Bambara
+ bm
+ bam
+
+
+ Basjkiers
+ ba
+ bak
+
+
+ Baskisch
+ eu
+ eus
+
+
+ Wit-Russisch
+ be
+ bel
+
+
+ Bengaals
+ bn
+ ben
+
+
+ Bihari
+ bh
+ bih
+
+
+ Bislama
+ bi
+ bis
+
+
+ Bosnisch
+ bs
+ bos
+
+
+ Bretons
+ br
+ bre
+
+
+ Bulgaars
+ bg
+ bul
+
+
+ Birmaans
+ my
+ mya
+
+
+ Catalaans
+ ca
+ cat
+
+
+ Chamorro
+ ch
+ cha
+
+
+ Tsjetsjeens
+ ce
+ che
+
+
+ Chichewa, Chewa, Nyanja
+ ny
+ nya
+
+
+ Chinees
+ zh
+ zho
+
+
+ Tsjoevasjisch
+ cv
+ chv
+
+
+ Cornisch
+ kw
+ cor
+
+
+ Corsicaans
+ co
+ cos
+
+
+ Cree
+ cr
+ cre
+
+
+ Kroatisch
+ hr
+ hrv
+
+
+ Tsjechisch
+ cs
+ ces
+
+
+ Deens
+ da
+ dan
+
+
+ Divehi, Dhivehi, Maledivisch
+ dv
+ div
+
+
+ Nederlands
+ nl
+ nld
+
+
+ Dzongkhaans
+ dz
+ dzo
+
+
+ Engels
+ nl
+ eng
+
+
+ Esperanto
+ eo
+ epo
+
+
+ Ests
+ et
+ est
+
+
+ Ewe
+ ee
+ ewe
+
+
+ Faeröers
+ fo
+ fao
+
+
+ Fijisch
+ fj
+ fij
+
+
+ Fins
+ fi
+ fin
+
+
+ Frans
+ fr
+ fra
+
+
+ Fula, Fulah, Pulaar, Pular
+ ff
+ ful
+
+
+ Galisisch
+ gl
+ glg
+
+
+ Georgisch
+ ka
+ kat
+
+
+ Duits
+ de
+ deu
+
+
+ Grieks, modern
+ el
+ ell
+
+
+ Guaraní
+ gn
+ grn
+
+
+ Gujarati
+ gu
+ guj
+
+
+ Haïtiaans, Haïtiaans Creools
+ ht
+ hat
+
+
+ Hausa
+ ha
+ hau
+
+
+ Hebreeuws (modern)
+ he
+ heb
+
+
+ Herero
+ hz
+ her
+
+
+ Hindi
+ hi
+ hin
+
+
+ Hiri Motu
+ ho
+ hmo
+
+
+ Hongaars
+ hu
+ hun
+
+
+ Interlingua
+ ia
+ ina
+
+
+ Indonesisch
+ id
+ ind
+
+
+ Interlingue
+ ie
+ ile
+
+
+ Iers
+ ga
+ gle
+
+
+ Igbo
+ ig
+ ibo
+
+
+ Inupiaq
+ ik
+ ipk
+
+
+ Ido
+ io
+ ido
+
+
+ IJslands
+ is
+ isl
+
+
+ Italiaans
+ it
+ ita
+
+
+ Inuktitut
+ iu
+ iku
+
+
+ Japans
+ ja
+ jpn
+
+
+ Javaans
+ jv
+ jav
+
+
+ Kalaallisut, Groenlands
+ kl
+ kal
+
+
+ Kannada
+ kn
+ kan
+
+
+ Kanuri
+ kr
+ kau
+
+
+ Kasjmiers
+ s
+ kas
+
+
+ Kazachs
+ kk
+ kaz
+
+
+ Centraal Khmer
+ km
+ khm
+
+
+ Kikuyu, Gikuyu
+ ki
+ kik
+
+
+ Kinyarwanda
+ rw
+ kin
+
+
+ Kirgizisch, Kirgizies
+ ky
+ kir
+
+
+ Komi
+ kv
+ kom
+
+
+ Kongo
+ kg
+ kon
+
+
+ Koreaans
+ ko
+ kor
+
+
+ Koerdisch
+ ku
+ kur
+
+
+ Kwanyama, Kuanyama
+ kj
+ kua
+
+
+ Latijns
+ la
+ lat
+
+
+ Luxemburgs, Letzeburgs
+ lb
+ ltz
+
+
+ Lugandees
+ lg
+ lug
+
+
+ Limburgs
+ li
+ lim
+
+
+ Lingala
+ ln
+ lin
+
+
+ Laotiaans
+ lo
+ lao
+
+
+ Litouws
+ lt
+ lit
+
+
+ Luba-Katanga
+ lu
+ lub
+
+
+ Lets
+ lv
+ lav
+
+
+ Manx
+ gv
+ glv
+
+
+ Macedonisch
+ mk
+ mkd
+
+
+ Malagasisch
+ mg
+ mlg
+
+
+ Malayalam
+ ms
+ msa
+
+
+ Maleis
+ ml
+ mal
+
+
+ Maltees
+ mt
+ mlt
+
+
+ Māori
+ mi
+ mri
+
+
+ Marathisch (Marāṭhī)
+ mr
+ mar
+
+
+ Marshallees
+ mh
+ mah
+
+
+ Mongools
+ mn
+ mon
+
+
+ Nauru
+ na
+ nau
+
+
+ Navajo, Navaho
+ nv
+ nav
+
+
+ Noors Bokmål
+ nb
+ nob
+
+
+ Noord-Ndebele
+ nd
+ nde
+
+
+ Nepalees
+ ne
+ nep
+
+
+ Ndonga
+ ng
+ ndo
+
+
+ Noors Nynorsk
+ nn
+ nno
+
+
+ Noors
+ no
+ nor
+
+
+ Yi
+ ii
+ iii
+
+
+ Zuid-Ndebele
+ nr
+ nbl
+
+
+ Occitaans
+ oc
+ oci
+
+
+ Ojibweg, Ojibwa
+ oj
+ oji
+
+
+ Oudkerkslavisch, Kerkslavisch, Oerslavisch, Oudbulgaars
+ cu
+ chu
+
+
+ Afaan Oromo
+ om
+ orm
+
+
+ Oriyaans
+ of
+ ori
+
+
+ Ossetisch
+ os
+ oss
+
+
+ Punjabi
+ pa
+ pan
+
+
+ Pāli
+ pi
+ pli
+
+
+ Perzisch
+ fa
+ fas
+
+
+ Pools
+ pl
+ pol
+
+
+ Pasjtoe, Pashto, Pushto
+ ps
+ pus
+
+
+ Portugees
+ pt
+ por
+
+
+ Quechua
+ qu
+ que
+
+
+ Romaans
+ rm
+ roh
+
+
+ Rundi
+ rn
+ run
+
+
+ Roemeens, Moldavisch, Moldovaans
+ ro
+ ron
+
+
+ Russisch
+ ru
+ rus
+
+
+ Sanskriet (Saṁskṛta)
+ sa
+ san
+
+
+ Sardisch
+ sc
+ srd
+
+
+ Sindhi
+ sd
+ snd
+
+
+ Noord-Samisch
+ se
+ sme
+
+
+ Samoaans
+ sm
+ smo
+
+
+ Sango
+ sg
+ sag
+
+
+ Servisch
+ sr
+ srp
+
+
+ Schots Keltisch, Keltisch
+ gd
+ gla
+
+
+ Shona
+ sn
+ sna
+
+
+ Sinhala, Singalees
+ si
+ sin
+
+
+ Slowaaks
+ sk
+ slk
+
+
+ Sloveens
+ sl
+ slv
+
+
+ Somalisch
+ so
+ som
+
+
+ Zuid Sothees
+ st
+ sot
+
+
+ Spaans, Castiliaans
+ es
+ spa
+
+
+ Soendanees
+ su
+ sun
+
+
+ Swahili
+ sw
+ swa
+
+
+ Swatisch
+ ss
+ ssw
+
+
+ Zweeds
+ sv
+ swe
+
+
+ Tamil
+ ta
+ tam
+
+
+ Telugu
+ te
+ tel
+
+
+ Tadzjieks
+ tg
+ tgk
+
+
+ Thais
+ th
+ tha
+
+
+ Tigrinyaans
+ ti
+ tir
+
+
+ Tibetaans Standaard, Tibetaans, Centraal
+ bo
+ bod
+
+
+ Turkmeens
+ tk
+ tuk
+
+
+ Tagalog
+ tl
+ tgl
+
+
+ Tswanees
+ tn
+ tsn
+
+
+ Tonga (Tonga-eilanden)
+ to
+ ton
+
+
+ Turks
+ tr
+ tur
+
+
+ Tsongees
+ ts
+ tso
+
+
+ Tataars
+ tt
+ tat
+
+
+ Twi
+ tw
+ twi
+
+
+ Tahitiaans
+ ty
+ tah
+
+
+ Oeigoers
+ ug
+ uig
+
+
+ Oekraïns
+ uk
+ ukr
+
+
+ Urdu
+ ur
+ urd
+
+
+ Oezbeeks
+ uz
+ uzb
+
+
+ Venda
+ ve
+ ven
+
+
+ Vietnamees
+ vi
+ vie
+
+
+ Volapük
+ vo
+ vol
+
+
+ Waals
+ wa
+ wln
+
+
+ Welsh
+ cy
+ cym
+
+
+ Wolof
+ wo
+ wol
+
+
+ Westfries
+ fy
+ fry
+
+
+ Xhosa
+ xh
+ xho
+
+
+ Jiddisch
+ yi
+ yid
+
+
+ Yoruba
+ yo
+ yor
+
+
+ Zhuang, Chuang
+ za
+ zha
+
+
+ Zulu, Zoeloe
+ zu
+ zul
+
+
+
+
+
+
+
+ Sneltoetsen voor het toetsenbord voor het bewerken
+
+ Deze korte tekst beschrijft het gedrag van de toetsen in het bewerkingsvenster. De term "Verplaats naar binnen het segment" betekent dat de cursor verplaatst naar het begin van het segment als het eerder vóór het segment stond en naar het einde van het segment als het er eerder achter stond.
+
+
+ Gedrag van de toets bij bewerken
+
+
+
+
+
+
+
+
+ Toetscombinatie
+
+ Actie
+
+
+
+
+
+ Links:
+
+ één teken naar links, maar niet verder dan het begin van het segment
+
+
+
+ Rechts:
+
+ één teken naar rechts, maar niet verder dan het einde van het segment
+
+
+
+ Ctrl+Links:
+
+ één woord naar links, maar niet verder dan het begin van het segment
+
+
+
+ Ctrl+Rechts:
+
+ één woord naar rechts, maar niet verder dan het einde van het segment
+
+
+
+ PgUp:
+
+ pagina omhoog door het document
+
+
+
+ PgDn:
+
+ pagina naar beneden door het document
+
+
+
+ Home*
+
+ verplaats naar het begin van de regel in het segment
+
+
+
+ End*
+
+ verplaats naar het einde van de regel in het segment
+
+
+
+ Ctrl+Home
+
+ verplaats naar het begin van het segment
+
+
+
+ Ctrl+End
+
+ verplaats naar het einde van het segment
+
+
+
+ Ctrl+PgUp
+
+ verplaats naar het begin van het document (Mac: Cmd+PgUp)
+
+
+
+ Ctrl+PgDn
+
+ verplaats naar het einde van het document (Mac: Cmd+PgDn)
+
+
+
+ Backspace*
+
+ verwijder het teken vóór de cursor
+
+
+
+ Delete*
+
+ verwijder het teken na de cursor
+
+
+
+ Ctrl+Backspace
+
+ verwijder de tekens tot aan het begin van het huidige woord (Mac: Alt+Backspace)
+
+
+
+ Ctrl+Delete
+
+ verwijder de tekens tot aan het begin van het volgende woord (Mac: Alt+Delete)
+
+
+
+ Ctrl+Enter
+
+ open het vorige segment (Mac: Cmd+Enter)
+
+
+
+ Ctrl+A
+
+ selecteer het complete segment (Mac: Cmd+A)
+
+
+
+ Ctrl+Shift+O
+
+ schakelen RTL-LTR
+
+
+
+
+
+ * Deze toetsen gedragen zich anders als de cursor buiten het bewerkbare segment staat:
+
+
+
+ Home: cursor naar het begin van het actieve segment
+
+
+
+ End: cursor naar het einde van het actieve segment
+
+
+
+ Backspace: niets
+
+
+
+ Delete: niets
+
+
+
+ Toets van elk teken, indien geklikt buiten het bewerkbare segment, zal worden genegeerd.
+
+
+
+ De toets "Shift" omvat niet per definitie enig speciaal gedrag: indien de "Shift"-toets is ingedrukt verplaatsen alle toetsen de cursor op de hun gewone manier.
+
+ Systeembrede opdrachten: Plakken (Ctrl+V of Ctrl+Insert), Knippen (Ctrl+X of Ctrl+C), Overeenkomst invoegen (Ctrl+I) en Bron invoegen (Ctrl+Shift+I) acteren in principe op elke selectie, inclusief die welke zich uitstrekken tot buiten het huidige segment. In een dergelijk geval zal de selectie natuurlijk worden beperkt tot de grenzen van het segment.
+
+
+
+ Aanpassen van sneltoetsen toetsenbord
+
+
+ <indexterm class="singular">
+ <primary>Sneltoetsen - aanpassen</primary> <secondary>Aanpassen</secondary>
+ </indexterm>Aanpassen van sneltoetsen toetsenbord
+
+ Aan de meeste items die verschijnen in het hoofdmenu kan een sneltoets worden toegewezen. Alleen aan de meest algemeen gebruikte menuitems zijn standaard sneltoetsen toegewezen. U kunt de reeds toegewezen sneltoetsen wijzigen en nieuwe sneltoetsen toevoegen door een bestand met definities voor de sneltoetsen in uw map voor voorkeuren voor OmegaT te plaatsen (zie Locatie gebruikersbestanden).
+
+ Het bestand met definities voor de sneltoetsen moet zijn genaamd MainMenuShortcuts.properties en mag ten hoogste één definitie voor een sneltoets per regel bevatten. Lege regels worden geaccepteerd en regels met opmerkingen zouden moeten beginnen met "//". Alles na de "//" zal worden genegeerd.
+
+ Als het bestand MainMenuShortcuts.properties is gewijzigd, moet OmegaT opnieuw gestart worden om de nieuwe sneltoetsen te kunnen laten werken.
+
+ De syntaxis voor de definitie van de sneltoets is de volgende: <code menuitem>=<sneltoets>, waar <code menuitem> een code is die wordt genomen uit de tabellen hieronder en <sneltoets> een combinatie is van ingedrukte toetsen die wordt gedefinieerd door de gebruiker.
+ De volledige syntaxis voor toetsaanslagen (sneltoetsen) wordt gedefinieerd in de volgende documentatie voor Java 1.6 van Oracle (onderaan de bladzijde): Java 1.6 keystrokes shortcuts
+ .
+
+ <sneltoets> moet in de volgende vorm zijn: 0 of meer <modifier> gevolgd door 0 of 1 <event> gevolgd door 1 <key>, waar:
+
+ <modifier> kan zijn: shift, control, ctrl, meta
+ Op de Mac moet de modifier meta worden gebruikt om de toets command te specificeren.
+ , alt,
+ altGraph
+
+
+
+ <event> kan zijn: typed, pressed, released
+
+
+
+ en <key> kan elke toets zijn die beschikbaar is op uw toetsenbord
+ De mogelijke gebeurtenissen voor de toetsen (events) worden opgesomd op de volgende documentatie voor Java 1.6 van Oracle: Java 1.6 keyEvents description
+ .
+
+
+
+ Bijvoorbeeld, de standaard sneltoetsen voor OmegaT
+ De standaard sneltoetsen voor OmegaT zijn beschikbaar via Sourceforge: Default OmegaT Shortcuts
+
+ De standaard sneltoetsen voor OmegaT voor de Mac zijn ook beschikbaar via Sourceforge, zij gebruiken allemaal "meta" in plaats van "ctrl": Default OmegaT Shortcuts for the Mac
+ , kan men vinden:
+
+
+
+ projectOpenMenuItem=ctrl O
+
+
+
+ editCreateGlossaryEntryMenuItem=ctrl shift G
+
+
+
+ De eerste is de sneltoets voor Project openen, de tweede voor Item voor woordenlijst maken.
+
+ Indien u ShiftCtrlO wilt gebruiken om een project te openen, past u MainMenuShortcuts.properties als volgt aan:
+
+
+ projectOpenMenuItem=shift ctrl O.
+
+ Indien u een Mac gebruikt en u wilt de sneltoets ShiftCommandS toevoegen aan ExtraStatistieken, voeg dan de volgende regel toe aan uw MainMenuShortcuts.properties:
+
+ toolsShowStatisticsStandardMenuItem=shift meta
+ S
+
+ Sla dan het bestand op en start OmegaT opnieuw op. Uw nieuwe sneltoetsen zouden nu naast de menuitems moeten verschijnen die u hebt aangepast. Als zij niet conflicteren met sneltoetsen van het systeem, zouden zij beschikbaar moeten zijn binnen OmegaT.
+
+
+
+ menu Project
+
+
+
+ 在实际中，最重要的数字是第二对，它告诉您总的有多少，到现在已经做了多少。在这个例子中显然项目已经完成了，因为已经翻译了所有的独特片段。
+
+
+ 编辑器窗格<indexterm class="singular">
+ <primary>OmegaT 窗口和窗格</primary> <secondary>编辑器窗格</secondary>
+ </indexterm>
+
+ 这是输入和编辑译文的地方。编辑窗格显示部分被翻译的文本：已经被翻译好的文本将会显示为已翻译，而未翻译的文本以原始语言显示。显示的文本被分成片段，您可以在文档中上下移动或者双击某个片段进行编辑。在上面的情况中，已译片段显示为黄色，然而可以修改此设置以符合自己的喜好（请参阅）。
+
+ 其中某个片段是激活状态的片段。这是那个显示为两部分的片段。上面部分是源语言，使用绿色背景并加粗字体显示；下面部分是编辑区域，以标记结尾：
+ 片段标记
+ 这里的标记是 <segment nnnn>，其中 nnnn 为当前片段在项目中的编号。您可以使用上面部分作为参考，覆盖或者修改编辑区域的内容以使它包括译文。
+
+ 根据不同的首选编辑行为，未译片段的编辑区域可能是空的、可能包含源文本或者与待译内容最接近的字符串的译文。移动到另一个片段时，译文将被确认并保存。如果您想让译文等同于原文，只需简单地删除所有文本使编辑区域为空（Ctrl+A 然后用 Del 删除）。OmegaT 会保存等同于原文的译文。该功能对翻译包含商标、姓名或专用名词以及不须翻译的第三方语言的文档非常有用。请参阅译文编辑了解更多信息。
+
+ 如果在编辑窗格中点击右键，会打开弹出菜单，其中提供了剪切、复制、粘贴（即功能等同于 CtrlX, CtrlC 和 CtrlV）和转到片段功能。
+
+
+
+ 匹配查看器
+
+
+ <indexterm class="singular">
+ <primary>匹配</primary> <secondary>匹配窗格 - 图示</secondary>
+ </indexterm><indexterm class="singular">
+ <primary>OmegaT 窗口和窗格</primary> <secondary>匹配面板 - 图示</secondary>
+ </indexterm>匹配窗格
+
+
+
+
+
+
+
+
+
+
+
+
+ 匹配查看器中显示译法记忆中最相似的片段，包括您在项目翻译过程中创建的项目翻译记忆，也包括从您早前工作中导入的辅助记忆，或者是您从客户或翻译代理那里得到得到的。
+
+ 当您进入下一片段，第一个模糊匹配（拥有最高匹配百分比的那个）自动被选中。您可以使用 Ctrl+2, 3, 4 或 5选择另一个。
+ 快捷键Ctrl+N - 选择匹配
+ 当然，如果没有第 5 号匹配，按下Ctrl5是没有效果的。要在译文中使用选中的匹配，请使用 Ctrl+R
+ 快捷键Ctrl+R - 替换文本
+ 以用匹配替换目标区域，或使用 Ctrl+I
+ 快捷键Ctrl+I - 插入文本
+ 以将匹配插入到当前光标位置。
+
+ 匹配率大体上相当于匹配片段和被匹配片段中相同的单词数量，并除以两者单词数量中较大者。被选中的模糊匹配会以粗体突出显示，对正在翻译片段中缺少的单词显示为蓝色，而在缺少单词旁边的单词显示为绿色。在上面示例中源片段为 Duration of exposure <15 min。最高的匹配是 60%，因为在 5 个单词中有 3 个相同。在显示匹配率的这一行还包括了包含这个匹配的翻译记忆的名称
+ 翻译记忆匹配
+ 。如果未显示文件名，则发现匹配的源为默认项目的翻译记忆。孤立片段
+ 翻译记忆孤立片段
+ （第 4 号匹配）表示该片段存在默认项目的翻译记忆中，但不存在于项目的源片段。
+
+ 实际上是三个可用的评价（在上面首个匹配中为 60/60/54）。它们的含义如下：
+
+
+
+ 使用解析器插件（tokenizer plugin）后的匹配百分率
+
+
+
+
+
+ 默认的 OmegaT 匹配 - 匹配的词汇数 - 忽略数字和标签 - 除以总的词汇数
+
+
+
+
+
+ OmegaT 匹配，包括数字、标签
+
+
+
+
+
+ 词汇表<indexterm class="singular">
+ <primary>OmegaT 窗口和窗格</primary> <secondary>词汇表窗格</secondary>
+ </indexterm>
+
+ 词汇表窗格允许您使用个人收集的词汇和专业术语，这些词汇都存放在词汇表文件中。它显示当前片段中找到的术语，但只用来做参考之用，无法将其译文插入或替换术语。
+
+
+ <indexterm class="singular">
+ <primary>词汇表</primary> <secondary>词汇表窗口 - 图示</secondary>
+ </indexterm>词汇表窗格
+
+
+
+
+
+
+
+
+
+
+
+
+ 上例中的源片段为“In most translation jobs it is considered important to have the translated document look similar to the original.”，在词汇表文件中找到了两个单词：document 和 translation。OmegaT 还支持多词术语：
+
+
+ <indexterm class="singular">
+ <primary>词汇表</primary> <secondary>在词汇表中的多词条目 - 图示</secondary>
+ </indexterm>词汇表中的多词条目
+
+
+
+
+
+
+
+
+
+
+
+
+ 如果您激活选项→翻译提示中的翻译提示，那么可在源片段中突出显示的单词上点击右键，以打开包含由词汇表提供的可选译文的弹出菜单。选择其中一个可将其插入目标片段的当前位置。您可以让词汇表窗格中的首选译文突出显示，并通过右键点击选区来将它插入目标片段中。
+
+
+
+ 词典查看器<indexterm class="singular">
+ <primary>OmegaT 窗口和窗格</primary> <secondary>词典窗格</secondary>
+ </indexterm>
+
+ 词典是等同于 Merriam Webster、Duden、Larousse 等桌面上的印刷词典的电子版本。
+
+
+
+ 机器翻译<indexterm class="singular">
+ <primary>OmegaT 窗口和窗格</primary> <secondary>机器翻译</secondary>
+ </indexterm>
+
+ 在机器翻译窗格中，打开后其中会包含由机器翻译工具为当前片段提供的翻译建议。按 Ctrl+M 可使用建议译文替换当前片段的译文。
+
+
+
+ 主菜单
+
+ 通过主菜单可访问 OmegaT 的所有功能。参阅主菜单附录了解所有菜单和菜单项的完整描述。最常用的功能可以使用键盘快捷键访问，因此当您习惯了使用它们之后，在翻译的时候根本不需要使用菜单。
+
+
+
+ 状态栏
+
+ 在主窗口底部的状态栏显示和工作流相关的信息。该栏目向用户给出仅在进行的某个操作的反馈。它也会显示和当前片段匹配的模糊和术语的数量。
+
+
+
+
+ 其它窗口
+
+
+ 项目文件<indexterm class="singular">
+ <primary>OmegaT 窗口和窗格</primary> <secondary>项目文件</secondary>
+ </indexterm>
+
+ 项目文件窗口显示所有的项目文件和其他项目的信息。当 OmegaT 载入项目时这个窗口自动出现。使用 Ctrl+L
+ 快捷键Ctrl+L - 项目文件列表
+ 打开，使用 Esc 关闭。项目文件窗口显示了下列信息：
+
+
+
+ 项目中所有可译文件组成的列表。这是目前在源文件文件夹中OmegaT 能够识别的文件。点击任何一份文件将打开它进行翻译
+
+
+
+
+
+ 当前在编辑窗格中打开的文件用蓝色背景突出显示。按 Enter 将在编辑窗格中移动到选中文件的开始处
+
+
+
+
+
+ 每个文件包含的片段数量现在在文件名的右边
+
+
+
+
+
+ 整个项目的总片段数、独特片段数和已译独特片段数显示在底部
+
+
+
+ 独特片段数目的计算方法为统计所有的片段并去除所有重复片段。（“独特” 的判断方法是区分大小写的："Run" 和 "run" 被看作是不同的片段）
+
+ 通过“片段数”和“独特片段数”的差异可粗略估算出文本中有多少重复内容。但是请注意：该数字并未透露这些重复的相关性，它们可能是多次重复的相当长的句子（此时是幸运的）或关键字表格（不那么幸运了）。项目 omegat 文件夹中的 project_stats.txt 提供了每份文件更多的片段细节信息。
+
+ 修改分割规则可能改变片段数和独特片段数。然而，一旦启动项目的翻译工作，就应该避免发生这样的事情。请参阅片段分割规则了解更多信息。
+
+
+ 源文件添加文件到项目
+ 添加文件到项目：您可以通过点击“导入源文件”按钮将源文件添加到项目中。它将选中的文件拷贝到 /source 目录并重新载入项目以导入新文件。通过点击“从 MediaWiki 导入”按钮并输入相应的 URL，您还可以添加互联网页中用 MediaWiki 编写的源文件。
+
+
+
+ 搜索窗口<indexterm class="singular">
+ <primary>OmegaT 窗口和窗格</primary> <secondary>搜索面板</secondary>
+ </indexterm>
+
+ 您可以用使用搜索窗口查找项目中的某个片段。可以同时打开多个搜索窗口。在主窗口中使用CtrlF可打开一个新的搜索窗口。搜索窗口由三个部分组成：用于输入搜索字符串或关键字的文本框、用于设置搜索的标志和单选按钮、包含搜索结果的显示区域。请参阅 搜索 来了解关于搜索窗口的更多信息。
+
+
+
+ 标签验证<indexterm class="singular">
+ <primary>标签验证</primary> <seealso>快捷键，标签</seealso>
+ </indexterm><indexterm class="singular">
+ <primary>OmegaT 窗口和窗格</primary> <secondary>标签验证</secondary> <seealso>标签</seealso>
+ </indexterm>
+
+ 标签检验窗口检测译文中出现的所有标签错误和不一致并列出来。使用Ctrl+T 打开该窗口。该窗口显示了一个三列表格，其中列出了指向出错片段的链接及其原文和译文内容：
+
+
+ <indexterm class="singular">
+ <primary>标签验证</primary> <secondary>窗口 - 配置</secondary> <seealso>标签</seealso>
+ </indexterm>标签验证窗口
+
+
+
+
+
+
+
+
+
+
+
+
+ 标签用加粗蓝色突出显示，以便于对源内容和译后内容进行比较。点击该链接可在编辑器窗格中跳转至该片段。如果必要的话，修正错误然后按Ctrl+T 键返回标签验证窗口以修正其它错误。在上述的第一和第三种情况中，标签的错误成对出现，而在第二种情况中开始标记缺失了 < 标记。
+
+ 标签错误是指译文中标签的顺序和数目与源片段不一致。在标签验证窗口中包含的某些情况的标签是必要的和良性的，但有些在创建已译文档时会导致问题。标签通常代表了原始文本中的某种格式。开始翻译前对源文本格式的简化很大程度上有助于减少标签的数目。
+
+
+
+ 匹配统计<indexterm class="singular">
+ <primary>匹配统计</primary> <seealso>工具菜单</seealso>
+ </indexterm>
+
+ 通过工具/匹配统计可访问统计信息。该统计需要 CPU 进行繁重的运算且耗时的，所以在计算时会显示进度条。至于相关的分类，使用工业标准的分类匹配到下面的组中：
+
+
+
+ 精确匹配
+
+
+
+ 95%-100%
+
+
+
+ 85%-94%
+
+
+
+ 75%-84%
+
+
+
+ 50%-74%
+
+
+
+ 无匹配
+
+
+
+ 单词数等同于在项目文件窗口中的数字，是严格遵循 OmegaT 的计算方法，计算术语上的一些区别是概念上的。统计片段、单词和字符（含和不含空格）的该信息。注意：这些总数是较接近项目中工作量的近似值，因此可作为您计算费用或价格的参考。
+
+
+ 匹配统计
+
+
+
+
+
+
+
+
+
+
+
+
+ 在最后一列片段间的空格无需考虑。重复表示多次出现在文本中的相同片段。第一个片段及其内容将被归类到“无匹配”中，而剩余片段则被视为第一个的重复。如果在项目的翻译记忆中存在多个相同源片段的译文，这些及其他已译独特片段将被归类为“精确匹配”。在需要时，标准统计窗口中会显示独特片段数，不论它们是否已经翻译。
+
+ 分类中的其他部分 (50-100%) 包含了具有模糊匹配的未译片段。在统计重复和精确匹配时模糊匹配不仅可以来自 /omegaT，也可以可以来自 /tm 文件夹。与 project_save 翻译记忆的匹配的唯一区别是外部 TM 中的统计不会得到精确匹配，而只是 100%。如果不想使用外部翻译记忆参与统计，可以让 /tm 文件夹为空或临时改变项目设置以让 /tm 指向其他地方。
+
+ 该匹配统计是 tab 分割的，您可用 Ctrl+A
+ 快捷键Ctrl+A - 全选
+ , Ctrl+C
+ 快捷键Ctrl+C - 复制文本
+ , Ctrl+V
+ 快捷键Ctrl+V - 粘贴文本
+ 来复制/粘贴它们，例如到工作表或费用统计程序中。在计算后，该数据还可以在 omegat/project_stats_match.txt 中找到。需要注意的是该文件是有时间戳记录的，因为计算不是瞬时的（相对于统计），所以可能很快过时。
+
+
+
+ 帮助浏览器<indexterm class="singular">
+ <primary>帮助菜单</primary> <secondary>帮助浏览器</secondary>
+ </indexterm>
+
+ 帮助浏览器（显示本手册）可通过按
+ 快捷键F1 - 帮助
+ F1 或调用主菜单中的
+ 帮助菜单用户手册……
+ 帮助→用户手册……条目来打开。在该窗口中会显示手册和两个按钮：退后和内容。用户手册是一份包含各个不同章节链接的 HTML 文档。像在网页浏览器中那样点击一个链接将会打开要看的页面。
+
+ 用户手册存放在 OmegaT 安装目录的 doc 子目录中，因此可在浏览器中打开 doc/en/index.hmtl 文件来查看英文文档。用这种方法，您也可以打开外部的链接，因为内建的帮助浏览器并不接受外部互联网链接。
+
+
+
\ No newline at end of file
diff --git a/OmegaT/doc_src/zh_CN/images/AppleKey.gif b/OmegaT/doc_src/zh_CN/images/AppleKey.gif
new file mode 100644
index 0000000..dabdac4
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/AppleKey.gif differ
diff --git a/OmegaT/doc_src/zh_CN/images/AsciiFilteroptions.png b/OmegaT/doc_src/zh_CN/images/AsciiFilteroptions.png
new file mode 100644
index 0000000..0040afe
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/AsciiFilteroptions.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/DictMerriamWebster.png b/OmegaT/doc_src/zh_CN/images/DictMerriamWebster.png
new file mode 100644
index 0000000..08bc241
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/DictMerriamWebster.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/Dock.gif b/OmegaT/doc_src/zh_CN/images/Dock.gif
new file mode 100644
index 0000000..4a6487c
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/Dock.gif differ
diff --git a/OmegaT/doc_src/zh_CN/images/EditingBehaviourOptions.png b/OmegaT/doc_src/zh_CN/images/EditingBehaviourOptions.png
new file mode 100644
index 0000000..e4328f9
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/EditingBehaviourOptions.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/Glossary_pane.png b/OmegaT/doc_src/zh_CN/images/Glossary_pane.png
new file mode 100644
index 0000000..41fe008
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/Glossary_pane.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/MatchStatistics.png b/OmegaT/doc_src/zh_CN/images/MatchStatistics.png
new file mode 100644
index 0000000..7297bf5
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/MatchStatistics.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/MatchesPane.png b/OmegaT/doc_src/zh_CN/images/MatchesPane.png
new file mode 100644
index 0000000..3bf219b
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/MatchesPane.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/Maximize.gif b/OmegaT/doc_src/zh_CN/images/Maximize.gif
new file mode 100644
index 0000000..24e1b0a
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/Maximize.gif differ
diff --git a/OmegaT/doc_src/zh_CN/images/Minimize.gif b/OmegaT/doc_src/zh_CN/images/Minimize.gif
new file mode 100644
index 0000000..f41fac5
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/Minimize.gif differ
diff --git a/OmegaT/doc_src/zh_CN/images/MobyDick.png b/OmegaT/doc_src/zh_CN/images/MobyDick.png
new file mode 100644
index 0000000..b6de59a
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/MobyDick.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/MultiTerm_Glossary.png b/OmegaT/doc_src/zh_CN/images/MultiTerm_Glossary.png
new file mode 100644
index 0000000..5cfbba7
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/MultiTerm_Glossary.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/NewProject.png b/OmegaT/doc_src/zh_CN/images/NewProject.png
new file mode 100644
index 0000000..e0496d4
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/NewProject.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/OmT_Cyrillic.png b/OmegaT/doc_src/zh_CN/images/OmT_Cyrillic.png
new file mode 100644
index 0000000..fd74105
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/OmT_Cyrillic.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/OmT_Japanese.png b/OmegaT/doc_src/zh_CN/images/OmT_Japanese.png
new file mode 100644
index 0000000..b760d89
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/OmT_Japanese.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/OmegaT_icon.png b/OmegaT/doc_src/zh_CN/images/OmegaT_icon.png
new file mode 100644
index 0000000..5e8762b
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/OmegaT_icon.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/OmegaT_panes.png b/OmegaT/doc_src/zh_CN/images/OmegaT_panes.png
new file mode 100644
index 0000000..1b823a1
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/OmegaT_panes.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/OmegaT_projects_and_subdirectories.png b/OmegaT/doc_src/zh_CN/images/OmegaT_projects_and_subdirectories.png
new file mode 100644
index 0000000..e277b5c
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/OmegaT_projects_and_subdirectories.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/Omegatproject.png b/OmegaT/doc_src/zh_CN/images/Omegatproject.png
new file mode 100644
index 0000000..2736898
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/Omegatproject.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/RegexTester.png b/OmegaT/doc_src/zh_CN/images/RegexTester.png
new file mode 100644
index 0000000..bb44bdf
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/RegexTester.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/Restore.gif b/OmegaT/doc_src/zh_CN/images/Restore.gif
new file mode 100644
index 0000000..4099595
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/Restore.gif differ
diff --git a/OmegaT/doc_src/zh_CN/images/SpellcheckerSetup2.png b/OmegaT/doc_src/zh_CN/images/SpellcheckerSetup2.png
new file mode 100644
index 0000000..d99bd27
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/SpellcheckerSetup2.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/SpellcheckingText.png b/OmegaT/doc_src/zh_CN/images/SpellcheckingText.png
new file mode 100644
index 0000000..44f1648
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/SpellcheckingText.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/TagValidation.png b/OmegaT/doc_src/zh_CN/images/TagValidation.png
new file mode 100644
index 0000000..e109554
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/TagValidation.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/TagValidator.png b/OmegaT/doc_src/zh_CN/images/TagValidator.png
new file mode 100644
index 0000000..44f994e
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/TagValidator.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/TextSearch.png b/OmegaT/doc_src/zh_CN/images/TextSearch.png
new file mode 100644
index 0000000..428a4e9
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/TextSearch.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/Undock.gif b/OmegaT/doc_src/zh_CN/images/Undock.gif
new file mode 100644
index 0000000..6680e9c
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/Undock.gif differ
diff --git a/OmegaT/doc_src/zh_CN/images/saveglossary.png b/OmegaT/doc_src/zh_CN/images/saveglossary.png
new file mode 100644
index 0000000..9923673
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/saveglossary.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/tagged_segment.png b/OmegaT/doc_src/zh_CN/images/tagged_segment.png
new file mode 100644
index 0000000..1b9e648
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/tagged_segment.png differ
diff --git a/OmegaT/doc_src/zh_CN/images/tagged_segment_target.png b/OmegaT/doc_src/zh_CN/images/tagged_segment_target.png
new file mode 100644
index 0000000..ddbd1c6
Binary files /dev/null and b/OmegaT/doc_src/zh_CN/images/tagged_segment_target.png differ
diff --git a/OmegaT/doc_src/zh_CN/license.txt b/OmegaT/doc_src/zh_CN/license.txt
new file mode 100644
index 0000000..c7e1697
--- /dev/null
+++ b/OmegaT/doc_src/zh_CN/license.txt
@@ -0,0 +1,340 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ -GNU ͨù֤
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+
+ Copyright (C)
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) year name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ , 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/OmegaT/doc_src/zh_CN/version.properties b/OmegaT/doc_src/zh_CN/version.properties
new file mode 100644
index 0000000..3bf16ae
--- /dev/null
+++ b/OmegaT/doc_src/zh_CN/version.properties
@@ -0,0 +1,2 @@
+# NOI18N
+version=2.4.9
diff --git a/OmegaT/docs/ar/images/AppleKey.gif b/OmegaT/docs/ar/images/AppleKey.gif
new file mode 100644
index 0000000..dabdac4
Binary files /dev/null and b/OmegaT/docs/ar/images/AppleKey.gif differ
diff --git a/OmegaT/docs/ar/images/Dock.gif b/OmegaT/docs/ar/images/Dock.gif
new file mode 100644
index 0000000..4a6487c
Binary files /dev/null and b/OmegaT/docs/ar/images/Dock.gif differ
diff --git a/OmegaT/docs/ar/images/Maximize.gif b/OmegaT/docs/ar/images/Maximize.gif
new file mode 100644
index 0000000..24e1b0a
Binary files /dev/null and b/OmegaT/docs/ar/images/Maximize.gif differ
diff --git a/OmegaT/docs/ar/images/Minimize.gif b/OmegaT/docs/ar/images/Minimize.gif
new file mode 100644
index 0000000..f41fac5
Binary files /dev/null and b/OmegaT/docs/ar/images/Minimize.gif differ
diff --git a/OmegaT/docs/ar/images/NewProject.png b/OmegaT/docs/ar/images/NewProject.png
new file mode 100644
index 0000000..d371eb3
Binary files /dev/null and b/OmegaT/docs/ar/images/NewProject.png differ
diff --git a/OmegaT/docs/ar/images/Restore.gif b/OmegaT/docs/ar/images/Restore.gif
new file mode 100644
index 0000000..4099595
Binary files /dev/null and b/OmegaT/docs/ar/images/Restore.gif differ
diff --git a/OmegaT/docs/ar/images/Undock.gif b/OmegaT/docs/ar/images/Undock.gif
new file mode 100644
index 0000000..6680e9c
Binary files /dev/null and b/OmegaT/docs/ar/images/Undock.gif differ
diff --git a/OmegaT/docs/ar/instantStartGuideNoTOC.html b/OmegaT/docs/ar/instantStartGuideNoTOC.html
new file mode 100644
index 0000000..cea973a
--- /dev/null
+++ b/OmegaT/docs/ar/instantStartGuideNoTOC.html
@@ -0,0 +1,171 @@
+
+
+
+
+ OmegaT 1.7.3 ـ دليل البداية الفورية، دليل المستخدم لإصدار
+
+
+
+
ابدأ باستعمال أوميجاتي في ظرف 5 دقائق! ـ دليل البداية الفورية
+
+
يغطي هذا الدليل الجوانب الرئيسية فقط. يستحسن أن يقرأ المستخدم الدليل حتى يستأنس بكل ما يمنحه البرنامج.
+
+
لاستعمال الدليل اضغط على "F1"أو استعمل القائمة مساعدة ← دليل المستخدم
+
دليل المستخدم هذا هو الوحيد الذي يتوفر على روابط لكل الفقرات الرئيسية.
+
لمستعملي الماك: الطرق المختصرة المذكورة هنا تستعمل تركيبة "ctrl+key"مما يعني"cmd+key".يكون مفتاح "cmd" ممثلا عن طريق طريق رسم التفاحة بلوحة مفاتيح الماك أو عن طريق علامة "command"
+
+
سوف يتم تعويض هذا الدليل بمشروع بمجرد فتحك له. و سوف يتم عرضه مجددا عندما تغلق المشروع.
+
+
+
كيفية عمل أوميجاتي بطريقة مختصرة
+
كيف تترجم باستعمال أوميجاتي
+
كيف تتعامل مع النصوص الموسومة
+
+
+
+
+
كيفية عمل أوميجاتي بطريقة مختصرة
+
+
تتكون شاشة أوميجاتي من فضاء واحد يتشكل من ثلاث نوافذ مختلفة. يمكنك تعديل مساحة كل نافذة بواسطة الفأرة. يتواجد المحرر لكتابة ترجمتك على اليسار. و على اليمين إلى الأعلى يتواجد عارض التطابقات الذي يظهر تطابقات ذاكرة الترجمة. تحته يتواجد عارض مسرد المصطلحات.
+
+
يقوم أوميجاتي بتجزئة النص الأصلي إلى جمل أو فقرات بنافذة العرض. قم بترجمة الأجزاء واحداً تلو الآخر. سوف يتم حفظ ترجمتك بذاكرة الترجمة عند مرورك من تجزئة إلى أخرى. عند انتهائك من ترجمة كل الأجزاء (أو قبل ذلك إذا أردت)، سوف يستعمل أوميجاتي ذاكرة الترجمة لتوليد ترجمة النص أو النصوص في المجلد الهدف.
+
+
يقوم أوميجاتي بتنظيم أعمال الترجمة في ما يسمى بمشاريع الترجمة. يتم إنشاء مجموعة من المجلدات لكل مشروع، بحيث يتم استعمال هاته الأخيرة لحفظ النصوص اﻷصلية التي ستتم ترجمتها، مسارد المصطلحات وأي ذاكرة ترجمة تود استعمالها. و يقوم أوميجاتي أيضاً بإنشاء مجلد هدف يتضمن نصوص الترجمة النهائية.
+
+
+
+
كيف تترجم باستعمال أوميجاتي
+
+
قم بإنشاء وفتح مشروع جديد
+
+
قم باختيار مشروع ← جديد... من القائمة
+
+
انتقل إلى المجلد الذي تود أن تحفظ ملفات المشروع به و اكتب اسم مشروع الترجمة. سوف يتم استعمال هذا الاسم لمجلد المشروع الرئيسي، بحيث سيتم حفظ كل الملفات بهذا المجلد أو بمجلداته الفرعية.
+
+
سوف يطلب منك أوميجاتي تأكيد أو تغيير مجلدات المشروع التي ينبغي إنشاؤها مستعملاً الخطاب التالي:
+
+
+
+
+
+
يمكنك قبول موقع المجلدات الفرعية، و لكن عليك أن تتأكد أن رموز لغات النصوص الأصلية و الترجمة صحيحة. قم باختيار رمز اللغة (حرفين) أو اللغة و المنطقة (حرفين لكل واحد منهما) من اللائحة المنسدلة، او اكتب الرموز بنفسك محترما في ذلك اتباع قاعدة الحرفين الاثنين كما ذكرنا. تذكر جيداً موقع المجلد الهدف الذي ستتواجد به نصوص الترجمة.
+
+
إذا كنت تريد أن يقوم أوميجاتي بتجزئة النص إلى جمل بدل تجزئته إلى فقرات، فعليك أن تراجع قواعد التجزئة عن كثب.
+
+
سوف يطلب منك أوميجا تي أن تختار النصوص الأصلية لاستيرادها عند موافقتك على تعديلات المشروع. يمكنك استيراد ملفات منفردة أو أشجار أدلة بكاملها بما في ذلك الملفات المتواجدة بالأدلة الفرعية. إذا قمت باستيراد ملفات خاطئة عن غير إرادة أو قمت باستيراد كم كبير من المستندات فإنه بإمكانك إزالتها من مجلد النصوص الأصلية من مشروعك، عن طريق استعمال منظم الملفات مثلاً.
+
+
لمراجعة لائحة الملفات التي تود ترجمتها، اذهب إلى نافذة ملفات المشروع (قائمة: المشروع ← ملفات المشروع ). إذا كنت تود تغيير محتويات المجلد الأصلي، فلا تنس أن تعيد تحميل المشروع أولاً : قائمة ( مشروع ← إعادة تحميل ). يقوم أوميجاتي مبدئياً بفتح الملف الأول المتواجد بلائحة المشاريع.
+
+
تذكر أن أوميجاتي لن يقوم إلا بترجمة الملفات المتوفرة بالصيغ المذكورة أدناه في حال تطابقها مع الأنماط المحددة بمرشحات الملفات، في حين سيتم تجاهل كل الصيغ الأخرى.
+
+
+
(Open Document Format (ODF ISO/IEC 26300
+
OpenOffice.org
+
XHTML, HTML
+
HTML Help Compiler
+
DocBook
+
plain text نص بسيط
+
bundle.properties Java
+
monolingual .po
+
(INI ('key=value' format
+
Okapi monolingual XLIFF
+
+
+
ترجم الأجزاء واحداً تلو الآخر
+
+
سوف يقوم أوميجاتي بفتح أول ملف أصلي في المحرر مباشرة بعد إنشائك للمشروع و تحديد الملفات التي تنبغي ترجمتها. يبرز الجزء الأول باللون اﻷخضر فيما تتواجد نسخة من النص الأصلي تحته، بالحقل الهدف. (في هذه المرحلة يكون كل النص المتواجد خارج الحقل الهدف محمياً و لا تستطيع تغييره. ) يجب عليك أن تكتب الترجمة بين الوسمين <segment 0001> و <end segment> وفوق النص الأصلي.
+
+
اضغط على "ENTER" لتمر إلى الجزء الموالي.
+
+
+
للانتقال إلى أي جزء من النص، سواء كان ذلك إلى الفوق أم إلى التحت، اضغط مرتين على الجملة أو الفقرة التي تود فتحها.
+
إذا كنت تفضل الترجمة في حقل هدف فارغ فعليك تعديل هذا الخيار في خيارات ← سلوك التحرير....
+
+
+
عندما تضغط على "ENTER" فإن هناك أشياء عديدة تقع وراء الستار: يقوم أوميجاتي بإضافة زوج التجزئة (الجزء الأصلي و ترجمته) إلى ذاكرة الترجمة كما يقوم أوتوماتيكيا بترجمة الأجزاء المماثلة التي يجدها في ملفات المشروع الأخرى، كما يقوم بمسح ذاكرة الترجمة و مسرد المصطلحات باحثاً عن أي تطابق للأجزاء الموالية غير المترجمة.
+
+
استعمل ذاكرة الترجمة و تطابقات المسرد
+
+
تطابقات ذاكرة الترجمة
+
+
إذا وجد أوميجاتي أي تطابق جزئي (30% و ما فوق ذلك ـ انظر الدليل) للجزء القادم في ذاكرة الترجمة، فإنه يظهره في عارض التطابقات. يتم اختيار التطابق الأول في عارض التطابقات مبدئياً.
+
+
لإدخال تطابقات ذاكرة الترجمة من خلال عارض التطابقات إلى الحقل الهدف، يمكنك استعمال مختصرات لوحة المفاتيح التالية:
+
+
+
اضغط على Ctrl+I لإدخال التطابق المختار بموضع مؤشر الفأرة
+
اضغط على Ctrl+R لكتابة التطابق المختار فوق الجزء بأكمله.
+
+
+
في حال توفر تطابقات عديدة و رغبتك في عدم استعمال التطابق المختار:
+
+
+
اختر التطابق الذي تريده بعارض التطابقات: Ctrl+2 للتطابق الثاني المعروض و Ctrl+3 للتطابق الثالث، ...الخ
+
ثم استعمل المختصر Ctrl+I أو Ctrl+R
+
+
+
(يمكنك أن تأمر أوميجاتي بإدخال أي تطابق أول يتعدى نسبة تطابق معينة أوتوماتيكياً إلى الحقل الهدف مباشرة بعد فتح التجزئة. اضبط هذا الخيار مستعملاً: خيارات ← سلوك التحرير...)
+
+
تطابقات مسرد المصطلحات
+
+
إذا وجد أوميجاتي تطابقا بنسبة 100% بمسرد المصطلحات فإنه سوف يقوم بعرضه في عارض مسرد المصطلحات. و لا يمكن نقله باستعمال المختصرات.
+
+
عمليات البحث
+
+
يوفر أوميجاتي مجالا قويا من وظائف البحث. افتح نافذة البحث بواسطة Ctrl+Fو أدخل الكلمة أو الجملة التي تود أن تبحث عنها في خانة "ابحث عن".
+
+
يمكنك بدل ذلك أن تختار الكلمة أو الجملة في حقل التحرير (النص الهدف بالجزء النشط) ثم الضغط علىCtrl+F . يتم إدخال الكلمة أو الجملة في خانة "ابحث عن" أوتوماتيكياً في هذه الحالة.
+
+
+
إنشاء النصوص المترجمة
+
+
عندما تنتهي من ترجمة كل الأجزاء أو قبل ذلك أيضاً، يمكنك تحديث النصوص الهدف عن طريق استعمال الترجمات المحفوظة في ذاكرة الترجمة. للقيام بذلك، عليك أن تختار: مشروع ← إنشاء المستندات المترجمة من القائمة
+
+
حينها سيقوم أوميجاتي بإنشاء إصدارات لكل المستندات القابلة للترجمة في المجلد الأصلي للمشروع، سواء أكانت قد اكتملت ترجمتها أو لم تتم. و سيتم حفظ الترجمات الكلية أو الجزئية بمجلد الترجمات الهدف.
+
+
ﻹنهاء الترجمة، افتح الملفات الهدف في تطبيقاتها المقترنة بها للتحقق من المحتوى و تهيئة الترجمة. يمكنك حينها الرجوع إلى أوميجاتي للقيام بأي تعديلات ضرورية ولا تنس إعادة إنشاء المستندات.
+
+
+
+
كيف تتعامل مع النصوص الموسومة
+
+
أوميجا تي يضمن الحفاظ على هيئة المستند (خط عريض أو مائل و ما إلى ذلك) عن طريق استعمال علامات خاصة. علامات أوميجاتي تتشكل من حرف أو أكثر، متبوع برقم أو أكثر كما تستعمل أحياناً حرف "/" (مثلاً: <f0>, <br10/> </s2> ...الخ )
+
+
يجب عليك أن تتعامل مع كل وسم بحذر و أن تحرص على تواجده بوضع مناسب في الجزء الهدف.
+
+
مثال...
+
+
في هذه الأمثلة قمنا بإبراز كل وسم حتى نجعله واضحاً، لكنه لن يكون بارزاً في أوميجاتي. الواصفات الزرقاء هي واصفات HTML التي يقوم أوميجاتي بإهمالها لأنها تحصر الجزء كلياً، الواصفات الخضراء هي التي يقوم أوميجاتي بالتعامل معها لأنها متضمنة بالجزء و الواصفات الحمراء هي التي تظهر بأوميجاتي .
+
+
فيما يلي مثال لجزء في HTML:
+
+
<p>يمكن اختيار خط آخر عن طريق<b>خطاب</b>خط العرض. افتحه عن طريق<i>خيارات</i> →<i>...خط العرض</i>.عنصر القائمة يمكن تغيير حجم ونوع الخط من خلال الخطاب.</p>
+
+
حيث سيبرزه أوميجاتي هكذا باللون الأحمر:
+
+
يمكن اختيار خط آخر عن طريق<b0>خطاب </b0>خط العرض. افتحه عن طريق<i1>خيارات</i1> →<i2>...خط العرض</i2>عنصر القائمة... يمكن تغيير حجم ونوع الخط من خلال الخطاب.
+
+
فيما يلي مثال لكيفية الترجمة (مثال مأخوذ من اللغة الأفريكانية):
+
+
'n Mens kan 'n ander vertoonfont kies met die<b0>Vertoonfont</b0>-dialoogkassie. Kies<i1>Opstelling</i1> →<i2>Vertoonfont...</i2>op die kieslys. Die lettertipe én die lettergrootte kan met dié dialoogkassie verander word.
+
+
عندما يقوم أوميجاتي بإنشاء مستند الترجمة، سوف يظهر HTML على الشكل التالي:
+
+
<p>'n Mens kan 'n ander vertoonfont kies met die<b>Vertoonfont</b>-dialoogkassie. Kies<i>Opstelling</i> →<i>Vertoonfont...</i>op die kieslys. Die lettertipe én die lettergrootte kan met dié dialoogkassie verander word.</p>
+
+
التحقق من الواصفات
+
+
لا يقوم أوميجاتي باكتشاف الواصفات العائبة بطريقة أوتوماتيكية في مستند الترجمة. قبل تسليم النص إلى زبونك، تحقق من صحة الواصفات.
+
+
اختر أدوات ← تحقق من الواصفات من القائمة، سوف يظهر لك جدول به المقاطع التي لا تتناسب فيها واصفات النص اﻷصلي مع الهدف. اضغط على رقم الجزء.
+
+
سوف يتم الانتقال بك مباشرة إلى المقطع العائب في المحرر حيث يمكنك القيام بالتصحيح.
+
+
الواصفات الخاطئة قد تؤدي أحيانا إلى عدم القدرة على فتح المستند. و بالتالي، يتوجب عليك تصحيح كل وسم قبل إنشاء ملفات الترجمة.
+
+
ختاماً، يجب عليك أن تتأكد بدقة من تنسيق المستند من خلال فتحه بالعارض أو المحرر المقترن به.
+
+
+
+
+
diff --git a/OmegaT/docs/ar/version.properties b/OmegaT/docs/ar/version.properties
new file mode 100644
index 0000000..d4dce43
--- /dev/null
+++ b/OmegaT/docs/ar/version.properties
@@ -0,0 +1,2 @@
+# NOI18N
+version=1.7.3
\ No newline at end of file
diff --git a/OmegaT/docs/be/Edit.html b/OmegaT/docs/be/Edit.html
new file mode 100644
index 0000000..95f9846
--- /dev/null
+++ b/OmegaT/docs/be/Edit.html
@@ -0,0 +1,83 @@
+
+
+
+
+ Функцыі рэдагаваньня
+
+
+
+
+
+
+
+
+
+
+ Функцыі рэдагаваньня OmegaT скарыстоўваюцца
+ ў поле рэдактара, якім зьяўляецца тэкст
+ перакладу актыўнага сэгмэнта. Апэрацыі
+ рэдагаваньня абмежаваныя гэтым полем, г.зн.,
+ у поўны момант можна рэдагаваць толькі тэкст
+ перакладу ў актыўным сэгмэнце. Тэкст у якім
+ заўгодна тэкставым полі па-за палямі рэдактара,
+ аднак, можна вылучыць і скапіяваць у буфэр
+ для наступнай устаўкі.
+
+
+
+ OmegaT падтрымлівае звычайныя апэрацыі мышшу,
+ клявішы кіраваньня курсорам і спалучэньні клявішаў кіраваньня курсорам, а таксама
+ спалучэньні клявішаў для апэрацый вылучэньня, выразаньня і ўстаўкі. Яны, хутчэй за ўсё, будуць адрозьнівацца ў розных апэрацыйных сыстэмах.
+
Апэрацыі адмены і паўтору дзеяньня можна выканаць з дапамогай Ctrl-Z і Ctrl-Y адпаведна.
+
+
+
+ Да перакладаемага тэксту
+
+ нельга
+
+ прымяняць фарматаваньне. Фарматаваньне файла з
+ фарматаваньнем (у цяперашні час падтрымліваюцца
+ фарматы Staroffice/Openoffice.org і HTML) захоўваецца, і існуе
+ абмежаваная ступень ягонага кантролю
+ (Падрабязнасьці — у разьдзеле
+
+
+ Рэдагаваньне тэкстаў з тэгамі (разьметкай)
+ .)
+
+ Каб ужыць фарматаваньне, устаўце пазнаку,
+ напрыклад, "##" і адфарматуйце тэкст у іншай
+ праграме, напрыклад, OpenOffice.org пасьля кампіляцыі.
+
+
+
\ No newline at end of file
diff --git a/OmegaT/docs/be/FilesDirs.html b/OmegaT/docs/be/FilesDirs.html
new file mode 100644
index 0000000..f8aa8e7
--- /dev/null
+++ b/OmegaT/docs/be/FilesDirs.html
@@ -0,0 +1,64 @@
+
+
+
+
+
+ Файлы і дырэкторыі праекта
+
+
+
Праект OmegaT утрымлівае наступныя файлы і дырэкторыі.
+
Галоўная дырэкторыя праекта. Гэтая дырэкторыя ствараецца, калі ствараецца праект. Ейнае імя вызначае карыстальнік.
+
omegat.project. Калі ствараецца праект, OmegaT аўтаматычна стварае гэты файл і зьмяшчае яго ў гэтую дырэкторыю. Каб адчыніць праект у OmegaT, трэба адчыніць ягоны файл omegat.project.
+
+
<название проекта>.tmx. Гэта файл памяці перакладаў, экспартаваны праектам. Omegat стварае яго аўтаматычна і зьмяшчае ў гэтай дырэкторыі пры кожнай кампіляцыі праекта. Варта памятаць, што гэты файл памяці перакладаў утрымоўвае толькі сэгмэнты з праекта на момант яго апошняй кампіляцыі. У яго не імпартуюцца сэгмэнты з іншых файлаў памяці перакладаў у дырэкторыі /tm.
+
+
Дырэкторыя /source. Разьмясьцеце файлы для перакладу ў гэтай дырэкторыі пасьля стварэньні праекта і перад ягоным адкрыцьцём. Усе файлы ў гэтай дырэкторыі і ейных паддырэкторыях уключаюцца ў праект для перакладу, калі падтрымліваецца іхні фармат, і яны маюць адпаведнае пашырэньне імя файла.
+
+
*.txt,
+
*.xhtml, *.html,
+
*.properties,
+
*.sxw
+
+
Файлы зь іншымі пашырэньнямі могуць таксама быць імпартаваныя, калі іхнія пашырэньня супастаўленыя пашырэньням, азначаным па змаўчаньні.
+
Файлы ў /source, якія не імпартаваныя ў праект, перадаюцца бязь зьменаў у /target пры кампіляцыі праекта. Гэта дае магчымасьць ствараць люстэркі цэлых вузлоў web з /source у /target разам з загружанымі імі малюнкамі ў такіх фарматах як GIF або JPEG.
+
+
Дырэкторыя /glossary. Пасьля стварэньні праекта зьмясьцеце ў гэтую дырэкторыю глясар, які жадаеце выкарыстаць.
+
*.tab, *.utf8: файлы глясара.
+
+
Дырэкторыя /omegat. OmegaT аўтаматычна зьмяшчае ў гэтую дырэкторыю наступныя файлы пры стварэньні:
+
+
project_save.tmx: гэты файл ствараецца пры першым захаваньні праекта. Ён мае фармат TMX і зьяўляецца працоўнай памяцьцю перакладаў праекта.
+
+
word_counts: гэты файл утрымоўвае два лічыльніка словаў завершанага праекта: адзін, які ўключае 100%-ныя супадзеньні, і адзін, які іх выключае.
+
+
Дырэкторыя /target. OmegaT пры кампіляцыі зьмяшчае ў гэтую дырэкторыю файлы зь перакладамі.
+
Неперакладзеныя файлы перадаюцца з /source пры кампіляцыі.
+
Дырэкторыя /tm. Пасьля стварэньні і перад загрузкай праекта зьмясьцеце ў гэтую дырэкторыю файл(ы) памяці перакладаў, які(я) жадаеце выкарыстаць. Памятайце: незалежна ад таго, выкарыстоўваюцца або не раней створаныя файлы памяці перакладаў, OmegaT стварае працоўную памяць перакладаў для праекта, project_save.tmx у дырэкторыі /omegat пры захаваньні праекта, а таксама зьмяшчае экспартаваную памяць перакладаў у каранёвую дырэкторыю пры кампіляцыі праекта.
+
*.tmx: файлы памяці перакладаў, створаныя ў папярэдніх праектах. Файлы *.tmx павінны быць у фармаце TMX Узровень 1.
+
+
+
Зьмяненьне разьмяшчэньня файлаў і дырэкторыяў праекта
+
+
Дырэкторыі праекта ствараюцца пры стварэньні праекта. Па змаўчаньні яны групуюцца ў каранёвай дырэкторыі праекта, але для іх можна вызначыць іншыя месцы, клікнуўшы па кнопцы Прагляд. Такім чынам, можна трымаць памяці перакладаў у вызначаных дырэкторыях, напрыклад, і выбіраць жаданую дырэкторыю пры стварэньні новага праекта, замест таго, каб капіяваць файл памяці перакладаў у зноў створаную дырэкторыю /tm.
+
+
Каб зьмяніць разьмяшчэньне дырэкторыяў рэтраспэктыўна, г.зн., для існуючага праекта, выдаліце адпаведную дырэкторыю (Гэтага нельга рабіць, калі праект адчынены.) Пры наступным адкрыцьці праекта OmegaT вызначае, што адсутнічаюць некаторыя дырэкторыі, і выводзіць дыялёг выбару дырэкторыяў, дзе можна вызначыць новыя месцазнаходжаньні.
+
+
\ No newline at end of file
diff --git a/OmegaT/docs/be/Fonts.html b/OmegaT/docs/be/Fonts.html
new file mode 100644
index 0000000..132acdc
--- /dev/null
+++ b/OmegaT/docs/be/Fonts.html
@@ -0,0 +1,27 @@
+
+
+
+
+
+ Выкарыстаньне розных шрыфтоў і альфабэтаў
+
+
+
Зьмяніць экранны шрыфт можна праз мэню Налады > Шрыфт. Можна выбраць гарнітуру і кегль. Выбраны шрыфт выкарыстоўваецца толькі для вываду на экран, шрыфты, выкарыстаныя ў дакумэнтах з фарматаваньнем, не закранаюцца. Для выбару даступныя шрыфты, усталяваныя ў сыстэме.
+
Каб змагчыміць пераклад між двума мовамі, якія выкарыстоўваюць розныя альфабэты, трэба выбраць шрыфт, які мае сымбалі абодвух альфабэтаў. Усталюйце дадатковы шрыфт у выпадку неабходнасьці.
+
Калі ні адзін асобны шрыфт ня мае знакаў абодвух альфабэтаў, можна выбраць віртуальны шрыфт Java (напрыклад, «Serif»), і вызначыць гэты шрыфт такім чынам, каб ён выкарыстаў множныя рэальныя шрыфты. У гэтым выпадку зьвярнецеся да інструкцыяў на сайце OmegaT па наладах і зьмяненьню OmegaT.
Паданая ніжэй працэдура служыць для тлумачэньняў, не абавязкова абсалютна дакладна трымацца яе на практыцы.
+
+
Запусьцеце OmegaT.
+
+
Стварэце новы праект праз мэню Преект > Стварэньне праекта.
+
Зьявіцца навігацыйны дыялёг. У гэтым дыялёгу вылучыце прыдатную дырэкторыю для разьмяшчэньня праекта.
+
+
У полі «Імя файла» падайце імя (напрыклад, ABC) праекта і пацьвярдзеце.
+
Выклікаецца наступны дыялёг, на гэты раз зь пералікам дырэкторыяў праекта. У гэтым дыялёгу OmegaT прапануе стварыць новую дырэкторыю з абраным імем, (напрыклад, ABC), і пяць паддырэкторыяў у ёй. Разьмяшчэньне гэтых дырэкторый, дадзенае па змаўчаньні, можна зьмяніць, але для прыкладу пацьвярдзеце змаўчаньні. (Падрабязная інфармацыя пра файлы і дырэкторыі праекта — тут.)
+
+
Падайце коды мовы і лякалі для зыходнай і мэтавай моў, напрыклад, DE-CH для нямецкай(Швэйцарыя), EN-UK для ангельскай(Вялікабрытанія). Коды ня маюць асаблівага значэньня, калі толькі не мяркуецца абмен файламі памяці перакладаў з кліентамі або калегамі, у выпадку чаго варта дбайна трымацца патрабаванага стандарта (звычайна ISO).
+
+
OmegaT цяпер створыць галоўную дырэкторыю (таксама званую «каранёвай дырэкторыяй праекта») з раней вызначаным імем (напрыклад, ABC). У дырэкторыі праекта зьмяшчаюцца пяць паддырэкторыяў: /glossary, /source, /omegat, /target і /tm.
+
Знайдзеце файл для перакладу. Захавайце яго як тэкставы файл з пашырэньнем *.txt і зьмясьцеце ў /source.
+
+
Адчынеце створаны праект праз Праект > Падчыніць. OmegaT аўтаматычна зьвяртаецца да дырэкторыі, адчыненай у папярэдні раз. Каранёвая дырэкторыя праекта адлюстроўваецца з абразком OmegaT, які паказвае, што гэта — праект.
+
Адчынеце праект, вылучыўшы спачатку дырэкторыю праекта, пазначаную абразком (падвойным клікам або вылучыўшы і націснуўшы на «Адчыніць»), затым файл omegat.project. Не спрабуйце адчыняць іншы файл, напрыклад, зыходны тэкставы файл — не атрымаецца!
+
OmegaT адчыніць праект і пакажа тэкст файла ў галоўным акне OmegaT.
+
+
Зьмясьцеце курсор у мэтавае поле першага сэгмэнта, паміж тэгамі <сегмент 0001> і <конец сегмента>. Надрукуйце пераклад і выдалеце арыгінальны тэкст. Націсьнеце Enter, каб пацьвердзіць.
+
Паўтарайце гэтую працэдуру для кожнага сэгмэнта, пакуль увесь тэкст ня будзе перакладзены.
+
+
Цяпер трэба выбраць Праект > Захаваць памяць перакладаў, затым Праект > Адкампіляваць пераклад. Затым можна зачыніць OmegaT (Праект > Выхад).
+
+ 
+