how to become a maintainer about xcompose HOT 6 OPEN

Thanks so much! I am going to update my Xcompose right away with yours now. You might want to update the README.md on your page - it still points to kragen. A short intro for the programs and maybe the recommended way to set everything up would also be great. I am still lost on how to use the small programs, the recommended way to put everything together and if there are standard system compose sequences which reside in /usr/share, and if they are used, not used or shouldn't be used with your Xcompose.

from xcompose.

I moved over to https://gitlab.com/ekaunt/ext-compose

from xcompose.

You should fork the project. There are lots of stale things needing attention. Documentation, proper howto, switch to python3 for treeprint.py and scan4dups.py are just the start. I would love to see your contributions to the sequences as well.

EDIT: Since it was not on your main page, I overlooked that you already did this 2 weeks ago. Nvm. I tried to submit an issue to your project, but issues are not open. I would like to see the helper apps updated to python3, and where's the frakturcompose?

from xcompose.

I forked it a couple months ago, and so far I've added tons of diacritics, japanese syllaberies, hebrew, yiddish, palmyrene, and many of the "poor mans markup" characters (like bold, italics, cursive, double struck, small caps, super/subscript), plus many miscellaneous characters.

I also added a quick search tool that can check what the compose sequence for a character is, if one exists. or inversely, it can check if a certain sequence has been taken already.

I also added an easy bulk compose sequence generator to quickly add many similar/related characters. a gui for this program is in the works too.

Adding proper documentation and fixing the scripts are part of the todos.

I did not know issues aren't open. will fix that now

fraktur is in fancyletters.compose with the rest of the alphaneumeric characters

from xcompose.

I definitely need to work on that…

I definitely make use of the standard compose sequences, but many of the sequences have been intentionally overwritten bc theres a lot of redundancy in the standard set. (ex: ¢ can be c+|, |+c, C+|, or |+C, but with my compose sequences, '|' is used as the selector for double struck characters, so |+c is 𝕔, and |+C is ℂ)

To install my xcompose, do not follow the install script (I understand that I need to update the readme and the install script. I didn't think anyone would ever use my fork so I was just being lazy, but ill get around to it now), rather make a file ~/.XCompose and put the following into it:

include "%L"
include "%H/path/to/xcompose/base.compose"
include "%H/path/to/xcompose/fancyletters.compose"
include "%H/path/to/xcompose/emoji.compose"
include "%H/path/to/xcompose/modletters.compose"
include "%H/path/to/xcompose/japanese.compose"
include "%H/path/to/xcompose/hebrew.compose"
include "%H/path/to/xcompose/diacritics.compose"

"%H" means "~"

from xcompose.

Hi @grenzionky!

I forked it a couple months ago, and so far I've added tons of diacritics, japanese syllaberies, hebrew, yiddish, palmyrene, and many of the "poor mans markup" characters (like bold, italics, cursive, double struck, small caps, super/subscript), plus many miscellaneous characters.

This seems interesting but I can't find your fork. .Xcompose deserves more love :)

from xcompose.