From kde-core-devel Mon Jul 03 14:03:34 2006 From: =?utf-8?q?Jaros=C5=82aw_Staniek?= Date: Mon, 03 Jul 2006 14:03:34 +0000 To: kde-core-devel Subject: Re: KDE4 proposal: Paths in i18n strings Message-Id: <200607031603.34664.js () iidea ! pl> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=115193704316878 Frans Englich wrote: > On Monday 03 July 2006 08:00, Jarosław Staniek wrote: >> Hello, >> This is a result of my discussion with Chusslove Illich >> on paths for i18n strings: >> >> http://kexi-project.org/wiki/wikiview/index.php?KDE4TODOs_PathsInI18n > > "since we're displaying a richtext," > > Does this assumption really hold? For KMessageBoxes (and QLabel in general), yes. > Some applications output to std/errout, and are logging. As I see it, that > will break if an i18n call generates "foo". This relates to the > KMessageHandler discussion here on k-c-d a month(?) ago. > > I think it would be great if i18n was aware of what medium the string > should be displayed in, in order to adapt in the most appropriate way. > That would achieve the best result. > > For example, imagine a compiler(KJS, Patternist, some KDevelop thingy, > etc) outputting a message. When having a GUI, the document URI is nicely > marked up, and identifiers are displayed in type writer front. When sent > to a console, pretty `´-quotes are used consistently and identifiers are > colored. > > Here the simplicity of i18n shines through. If an object was used instead > of global, static functions, it would be different. Perhaps one can have > that too as an alternative to the i18n calls. Somehow. Exactly, and I mentioned the logs case in the proposal: "Posible problem: we may want to display the mesage with path to a log file or std(out|err}. The KLocalizedString class should know it's the case, so there may be aditional flag for doing this (i.e. displaying the path using " " characters only -- not as frequently used, so the default could be the rich text output). " -- regards / pozdrawiam,   Jaroslaw Staniek / OpenOffice Polska Sponsored by OpenOffice Polska to work on * Kexi & KOffice: http://www.kexi-project.org | http://koffice.org/kexi * KDE3 & KDE4 Libraries For Developing MS Windows Applications:                    http://www.kdelibs.com/wiki See also: * Kexi For MS Windows: http://kexi.pl/wiki/index.php/Kexi_for_MS_Windows * Kexi Support:        http://www.kexi-project.org/support.html