Opened 6 years ago

Last modified 3 years ago

#164 new enhancement

Character count and Monospaced font

Reported by: Dianakc Owned by:
Milestone: Future Release Priority: major
Version: 0.1 Component: interface
Keywords: has-patch Cc: sushkov


Beside contexts, I think characteres count and monospaced font can help translation process.

Sure, sometimes there's no way to fit a string in some languages, but that can help us figure out how long should be.

Attachments (1)

translation-row.php.diff (628 bytes) - added by vanillalounge 6 years ago.

Download all attachments as: .zip

Change History (9)

#1 @vanillalounge
6 years ago

Given that GlotPress is potentially "themeable", I'm not sure of the wisdom of forcing monospaced fonts for every situation. Character count, on the other hand, does make sense to me. Maybe in the "Meta" section of the string?

#2 @vanillalounge
6 years ago

  • Keywords has-patch needs-testing added; removed

Tentative character count patch. Please test.

#3 @vanillalounge
6 years ago

  • Keywords needs-review added; needs-testing removed

#4 @nacin
6 years ago

  • Keywords characters font needs-review removed

Is it possible that some translators might see a count of characters and find this to be a limit?

Also, it may not be accurate, due to HTML and sprintf placeholders, though that is also not much of a concern.

#5 @sushkov
5 years ago

  • Cc sushkov added
  • Milestone changed from Future Release to 1.0

#6 @markoheijnen
5 years ago

I like the idea of a character count. I can see the issue Nacin mentioned. The HTML and sprinf placeholder isn't a concern at all. This because you would use the original character count to the translate text. By doing that something like showing the string length difference would probably be more meaningful.

#7 @markoheijnen
4 years ago

  • Milestone changed from 1.0 to 1.1

#8 @markoheijnen
3 years ago

  • Milestone changed from 1.1 to Future Release
Note: See TracTickets for help on using tickets.