-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: GEDZIP support #516
Comments
Specifically, are you more interested in reading GEDZIP, or writing? Because I’m almost sure that most of my users will not be interested in saving to this format. Here's the reading... yes, it's possible. |
Both? We do share the tree files between multiple persons within family, it'd be much easier to have the software import and export gedzip rather than have to manually pack and unpack it That being said it's just a suggestion and given that not a lot of people probably need it, I will understand if it doesn't get implemented :) |
I'm not at all against implementing this. I've been thinking about this for a long time. Simply because of the small circle of users and the small number of active participants in the project, I always first of all evaluate how much I or a nearby user needs a new function and to what extent. If we consider first of all simple support for packaging GED files in GEDZIP, this is one thing. If at the same time placing multimedia objects there is already more code rework, we will need a global option to switch the storage of all data in such a file. And the third level - to what extent is GEDZIP designed for storing very large objects in it - for example, video files? |
Gedzip is just a zip with .GED and all media files referenced by it. It has no other limitations, incl file size limitations, other than the ones put in by ZIP specification. |
Wish I knew c#, I'd be happy to try implementing it |
I'd like to suggest support for exporting/importing (and maybe opening and saving) GEDZIP files as defined by https://gedcom.io/gedzip/ and https://www.gedcom.org/gedcom.html
The text was updated successfully, but these errors were encountered: