2015-05-11 14:41 GMT+02:00 Kevin Brubeck Unhammer <[email protected]>:
>
> > Please give it a go!!!
>
>
> A *validating* editor that requires no setup is quite rare :-)
Yes, and it wasnt really that much work, as I found a component that can
nicely edits very big text files <https://github.com/nordfalk/jsyntaxpane>,
and even highlight them as XML.
The component also supports autocompletion and other stuff which eases
edition, but currently its not configured for the special needs of editing
DIX/transfer files (does anyone know Flex parsers (jflex.de)) ?
> And it manages to find the correct source file for dependent monolingual
> packages, neat.
Yes. The goal is to make it easier for newcomers to get startet on Apertium.
Fortunately the pairs are all structured in the same way.
>
>
I also like how it remembers the line number
> if you close it and re-open it.
>
It also remembers window position and -size for each file.
>
> Some bugs I found:
> * I can change stuff in a source file and exit the editor, and it
> doesn't save or ask about saving
>
Correct - Ive fixed this in SVN now.
> * If I introduce an error on e.g. line 70190 (or something way down in
> the file), it jumps to the wrong line number on Validate. You can try
> this in the bidix on nno-nob; just scroll to the bottom and change
> e.g. "rpar" to "bug" and it'll jump to line 65535. Oh, that number
> looks familiar :)
>
This is a bug in xmlling which apertium-validate-dictionary uses. xmlling
it gives the wrong line number. If I introduce an error in line 70190, and
rund
$ apertium-validate-dictionary apertium-nno-nob.nno-nob.dix
I will get:
*apertium-nno-nob.nno-nob.dix:65535: Schemas validity error : Element 's':
No match found for key-sequence ['xxxxrpar'] of keyref 'symbolNameRef'.*
*apertium-nno-nob.nno-nob.dix fails to validate*
See also
http://stackoverflow.com/questions/2410806/xml-schema-validation-for-large-schema-files
I guess we'll just have to wait for the fix for xmllint.....
> * If I click Edit Source for an .hfst file it tries to edit the binary …
>
> * apertium-$lang.$lang.lexc – the lexicon and pardefs
> * apertium-$lang.$lang.twol – morphophonological rules (like "turn -y
> into -ie before -s")
> I'm guessing most of the time, people will be editing the lexc. I don't
> know if there's an obvious way to assign >1 source per binary; it might
> not be worth it if the lexc is edited most of the time (and so far
> automorf.hfst's are the only binaries with >1 source). Maybe some actual
> HFST users should chime in first at least :-)
Ive added support for opening the .lexc file in SVN.
I havent tested it, as I dont have the tools for HFST installed.
Could you provide me with some example pairs and the file names generated
(ls -l in the pair).
> * If I click Edit Source and "apertium-nno-nob.nno-nob.dix~" exists,
> it'll prefer that.
>
Uh oh! Fixed in SVN
> * It's possible to drag the toolbar off (so it disappears until you
> close and re-open the file)
>
Thanks. Fixed in SVN
>
> Some ideas I had:
> * If it can't auto-find the source, maybe it could ask for (and store)
> the location of the source? (Should probably also be editable for the
> auto-found sources, in case it finds the wrong file.)
Most of the time I find the files, and if not I try some 'desperate
searches' using wildcards.
I'll do a select list of I get to the 'desperate' step and remember the
decision. The problem is, what if the user chooses the wrong file?
I would also need an option to select another file..
> * Setting for -j option for compilation
>
Ive changed to 'make -j 3' which would be OK for most use cases (I think
there are actually at most 2 things that can be done in parrallel when a
DIX has been touched, namely the 2 language directions)
> * Add the --trace option to -transfer/-interchunk, and on hover, show
> the rule number used (or some other UI?)
> * A "jump to rule number" button for editing transfer rules
>
>
I can add: If I use Ctrl-F to search a word, and then click in the editor
with the mouse, I jump back to where I was before searching
Good ideas, Ive added them to the wishlist on
http://wiki.apertium.org/wiki/Apertium-viewer#TODO
Ive compiled and pushed a new binary, you can check it out with
wget
https://svn.code.sf.net/p/apertium/svn/builds/apertium-viewer/apertium-viewer.jar
java -jar apertium-viewer.jar
Jacob
--
Jacob Nordfalk <http://profiles.google.com/jacob.nordfalk>
javabog.dk
Androidudvikler og -underviser på DTU
<http://www.cv.diplom.dtu.dk/Diplomuddannelser/IT-Diplomuddannelsen/Valgfrie-moduler/Mobilapplikationsudvikling/Formaal-og-laeringsmaal>
og Lund&Bendsen
<https://www.lundogbendsen.dk/undervisning/beskrivelse/LB1809/>
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
