Migrate Microsoft Word documents in pre-Unicode Ethiopic fonts into a Unicode font supporting Ethiopic script. The converter presently provides support for eleven legacy (non-Unicode) systems and their respective fonts:
- Agafari
- AGF - Zemen
- AGF - Dawit
- AGF - Ejji Tsihuf
- AGF - Rejim
- AGF - Yigezu Bisrat
- Brana 90
- Brana I
- Brana II
- Feedel
- Geezigna
- Feedel
- Geez
- GeezII
- Feedel "New"
- GeezA
- GeezB
- GeezNewA
- GeezNewB
- GeezSindeA
- GeezSindeB
- ZewdituA
- ZewdituB
- GeezNet
- GeezFont
- GeezAddis
- geezBasic
- geezDirib
- geezLong
- GeezThin
- Ge'ezSoft
- GeezType
- GeezTypeNet
- Power Ge'ez
- Ge'ez-1
- Ge'ez-2
- Ge'ez-3
- Ge'ez-1 Numbers
- Samawerfa
- Addis98
- Blknwt98
- Visual Ge'ez
- VG2 Agazian
- VG2 Main
- VG2 Titles
- VG Geez Numbers
- Visual Ge'ez 2000
- VG2000 Agazian
- VG2000 Main
- VG2000 Titles
The conversion mappings come directly from the long defunct LibEth C language library which supported conversion of many more legacy encoding systems. Support for additional encodings systems can be ported from LibEth as the need arises. Please feel free to request support for additional systems.
This repository may be imported into Eclipse as a simple Maven Java project. The "Eclipse IDE for Java Developers" download option will include both Maven and Git integration, no additional installation will be needed to build this project. Maven in turn will retrieve all dependencies, primarily the docx4j (6.1.0) and ICU (63.1) and Java libraries.
- Windows EXE (Java bundled internally)
- Windows MSI (Java bundled internally)
- Mac DMG (Java bundled internally)
- Jar (Best if Java already installed)
- Read the notes on the latest updates.
- Select one or more Microsoft Word files (files must be in .docx format).
- Select the "Font In" (optional, supported fonts will be autodetected)
- Select the "Font Out"
- Click "Convert File(s)"
- Converted files will automatically open.
If your document contains more than one legacy font system, you may convert the fonts one at a time where the output document of the first conversion is used as the input document of the 2nd conversion and so on.
In the GitHub the "releases" folder you can find and download the "DocxConverter-0.8.0-full-gui.jar" file. This version contains the converter and all of its dependencies (jar libraries). Double clicking the jar file will launch a user interface where fonts and files may be selected via mouse and menus.
Output files will have the name of the selected output font appended to them. For example if "Abyssinica SIL" (the default) is selected as the output font name, an input file named "MyFile.docx" will have the output name "MyFile-Abyssinica-SIL.docx".
The application uses the Abyssinica SIL font as a default for output. The "Nyala" font that comes with Microsoft Windows and "Kefa" which comes OSX are other output options. The full list of output font options:
- Abyssinica SIL
- Bembino
- Brana
- Kefa
- GS Mahtem Unicode
- Nyala
- Power Geez Unicode1
If your desired font is not available for output, you may still use it by selecting text and changing the font style to another Unicode compliant font for Ethiopic.
The Docx Converter has been tested on a small sample of Amharic documents that covers most, but not all of, the Ethiopic syllabary. Testing is thus not comprehensive and is limited by the corpus sample available for testing. Conversion errors will likely be found as new documents uses letters not found in the testing corpus.
Conversion issues may also be found when documents produced by additional versions of Microsoft Word are tested, or for documents produced by other word processors that support the .docx format. Conversion may also fail for more complex formatting such as for tables which have not been tested.
Issues can be reported to the author directly, or via the GitHub issues tracker for the project.
If nothing happens when you double click the "DocxConverter-0.8.0-full-gui.jar" file, and you are certain that Java is installed on your Windows system, you likely need to fix the Window's registry. Try downloading and launching Jarfix to fix the registry.