Difference between revisions of "Northern Sámi and Norwegian/release"

From Apertium
Jump to navigation Jump to search
(Created page with 'Stuff to do before release: * make sure each possible chunk that might need postchunk operations has a postchunk rule ** so any pron/det, noun, adjective, verb')
 
Line 1: Line 1:
This page holds information about the release schedule for
Stuff to do before release:
[[apertium-sme-nob]].
* make sure each possible chunk that might need postchunk operations has a postchunk rule

** so any pron/det, noun, adjective, verb
==Issues==
===High priority bad translations===
What are the high-priority linguistic issues to deal with?

Would we gain a lot by inserting modals instead of adverbs for
Pot/Cond verbs? Is there a better, general, way to translate the
progressive? Should we get some of Francis' automatically discovered
lex.sel rules? And are there any "simple" constructions that we could
handle but don't yet?

===Derivations:===
Any [[Northern Sámi and Norwegian/Derivations|derivations]] that are
not handled should be removed from the analyser. Maybe we could have
a "negation" twol rule like

<pre>
? /<= UnhandledDerivations _ ; ! fail if analysis contains a tag from the set UnhandledDerivations
</pre>

If this works, we could probably also write a rule like

<pre>
? /<= AnyDerivationtag+ PoStag+ AnyDerivationtag+ _ ;
</pre>

to remove any derivations of derivations, since these are not handled
either unless there are explicit transfer rules for them. We should
remove any unhandled derivations before testvoc.
[[Northern Sámi and Norwegian/Derivations#Summary of fallbacks]]
contains the list of derivations that are and aren't handled.

===Testvoc===
Before release, we need to get [[testvoc]] out of the way – making
sure there are no #'s and @'s in the output. As yet we don't have a
way to create all possible surface forms from an [[HFST]] analyser,
but we can at least run as large a corpus as we can find through
sme-nob and look for # and @.

Postchunk rules are needed for any chunk containing a
determiner/pronoun/adjective/noun/verb, we can easily make sure each
possible chunk name has a postchunk rule (new chunks are created in
t1x with names like det_adj_nom, but may also be merged in t2x to
eg. det_adj_nom_conj_nom)

==Schedule==
{|class=wikitable
! Task !! Date
|-
| Work on high priority bad translations || until 2010-07-25
|-
| Remove unhandled derivations, ensure we have all postchunk rules || 2010-07-26…2010-08-01
|-
| Testvoc || 2010-08-01…2010-08-15
|-
| Tentative release date for apertium-sme-nob 0.1.0 || August 15th 2010.
|-
|}

Revision as of 08:02, 27 June 2010

This page holds information about the release schedule for apertium-sme-nob.

Issues

High priority bad translations

What are the high-priority linguistic issues to deal with?

Would we gain a lot by inserting modals instead of adverbs for Pot/Cond verbs? Is there a better, general, way to translate the progressive? Should we get some of Francis' automatically discovered lex.sel rules? And are there any "simple" constructions that we could handle but don't yet?

Derivations:

Any derivations that are not handled should be removed from the analyser. Maybe we could have a "negation" twol rule like

? /<= UnhandledDerivations _ ; ! fail if analysis contains a tag from the set UnhandledDerivations

If this works, we could probably also write a rule like

? /<= AnyDerivationtag+ PoStag+ AnyDerivationtag+ _ ;

to remove any derivations of derivations, since these are not handled either unless there are explicit transfer rules for them. We should remove any unhandled derivations before testvoc. Northern Sámi and Norwegian/Derivations#Summary of fallbacks contains the list of derivations that are and aren't handled.

Testvoc

Before release, we need to get testvoc out of the way – making sure there are no #'s and @'s in the output. As yet we don't have a way to create all possible surface forms from an HFST analyser, but we can at least run as large a corpus as we can find through sme-nob and look for # and @.

Postchunk rules are needed for any chunk containing a determiner/pronoun/adjective/noun/verb, we can easily make sure each possible chunk name has a postchunk rule (new chunks are created in t1x with names like det_adj_nom, but may also be merged in t2x to eg. det_adj_nom_conj_nom)

Schedule

Task Date
Work on high priority bad translations until 2010-07-25
Remove unhandled derivations, ensure we have all postchunk rules 2010-07-26…2010-08-01
Testvoc 2010-08-01…2010-08-15
Tentative release date for apertium-sme-nob 0.1.0 August 15th 2010.