From kde-devel Mon Jan 29 17:05:54 2007 From: David Jarvie Date: Mon, 29 Jan 2007 17:05:54 +0000 To: kde-devel Subject: =?US-ASCII?B?UmU6IFtXaXNoXSBUaXRsZSwgQWRkcmVzcyBhbmQgRGF0ZSBmb3JtYXQ=?= Message-Id: X-MARC-Message: https://marc.info/?l=kde-devel&m=117009038205401 On Monday 29 January 2007 16:32 , Aaron J. Seigo wrote: >On Monday 29 January 2007 6:36, Yukiko Bando wrote: >> 1. Title >> >> When it refers to persons, we say è&#8218;©æ&#8250;¸ or 称å&#143;·. >> When it refers to documents, we say ã&#8218;¿ã&#8218;¤ã&#402;&#710;ã&#402;« or é¡&#338;å&#144;&#141;. > >would it be possible for you to start cataloging this information somewhere, >for instance on developernew.kde.org? we have a section there for >localization tutorials: > > http://developernew.kde.org/Development/Tutorials/Localization/ > >perhaps we could add one that simply lists these kinds of strings along with >the comment fields that should accompany them? e.g. > >i18n("A person", "Title") >i18n("A thing", "Title") > >or whatever. this way we can keep them consistent. if you need direction/help >with the wiki, i'm happy to assist. If we could compile a list of strings which are ambiguous and which need comments, perhaps a new Krazy check could be implemented which highlights any uses of these strings without comments. In real life, developers won't always check the string list, so some automatic method of spotting such strings without comments would be really useful. Ideally Krazy would automatically email the maintainer of the code when offending string usage was spotted - after all, Krazy output won't necessarily be seen by many developers either. Some such mechanism could be really useful in improving the quality of KDE translations if translators could get into the habit of notifying ambiguities. -- David Jarvie. KAlarm author & maintainer. http://www.astrojar.org.uk/linux/kalarm.html >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<