Menu
▾
▴
#42 glossary for OmegaT
Dear Keith,
I want to present you an open source tool I've written for
publication and administration of terminology and
glossary in order to collaborate in your OmegaT project.
Its called XMLglossary and is XML based. You can
download and see examples on :
http://axitd.goshaky.com/
Unfortunately the program and documentation in the
moment is in german but I'm planning to localize it by
this year.
The front end is an Excel spreadsheet where the user
can administrate his glossaries in 5 languages
(de,en,fr,it,es).
The core competence of XMLglossary is that you can
publish your content to some HTML formats and to a
printout for each language (in PDF).
XMLglossary also has support for graphics, links
(internal and external) which are also relevant for the
output.
You can easily customize the output to your needs. I've
implemented a lot of parameters in a central
common_para.xsl to do so.
With every publication XMLglossary also exports
TMX1.1 and TMX 1.4 to import in a commercial CAT tool
or in OmegaT .
Additionaly XMLglossary exports an tab separated utf8
file which can be directly exported to an OmegaT
glossary directory.
The file contains the source, the translation language as
well as the definition in both languages which might help
the tranlator on his work.
In summary you have a complete tool to administrate,
publish and do translations with your teminology.
Some details regarding the technique:
Excel export its data via an VBA Macro to a pure XML
base. From there all is done with XSLT transformation
sheets. I transform the XML via XSLT to HTML (frame
sand no frames) and to XSL:FO which is transformed ba
Apache FOP to PDF. The transformations into the TMX
and the utf8 file are also done by XSLT transformation
stylesheets.
So the Excel frontend is no must for the user. I also
added a XMLglossary DTD if someone wants to work in
another XML Editor or whatever to collect his data.
So you might ask why I've choosen the commercial MS-
Excel as the frontend. Well the answer is that use the
tool in our company in an professional environment and
it has proofed as the easiest way for the user to work in
an environment he knows and which is widely flexible in
all tasks you can imagine when administrating your data
and is not as much restrictive as some other database
format. For example you can search/replace rename
throug all your terms, you can copy and paste, duplicate
them wherever you want and so on.
Perhaps in the future someone would also convert the
Excel macros to the Open Office application.
As I work in a documentation environment the aim of my
XML projects is to develop and improve the tools in the
Open Source community in order to use them in our
company.
I added some examples for the output formats in order
to let you have a look and evaluate them in the OmegaT
tool.
You can see some more examples on the
http://axitd.goshaky.com/ website. If you want to see
some professional outputs we created here I can also
provide you with them.
So why I'm writing to you? I want to XMLglossary be one
of the favourite tool for glossary administration in
OmegaT and want to become part of the team for your
great OmegaT project.
So if there might be some ways for a collaboration
please inform me
Many thanks in advance
regards
René Feuchtinger
Logged In: YES
user_id=488500
Hi Rene,
It seems I'm really late with response.
And it isn't looking like I can use your project: Download
Section (http://axitd.goshaky.com/download.html) is empty...
Maxym
Logged In: YES
user_id=545103
This is not platform-independent (Windows only).
Can we close this RFE?
Logged In: YES
user_id=915082
It looks like Rene's proposal is genuine. Maybe discuss with him more before making any decision. I checked the page and it seems to
project is evolving.
Logged In: YES
user_id=545103
Yes, his offer seems genuine, but the only way to really
make use of it, is by using Excel, which is totally
dependent on Windows. If someone would write a front end for
OOo though, it'd be interesting to bundle that with OmegaT,
as long as it doesn't have its own glossary manager. In the
end though, I think it's better to have an integrated
glossary manager (changes instantly reflected in your open
project), than a separate tool (time-consuming reload
necessary).
Logged In: YES
user_id=915082
there is a Java library to deal with excel files:
http://sourceforge.net/projects/jexcelapi/
since the involved format would not be that complex I suppose this library would be enough: no dependancy on windows/excel.
we could also consider asking him to port his work to OOo.
Logged In: YES
user_id=915082
for info:
http://schmidt.devlib.org/java/document-libraries.html
List of Java libraries to read and write document files
Logged In: YES
user_id=545103
Yes, his offer seems genuine, but the only way to really
make use of it, is by using Excel, which is totally
dependent on Windows. If someone would write a front end for
OOo though, it'd be interesting to bundle that with OmegaT,
as long as it doesn't have its own glossary manager. In the
end though, I think it's better to have an integrated
glossary manager (changes instantly reflected in your open
project), than a separate tool (time-consuming reload
necessary).
Logged In: YES
user_id=545103
Still, wouldn't it be much better if OmegaT supported
editing glossaries natively?
Logged In: YES
user_id=915082
definitely. on the fly glossary functions are something that we need to have. i was just commenting on the file format support issue.
as far as glossary formats are concerned, the current TSV format is nice but a generalized CSV filter+ TBX import would be nice too.
http://www.lisa.org/standards/tbxlink/tbxlink.html
re. CSV, most exports support by default field separator=", word separator=' if I am not wrong. Maybe using the first line of the file to
give hints to OmegaT as how to parse the data that follows would be a nice way to offer a lot of flexibility.
Logged In: YES
user_id=915082
Last but not least. Rene's tool is only a glossary management tool that exports to anything defined in the XSL. I should have considered
reading his whole comment before posting :) Sorry for the noise.
In case Rene is still reading this thread: 1) there are tools to adapt Excel VBA macros to OOo and creating an interface in OOo for
export to TBX/TMX or the current format TSV would be great. There is full XML filtering support in OOo and that would be too bad not
to use that.
2) glossary administration can be taken care of externally with specialized tools but what we need currently is an internal Java solution
that does on the fly update etc. The Excel approach is only adding a layer to the currently required process.
Conclusion: unless there are possibilities to port the proposed tool to OOo I think this item should be closed because it does not
correspond to the current direction of OmegaT.
Logged In: YES
user_id=545103
Ok, so we agree that OmegaT should have an internal glossary
editor, able to work with TSV, CSV, and TBX files? Can we
close this RFE then?
RFE for internal glossary editor:
1056853 - [2.0] Interactive glossary
http://sourceforge.net/support/tracker.php?aid=1056853
Logged In: YES
user_id=915082
agreed. "invalid" is a strong word for this RFE but I think that this is the only one available.
I hope we'll have OOo tools that offer proper generic glossary management functions in the future.