Add legacy .elp support #1
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds support for legacy
.elpfiles in addition to the existing.zipand.elpxformats. Users can now upload, drag-and-drop, or load.elpfiles, which will be processed using a new converter module. The UI, validation logic, and error handling have all been updated to reflect this expanded support, with appropriate internationalization changes for both English and Spanish.Legacy .elp file support:
processLegacyElpfunction injs/app.jsto handle.elpfiles using theElpConvertermodule, including error handling and integration with the Service Worker..elpsupport inindex.html, including polyfills and the converter module.UI and validation updates:
index.htmlandlang/en.json/lang/es.jsonto include.elpfiles. [1] [2] [3]js/app.jsto recognize.elpfiles for both local and URL-based uploads. [1] [2]Internationalization:
.elpconversion in both English and Spanish locales (lang/en.json,lang/es.json). [1] [2] [3] [4]