Skip to content
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

GUI-CLI inconsistency with translation pair storage #253

Closed
bruceleerabbit opened this issue Apr 22, 2022 · 0 comments
Closed

GUI-CLI inconsistency with translation pair storage #253

bruceleerabbit opened this issue Apr 22, 2022 · 0 comments

Comments

@bruceleerabbit
Copy link

bruceleerabbit commented Apr 22, 2022

When a user installs a language pair using the CLI, the user is told where it’s stored, which is in ~/.local/cache/argos-translate/downloads/. When the GUI is used to install a language pair, the lib is stored somewhere different, and the user is not told where that location is. And because there is no man page, knowing what happened requires users to look at the source code.

The GUI should store the pairs in the same location that argospm uses because it’s the same kind of data and it should get the same treatment when users backup their systems.

Please document the location used by the GUI in this thread and in the documentation so users can experiment with making one of the directories a symbolic link to the other.

(edit)
After some investigation, I’ve come to realize that ~/.local/cache/argos-translate/downloads/ is where translate-«pair».argosmodel files are dumped, but those are not used by the app. These are simply ZIP files that get unpacked in ~/share/argos-translate/packages. I have 2 zip files cached and 3 language pairs installed in ~/share/argos-translate/packages. So I suspect the GUI deletes the *.argosmodel file after unpacking but argospm does not. That inconsistency threw me off.

IMO, it’s probably sensible to delete the ZIP files after successfully unpacking them because they don’t seem to be useful thereafter. But partially fetched or broken ZIPs should be retained in that folder because they have troubleshooting value & can possibly be useful in a crash recovery scenario.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants