This article is within the scope of WikiProject Chess, a collaborative effort to improve the coverage of Chess on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ChessWikipedia:WikiProject ChessTemplate:WikiProject Chesschess articles
One of the main reasons to have unicode chess pieces is definitely to use them in text mode. Showing a full text-mode board is definitely relevant here.
If the board doesn't display correctly in some browsers that is to be expected with unicode. We could replace it with an image of rendering in some terminal emulator. — Preceding unsigned comment added by SimonTheSaint (talk • contribs) 09:32, 28 October 2019 (UTC)[reply]
This is how the current version displays for me in Firefox.
Thanks for being willing to discuss this. As a note, additions to talk pages should normally go at the end. If you're starting a new section you can click the "new section" tab or link at the top of the page to start a new section at the end. These sorts of things will become second nature after you have done more editing.
I'm glad that the text board displays correctly for you as I was concerned that perhaps you knew it does not display correctly and added it to the article anyway. I checked Chrome, FF and Edge in Windows 10 and Chrome in Android and the display is bad in all four cases. I think it won't be easy to fix the display issue. My guess is that often the chess symbols are displayed using font substitution commonly used fonts might not have chess symbol glyphs. The substituted fonts have different widths which garbles the board display. I hold that broken things should not be left in articles, so until it displays correctly in the commonly used browsers using common fonts, I would say it shouldn't be in the article.
Even if the display issue were corrected, I would still not put it in the article. The board isn't drawn correctly since a chess board has light and dark squares which are not indicated in the text display.
Do we have an example of any WP:N software that displays chess positions in the way that you want to demonstrate? If the answer is no then I think this is a personal exercise and would also rule it out as lacking a WP:RS reliable source. Even if one particular program displays positions this way it may be that that fact deserves notice in an article on that particular program rather than here.
I've seen this method used in reddit and stackoverflow posts so I thought it might be good to have a reference. I added this to show what it looks like not to suggest this is a good way of doing it. There are some similar options for cases when the background cannot be changed: https://twitter.com/wobable/status/317724259784986624https://www.pinterest.com/pin/130885932892103650/ which we could also consider
For something less controversial: Let's add a version that uses changing background colors and is definitely relevant: gnuchess SimonTheSaint (talk) 14:10, 29 October 2019 (UTC)[reply]
gnuchess terminal graphics
Thanks for discussing this. I still don't agree with inclusion of the Chess symbols in Unicode#Chessboard using Unicode symbols for pieces and board and since we have had two different editors remove it, I was tempted to remove it again. But I think instead I'll leave it and we'll see if we can get someone else to register their opinion here. If they think it should be removed it would be three to one and it could go, but if they think it should stay it would be even at two–two and it could stay pending hearing from others. Quale (talk) 04:28, 30 October 2019 (UTC)[reply]
I'm not quite sure how this usually works. I think it's appropriate in this article and it doesn't really clutter up the article so I see no reason to remove it. I'm not married to it either. If you hate it just remove it again. ;) SimonTheSaint (talk) 12:19, 30 October 2019 (UTC)[reply]
Weird. The chess characters have to be significantly enlarged to be the same size as letters. Thus it becomes hard to just have Nf3 where the N symbol looks good next to the f3.--Sonjaaa 19:04, Sep 7, 2004 (UTC)
The problem is with fonts, as usual. — Monedula 19:19, 7 Sep 2004 (UTC)
Can anyone recommend an open source font that includes these symbols? --Ken Seehart 00:57, 12 April 2007 (UTC)
Note that :Arial Unicode MS and :Tahoma are MS proprietary and MS will not permit redistribution.
I have tried :Code2000, which is very complete, but the chess pieces don't look very good (the King looks like a cow head).
--Ken Seehart 00:57, 12 April 2007 (UTC)
Does anyone know about special notations using Unicode? I know of ± and ∓, but i would also like "+ over =" and "+ below =". Thanks in advance. -- Jokes Free4Me13:44, 30 March 2006 (UTC)[reply]
It might be a good idea for the article to cover these, along with the remaining Informator symbols that have been encoded in the Miscellaneous Symbols and Arrows block since Unicode 11.0. I'd do it myself but I was involved in the latter proposal so it might be considered a WP:COI. — Gwalla | Talk00:26, 7 April 2019 (UTC)[reply]
Since this board was created, Black Pawn was added to the emojis. The consequence is that black pawns tend to render differently. Quoting from the Unicode committee report.
“its representation can vary through the use of the following EVSes (Emoji Variation Sequences): <265F,FE0E> ♟ (text style) and <265F,FE0F> (emoji style). The Chess symbols in Unicode page (Wikipedia), which would be where most people would find information about this issue, is insufficient in that it does not mention the EVSes that are associated with U+265F ♟ BLACK CHESS PAWN, yet the text style EVS is used in the last row of its Chess Symbols table.”
Consequently, the two byte code pair <265n, FE0E> should be documented on this page. Using FE0E will encourage browsers, etc. to not use emojis for black pawns only. 70.54.26.226 (talk) 22:05, 1 May 2024 (UTC)[reply]
good job! now we just need to implement the chess rules in CSS or JS (a CSS implementation would be better as it tethers to people running without javascript support, NoScript & the likes, while a JS implementation would be much easier to implement, IMO..) Divinity76 (talk) 14:10, 17 June 2017 (UTC)[reply]
Multiple (81) instances of style="width:24pt; height:24pt; border-collapse:collapse; border-color: black; border-style: solid; border-width: 1pt 0pt 0pt 1pt" yay Alliumnsk (talk) 11:27, 25 March 2020 (UTC)[reply]
No, but then how many Wikipedia readers are aware of such technical details (I'm not, and I've worked with computers for decades!). That suggests either this article needs revision to ensure it works with common browsers "out of the box" or we need another one that works with common browsers "out of the box" so that we can link to it in other relevant articles (see Talk:Chess). —Preceding unsigned comment added by Philcha (talk • contribs) 01:40, 27 December 2007 (UTC)[reply]
Well I also just viewed the article with K-meleon (version 1.1.2, on Windows XP) and had no problems with the characters. I don't think I've changed much settings in K-meleon, though I may have added extra Unicode fonts in Windows, I'm not sure. Vadmium (talk) 09:45, 5 January 2008 (UTC)[reply]
Of course! Half of me feels ashamed for not thinking of that (the other half thinks "On Wikipedia I'm in user mode, not tech mode"). I've edited the article to point out the need to download an appropriate character set, with a ref. Thanks! Philcha (talk) 12:30, 5 January 2008 (UTC)[reply]
Alas, no. There is not even a real consensus for what to call them, much less what to represent them by. Without a graphical representation, they can't go in Unicode, which doesn't encode abstract characters with meanings but no fixed representations. So, no, not even the princess (B+N), empress (R+N), and amazon (Q+N) that just about everyone would have invented independently. Double sharp (talk) 15:50, 5 February 2016 (UTC)[reply]
Looking at the Unicode encoding, I see that the white pieces have consecutive numbers, but the black pieces all have the same number with a letter suffix. This suggests to me that the white pieces were an earlier, perhaps original part of the unicode and that black symbols were an afterthought. That does make some sense: if you want to transcribe a chess match using algebraic notation, you don't need to distinguish colour, because the first move of each pair is always white. In fact, I'm not sure what the black symbols are necessary for, though they are obviously cool. So just wondering: if anyone knows the history of this - when this came in the development of unicode, or even who motivated it - it would be an interesting two-sentence appendix. --Doric Loon (talk) 22:58, 2 February 2016 (UTC)[reply]
Anyone know of any effort to document the state information that is not directly a piece? For example, one board where the last move allow en-passant, vs one that is exactly the same piece placement, but the move order do not allow en-passant now. Most engines document that graphically in one way or another (highlight last move, arrows, etc).
or maybe even state that no engine UI bothers to show today, such as castleling opportunity being spent or not.