Issue 7 in pseudolocalization-tool: Digits?

[pseudolocal...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 7 by ebraminio: Digits?
http://code.google.com/p/pseudolocalization-tool/issues/detail?id=7

What about supporting digits here?

AFAIK this is also used on Android zz_ZZ and AFAICS there is not accented
digits or something like that but it is needed IMO. Native digits generally
are generated via String.format() on Android.



--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[pseudolocal...@googlecode.com]

Comment #1 on issue 7 by aha...@google.com: Digits?
http://code.google.com/p/pseudolocalization-tool/issues/detail?id=7

Not sure what you mean by "supporting digits", or in which
pseudolocalization method.

If you are talking about the "accenter" method, I guess it is possible to
map ASCII digits to U+FF10 - U+FF19 or to U+1D7D8 - U+1D7E1, but I don't
see how it is really important.

If you are talking about the "fakebidi" method, then the idea there is to
produce text that behaves like RTL text but remains readable to
Latin-script-only users. Thus retaining ASCII digit numbers without
alteration is perfectly fine, since all Hebrew and much Arabic text uses
ASCII digits, while mapping the ASCII digits to native Arabic or Farsi
digits is unacceptable because Latin-only users would not be able to read
them.

[pseudolocal...@googlecode.com]

Updates:
Status: WontFix
Owner: j...@jaet.org
Labels: -Type-Defect Type-Enhancement

Comment #2 on issue 7 by j...@jaet.org: Digits?
http://code.google.com/p/pseudolocalization-tool/issues/detail?id=7

Originally we tried substituting other Unicode digits that would remain
readable but be clearly marked as having gone through the translation
system. However, there were two problems:
1) we couldn't find a set of such characters that worked cross-platform
2) most digits aren't in translated strings anyway, but are generated by
number formatters that exist outside the translation system. So,
supporting it in pseudolocalization-tool would not be enough -- you would
also have to modify those libraries. For example, in GWT it is possible to
create new resources describing what digit characters to use for a
pseudolocale, but that is outside the scope of this library.

If you have a suggestion for #1 above that is cross-platform now, then
please suggest them. There isn't anything we can do for #2 other than to
provide documentation for how to do it in various environments.

[pseudolocal...@googlecode.com]

Comment #3 on issue 7 by aha...@google.com: Digits?
http://code.google.com/p/pseudolocalization-tool/issues/detail?id=7

Actually, looking at
https://code.google.com/p/pseudolocalization-tool/source/browse/trunk/java/com/google/i18n/pseudolocalization/methods/Accenter.java
now, it seems that it does map the ASCII digits to the circled ones.
Doesn't it?

[pseudolocal...@googlecode.com]

Updates:
Status: Accepted

Comment #4 on issue 7 by j...@jaet.org: Digits?
http://code.google.com/p/pseudolocalization-tool/issues/detail?id=7

Hmm, yes it does. I thought I had reverted that because some browsers
didn't support them.

So, I think all we can do here is to document how to get number formatters
to use these digits in various environments. I can write that up for GWT,
but I don't know how to do it in JVM or Android applications.

[pseudolocal...@googlecode.com]

Comment #5 on issue 7 by ebraminio: Digits?
http://code.google.com/p/pseudolocalization-tool/issues/detail?id=7

I didn't describe my suggestion well, I guess this would
Steps to reproduce:
1. Enable Android's developer menu
2. Choose zz_ZZ language
What I see actually?
I see on every Android related menu every string is accented but numbers not

What I like to see?
As an developer I also should check if numbers are localized and formatted
correctly.

How about Zalgofying them? http://eeemo.net/ or using Arabic or Indic
diacritics?

Sorry if this was actually an Android bug and not related here. Please move
it to related if is accepted.

[pseudolocal...@googlecode.com]

Comment #6 on issue 7 by j...@jaet.org: Digits?
http://code.google.com/p/pseudolocalization-tool/issues/detail?id=7

@aharon - do you know if Android is using this library for zz_ZZ? I'm
guessing not if the numbers are behaving differently.