Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upReported background pattern labels don't match with the patterns in Excel 2016 #6092
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
@ManshulBelani, could you look into this please? CC @dineshkaushal. |
ManshulBelani
referenced this issue
Jul 5, 2016
Merged
making background pattern labels match with the patterns in formattin… #6124
nvaccessAuto
added
the
p2
label
Jul 5, 2016
michaelDCurran
closed this
in
#6124
Jul 24, 2016
added a commit
that referenced
this issue
Jul 24, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
josephsl
Aug 2, 2016
Collaborator
Reopening due to a major regression found:
@ManshulBelani, It seems background text is causing issues for translators, in that .po cannot be compiled into .mo.
Thanks.
|
Reopening due to a major regression found: @ManshulBelani, It seems background text is causing issues for translators, in that .po cannot be compiled into .mo. Thanks. |
josephsl
reopened this
Aug 2, 2016
josephsl
referenced this issue
Aug 2, 2016
Closed
Excel: Labels for background text causes errors when converting .po to .mo #6229
jcsteh
referenced this issue
Aug 8, 2016
Merged
Fix validation errors for some Excel background pattern strings in Poedit, xgettext, etc. #6235
jcsteh
closed this
in
#6235
Aug 8, 2016
jcsteh
added this to the 2016.3 milestone
Aug 8, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
leonardder commentedJun 18, 2016
NVDA reports Excel background patterns thanks to #3683. I've been looking into this to translate the patterns, and I noticed that the pattern names aren't in line with the names given in Excel 2016. For example:
Especially the latter two make absolutely no sense to me. Since #3683 is closed and included in 2016.2, I thought it would be best to report this in a new issue here.