163720 - Allow translator teams to find out whether pkcs#11 translations are short enough

Status: RESOLVED DUPLICATE of bug 1466942

(Core :: Security: PSM, defect, P5)

Description

[Kai Engert [:KaiE:]]

File pipnss.properties has some comments, that strings have a size restriction,
and that it is difficult to find out whether translated strings are short enough
or not.

We should offer a way for translator to find out easily, whether strings are
short enough or not.

Comment 1

[Ying-Lin Xia]

can we make the smartcard to accept long strings?

Comment 2

[Kai Engert [:KaiE:]]

Ying: No, I think we can't. It is not a single smartcard we would have to
change. If I understand correctly, the restriction comes from a *standard* that
has those maximum size retrictions. There are dozens of vendors who rely on that
standard.

Comment 3

[John G. Myers]

Mass reassign ssaux bugs to nobody

Comment 4

[John G. Myers]

Any suggestions for how this should work?

Comment 5

[Nelson Bolyard (seldom reads bugmail)]

Mass change "Future" target milestone to "--" on bugs that now are assigned to
nobody.  Those targets reflected the prioritization of past PSM management.
Many of these should be marked invalid or wontfix, I think.

Comment 6

[Dana Keeler (she/her) [:keeler]]

Well, we could just do the check at runtime and assert with an informative message if the strings are two long.

Comment 7

[Dana Keeler (she/her) [:keeler]]

Bug 1466942 made it so this restriction no longer applies (by not localizing these strings in NSS, but rather on the frontend when the users interacts with them).