-
Notifications
You must be signed in to change notification settings - Fork 39
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
Bullet & Numbering #15
Comments
Also emoji. I see one emoji is expressed with |
@qimuxi1990 Yeah, I agree! I'd love to see these fixed (my use case has been very limited, thus the overall limited implementation here). Would you be interested in being co-maintainer of this project? If yes, I'll add you here and on npm! (But you'll have to tell me your npm account name. 😀) Please feel free to email me at |
@iarna Thank you very much for inviting me but I think I would not have sufficient time to be a co-maintainer and I did not got an npm account yet. ;-) |
Yeah, I get that. Mostly I just wanted to give you the ability to land your patches, when you have them, on your own, as my own ability to be here is limited too. |
It can be fixed by changing this function:
|
Dear @iarna
I just discover that fcharset2 Symbol is not supported here.
Due to the fact that it does not related to any window codepage. So it will never be handled by iconv.
However in rtf documents, bullet and numbering are frequently. I believe it would be pretty nice to have support on Symbols or simply Bullet & Numbering.
Here is an example rtf string:
Same thing possibly also happens to fcharset1 DEFAULT, and fcharset255 OEM. But I have not seen examples from my experience.
Thank you.
The text was updated successfully, but these errors were encountered: