The - legally binding - data protection clause demands
an answer of "JA" to show voter agreement for vote
processing. Hence UseVote should only accept "JA"
(in upper or lower case), but not "DAFUER" or some
other synonyms.
* Add bdsg_confirm (regexp) to usevote.cfg
* Change check in uvvote.pl accordingly
Signed-off-by: Thomas Hochstein <thh@inter.net>
If the ballot is not quoted, the current
regular expression will match $nametext
(minus its first word) as second line
of $votename.
Change regular expression to match only
certain common quote characters at beginning
of second line. (Perhaps it would be even
better to stop matching on empty lines ...)
Check for erroneus match on $nametext as a
safety measure.
Signed-off-by: Thomas Hochstein <thh@inter.net>
It's possible that ballots get mixed up when
a voter is participating in more than one
voting and sending the ballots manually (by
copying and pasting them into his mail client).
UseVote could - and should! - check that the
ballot belongs to the current voting by comparing
the ballot introduction ("WAHLSCHEIN fuer ...")
with the votename and throw an error if they
don't match.
* Add ballotintro (default: WAHLSCHEIN fuer) and
tpl_wrong_voting (default: wrong-voting) to
usevote.cfg
* Add messages to messages.cfg
* Modify ballot and ballot-personal templates
accordingly
* Add check to uvvote.pl
* Add error handling to UVmenu.pm
* Change UVmenu::menu call in uvcfv.pl due
to new parameter ($voting)
Signed-off-by: Thomas Hochstein <thh@inter.net>
VOTE_NO_VOTES is defined (and used) twice in
messages.cfg and uvvote.pl - once for "no mails
to process" ("Keine Stimmen zu verarbeiten") and
once for "you didn't vote in your ballot"
("Keine Stimmen abgegeben").
Change the first use to VOTE_NO_VOTEMAILS.
Signed-off-by: Thomas Hochstein <thh@inter.net>
