just pulled the trigger on a pocket pro

[jusmee]

Originally Posted by Robertb

Dear Kenny and all:

The bookmarking was improved in a September Firmware Upgrade. All I have heard on here is that the bookmarking is now fine.

REALLY? You haven't seen the many messages about it not saving bookmarks when there are spaces in the folder/file name?

[kennyc]

Originally Posted by jusmee

REALLY? You haven't seen the many messages about it not saving bookmarks when there are spaces in the folder/file name?

(Edit: sorry I thought that was to me.....Never Mind.....)
......

[Robertb]

Originally Posted by jusmee

REALLY? You haven't seen the many messages about it not saving bookmarks when there are spaces in the folder/file name?

Dear Jusmee:

Saw a post or two but not many saying it needed to be improved.

Can you give me an example or write it not as a question but as a statement? I will send it off tonight. Be kind. Just state what you feel needs to be improved.

[jusmee]

Originally Posted by Robertb

Dear Jusmee:

Saw a post or two but not many saying it needed to be improved.

Can you give me an example or write it not as a question but as a statement? I will send it off tonight. Be kind. Just state what you feel needs to be improved.

I am not asking for anything new. I am asking for bookmarks to be fixed. It's a bug.

Bookmarks are not saved when you exit a book. When you reopen the book, all bookmarks a gone. (I tried this on an ePub - haven't tried mobi). There are many reports on various forums around the place, saying that this happens when there are spaces in the pathname where the book is saved. It is very common to have spaces in the folder name, for example, as this is the way Calibre organises things, so it's a big problem.

[Robertb]

Originally Posted by jusmee

I am not asking for anything new. I am asking for bookmarks to be fixed. It's a bug.

Bookmarks are not saved when you exit a book. When you reopen the book, all bookmarks a gone. (I tried this on an ePub - haven't tried mobi). There are many reports on various forums around the place, saying that this happens when there are spaces in the pathname where the book is saved. It is very common to have spaces in the folder name, for example, as this is the way Calibre organises things, so it's a big problem.

Dear Jusmee:

I am sending a copy of your post as is to the chief engineer at the factory. Let us see if we can solve this for all.

Thank you for your patience. It is NOT that I do not want to act... I just need to know that a few people have noted the problem and a clear statement as to what it is.

Thank you!!

[theducks]

Originally Posted by jusmee

I am not asking for anything new. I am asking for bookmarks to be fixed. It's a bug.

Bookmarks are not saved when you exit a book. When you reopen the book, all bookmarks a gone. (I tried this on an ePub - haven't tried mobi). There are many reports on various forums around the place, saying that this happens when there are spaces in the pathname where the book is saved. It is very common to have spaces in the folder name, for example, as this is the way Calibre organises things, so it's a big problem.

There is a setting in Calibre IF you use "Save to Disk"
X replace space with underscore_ in file names.

I do not think this applies when saving to Device.

IMHO Save to Disks gives you better control of you library (directory) layout on the PEz.

[jusmee]

Originally Posted by theducks

There is a setting in Calibre IF you use "Save to Disk"
X replace space with underscore_ in file names.

I do not think this applies when saving to Device.

IMHO Save to Disks gives you better control of you library (directory) layout on the PEz.

You are right, and no, it doesn't apply when sending books to your device (the easy and intended way to do it).

Still, Calibre isn't the only reason you might have spaces. Spaces are quite legal in folder and file names, and so the device has to cope with them.

[DaleDe]

Originally Posted by jusmee

You are right, and no, it doesn't apply when sending books to your device (the easy and intended way to do it).

Still, Calibre isn't the only reason you might have spaces. Spaces are quite legal in folder and file names, and so the device has to cope with them.

Actually they are not really legal in Unix (Linux) where they are special characters used as file separators. Their use requires escaping. They are legal in Windows. However, there are ways to deal with them so I believe that this can be fixed.

[jusmee]

Originally Posted by DaleDe

Actually they are not really legal in Unix (Linux) where they are special characters used as file separators. Their use requires escaping. They are legal in Windows. However, there are ways to deal with them so I believe that this can be fixed.

yes and no If you use a linux command line command like ls , you will see all the filenames, including the ones with spaces. This is legal and supported by bash, and the underlying filesystem.

You often need to escape, or quote strings with spaces, especially when used for filenames in commands and programming, but this does not make them less legal.

[Javed]

+1 for Bookmark Bug fix please.

[theducks]

Originally Posted by jusmee

yes and no If you use a linux command line command like ls , you will see all the filenames, including the ones with spaces. This is legal and supported by bash, and the underlying filesystem.

You often need to escape, or quote strings with spaces, especially when used for filenames in commands and programming, but this does not make them less legal.

Thanks for adding Clarity.
I was scratching my Head, "But there were spaces allowed in "Unix" file names when I used them it the 1980's, why would Linux 'remove' them? "

[DaleDe]

Originally Posted by theducks

Thanks for adding Clarity.
I was scratching my Head, "But there were spaces allowed in "Unix" file names when I used them it the 1980's, why would Linux 'remove' them? "

Bash man page says the following:

A simple command is a sequence of optional variable assignments followed by blank-separated words and redirections, and terminated by a control operator. The first word specifies the command to be executed, and is passed as argument zero. The remaining words are passed as arguments to the invoked command.

With the following definitions:

blank A space or tab.
word A sequence of characters considered as a single unit by the
shell. Also known as a token.
metacharacter
A character that, when unquoted, separates words. One of the
following: | & ; ( ) < > space tab

Thus a space is a metacharacter with special powers and not just a standard character. It requires special handling.

Dale

[theducks]

Originally Posted by DaleDe

Bash man page says the following:

A simple command is a sequence of optional variable assignments followed by blank-separated words and redirections, and terminated by a control operator. The first word specifies the command to be executed, and is passed as argument zero. The remaining words are passed as arguments to the invoked command.

With the following definitions:

blank A space or tab.
word A sequence of characters considered as a single unit by the
shell. Also known as a token.
metacharacter
A character that, when unquoted, separates words. One of the
following: | & ; ( ) < > space tab

Thus a space is a metacharacter with special powers and not just a standard character. It requires special handling.

Dale

not to nit, to much
Nowhere does that say that file names can not have spaces.
What it says is : If a filename with spaces is used as a shell command or argument, the special treatment is required.

This is hardly different from windows: "C:\Program Files\Calibre2\calibre" must receive special treatment (inside quotes) when used in a Batch file or as an argument.

[DaleDe]

Originally Posted by theducks

not to nit, to much
Nowhere does that say that file names can not have spaces.
What it says is : If a filename with spaces is used as a shell command or argument, the special treatment is required.

This is hardly different from windows: "C:\Program Files\Calibre2\calibre" must receive special treatment (inside quotes) when used in a Batch file or as an argument.

Yes that is not different from the command line in Windows but the gui does not require special treatment and is standard in Windows but extra addon in Unix/Linux. The quotes, by the way, are mostly added automatically in command line completion in Windows when used as an argument. If you look at my original post all I said was that a space required special handling not that it was illegal. If you go back to Unix in the 70's as I do then you will find that Unix in those days did not have any required files or directories that used a space and it was discouraged normal usage. Some early file systems didn't even support it. It wasn't until Windows forced the issue with the Program Files name that it became accepted. Ok, back to the orignal program, still in progress.

Dale

[jusmee]

Originally Posted by DaleDe

Yes that is not different from the command line in Windows but the gui does not require special treatment and is standard in Windows but extra addon in Unix/Linux. The quotes, by the way, are mostly added automatically in command line completion in Windows when used as an argument. If you look at my original post all I said was that a space required special handling not that it was illegal. If you go back to Unix in the 70's as I do then you will find that Unix in those days did not have any required files or directories that used a space and it was discouraged normal usage. Some early file systems didn't even support it. It wasn't until Windows forced the issue with the Program Files name that it became accepted. Ok, back to the orignal program, still in progress.

Dale

Keep in mind that linux is not bash (or any other command interpreter) nor the xwindow layer, nor the gui on top of that. If you lump them together, you are talking about a distribution that is based on linux - e.g. Ubuntu. Suse, Debian, Fedora etc etc.

Also, I suggest we look at what is current, not what was historically the case. People have moved on. Consider the normal user (as opposed to the computer savvy or geek). If I write a label on a manila folder in my filing cabinet, I use spaces. Computers have to allow this or else they don't meet the convenience users.

Spaces HAVE to be allowed in folder/filenames!