Touch Kobo Touch Firmware 2.0

[camtosh]

Yes, I now suspect that is what is wrong on my Mac. A quick google turns up this tip to change the setting, but its kinda scary for a newbie:
http://www.joshklein.net/how-to-show...-mac-os-x-lion

and more here: http://www.mactricksandtips.com/2008...den-files.html

[ischeriad]

You don't have to change settings on Mac OS X.
In the Finder, use the "Go to Folder..." (Shift-Command-G) menu command to enter the path you want to go to manually, for me that would be "/Volumes/KOBOeReader/.kobo"

[Urdu]

Originally Posted by camtosh

Yes, I now suspect that is what is wrong on my Mac. A quick google turns up this tip to change the setting, but its kinda scary for a newbie

Use Bifocals: http://stevenwright.github.com/Bifocals/

Bifocals is a simple, unobtrusive, app for your Mac which lets you show or hide these hidden files with an always-available menu bar icon

[camtosh]

thanks Urdu!

[dioioib]

Originally Posted by camtosh

Yes, I now suspect that is what is wrong on my Mac. A quick google turns up this tip to change the setting, but its kinda scary for a newbie:
http://www.joshklein.net/how-to-show...-mac-os-x-lion

and more here: http://www.mactricksandtips.com/2008...den-files.html

You could also use a tool like Deeper from titanium it is free and lets you tweak several other settings beyond just hidden files.

http://www.titanium.free.fr/

[davidfor]

In case no-one has notice, the Touch with firmware 2.0.x, is very lax with shelf names. You can have leading or trailing space and they are case sensitive. So, you can create (without the quotes):

" mystery"
"mystery "
"mystery "
" mystery "
"Mystery"

And just about any other combination you want.

I hate this sort of thing. If I meet the person who decided this to alllow this...

[murg]

Originally Posted by davidfor

I hate this sort of thing. If I meet the person who decided this to alllow this...

No one decided to allow this, probably. It's just sloppy development, testing and management.

Unless it was speced this way, in which case...

[Howlingwolf]

Originally Posted by murg

No one decided to allow this, probably. It's just sloppy development, testing and management.

Unless it was speced this way, in which case...

You're on the wrong track there guys.

This is simply the 'natural' behaviour of any database text handling 'function'.

You have to actually implement additional 'features' such as leading/trailing whitespace removal, case normalisation, case insensitive duplicate checking, etc.

[Terisa de morgan]

Originally Posted by Howlingwolf

You're on the wrong track there guys.

This is simply the 'natural' behaviour of any database text handling 'function'.

You have to actually implement additional 'features' such as leading/trailing whitespace removal, case normalisation, case insensitive duplicate checking, etc.

Sloppy development, as it has been told.

[davidfor]

Originally Posted by murg

No one decided to allow this, probably. It's just sloppy development, testing and management.

Unless it was speced this way, in which case...

I'm pretty sure the leading/trailing spaces is sloppy work. I can't think of any reason to want to do this. The case sensitivity could be deliberate, but with the other, I suspect it isn't.

[davidfor]

Originally Posted by Howlingwolf

You're on the wrong track there guys.

This is simply the 'natural' behaviour of any database text handling 'function'.

You have to actually implement additional 'features' such as leading/trailing whitespace removal, case normalisation, case insensitive duplicate checking, etc.

That is completely correct. But, to remove the whitespace in any current language is usually just a call to "trim" or "strip". Not doing this is just lazy.

The case sensitivity is a bit harder. But not impossible.

[daldred]

Originally Posted by davidfor

I'm pretty sure the leading/trailing spaces is sloppy work. I can't think of any reason to want to do this. The case sensitivity could be deliberate, but with the other, I suspect it isn't.

Case sensitivity is good. Only a generation raised on Windows ability to tell the difference between upper and lower case would think otherwise.

[davidfor]

Originally Posted by daldred

Case sensitivity is good. Only a generation raised on Windows ability to tell the difference between upper and lower case would think otherwise.

Did you mean to say "inability"? If so...

I can't agree with you. Respecting the case so I can use mixed case to make the file names easier to read is very good. But, I hate the idea that a file called "AAAAA" is different to one called "aaaaa". I can't think of a place in the "real world" where it would be expected that those two names were naming completely different items.

[murg]

Originally Posted by daldred

Case sensitivity is good. Only a generation raised on Windows ability to tell the difference between upper and lower case would think otherwise.

Case sensitivity on a consumer device is bad. Really bad.

For 'normal' people, there is no difference between 'Wizard of Oz' and 'Wizard of OZ'. Only those weird computer people think they are different.

And I've been dealing with Unix since it was still at Bell Labs...

[MisterMax]

Originally Posted by murg

Case sensitivity on a consumer device is bad. Really bad.

For 'normal' people, there is no difference between 'Wizard of Oz' and 'Wizard of OZ'. Only those weird computer people think they are different.

And I've been dealing with Unix since it was still at Bell Labs...

Yes, but I also think that case sensivity is bad even software development: why the function CalculateMyValue should work in a different way that the function CalculatemyValue?

The description ability of a name is contained in letters and spacing, not in the case of the letter.

Pretending to associate different meaning to different latter case is not what letter case is intended for :-)