[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 87805] Can't use slash in album filename
From:       Gilles Schintgen <gilles () vonet ! lu>
Date:       2005-02-03 8:20:56
Message-ID: 20050203082056.14972.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=87805         




------- Additional Comments From gilles vonet lu  2005-02-03 09:20 -------
On Thursday 03 February 2005 01:09, Achim Bohnet wrote:
> comment #6:  Gilles you mixed something up ;) utf-8 _is_ the solution for
> the encoding hell.   I have user from around the globe and all those
> different 8bit encodings are #$^  ^^$@ (especially on servers)
Yes, I know that in the long run it's the only viable solution, and I'm no 
longer using anything non-utf-8. Yet, in the past, I had some problems when 
writing CDs or using a USB pen drive and so on. AFAIK Windows doesn't use 
utf-8 as default and this can lead to problems. Ok, that's only insofar 
digikam's fault that I cannot choose the directory name. After all, the album 
name is prominently used in digikam as a title. Therefore I'm forced to name 
the album something useful (with spaces and everything).
But from a Unix perspective these filenames (with spaces or shell 
metacharacters) can be problematic. Additionally, this leads to a superfluous 
restriction (no slashes). Do other photo management apps have the same 
limitation? I doubt it.

> Now no new installatation without UTF-8 as default here!
Here too :-)

I guess it's up to the developers to decide. ;-)

Kind regards,

Gilles
[prev in list] [next in list] [prev in thread] [next in thread]