GNOME Bugzilla – Bug 309896
Some schema string improvement suggestions
Last modified: 2005-07-09 16:31:05 UTC
From bug 309879: (f) a whole group of them: do we need both sets? .po:130 reference: ⑤ ../data/totem.glade.h:111 Original: ⌘0 Zoom In .po:131 reference: ⑤ ../data/totem.glade.h:112 Original: ⌘0 Zoom Out .po:132 reference: ⑤ ../data/totem.glade.h:113 Original: ⌘0 Zoom Reset .po:133 reference: ⑤ ../data/totem.glade.h:114 Original: ⌘0 Zoom in .po:134 reference: ⑤ ../data/totem.glade.h:115 Original: ⌘0 Zoom out .po:135 reference: ⑤ ../data/totem.glade.h:116 Original: ⌘0 Zoom reset (g) po:162 reference: ⑤ ../data/totem.schemas.in.h:1 Original: ⌘0 Enable deinterlacing .po:163 reference: ⑤ ../data/totem.schemas.in.h:2 Original: ⌘0 Enable deinterlacing. (h) another series: po:165 reference: ⑤ ../data/totem.schemas.in.h:4 Original: ⌘0 Name of the visual effects plugins .po:166 reference: ⑤ ../data/totem.schemas.in.h:5 Original: ⌘0 Name of the visual effects plugins. .po:167 reference: ⑤ ../data/totem.schemas.in.h:6 Original: ⌘0 Path to the optical media device .po:168 reference: ⑤ ../data/totem.schemas.in.h:7 Original: ⌘0 Path to the optical media device. .po:169 reference: ⑤ ../data/totem.schemas.in.h:8 Original: ⌘0 Repeat mode .po:170 reference: ⑤ ../data/totem.schemas.in.h:9 Original: ⌘0 Repeat mode. .po:171 reference: ⑤ ../data/totem.schemas.in.h:10 Original: ⌘0 Resize the canvas automatically on file load .po:172 reference: ⑤ ../data/totem.schemas.in.h:11 Original: ⌘0 Resize the canvas automatically on file load. (i) po:175 reference: ⑤ ../data/totem.schemas.in.h:14 Original: ⌘0 Shuffle mode .po:176 reference: ⑤ ../data/totem.schemas.in.h:15 Original: ⌘0 Shuffle mode. (j) another series .po:179 reference: ⑤ ../data/totem.schemas.in.h:18 Original: ⌘0 The brightness of the video .po:180 reference: ⑤ ../data/totem.schemas.in.h:19 Original: ⌘0 The brightness of the video. .po:181 reference: ⑤ ../data/totem.schemas.in.h:20 Original: ⌘0 The contrast of the video .po:182 reference: ⑤ ../data/totem.schemas.in.h:21 Original: ⌘0 The contrast of the video. .po:183 reference: ⑤ ../data/totem.schemas.in.h:22 Original: ⌘0 The hue of the video .po:184 reference: ⑤ ../data/totem.schemas.in.h:23 Original: ⌘0 The hue of the video. .po:185 reference: ⑤ ../data/totem.schemas.in.h:24 Original: ⌘0 The saturation of the video .po:186 reference: ⑤ ../data/totem.schemas.in.h:25 Original: ⌘0 The saturation of the video. (k) po:191 reference: ⑤ ../data/totem.schemas.in.h:30 Original: ⌘0 Whether to enable debug for the playback engine .po:192 reference: ⑤ ../data/totem.schemas.in.h:31 Original: ⌘0 Whether to enable debug for the playback engine. (l) .po:194 reference: ⑤ ../data/totem.schemas.in.h:33 Original: ⌘0 X coordinate for the Playlist .po:195 reference: ⑤ ../data/totem.schemas.in.h:34 Original: ⌘0 X coordinate for the Playlist. .po:196 reference: ⑤ ../data/totem.schemas.in.h:35 Original: ⌘0 Y coordinate for the Playlist .po:197 reference: ⑤ ../data/totem.schemas.in.h:36 Original: ⌘0 Y coordinate for the Playlist.
(f) Some are the menu items (the one with title casing), and the other ones are the associated tooltips, so they need to be different. (g) The ones without the period are for the short description, the ones with the period are for the long description. Both of those are following the HIG, and common practices in GNOME modules.
Is there any point in providing strings which are meant to provide additional semantic information if their onliest difference to the original strings (menuitem labels, short strings) is formal, capitalization/trailing dots that is?
Not really, apart from following the conventions. (f) follows: http://developer.gnome.org/projects/gup/hig/2.0/design-text-labels.html#layout-capitalization (g) changes were due to: http://bugzilla.gnome.org/show_bug.cgi?id=118710
On (g): Well, but the <long> strings existed before these changes. Let's just drop them. :)
Huh? What changes are you talking about? Those strings haven't changed in 2 years+.
From comment 4: Let's just drop them. :)
Created attachment 48868 [details] [review] Proposed patch.-
Please commit to HEAD only.
Thanks for the quick review.