Show opening names

[GoogleCodeExporter]

The opening-book-side-panel could support showing the names of the openings
provided.
This would look good using a multilined treeview, only adding the name line
when the opening i changing.

Original issue reported on code.google.com by lobais on 1 Jan 2008 at 10:05

[GoogleCodeExporter]

Using a list like http://www.geocities.com/siliconvalley/lab/7378/eco.htm we 
would
also be able to add the ECO tag in pgn files.

However this might lead to some problems for the translators.

Original comment by lobais on 1 Jan 2008 at 10:08

[GoogleCodeExporter]

A config option (default=disabled, similar to show cords) can be good too.
The translation at least to hungarian is not problem.

Original comment by gbtami on 11 Jan 2008 at 7:54

[GoogleCodeExporter]

Hm yeah, that might be an idea.
Actually we might be able to find list in many different languages. Wikipedia 
has:
    * Български
    * Česky
    * Deutsch
    * English
    * Français
    * Italiano
    * 日本語
    * Slovenščina
    * Svenska
Perhaps it should only be default=disabled for languages that haven't got it 
translated?

Original comment by lobais on 11 Jan 2008 at 5:43

[GoogleCodeExporter]

I think, it should be disabled by default genrally, similar to show chords, to 
not
scare away hobby/beginner players.

Original comment by gbtami on 11 Jan 2008 at 6:44

[GoogleCodeExporter]

If there is no language file for it you can show the name in english and for 
Deutsch
(German) I can do the translation :)

Original comment by maxmust...@gmail.com on 22 Mar 2009 at 12:57

[GoogleCodeExporter]

Issue 411 has been merged into this issue.

Original comment by gbtami on 30 Mar 2009 at 7:09

[GoogleCodeExporter]

I agree: This is a very good idea.

But: We should not use a sequence of move, as this sequence is not fixed. For 
example both "1.e4 c5 2. Nf3 Nc6 3. d4 xd4 4. Nxd4 Nf6 5. Nc3" and "1.e4 c5 2. 
Ne2 Nc6 3.  Nc3 Nf6 4.d4 xd4 5. Nxd4" lead to same position. Happens not in 
practice? I played the second sequence (as Black) yesterday.

So generally we should use FEN-codes to determine the opening, as they identify 
a position clearly. Of course someone could write a script to get fencodes from 
such sequences…

Keba

Original comment by MarioFu...@aol.com on 15 Mar 2011 at 5:58

[GoogleCodeExporter]

This could be shown in the annotations panel if enabled.
Can you remember if there is code for it, in that new opening book module?

Original comment by lobais on 3 Jul 2011 at 12:31

[GoogleCodeExporter]

Implemented it in gbtami-eco clone here:
http://code.google.com/r/gbtami-eco/source/checkout

FEN strings in eco.py was generated from
http://www.chessville.com/downloads_files/instructional_materials/ECO_Opening_Va
riations.zip 

I was thinking about using sqlite instead of a big dict, but this was the easy 
way to make opening names translatable. What do you think? 

Original comment by gbtami on 30 Nov 2011 at 5:13

• Changed state: Started

[GoogleCodeExporter]

Changed to use sqlite.

Running pgn2fen.sh will produce the eco.db from lang/*/eco.pgn files.
At this moment da, de, es, hu languages has eco.pgn files.
They were converted with utilities/eco-*.py scripts from respective wikipedia 
pages.

The lang/*/eco.pgn files need some review, as some contain too long summary 
style Opening tags.

Next step will be changing from FEN to polyglot hash values.

Original comment by gbtami on 4 Dec 2011 at 9:37

[GoogleCodeExporter]

Done. Please test!

Original comment by gbtami on 5 Dec 2011 at 10:05

[GoogleCodeExporter]

Works good, nice job!

Original comment by mattgatto on 8 Dec 2011 at 2:07

[GoogleCodeExporter]

Original comment by gbtami on 2 Apr 2012 at 5:34

• Changed state: Fixed