use of Folders (moved frm Sigil)

[theducks]

@eschwartz

I have seen that path mess before.

It has to do with using the Arrange into Folder (structure) feature and use of ADD. (IMHO Add blank could offer some better user assistance in the type and path department.)

If you start with a Sigil structure it is fine.

[DiapDealer]

Originally Posted by theducks

@eschwartz

I have seen that path mess before.

It has to do with using the Arrange into Folder (structure) feature and use of ADD. (IMHO Add blank could offer some better user assistance in the type and path department.)

If you start with a Sigil structure it is fine.

It does take a bit of getting used to (especially when going from Sigil to Calibre) that the logical representation of the epub's files in calibre's editor is not necessarily the same as the physical file structure.

[eschwartz]

@theducks

All Arrange into Folders does is runs as a manual tool to duplicate the effects of renaming every file by hand. You have to import them regularly, then run the tool, so where would they conflict? Unless I misunderstand what you mean.

I should know, as I asked for this tool in the first place.

@DiapDealer

Anyway, the original complaint said the CSS was being reported as non-existent, and the files were being entered with a different file extension than the one reported in the OPF. Nothing to do with confusing the type sorting with the folder structure, AFAICT.

[theducks]

Originally Posted by eschwartz

@theducks

All Arrange into Folders does is runs as a manual tool to duplicate the effects of renaming every file by hand. You have to import them regularly, then run the tool, so where would they conflict? Unless I misunderstand what you mean.

I should know, as I asked for this tool in the first place.

.

(really a Calibre topic)

There are 2 issues (and it might be me in both cases)


Add (anything)/Import (anything) should always ask where? if it detects folders in the book (we can assume flat otherwise)

If I add a blank: Styles/blank.css
it does not assume OEBPS/Styles/blank.css
to me, that is wrong (and a check usually complains). Book root or designated folder

[eschwartz]

Originally Posted by theducks

(really a Calibre topic)

There are 2 issues (and it might be me in both cases)


Add (anything)/Import (anything) should always ask where? if it detects folders in the book (we can assume flat otherwise)

If I add a blank: Styles/blank.css
it does not assume OEBPS/Styles/blank.css
to me, that is wrong (and a check usually complains). Book root or designated folder

Further calibre

It is a moot point I suspect, as the OP claims the manifest cannot locate the file, implying calibre wrote a different piece of info to the OPF and to the file/folder structure.

Add file(s) shouldn't ask anything, unless the whole editor should ask it.
The editor does not care where the files go (and Check book does NOT warn you) and in fact, does not go out of its way to show you where they are.
It would not be in theme for calibre editor to ask you where to put the files.

AFAIR, the spec does not mandate the use of an OEBPS folder, it is simply a very strong tradition. Check book did not report the lack of one as an error.

[BetterRed]

@theducks - is it possible to move the posts discussing the calibre editor to a thread in the Calibre/Editor subforum - the OP's problem is with the Sigil editor.

@eschwartz - I may have missed it, but I can't see where the OP 'blamed' calibre for the problem he has/had with Sigil. All the OP said is that they didn't enjoy the experience of using the calibre editor. If that's the case then the 'Just don't blame calibre for anything else.' instruction seems uncalled for, it's also somewhat menacing, in that that there's an implied 'or else you will suffer the consequences' left hanging.

BR

[eschwartz]

Originally Posted by BetterRed

@eschwartz - I may have missed it, but I can't see where the OP 'blamed' calibre for the problem he has/had with Sigil. All the OP said is that they didn't enjoy the experience of using the calibre editor. If that's the case then the 'Just don't blame calibre for anything else.' instruction seems uncalled for, it's also somewhat menacing, in that that there's an implied 'or else you will suffer the consequences' left hanging.

BR

Perhaps I could've been more clear, but what I meant was "don't accuse calibre of being deficient in areas where it isn't" although it is true that it lacks a clip manager.

To clear, there were 4 objections raised against calibre:

1. calibre mangles/mislinks the locations of files added/linked.
2. Blue background makes it difficult to use editor.
3. Marked text is difficult to search with.
4. Lack of clips.

To which I say:

1. Sounds very fishy, I bet everyone here would love to know how to replicate that mission-critical bug.
2. This is a non-default that can easily be changed (back).
3. Other than not relabeling dynamically based on current situation, this works exactly the same. And I have suggested this be fixed anyway.
4. This is actually a valid reason to prefer Sigil.

#'s 2-3 are either lack of knowledge or disingenuous.

[phossler]

@eschwartz

Sounds very fishy, I bet everyone here would love to know how to replicate that mission-critical bug.

FWIW -- The only issue I've had with the Editor Folders feature is that some times if I start with a CSS with font locations specified, the result is something like

..\..\Fonts\Charlis.ttf

and I have to manually edit the ..\ out

[roger64]

Hi

This naming of folders has been a tricky question for me some time ago and I even reported in March a - non existent - bug of the Calibre editor for this reason.

https://www.mobileread.com/forums/sho...d.php?t=236427

What happened was that I first produced an EPUB with a "faulty" structure using my usual converter. Opening it with Sigil, Sigil automatically ( and without warning) corrected this faulty structure. Calibre did nothing of the sort and that's why I thought that Calibre did something wrong when I first opened an EPUB with the Calibre editor and I reported this - non existent - bug.

As I keep using this converter (I am a little stubborn), I am used now to open it first with Sigil 6.2, close it immediately after saving - and correction - and then I begin work with the Calibre editor... Believe it or not, this saves me a lot of time. As few people use my converter, this seems to be a limited problem.



But there is something really unintuitive about the whole thing. I wish I could select a plain button in the Calibre editor that leaves me with a physical EPUB structure identical to the logical structure... And also that the physical path of each folder could be more clearly displayed.

Maybe I ask for too much

[theducks]

Originally Posted by roger64

But there is something really unintuitive about the whole thing. I wish I could select a plain button in the Calibre editor that leaves me with a physical EPUB structure identical to the logical structure... And also that the physical path of each folder could be more clearly displayed.

Maybe I ask for too much

If you try and rename a file in the Fie Browser, it will show the relative path level.

Being a 'visual' kind of user, it would be nice if there were some clue of nesting (if any): Color background change? root being the current White
Files in each folder in a section (Text,CSS,Image) would get a common shade change (eg. Omnibus made by simple combining with a non-uniform styles : Book1, book2, book3 could get 2-3 shadings.

Title

Book1
Book2
Book3

End Matter

[eschwartz]

Wouldn't it be better to simply maintain the traditional structure like Sigil does?

Perhaps an option on opening to run Arrange into folders.

Err, maybe not for omnibuses. But I would prefer, in that case, to not have identically named files regardless. (Even if they are in different folders.)

[theducks]

Originally Posted by eschwartz

Wouldn't it be better to simply maintain the traditional structure like Sigil does?

Perhaps an option on opening to run Arrange into folders.

Err, maybe not for omnibuses. But I would prefer, in that case, to not have identically named files regardless. (Even if they are in different folders.)

Not really

There is no provision for duplicated file names when merging.Things get overwritten without warning.

I will vote for a semi automatic.

Open a FLAT book: Sigil way it
Open a FOLDERED book: Leave it alone
Add a second book: Pre-scan Ask if ANY duplicates detected. defaults to next folder sequence: Text1,Images1,Styles1 <could be common styles, and just another PART of a single Title being built>

[eschwartz]

Sounds cool. So, are you writing the plugin?