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 592410 - Take advantage of Unicode
Take advantage of Unicode
Status: RESOLVED OBSOLETE
Product: rhythmbox
Classification: Other
Component: general
HEAD
Other All
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks: 621639 772263
 
 
Reported: 2009-08-20 05:52 UTC by Philip Withnall
Modified: 2018-05-24 14:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Use proper ellipses (13.92 KB, patch)
2009-08-20 05:52 UTC, Philip Withnall
none Details | Review
Use Unicode in translatable strings (35.00 KB, patch)
2016-09-30 20:24 UTC, Piotr Drąg
none Details | Review
Use Unicode in translatable strings (35.27 KB, patch)
2017-04-06 14:20 UTC, Piotr Drąg
none Details | Review
take advantage of unicode: use u+2236 ( ratio ) rather than colon[:] (6.17 KB, patch)
2017-11-19 12:43 UTC, gkrithi8
none Details | Review
Use Unicode in translatable strings (44.82 KB, patch)
2017-11-19 17:39 UTC, Piotr Drąg
none Details | Review

Description Philip Withnall 2009-08-20 05:52:15 UTC
There are various places in Rhythmbox where three dots ("...") are being used instead of a proper ellipsis character ("…"). Patch coming to use the correct character instead.
Comment 1 Philip Withnall 2009-08-20 05:52:45 UTC
Created attachment 141215 [details] [review]
Use proper ellipses
Comment 2 Piotr Drąg 2016-09-30 20:24:07 UTC
Created attachment 336697 [details] [review]
Use Unicode in translatable strings

Attached patch converts ASCII characters to Unicode, as recommended by <https://developer.gnome.org/hig/stable/typography.html>.
Comment 3 Piotr Drąg 2017-04-06 14:20:15 UTC
Created attachment 349370 [details] [review]
Use Unicode in translatable strings

Rebased on current master.
Comment 4 gkrithi8 2017-11-19 11:46:09 UTC
(In reply to Piotr Drąg from comment #3)
> Created attachment 349370 [details] [review] [review]
> Use Unicode in translatable strings
> 
> Rebased on current master.

Patch still works fine with offsets without issues.

But. why are the single quotes replaced with LEFT DOUBLE QUOTATION MARK ( U+201C ) and RIGHT DOUBLE QUOTATION MARK ( U+201D ), rather than LEFT SINGLE QUOTATION MARK ( U+2018 ) and RIGHT SINGLE QUOTATION MARK ( U+2019 )
Comment 5 gkrithi8 2017-11-19 12:41:33 UTC
(In reply to Piotr Drąg from comment #3)
> Created attachment 349370 [details] [review] [review]
> Use Unicode in translatable strings

Also, the encoding of source files needs to be updated to 'utf-8' in header comments. Please refer to patch below.
Comment 6 gkrithi8 2017-11-19 12:43:25 UTC
Created attachment 364001 [details] [review]
take advantage of unicode: use u+2236 ( ratio ) rather than colon[:]

This patch applies independently of the above submitted patch.
Comment 7 gkrithi8 2017-11-19 14:09:50 UTC
(In reply to gkrithi8 from comment #4)
> (In reply to Piotr Drąg from comment #3)
> > Created attachment 349370 [details] [review] [review] [review]
> > Use Unicode in translatable strings
> > 
> > Rebased on current master.
> 
> Patch still works fine with offsets without issues.
> 
> But. why are the single quotes replaced with LEFT DOUBLE QUOTATION MARK (
> U+201C ) and RIGHT DOUBLE QUOTATION MARK ( U+201D ), rather than LEFT SINGLE
> QUOTATION MARK ( U+2018 ) and RIGHT SINGLE QUOTATION MARK ( U+2019 )

FWIW, I think the single quotes and double quotes in code are better left off at their current state. The unicode replacement doesn't look any better, though it might confirm to the standards.
Comment 8 Piotr Drąg 2017-11-19 17:36:45 UTC
(In reply to gkrithi8 from comment #4)
> But. why are the single quotes replaced with LEFT DOUBLE QUOTATION MARK (
> U+201C ) and RIGHT DOUBLE QUOTATION MARK ( U+201D ), rather than LEFT SINGLE
> QUOTATION MARK ( U+2018 ) and RIGHT SINGLE QUOTATION MARK ( U+2019 )

Double quotation marks are almost always preferable in English, and it’s what was codified in GNOME HIG.

(In reply to gkrithi8 from comment #7)
> FWIW, I think the single quotes and double quotes in code are better left
> off at their current state. The unicode replacement doesn't look any better,
> though it might confirm to the standards.

Obviously, I disagree.
Comment 9 Piotr Drąg 2017-11-19 17:39:37 UTC
Created attachment 364009 [details] [review]
Use Unicode in translatable strings

• Rebased on master.
• Replaced colons with proper ratio characters.
• Added “coding: utf-8” to existing modelines.
Comment 10 gkrithi8 2017-11-27 15:00:22 UTC
Comment on attachment 364001 [details] [review]
take advantage of unicode: use u+2236 ( ratio ) rather than colon[:]

this change is included in the main patch. so marking as obsolete.
Comment 11 GNOME Infrastructure Team 2018-05-24 14:32:00 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/789.