In T232544#7350363, @Tacsipacsi wrote:

Actually I think the underlying issue is resolved (or at least definitely improved) in T213658: since the original and the translation will now use the same font, if they have approximately the same width in Tux, they will have approximately the same width in real usage as well. Just looking at them doesn’t provide a totally accurate result, but it’s neither what was asked for. (Yes, monospace vs proportional can make a difference, but unlikely to make a such huge one as in @Aklapper’s example above.)

I get your point but I believe Crowdin's intent was not to give an exact length in pixels, but rather as an estimation. Anyway, you can close this task since I have no clue how to do it myself (or even if users are allowed to close their own tasks) and I can always make a bookmarklet out of this for personal use.

IMHO, "22 / 194" provides the wrong impression that my translation must have less than 195 characters.

I stole this idea from the translation platform Crowdin, but I can see now that I have accidentally swapped the numbers: