Tagaini Jisho 0.2.3 released

[Alexandre Courbot]

A new Tagaini Jisho release has been made available.

http://www.tagaini.net/download

This release fixes many bugs and adds a couple of improvements, like a
much better dates handling (supporting relative and absolute dates)
and the possibility to save and organize searches in sets that
basically act like bookmarks.

New features include print preview (especially handy to evaluate the
size of a booklet) and a new reading practice mode, that puts studied
words that only contain studied kanjis in front of the user and ask
for the correct reading.

The user also gains more control over which entries to train with a
new train settings configuration dialog, that allows to filter entries
by score or last training date and to influence the order in which
entries should be appearing.

Changelog:

* Fixed display bug when selecting multiple entries in the results view
* Added "sets" that act like search bookmarks
* Added a "Train settings" configuration dialog
* New reading practice mode, where the user must guess the correct
reading of studied entries containing studied kanjis
* Added print preview options for regular and booklet printing
* Added page range and selection printing
* Added reset buttons to extenders
* Icons appear in result views for entries that are tagged or annnotated
* Training history not limited to last two weeks anymore
* Better dates handling, featuring both relative and absolute dates
* Added last trained date search option
* Extender buttons size now limited, tooltip displays entire
content when useful
* Uses flow layout to handle extender buttons
* Improved and simplified notes edit dialog
* ... plenty of small fixes and improvements

The main development efforts will new concentrate on the 0.3 series,
which will see a redesign of a good part of the lower-level code to
allow more powerful features to take place and should put the bases to
a 1.0 release. The 0.2 series may still see a couple more releases
with backported features.

As always, people willing to take over various side-aspects of the
software (binary packaging, user manual, ...) are more than welcome to
apply. ;)

[okido]

Hi Alexandre,

I build the 023 version today, builddb.py gave numerous errors but no
critical ones.
Tagainijisho was build with QtCreator SDK on openSuse 11.1, no
problems.

Good work, Okido

[Alexandre Courbot]

Hi,

> I build the 023 version today, builddb.py gave numerous errors but no
> critical ones.
> Tagainijisho was build with QtCreator SDK on openSuse 11.1, no
> problems.

Mmm, saying which errors would actually help. :) I suppose you refer to the few

Entry 1537710: re_restr found 0 potential results!

The can be safely ignored, as they are slight inconsistencies in the
JMdict and do not affect Tagaini's behavior.

By the way, I played a bit with OpenSUSE Build Service, and although I
cannot use it for the current version (because some packages need to
refer the same file - RPM limitation?), I'll make sure the next one
has RPM packages for the major RPM-based distros.

Alex.

[okido]

Hi, here they are:

nx4rd@linux-vs1x:~/tagainijisho-0.2.3> python builddb.py
amalgamation/sqlite3.c: In function ‘porter_stemmer’:
amalgamation/sqlite3.c:102281: warning: value computed is not used
amalgamation/sqlite3.c:102285: warning: value computed is not used
amalgamation/sqlite3.c:102298: warning: value computed is not used
amalgamation/sqlite3.c:102303: warning: value computed is not used
amalgamation/sqlite3.c:102309: warning: value computed is not used
amalgamation/sqlite3.c:102314: warning: value computed is not used
amalgamation/sqlite3.c:102323: warning: value computed is not used
amalgamation/sqlite3.c:102330: warning: value computed is not used
amalgamation/sqlite3.c:102373: warning: value computed is not used
amalgamation/sqlite3.c:102393: warning: value computed is not used
amalgamation/sqlite3.c: At top level:
amalgamation/sqlite3.c:100532: warning:
‘sqlite3Fts3IcuTokenizerModule’ declared ‘static’ but never defined
amalgamation/sqlite3.c: In function ‘fts3GetVarint32’:
amalgamation/sqlite3.c:94013: warning: ‘i’ may be used uninitialized
in this function
amalgamation/sqlite3.c: In function ‘dlrStep’:
amalgamation/sqlite3.c:94232: warning: ‘iDocidDelta’ may be used
uninitialized in this function
In function ‘memset’,
inlined from ‘exprDup’ at amalgamation/sqlite3.c:59422:
/usr/include/bits/string3.h:82: warning: call to
‘__warn_memset_zero_len’ declared with attribute warning: memset used
with constant zero length parameter; this could be due to transposed
parameters
amalgamation/sqlite3.c: In function ‘segdir_delete’:
amalgamation/sqlite3.c:95941: warning: ‘iEndBlockid’ may be used
uninitialized in this function
amalgamation/sqlite3.c:95941: warning: ‘iStartBlockid’ may be used
uninitialized in this function
amalgamation/sqlite3.c: In function ‘sqlite3DeleteFrom’:
amalgamation/sqlite3.c:68276: warning: ‘sContext.zAuthContext’ may be
used uninitialized in this function
amalgamation/sqlite3.c: In function ‘sqlite3Update’:
amalgamation/sqlite3.c:80766: warning: ‘sContext.zAuthContext’ may be
used uninitialized in this function
amalgamation/sqlite3.c: In function ‘optimizeFunc’:
amalgamation/sqlite3.c:99959: warning: ‘nReaders’ may be used
uninitialized in this function
amalgamation/sqlite3.c:99957: warning: ‘iMaxLevel’ may be used
uninitialized in this function
Building JMdict database
Creating JMdict DB...
[jmdict] Creating tables...
[jmdict] Inserting entries...
[jmdict] 10000 entries processed
[jmdict] 20000 entries processed
[jmdict] 30000 entries processed
[jmdict] 40000 entries processed
[jmdict] 50000 entries processed

Entry 1537710: re_restr found 0 potential results!

[jmdict] 60000 entries processed
[jmdict] 70000 entries processed
[jmdict] 80000 entries processed
[jmdict] 90000 entries processed
[jmdict] 100000 entries processed
[jmdict] 110000 entries processed
[jmdict] 120000 entries processed
[jmdict] 130000 entries processed
Entry 2441290: re_restr found 0 potential results!
[jmdict] 140000 entries processed
Entry 2477150: re_restr found 0 potential results!
Entry 2506800: re_restr found 0 potential results!
[jmdict] Inserting JLPT levels...
[jmdict] Creating tables indexes...
[jmdict] Optimizing database organization...
Building Kanjidic database
Creating Kanjidic2 DB...
[kanjidic2] Creating tables...
[kanjidic2] Inserting entries...
[kanjidic2] 1000 entries processed
[kanjidic2] 2000 entries processed
[kanjidic2] 3000 entries processed
[kanjidic2] 4000 entries processed
[kanjidic2] 5000 entries processed
[kanjidic2] 6000 entries processed
[kanjidic2] 7000 entries processed
[kanjidic2] 8000 entries processed
[kanjidic2] 9000 entries processed
[kanjidic2] 10000 entries processed
[kanjidic2] 11000 entries processed
[kanjidic2] 12000 entries processed
[kanjidic2] 13000 entries processed
[kanjidic2] Inserting JLPT levels...
[kanjidic2] Building kanji/component data...
[kanjidic2] Inserting strokes data...
[kanjidic2] Creating tables indexes...
[kanjidic2] Optimizing database organization...
nx4rd@linux-vs1x:~/tagainijisho-0.2.3>

None of them is critical, Okido

[Alexandre Courbot]

Ah, right, I forgot about the SQLite ones. Both are actually over my
control, unfortunately, as SQLite and JMdict are 3rd party software
and data. I could ignore them in the output but that would still not
fix them. ;)

Anyway, there's nothing to worry about that.

Alex.