janggi-korea wrote:[problem]
1. It is inconvenient due to a piece pic display error in the current version of Winboard. Previously, when used with the xiangqi variant it worked relatively well. It was just a problem because it doesn't recognize janggi rules. For example, the engine ended the game, but Winboard was still running. (Possibility of defining janggi rules using Marshall symbols?)
I don't understand. What is inconvenient? The current Jangqi implementation is just like the existing Xiangqi implmentation, except that it knows how the pieces move without any engine help. I don't see how that could ever be a disadvantage.
Also, when an engine ends the game (for whatever reason), it should notify WinBoard, and it would end the game too.
2.All Koreans use the "use piece font". So, in order to use the pieces that have been changed, there is a hassle of having to re-create the font. Currently, PAWN and KING are not displayed. Their pictures are different.
WinBoard has an option -fontPieceToCharTable, which can even be set from the View -> Board Themes menu ('Font piece to char'), which determines how internal symbols are mapped onto ASCII characters of a piece font. As long as all the pieces you need are present in the font, there would never be any reason to recreate the font. You can just change the mapping.
3. There is a problem with saving and loading the game. Previously, the FEN value was stored in the PGN together transformation. However, the game cannot be loaded by default at this time. (another start position)
* FEN value does not occur according to the starting position.
I am not sure what exactly the problem is. Note that PGN is entirely independent of what symbols WinBoard uses for the pieces. It only depends on what letters it uses as ID for the pieces. Which is determined by the pieceToCharTable. I don't know what game you tried to load, but there is the possibility that it contained a FEN that used different piece IDs as those that WinBoard expects. E.g. using B for an Elephant instead of E. That would of course not work. But there is a work-around for that: WinBoard has an option -pieceNickNames, with which you can define an alternative pieceToCharTable, of letters it should also recognize. In the WinBoard distro configured for Xiangqi I have set that to recongnize B and N as alternative names for E and H.
[Improvement Points and Wanted]
1. I want to implement janggi rules in JANGGI using existing picture symbols.
Because for the newly changed picture image, we have to work on everything again. (Example: Opening book, PGN file)
Well, we apparently have a conflict of interest here, because I would like Janggi to use Pawns as Pawns. It is plain silly to use Marshall symbols for Pawns. It was a mistake to ever use those, and I am not going to elevate mistakes to a standard.
I'd rather do the bit of extra work required to convert your book to the new internal piece encoding than to spoil the design of XBoard forever.
As I explained above, this has absolutely no effect on PGN.
2. Automatic opening book creation function activated (I want to implement it so that it can be created automatically without errors), it does not work at present.
Well, last time I tried it, it did work (for Chess). It is hard for me (read: impossible) to fix errors that do not occur. If you send me the PGN that you could not convert, I can try it, and diagnose the problem.
3. Activate the Ponder function (this seems to require the help of the engine developer.)
Not the help. The engine developer is the one who should do it. Nothing WinBoard can do about it.
4. I want to keep using hash memory (hash table) even if I play a new game. Clicking on a new game currently deletes the hash table.
* want a stronger play.
That also is purely an engine matter. WinBoard never asks the engine to clear its hash table; the engine is free to decide whether it wants to do that for a new game or not.
5. "Pass" function= OK (The modified version works normally when I click the clock.) . want start 1 move possible pass. This is because the PASS function is activated from the first 1 MOVE, and can be yielded by passing the first one to the other party.
Are you saying that turn passing does not work in the initial position? That is indeed unintended, and now that you mention it I can imagine why that is. (WinBoard has a special internal state at the start position; it is not yet in engine-human mode then.)
6. First start position selection menu => It doesn't seem to be applied yet. (The four rules are probably defined by engine commands? edite engine list?)
* I think it would be convenient to use them using pop-up windows.
* Add: In the long-term rule, black (elder) first selects the starting position, and next white select position.
The four rule sets (janggi, janggicasual, ...) have nothing to do with the start position, but whether point counting and Bikjang will be used. If the start position must be negociated (through pop-up windows or graphical screens), it is the engine that would have to do it. This is a logical necessity, as the engine should make its own choice. WinBoard already offers the possibility for en engine to trigger a popup with an arbitrary question, and send the user's answer back to the engine.
7. Standard moving coordinates used in Korea apply (board and engine output and PGN)
* Currently displayed in Chinese coordinates.
I don't want different variants to use different coordinates in WinBoard. PGN uses coordinates according to the PGN standard, and WinBoard's format for saving games is PGN.
PS. Is it difficult to apply janggi rules to Fairy-Max to make it a janggi engine? (Currently there is only one Janggi engine)
Yes, that would be hard, because Janggi has some very unusual rules. It violates the principle that moves of a piece are independent of its location. It violates the principle that capture is is 'piece-type blind' (because Cannons cannot capture Cannons). It has turn passing.
But perhaps more complex multi-variant engines (such as Sjaak II) can be configured to play it. I am not sure.