You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 16, 2022. It is now read-only.
I'm utterly enamored of the ebviewer you wrote, especially the style in the chameleon screenshot of README, and the part where you started to implement mdict format parser in #38.
And I still have some questions of the in-app layout.
indicated as following two images (ebviewer above, goldendict below), all text are "congested", that's neat for short explanation, but it becomes a little bit tiresome to eyes for long long explanation. So is it possible to display the original CSS format, or add an option to manually adjust (e.g. line spaces)?
dict files need uploading at every startup, so is it possible to preserve the file path into an option or a config file, to avoid the manual part ?
Yours sincerely,
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Dear miurahr,
I'm utterly enamored of the ebviewer you wrote, especially the style in the chameleon screenshot of README, and the part where you started to implement mdict format parser in #38.
And I still have some questions of the in-app layout.
indicated as following two images (ebviewer above, goldendict below), all text are "congested", that's neat for short explanation, but it becomes a little bit tiresome to eyes for long long explanation. So is it possible to display the original CSS format, or add an option to manually adjust (e.g. line spaces)?
dict files need uploading at every startup, so is it possible to preserve the file path into an option or a config file, to avoid the manual part ?
Yours sincerely,
The text was updated successfully, but these errors were encountered: