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 551694 - Typo »exluded« in baobab.schemas.in.h
Typo »exluded« in baobab.schemas.in.h
Status: RESOLVED DUPLICATE of bug 573530
Product: gnome-utils
Classification: Deprecated
Component: baobab
2.27.x
Other All
: Normal trivial
: ---
Assigned To: Fabio Marzocca
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-10 17:56 UTC by Jochen Skulj
Modified: 2009-09-16 14:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description Jochen Skulj 2008-09-10 17:56:30 UTC 
Please describe the problem:
While updating de.po I found following entry:

#: ../baobab/data/baobab.schemas.in.h:3
msgid "Exluded partitions uris"
msgstr "Adressen der ausgeschlossenen Partitionen"

I guess this is a typo and should be »Exluded partitions ...«. It would be nice to correct this since it would make translating gnome-utils easier. Thank you!

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Daniele Forsi 2009-08-30 17:07:10 UTC 
The typo is still present in 2.27.x, also shouldn't be "URI" all uppercase in both short and long descriptions?

    <schema>
      <key>/schemas/apps/baobab/properties/skip_scan_uri_list</key>
      <applyto>/apps/baobab/properties/skip_scan_uri_list</applyto>
      <owner>baobab</owner>
      <type>list</type>
      <list_type>string</list_type>
      <default>[]</default>
      <locale name="C">
	<short>Exluded partitions uris</short>
	<long>A list of uri for partitions to be excluded from scanning.</long>
      </locale>
    </schema>
Comment 2 Cosimo Cecchi 2009-09-16 14:45:28 UTC 
This is probably something for 2.29.
Comment 3 Cosimo Cecchi 2009-09-16 14:47:35 UTC 
This is actually a duplicate.

*** This bug has been marked as a duplicate of bug 573530 ***