-
Issue:
1. Getting weird printout on User comment field
Version: metadata-extractor-2.8.1.jar and xmpcore-5.1.2.jar
Target Device: Samsung Note 3 Running Android 5.0
I h…
-
This is a spin-off of #8994.
@Alizter @rgrinberg The current character choice for the TUI has several issues that could hurt portability. My concrete suggestion is to stick with **ASCII printable c…
-
This concerns changes introduced by PR #249, specifically [lint](https://github.com/zmap/zlint/blob/master/v3/lints/rfc/lint_subject_dn_not_printable_characters.go) `e_subject_dn_not_printable_charact…
-
I'm trying to make [pyenv-win](https://github.com/pyenv-win/pyenv-win) (packaged by Chocolatey) more usable with the help of shimgen: https://github.com/pyenv-win/pyenv-win/issues/352
I create python…
-
### Use case
The DropdownMenu widget requires roles, ARIA properties, and expected keyboard support to meet accessibility compliance requirements outlined in the Web Content Accessibility Guideline…
-
Continuation of the discussion in #4272
> [...] in my e-mail listing (index), some subject names shows those `?`.
>
> ```
> Google Payments | ??? ? ? ? ? ? ? ? ??Googl…
-
# Summary
I have a problem with the elpy output when I run the tests.
A lot of non printable shell characters are shown in the traceback and make the output unreadable.
Here is the part of th…
arael updated
2 years ago
-
**Is your feature request related to a problem? Please describe.**
Users that use international layouts and such can output special characters by for example typing `' + a -> á` before the letter, et…
-
Osmose flags the linefeed characters in the inscription textfield as non-printable. The wiki page suggests `|` or slashes `/`, but this approach is problematic because real objects might contain those…
-
Hi, I was looking at your `wcwidth` library for comparison, since in the utf8proc library we are also implementing a similar feature (see JuliaLang/utf8proc#2). The first disagreement that I came ac…