[BUG]Widths table and Default Width not parsed for pdfCIDFontType0

[sshxmz]

Description

Based on code review, it is found that dict /DW, /W is not parsed for pdfCIDFontType0 rather than pdfCIDFontType2.
In many cases, /DW and /W are embedded in CID font Type 0.

Expected Behavior

/DW and /W are parsed just like pdfCIDFontType2.

Actual Behavior

Attachments

I wonder how can I upload the attachments privately.

[gunnsth]

You can email [email protected]

[sshxmz]

It was noticed that some issues were ingored. I wonder where is the rule of issues expected.
If some issues are not welcome, I will not file in them later.

[gunnsth]

@sshxmz Thanks for posting the issues, it is very valuable. The way issues work for us is that we prioritize issues from customers. For general issues we try to fit them into our development roadmap on an ongoing basis. It can sometimes take a while, but we will eventually get to it. In the meantime if someone has come up with a fix for certain issues, we are happy to accept PRs.

[sshxmz]

@sshxmz Thanks for posting the issues, it is very valuable. The way issues work for us is that we prioritize issues from customers. For general issues we try to fit them into our development roadmap on an ongoing basis. It can sometimes take a while, but we will eventually get to it. In the meantime if someone has come up with a fix for certain issues, we are happy to accept PRs.

Got it, thank you very much~~

[sshxmz]

Sorry, the mail was deliveried to may trashbox. I just notice it. I'll find them tomorrow and send them for you. Thank you very much.

…

----- Original Message ----- From: Gunnsteinn Hall <[email protected]> To: unidoc/unipdf <[email protected]> Cc: sshxmz <[email protected]>, Mention <[email protected]> Subject: Re: [unidoc/unipdf] [BUG]Widths table and Default Width not parsed for pdfCIDFontType0 (#157) Date: 2019-09-05 16:41 @sshxmz Thanks for posting the issues, it is very valuable. The way issues work for us is that we prioritize issues from customers. For general issues we try to fit them into our development roadmap on an ongoing basis. It can sometimes take a while, but we will eventually get to it. In the meantime if someone has come up with a fix for certain issues, we are happy to accept PRs. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[gunnsth]

@sshxmz We were just starting to look at this issue again. Did you have a way to reproduce the bug? How is the bug manifested? We need a way to reproduce a bug that results due to this.