Linux Scrivener 035 Fail: Default Project Templates Broken

Zip attached. This is a project I created with the “novel” project. Note that the test.scriv file has some very odd things in it, including directories with trailing back-slashes in their names (like “newnovel.scriv”)
The project “newnovel.scriv” opens. Although it seems that the expected files are there, none of them, even the project template explanation file, has any text at all.

Since this renders Scrivener under Linux unusable for me, I’m using the Windows version under VirtualBox until the next beta comes out. (16.9 KB)

I noticed this with the backup files created by the Windows version, too, so I’m not sure if it is specifically a Linux problem. It should be safe to strip out all of the “WeirdStuff” with a backslash on the end like that. No harm in trying with a new template instantiation, anyway.

I bumped into this, as well.

When backing up, don’t zip it. Compress it yourself.

If you do use the builtin zip function, be sure to delete all the 0 byte files before you open the file in Scrivener.

This is not a backup. This has nothing to do with backups.

I created the zip file purely for the purpose of posting it here.

These directories represent the output of a clean template instantiation, including the [resulting] internal garbage. Note that when you open the top level project.scriv file in scrivener the result is identical with the “blank” default template.

My custom templates instantiate correctly.

This problem never happened before 35. It happens every time in 35. It does not happen on Windows.

Sorry, I wasn’t clear enough. It might be related in that template files are stored as zip compressed. So thus if they are created by the same zip engine, might bear similar flaws. It seems that zip files created in the Windows version have these junk files. Since the templates have been created using the Windows version, then these junk files appear due to having come out of the same zip engine. The templates you created yourself presumably originated from the Linux version, which is likely using a different zip engine.

So to put it another way: the template files themselves have this junk data in them. They are just dutifully reproducing what is in the zip archive that is them, when they become a project on your disk, and so the problem originates in the creation of the templates via the Windows zip engine, not the extraction of them.

Whatever these junk files are, they are not visible on Windows for whatever reason, but they are there. Move the project to Dropbox, or out of your VM and they should appear.

No, they don’t. It’s just that that however the project template files are being compressed in Windows, on the Linux side the decompression is now broken. Something has to have changed, otherwise, why hasn’t this been happening all along? Is it that you are now using the windows-compressed project templates, instead of compressing the (model project) originals in Linux?

So from Windows I created models projects for each of the project templates I tend to use, copied them over to Linux, and made project templates out of them. Which all work fine.

It wasn’t enough to create templates on Windows and copy the scrivtemplate files over to Linux, since they arrived with the same problems.

So for the next Linux beta, how about making the project templates in Linux?

I’m not sure what changed on that, though the slash bug is a known problem. I don’t think the templates were made on Linux before—I could be wrong on that however. They might have been, because Lee was making them before and now Jennifer is.

Yeah, that’s what I meant in my prior comment about how they should show up messy after moving them out of the Windows VM.

Well at any rate, the main bug here to fix is the slash-file problem in the Windows based compressor. It would be better to spend time fixing that then switching to making templates in Linux to get around the problem, since Windows people are still going to be using the Windows compressor to (a) make backups and (b) save templates. The root problem is that compressor. Fix that and this whole thing goes away no matter where the templates are created.

…and in doing so you will break every custom template ever created in the previous Windows versions, because of that compressor bug that’s been there all along only isn’t any more… I’d tread carefully there. Maybe advance warning at least.

In any case, thanks for your time(s)!