XML Copy Editor HowTo
How do I build from source on Windows?
The first step is to install Dev-C++ and the relevant libraries. I'd like to be able to say that there's a quick way of doing this, but unfortunately this is not the case. (On Linux it's trivial, but I appreciate that often we don't have a choice in that regard.)
I recommend using the DLLs that ship with the binary download of XCE. In the case of Xerces-C, this saves you the trouble of building from source in msys.
For PCRE, make sure you build the library with Unicode support or download a version that has Unicode enabled.
For Libxml and Libxslt I have used the Zlatkovic binaries and headers. (Zlatkovic also provides iconv etc.)
For wxWidgets I recommend Fred Cailleau-Lepetit's excellent Unicode DevPaks for Dev-C++ (be sure to install both headers and the library).
The source itself should compile without warnings except for a few Xerces-C linker warnings – on Linux the same source compiles against Xerces-C without them.
For Aspell, simply download the Windows port of the current *-dev package from the GNU project to fetch aspell.h. That done, you can download the full binary installer. All you will need is the DLL (the executable itself is not needed).
PCRE (the PCRE home page at http://www.pcre.org/ suggests this port is slightly out of date though)
Zlatkovic.com Libxml, Libxslt, etc.
Fred Cailleau-Lepetit's wxWidgets DevPaks (alternatively, you could always download wxWidgets from the official wxWidgets download page)
GNU Aspell Windows port
How do I go about creating a new translation?
Contributed by SHiNE CsyFeK
1) For Linux users
That's quite easy. Download Xml-copy-editor(called XCE below :P),
unpack it. Go to the source directory src. Here you can see many ".cpp"
files and ".h" files. Input command:
$ xgettext -k_ -kwxPLURAL:1,2 --from-code=utf-8 *.cpp *.h
then you get a "messages.po" in the directory. That's the ".po" file we
need to translate. You need a tool to help you finish the translation
job. I recommend poedit, a fast and light-weight translation tool.
You can get it from http://www.poedit.net/ or http://poedit.sf.net/ .
They are the same. Install it then use to open the ".po" file,
There are a few things need to be filled into the poedit. Run poedit,
select "File"-"Preferences", fill in your name and email address blanks.
Back to main window, select "Catalog"-"Settings", fill the items like
"Project name and version:" -> "XML Copy Editor (your source version)"
"Team:" -> "(your translation team)"
"Team's email address:" -> "(your team's email address)"
"Language:" -> "(your native language)"
"Country:" -> "(your country)"
"Charset:" -> "(charset you currently using. utf-8 would be better)"
"Source code and charset:" -> "utf-8"
"Plurals Forms:" -> "nplurals=2; plural=(n != 1)"
OK! Now go to the main window and the rest thing is ... translate them
When you've finished translating the ".po" file, you can use:
$ msgfmt messages.po
to get the ".mo" file. Send the ".po" and ".mo" files to XCE's authors
2) For Windows users
Like in Linux, we should get XCE's source code and poedit windows
version. Uncompress the source and install poedit in "c:\poedit", then
open a "Command Window" by executing "cmd.exe". Go to the XCE's source
c:\poedit\bin\xgettext.exe -k_ -kwxPLURAL:1,2 --from-code=utf-8 *.cpp *.h
to a messages.po file. Setup poedit the same as in the Linux part, then
open the ".po" file you just created and translate all items. When you
close poedit, a "messages.mo" will be made automatically.
2. Update translation
1) For Linux users
Create a new version of "messages.po" file and rename it to "msg-new.po".
Copy the old version ".po" file to the same directory and rename it to
"msg-old.po", then run:
$ msgmerge msg-old.po msg-new.po >output.po
the "output.po" file is the new version of ".po" file with old
translations added. Then translate the "output.po" file.
2) For Windows users
Do the first part as Linux users, then run:
c:\poedit\bin\msgmerge.exe msg-old.po msg-new.po > output.po
translate the "output.po" file.
Written by SHiNE CsyFeK <csyfek@…>
How To Build XML-Copy-Editor 22.214.171.124 under Ubuntu 8.10
I don't know who would look at this but I did find troubles building XML-Copy-Editor under Linux.
Make sure that you have the required libraries installed first; these are the following libraries that my system needs before I build
this script will check for all the prerequisite libraries. If requirements are met, this script will generate a make script. Once the configure completes, run make command
After several minutes depending on your system, go to ./src directory, you will see the Xml-Copy-Editor executable.
NOTE: if you run and cannot see icon or images in the error dialog, this is because xmlcopyeditor points to wrong directory. This can fixed by changing the application directory in Preferences
if you didn't have a chance to read the INSTALL, here it is (126.96.36.199):
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file `config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.
The file `configure.in' is used to create `configure' by a program
called `autoconf'. You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.
The simplest way to compile this package is:
- `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
Running `configure' takes a while. While running, it prints some
messages telling which features it is checking for.
- Type `make' to compile the package.
- Type `make install' to install the programs and any data files and
- You can remove the program binaries and object files from the
source code directory by typing `make clean'.
Compilers and Options
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
Compiling For Multiple Architectures
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
By default, `make install' will install the package's files in`/usr/local/bin', `/usr/local/man', etc. You can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Some packages pay attention to `--enable-FEATURE' options to`configure',
where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The `README' should mention any `--enable-' and `--with-' options that the
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and `--x-libraries=DIR' to specify their locations.
Specifying the System Type
There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the `--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'. `configure' looks for `PREFIX/share/config.site' if it exists, then `PREFIX/etc/config.site' if it exists. Or, you can set the `CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
`configure' recognizes the following options to control how it
Use and save the results of the tests in FILE instead of `./config.cache'. Set FILE to `/dev/null' to disable caching, for
Print a summary of the options to `configure', and exit.
Do not print messages saying which checks are being made.
Look for the package's source code in directory DIR. Usually `configure' can determine that directory automatically.
Print the version of Autoconf used to generate the `configure'
script, and exit.
`configure' also accepts some other, not widely useful, options.
Written by Anh Trinh (anh.trinh.n@…)