ENAMETOOLONG for chapters with long title names about epub-gen HOT 3 CLOSED

Hey @alecgibson, that totally makes sense, I'll put up a PR with it. 👍

from epub-gen.

Yeah, didn't know we had that option! Makes sense. Happy to close this.

from epub-gen.

Hi @alecgibson, so I've been looking to the code and how it is, might be tricky to provide that on Promise resolution, because at that point the TOC is already generated (file zipped and all) – isn't ringing as optimal to me, idk.

How about a different approach, along these lines:
- allow the lib users to provide their own optional slugs for contents – as a content.slug option for instance, we'll add and document that;
- this way it is the user responsibility to truncate the slugs (used for filenames too) as they deem fit(1);

(1) I'm stating this one, because I'm thinking that each user/project will have their files/folders in different depths/path sizes on each system and path/filename sizes might be dependent of each environment, hence giving that option to lib users. IDK, does this make sense? 🤔

EDIT: Just noticed one can use an optional content.filename on each content, wouldn't this work out to mitigate this error? (I think the slug it's also mainly used to build the filename, so...)

Stating this, because I'm thinking that each user/project will have their files/folders in different depths/path sizes on each system thus path/filename sizes might be dependent of each environment, hence could be something to lie upon the lib users/projects to tweak out in this case? IDK, does this make sense? 🤔

from epub-gen.