Difference between revisions of "Apertium-view"
Jump to navigation
Jump to search
m (Text replacement - "(chat|irc)\.freenode\.net" to "irc.oftc.net") |
|||
| (21 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
{{Github-unmigrated-tool}} |
|||
{{TOCD}} |
{{TOCD}} |
||
Apertium-view is a little program which can be used to view and edit the output of the various stages of an apertium translation. |
Apertium-view is a little program which can be used to view and edit the output of the various stages of an apertium translation. |
||
| Line 7: | Line 8: | ||
Currently, the program is in its early stages and it will take some time before it becomes fully usable. But if you are a developer with some knowledge of Python and PyGTK, you can already dive in. |
Currently, the program is in its early stages and it will take some time before it becomes fully usable. But if you are a developer with some knowledge of Python and PyGTK, you can already dive in. |
||
== What you need == |
|||
* The [[D-Bus_service_for_Apertium|Apertium D-Bus Service]] |
|||
* A working Apertium 3.0 installation (note: this must be installed) |
|||
* The python bindings for the GTK SourceView V 2.0 module if you want syntax highlighting |
|||
== Getting apertium-view == |
== Getting apertium-view == |
||
'''Note:''' After Apertium's migration to GitHub, this tool is '''read-only''' on the SourceForge repository and does not exist on GitHub. If you are interested in migrating this tool to GitHub, see [[Migrating tools to GitHub]]. |
|||
Check out the <code>apertium-tools/apertium-view</code> from the subversion repository. |
Check out the <code>apertium-tools/apertium-view</code> from the subversion repository. |
||
| Line 14: | Line 23: | ||
== Running apertium-view == |
== Running apertium-view == |
||
If you installed the D-Bus service for Apertium correctly, Apertium-view should just work (you should only have to run <code>python apertium-view.py</code>). If it fails to start up, then there might be a problem with your D-Bus setup. Have a look at the [[D-Bus_service_for_Apertium|D-Bus page]] for possible solutions, or come and ask for help in #apertium on irc.oftc.net. |
|||
=== Configuring apertium-view === |
|||
=== Testing unreleased language pairs from source === |
|||
Edit the contents of <code>config.py</code> to reflect you installation setup. |
|||
<code>apertium_bin_path</code> is the path of the directory containing the Apertium executables. <code>apertium_dict_path</code> is the path to directory on your computer containing all of the compiled language pairs. On my computer it's <code>/usr/local/share/apertium</code>. This directory contains <code>apertium-en-af</code>, <code>apertium-en-ca</code>, etc. |
|||
You need to install your language pair it in /usr: <code>./configure --prefix=/usr; make; make install</code> (the last as root). |
|||
=== Executing the program === |
|||
If <code>make install</code> fails with <code>stat() './en-eo.mode': No such file or directory</code>, then try first <code>ln -s modes/* .</code> |
|||
Apertium-view is very user-hostile at the moment and it won't even properly tell you what you did wrong if you pass it the wrong flags. |
|||
The format is |
|||
<pre> |
|||
$ python apertium-view.py <language code> <modes file path> [<mode code>] |
|||
</pre> |
|||
The language code is something like <code>en-af</code> or <code>en-ca</code>. The modes path is the path to your modes XML file. The mode code is optional and refers to the name of a mode in the modes file; if you omit it, the first mode is used. |
|||
==Feature requests== |
==Feature requests== |
||
| Line 36: | Line 36: | ||
* Automatically resizing panes to fill the screen (when others are minimised) |
* Automatically resizing panes to fill the screen (when others are minimised) |
||
* Syntax highlighting |
* Syntax highlighting |
||
::tags are #aaaaaa, ^ and $ are #009900 { } are #999900 @ * # are #990000 and [] are #aaaaff |
|||
* Moving chunks as units rather than text. |
* Moving chunks as units rather than text. |
||
* Configuration / choosing language pair in the GUI. |
* Configuration / choosing language pair in the GUI. |
||
* Option to be able to click on an analysis to remove it. (basically, when you click in between / /, it removes the part in between. Would need CTRL+Z to be able to restore analyses (see below). |
|||
* Some kind of undo on a per text-pane/stage basis. |
|||
* <s>Ability to detach windows (particularly input and output windows).</s> |
|||
* Scroll panes down when they fill with more information. |
|||
* Remember settings when closed. |
|||
==Related software== |
|||
* [[Apertium-viewer]] is an improved version, which does not require dbus and which is written in Java |
|||
* [[Apertium-tolk]] is similar to, but much simpler than Apertium-view. It only has an input window and an output window. Where Apertium-view is aimed at developers, Apertium-tolk is intended to be as user friendly as possible. |
|||
[[Category:Tools]] |
[[Category:Tools]] |
||
[[Category:User interfaces]] |
|||
Latest revision as of 06:26, 27 May 2021
Note: After Apertium's migration to GitHub, this tool is read-only on the SourceForge repository and does not exist on GitHub. If you are interested in migrating this tool to GitHub, see Migrating tools to GitHub.
Apertium-view is a little program which can be used to view and edit the output of the various stages of an apertium translation.
The various stages update while you type, and a change made in any one pane updates the subsequent stages.
Currently, the program is in its early stages and it will take some time before it becomes fully usable. But if you are a developer with some knowledge of Python and PyGTK, you can already dive in.
What you need[edit]
- The Apertium D-Bus Service
- A working Apertium 3.0 installation (note: this must be installed)
- The python bindings for the GTK SourceView V 2.0 module if you want syntax highlighting
Getting apertium-view[edit]
Note: After Apertium's migration to GitHub, this tool is read-only on the SourceForge repository and does not exist on GitHub. If you are interested in migrating this tool to GitHub, see Migrating tools to GitHub.
Check out the apertium-tools/apertium-view from the subversion repository.
Running apertium-view[edit]
If you installed the D-Bus service for Apertium correctly, Apertium-view should just work (you should only have to run python apertium-view.py). If it fails to start up, then there might be a problem with your D-Bus setup. Have a look at the D-Bus page for possible solutions, or come and ask for help in #apertium on irc.oftc.net.
Testing unreleased language pairs from source[edit]
You need to install your language pair it in /usr: ./configure --prefix=/usr; make; make install (the last as root).
If make install fails with stat() './en-eo.mode': No such file or directory, then try first ln -s modes/* .
Feature requests[edit]
Removing scrollbars when not wanted.Allow users to set 'mark unknown words' or not.- Automatically resizing panes to fill the screen (when others are minimised)
- Syntax highlighting
- tags are #aaaaaa, ^ and $ are #009900 { } are #999900 @ * # are #990000 and [] are #aaaaff
- Moving chunks as units rather than text.
- Configuration / choosing language pair in the GUI.
- Option to be able to click on an analysis to remove it. (basically, when you click in between / /, it removes the part in between. Would need CTRL+Z to be able to restore analyses (see below).
- Some kind of undo on a per text-pane/stage basis.
Ability to detach windows (particularly input and output windows).- Scroll panes down when they fill with more information.
- Remember settings when closed.
Related software[edit]
- Apertium-viewer is an improved version, which does not require dbus and which is written in Java
- Apertium-tolk is similar to, but much simpler than Apertium-view. It only has an input window and an output window. Where Apertium-view is aimed at developers, Apertium-tolk is intended to be as user friendly as possible.
