-
Notifications
You must be signed in to change notification settings - Fork 1
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
🌐 Translate About and Architecture #91
Conversation
Just think, does it make you sense to add info about which protocols we're supporting somewhere in README info? I think that support of other protocols instead just HTTP or HTTPS does not make sense but I am not sure.... |
It may make sense in the Downloader section or the general overview. But it feels similar to the JSON dispute earlier: it is too implementation-specific. Also, although we didn’t think about supporting anything other than HTTP, it makes sense to scrape an FTP drive, a Git repository, an IMAP mailbox, or a WebDAV storage. We don’t support anything other than HTTP for now, but even that is still very rudimentary. It would be bold even to say we support HTTP. |
I started to dislike the changes I proposed. The translation was not accurate and even incorrect. Also, the Pull Request is too big, amending two sections simultaneously. I’ll replace it with better ones. Thank you for the review! |
Ok, unfortunately my english skills are not up to the level which I could assess quality of your translation. I've just known that it made sense and I understood the content from it. |
0124269
to
effba1c
Compare
Replaced by #107. |
No description provided.