Opened 15 years ago
Closed 14 years ago
#21800 closed submission (fixed)
new port: apertium 3.1.1
Reported by: | p.ixiemotion@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | apertium |
Description
Apertium is a machine translation platform, especially meant for closely related languages. It uses port:lttoolbox for finite state morphology, hidden Markov models for disambiguation, and finite-state three-stage chunk-based transfer.
This package provides the language-independent machine translation engine, including both translation tools (deformatters for ODT, HTML, DOCX, etc; TMX handling; the actual translation pipeline) and the tools necessary to create new language pairs. Language data is not included (there are a lot of language pairs available on sf.net/projects/apertium and in SVN though).
The Portfile is attached.
http://wiki.apertium.org/wiki/Apertium_on_Mac_OS_X_%28System%29 lists dependencies; however, I got it to build with only these ports active:
lttoolbox gawk pkgconfig expat gettext gperf libiconv ncurses ncursesw pcre zlib
(Although I don't know whether any of them are considered _build_ dependencies?) libxslt was necessary to build the language pairs apertium-nn-nb and apertium-en-es
I'm not sure whether the following ports are necessary anywhere:
m4 flex libtool help2man perl5.8 p5-locale-gettext
...so I left them out for now.
Attachments (1)
Change History (3)
Changed 15 years ago by p.ixiemotion@…
comment:1 Changed 15 years ago by p.ixiemotion@…
Ah, now I see also the following ports
m4 perl5.8 autoconf automake
are necessary to configure individual language pairs. Should they be added to the apertium port since pretty much all language pairs use them? Or should they be added as requirements to each pair?
comment:2 Changed 14 years ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Version: | 1.8.1 |
apertium portfile