What file extension to use? #2
Replies: 5 comments 3 replies
-
Pinging @bronger @CEschke @FlorianRhiem @martin-held-hereon @mikee1976 @nicobrandt @nicolejung @SteffenBrinckmann (btw you should subscribe to activity on this repo!) |
Beta Was this translation helpful? Give feedback.
-
Sorry, could not resist: https://wilson.bronger.org/12246653_789997134444585_8425954147094342405_n.jpg |
Beta Was this translation helpful? Give feedback.
-
I feel like simply using Alternatively, we could also just use the regular |
Beta Was this translation helpful? Give feedback.
-
If I change my vote to |
Beta Was this translation helpful? Give feedback.
-
+1 :-D
Viele Grüße
Michael
|
Beta Was this translation helpful? Give feedback.
-
What do you think the file extension should be?
On one hand we have
.eln
which is unknown to the world, and makes the archive an unknow binary file. Advanced users know that they can open it as if it was any other zip, the same way one can open a .docx file. Keeping this extension might prevent users from fiddling with it, zipping it back again and we end up with an incorrect archive. The idea being that the archive should be immutable, and inspection of content by a human should only be done by devs. The end users don't really have to know what is the internal structure.On the other hand, we have
.eln.zip
, the same way we have.tar.gz
which is a gzipped tarball, we have a zipped eln/ro-crate. The advantages are that it makes it easy to be opened to inspect content on the desktop, because it is now obvious that it is a zip, it also means that unarchivers will be able to open it easily and OS actions (right click > unzip) will be available.Both options are valid with their pros and cons.
4 votes ·
Beta Was this translation helpful? Give feedback.
All reactions