The designer of this FontStruction has chosen not to make it available for download from this website by choosing an “All Rights Reserved" license.
Please respect their decision and desist from requesting license changes in the comments.
If you would like to use the FontStruction for a specific project, you may be able to contact the designer directly about obtaining a license.
22 Comments
Silly question: why did you chose to design the knight facing to the right? I feel it would be more natural to have it facing left (although I can't really explain why :-).
@gferreira: on the "facing" of the Knight. It is a good point, and I can give you three possible answers. But let's have a joke first.
*************
The cowboy and his horse went into the saloon. As they stood at the bar the bartender turned around and asked him: why the long face?
*************
A1: I've made my sketches after a picture of a rose/cherrywood figurine, which happened to be in that position.
A2: As I experimented with bricks to shape a horse, by pure chance I hit upon this pretty configuration, or at least the core of it, and I was happy and content with ever since.
A3: This answer has strong implications with my forthcoming project, and I think it's not wise to talk about it right now.
Bilateral symmetry is a tricky phenomenon, not to be underestimated. I don't know whether it would look "more natural" the other way around or not. To me it's natural enough either ways. However, all commercial chess fonts (e.g. Linares, Hastings, Chess Alpha, just to name a few) have the Knight in the opposite position, so I think I ought to follow the tradition.
Speaking about chess fonts and traditions, there is a Unicode range dedicated to chess symbols (from uni2654 to uni265F), yet unsupported by FS. and there is built in support for in HTML (♔-♟) as well. I wonder why is it, that none of the fonts mentioned above have used it for their character map. They simply placed the figures according to some hobbit sense: white pawn to P, w king to K, w bishop to B, w rook to R, w queen to Q, w knight/horse to H, and the black ones to the corresponding lower case letters, so on and so fort. However, they are occasional and inconsistent if you compare and scrutinize them. Who should I follow to make a truly useable font for typesetting chess? Shall I invent my own keyboard layout?
J'ai choisi "la Défense Française" pour le titre au lieu du terme général "échecs" parce que ça sonnait bien. "Le Français" comme une ouverture dans les échecs a une réputation de la solidité et la résilience.
Votre question quant à la petite image à gauche j'ai répondu dans un message.
B - white Bishop on black square
b - white Bishop on white sq
H - white Horse/Knight on black sq
h - white Horse/knight on white sq
J - black Horse/Knight on black sq
j - black Horse/Knight on white sq
K - white King on black sq
k - white King on white sq
L - black King on black sq
l - black King on white sq
N - black Bishop on black sq
n - black Bishop on white sq
O - black Pawn on black sq
o - black Pawn on white sq
P - white Pawn on black sq
p - white Pawn on white sq
Q - white Queen on black sq
q - white Queen on white sq
R - white Rook on black sq
r - white Rook on white sq
T - black Rook on black sq
t - black Rook on white sq
W - black queen on black sq
w - black queen on white sq
Y/Space - White square
Z - Black square
Can you add the SUMA piece its similar to a two square pawn see https://www.vectorizer.io/images/93ceb7051bd0885b0d4a4ed85c741d7e/SUMA-blk.html or tiny.cc/samuraichess
Lovely 'dingbats', very detailed as contours only.
---
My (not-so-related) minimalist pixel art (just for the Live):
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░█░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░███░░█░█░█░░░█░░░░░█░░░░░░░░░░░░
░░░█░░░░█░█░░░██░░░░███░░█░██░░█░░
░░█░█░░░███░░░███░░████░░████░███░
░░░█░░░░░█░░░░░█░░░░░██░░░██░░███░
░░███░░░███░░░███░░░███░░████░░█░░
░█████░█████░█████░█████░████░███░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Chessboard Attack (2011, LCD) by Leszek Chmielewsk Daniel,
which I modified on 2016-09-19 as seen above.
Please sign in to comment.