KDE4 proposal: Paths in i18n strings

Gary L. Greene Jr. greeneg at phoenuxos.com
Mon Jul 3 16:40:03 BST 2006


On Monday 03 July 2006 09:45, Jarosław Staniek wrote:
> Alexander Petrov wrote:
> > Hello,
> >
> > On Monday 03 July 2006 12:00 Jarosław Staniek wrote:
> >> http://kexi-project.org/wiki/wikiview/index.php?KDE4TODOs_PathsInI18n
> >> environment it should be converted using QDir::convertSeparators())
> >> (TODO:
> >
> > what about Mac?)
> >
> > Mac OS X uses '/' separators
>
> By mentioning Mac I knew someone will point out this. ;)
>
> I've seen ':' separators in 10.3, but yes, I would use this tradition.
> What's different on Mac? I'd say, most 'friedly' apps avoid to display the
> relative paths in favour of the top level directory (if the path is a dir)
> or in favioud of the filename only (if the path is pointing to a file).
> Thus I'd think about using this knowledge when rendering the final message
> string, but I am not sure.

Most Mac development literature from Apple says that if the application is one 
being used by the end user, the paths should be represented in 
the "volume:Path:To:File" format. The only time it should be output 
as /Path/To/File is in console applications. Mind you, this makes it a little 
inconsistent, but this is what most Mac users are accustomed to.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060703/012be80a/attachment.sig>


More information about the kde-core-devel mailing list