Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

<Multi_key> <bar> <B> is a combination and a prefix at the same time #24

Open
dniku opened this issue Jan 2, 2016 · 5 comments
Open

Comments

@dniku
Copy link

dniku commented Jan 2, 2016

There is a set of combinations that start with <Multi_key> <bar> <B>:

<Multi_key> <bar> <B> <K>    : "♚" U265A  # BLACK CHESS KING
<Multi_key> <bar> <B> <Q>    : "♛" U265B  # BLACK CHESS QUEEN
<Multi_key> <bar> <B> <R>    : "♜" U265C  # BLACK CHESS ROOK
<Multi_key> <bar> <B> <B>    : "♝" U265D  # BLACK CHESS BISHOP
<Multi_key> <bar> <B> <N>    : "♞" U265E  # BLACK CHESS KNIGHT
<Multi_key> <bar> <B> <P>    : "♟" U265F  # BLACK CHESS PAWN
<Multi_key> <bar> <B> <D> <M>    : "⛂" U26C2  # BLACK DRAUGHTS MAN
<Multi_key> <bar> <B> <D> <K>    : "⛃" U26C3  # BLACK DRAUGHTS KING
<Multi_key> <bar> <B> <S>    : "☗" U2617  # BLACK SHOGI PIECE

However, <Multi_key> <bar> <B> is already reserved for

<Multi_key> <bar> <B> : "฿" U0E3F # BITCOIN CURRENCY SIGN, ORIGINAL THAI CURRENCY SYMBOL BAHT
@inaltoasinistra
Copy link
Contributor

We myght use the combination for ฿

@dniku
Copy link
Author

dniku commented Jan 2, 2016

I agree, for me it's a mystery who could need chess icons in the layout in the first place.

@Evidlo
Copy link

Evidlo commented Feb 13, 2016

Since it doesn't seem like these are too popular, could we map them to something longer, like:
<Multi_key> <Multi_key> <k> <i> <n> <g>

@clsn
Copy link
Collaborator

clsn commented Mar 29, 2017

There are a few prefix conflicts, most of which I'm blithely ignoring. Now that BITCOIN SIGN is coming into Unicode, we'll have to map it. I wonder, what about <Multi_key> <dollar> <B>, using <dollar> as a currency mnemonic? (Or remapping the chess stuff; that's also an option.)

@clsn
Copy link
Collaborator

clsn commented Mar 29, 2017

Oops, actually doesn't conflict at the moment. But still, <bar> <X> is generally double-struck X, conflicting with the chess usage... something to consider.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants