After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 774753 - Clean some translatable strings
Clean some translatable strings
Status: RESOLVED FIXED
Product: balsa
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Balsa Maintainers
Balsa Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-11-20 16:50 UTC by Piotr Drąg
Modified: 2016-11-26 15:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Clean some translatable strings (37.33 KB, patch)
2016-11-20 16:50 UTC, Piotr Drąg
none Details | Review

Description Piotr Drąg 2016-11-20 16:50:44 UTC
Created attachment 340361 [details] [review]
Clean some translatable strings

While working on bug #774752, I noticed some improvements we could make to user-visible strings.
Comment 1 Peter Bloomfield 2016-11-20 21:43:37 UTC
Hi Piotr,

Again, many thanks for the patch--we appreciate the effort!

Regarding CC, BCC: When they are written with the colon, they refer to (or at least resemble) the RFC 2822/5322 header names "Cc:" and "Bcc:", and they should probably not be all-caps (and possibly not translated). Without the colon, they are just labels for the corresponding groups of recipients; I'm not sure what the convention is for capitalization: Yahoo mail has them in all-caps, Gmail has initial-caps. Does it make a difference to translators? Would it be better to drop the colons?

Regarding INBOX: RFC 3501 (the IMAP RFC) states that "The case-insensitive mailbox name INBOX is a special name...", so changing it to "Inbox" is certainly acceptable. However, in the IMAP context it is always written in all-caps, and to me at least that helps to distinguish it from my local /var/spool/mail/peter inbox. But should it be translated? If a user accessing Gmail using the IMAP interface sees the inbox labeled literally as "INBOX", then that is how the strings should present it.
Comment 2 Piotr Drąg 2016-11-21 14:02:33 UTC
Gmail (and I presume every other mail service) translates every single string in the user interface. Users who don't speak English, and that is a vast majority, wouldn't understand "Inbox", "Cc", "Bcc", etc. Imagine if you'd have "Odebrane" and "UDW". :)

As for the capitalization of abbreviations: English rules say that they should be in all caps. I doubt the creators of RFCs cared about it, though. I'm fine if you want them in initial caps, just please keep them translatable.
Comment 3 Peter Bloomfield 2016-11-23 01:05:00 UTC
Understood! I'll commit the patch, and wait to see if any issues arise. Albrecht Dreß <albrecht.dress@arcor.de> wrote[1]:

The German Thunderbird shows the IMAP INBOX in the folder tree as "Posteingang" (i.e. translated).  It always has a top-level by-account folder grouping which avoids possible confusion about many inbox'es...  In the subscribe dialogue, Thunderbird shows INBOX (all caps) even in the German GUI.  IIRC, Lookout also presents an IMAP INBOX in German as "Posteingang".  So the translation would make sense.

So in at least one place, INBOX is presented as is. That may be an oversight--we'll hope it gets fixed!

[1] https://mail.gnome.org/archives/balsa-list/2016-November/msg00018.html