-
Notifications
You must be signed in to change notification settings - Fork 59
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
[/results/bidi-algorithm] Print driver support for FSI/PDI #280
Comments
@jeffreyatveridian thanks for mentioning that. I don't think i'll add it to the article, but i'll mention it to some Chrome developers. Is there a bug report already, or should we create one? |
Thanks,
I don't think there is a bug report already. Please help to create one.
Cheers,
Jeffrey
…On 6/05/21 11:29 pm, r12a wrote:
@jeffreyatveridian <https://github.com/jeffreyatveridian> thanks for
mentioning that. I don't think i'll add it to the article, but i'll
mention it to some Chrome developers. Is there a bug report already,
or should we create one?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#280 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATC5CDLPVD3I6LGN6BDRZRTTMJ4SHANCNFSM4YUCYS4Q>.
--
*Kuan-Yu (Jeffrey) Ke*
/Project Lead & Sales Engineer/
Veridian Logo <https://veridiansoftware.com>
Veridian Software, DL Consulting Ltd.
Phone: +64 7 857 0830 | Email: ***@***.***
***@***.***> | Visit:
www.veridiansoftware.com <https://www.veridiansoftware.com>
Veridian Facebook <https://www.facebook.com/VeridianSoftware/> Veridian
Twitter <https://twitter.com/veridiandigilib> Veridian LinkedIn
<https://nz.linkedin.com/company/dl-consulting_3/>
|
@jeffreyatveridian please go here https://bugs.chromium.org/p/chromium/issues/list to raise your issue. In the meantime, i'll close this. |
Will do! Thanks.
Ooops... where do I report a bug when a bug-report system has a bug... :D
I think I will just have to leave this problem in the air...
Jeffrey
…On 24/06/21 12:11 am, r12a wrote:
@jeffreyatveridian <https://github.com/jeffreyatveridian> please go
here https://bugs.chromium.org/p/chromium/issues/list
<https://bugs.chromium.org/p/chromium/issues/list> to raise your issue.
In the meantime, i'll close this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#280 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATC5CDNOXKRZ2N4WJN2FJO3TUHFQLANCNFSM4YUCYS4Q>.
--
*Kuan-Yu (Jeffrey) Ke*
/Project Lead & Sales Engineer/
Veridian Logo <https://veridiansoftware.com>
Veridian Software, DL Consulting Ltd.
Phone: +64 7 857 0830 | Email: ***@***.***
***@***.***> | Visit:
www.veridiansoftware.com <https://www.veridiansoftware.com>
Veridian Facebook <https://www.facebook.com/VeridianSoftware/> Veridian
Twitter <https://twitter.com/veridiandigilib> Veridian LinkedIn
<https://nz.linkedin.com/company/dl-consulting_3/>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
[source] (https://www.w3.org/International/i18n-tests/results/bidi-algorithm) [en]
Just a quick feedback. As of 2021-03-05, while working on one of our projects, we've noticed even though Blink Chrome and Blink Edge are both displaying the bidirectional characters correctly with FSI/PDI characters within the browser, but it seems the print driver is not handling those character properly. Not sure if this is helpful to your report.
Cheers,
Jeffrey
The text was updated successfully, but these errors were encountered: