Opened 20 months ago

Last modified 2 months ago

#164 new enhancement

Character count and Monospaced font

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

Description

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 20 months ago.

Download all attachments as: .zip

Change History (7)

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?

  • Keywords has-patch, needs-testing added

Tentative character count patch. Please test.

  • Keywords needs-review added; needs-testing removed
  • Keywords has-patch added; characters, font, has-patch, 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.

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

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.

Note: See TracTickets for help on using tickets.