当在 android 中进行对话时，字符串被读取为数字而不是一个数字一个数字地读取它 [英] String is read as number rather than reading it digit by digit when talk back is on in android

问题描述

我有一个字符串9039662543"，当回话打开时，这个字符串在 4.3 android 设备中被读取为900万...."，在 4.3 设备以上它工作正常，通过读取九零三...".我应该怎么做才能解决这个问题?

I have a string "9039662543", and when talk back is on, this string is read as "nine million...." in 4.3 android devices, above 4.3 devices its working fine, by reading "nine zero three...". What should I do to fix this?

推荐答案

我假设这是一个电话号码?我不知道，因为没有格式.这是问题的核心.对此有多个修复.

I'm assuming this is a phone number? I can't tell because there is no formatting. Which is the heart of the problem. There are multiple fixes for this.

A:别管它.TalkBack 用户可以选择按视图、段落、句子、单词、字符等解析元素.如果用户无法通过上下文判断它是电话号码，则您需要更多上下文.号码本身没问题！

A: Leave it alone. TalkBack users have the option of parsing elements by view, paragraph, sentence, word, character, etc. If a user can't tell it's a phone number by the context, you need more context. The number itself is fine!

B:更好地格式化.(903)-966-2542 vs 9039662543，没有任何额外的上下文，是两条不同的信息.它可能仍会读为类似括号九百零三……"之类的内容，但更明显的是它是一个电话号码，并且这些块很容易跟踪.抱歉，我没有 4.3 之前的设备来查看实际公告是什么.

B: Format it better. (903)-966-2542 vs 9039662543, without any additional context, are two different pieces of information. It may still read out as something like "Parentheses nine-hundread and three........" but it will be more obvious it is a phone number, and the chunks are easy to keep track of. Sorry I dno't have a pre 4.3 device to check out what the actual announcement is.

C:覆盖内容描述.如果文本表示是:

C: Override the content description. If the text representation is:

文字:9039662543内容描述:9 0 3 9 6 6 2 5 4 3

Text: 9039662543 Content Description: 9 0 3 9 6 6 2 5 4 3

我建议不要使用这种方法.这两个值并不相同.仅仅因为您对公告感到不舒服并不意味着 TalkBack 用户会如此.当您习惯使用 TalkBack 时，您就会习惯于切换到不同的文本解析模式.不关心电话号码的用户会因分离版本的读取速度较慢而感到沮丧.让他们选择忽略它，让它以更压缩的形式迅速消失.此外，如果没有上下文，那么这两个数字并不真正代表同一件事.在这种情况下的解决方案是提供此上下文而不是更改演示文稿.分开不等于.

I recommend against this approach. These two values are not the same. Just because you are uncomfortable with the announcement doesn't mean a TalkBack user would be. As you get accustomed to using TalkBack you get accustom to switching to different text parsing modes. A user who doesn't care about the phone number would be frustrated by the slower read out of the separated version. Leave them the option of ignoring it, and having it blow by quickly in the more compressed form. Also, informatively, if there is no context those two numbers don't really represent the same thing. The solution in this case is provide this context NOT to change the presentation. Separate is NOT equal.

这篇关于当在 android 中进行对话时，字符串被读取为数字而不是一个数字一个数字地读取它的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！