-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
*: remove non-ASCII characters where appropriate #5768
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
Conversation
I'll search for the characters that I've removed here in the translation pages. |
- Check pathames for validity in the current system: | ||
|
||
`pathchk {{path1 path2 …}}` | ||
`pathchk {{path1}} {{path2}}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It almost looks like the original is standard syntax for multiple options (which I'm a fan of 👍🏻). If it is, I'd like to open a new PR to standardize this across the other pages (and I'll fix it here as well). Is it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like it too. It should render to the exact same result and looks cleaner.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, not exactly the same, depending on your client. Mine, the node client, underlines text in token syntax, so the difference between the old one (which I prefer) and the new modification I made (which I'll revert) is that the old one underlines the space because the space is included between the handlebars, while in the newer version, the space is outside of them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally in other pages I've done {{thing1}} {{thing2}} {{thingN}}
personally
I think it's dependent on context
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure I'm a fan of these changes, @bl-ue. You've completely dropped the …
in places which carries important meaning, which should ideally be replaced with ...
.
There are some grammatical improvements here and some apostrophe changes which are fine though.
- Aggiungi uno o più ebook alla libreria: | ||
|
||
`calibredb add {{file1 file2 …}}` | ||
`calibredb add {{file1}} {{file2}}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can be an arbitrary number of items.
`calibredb add {{file1}} {{file2}}` | |
`calibredb add {{file1}} {{file2}} {{fileN}}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be possible to replace path/to/file
with file
in general? It looks much cleaner and readable and in most cases it's redundent. In cases where it's important we could keep it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a fan of path/to/file
because it clearly indicates that it's a file path, as opposed to a file name (because there are commands that take a file name, not path, e.g. this). It also makes it easy to indicate if the path must be an absolute one, which, in fact, many tools require.
Also, file
can look more like a variable in many contexts, whereas path/to/file
is very clearly one and only one thing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
path/to/file
is our convention elsewhere, so generally speaking we prefer it over file
. But file
can be useful if you have many items, sure as here.
- Rimuovi uno o più ebook dalla libreria. Sono necessari gli ID (vedi sopra): | ||
|
||
`calibredb remove {{id1 id2 …}}` | ||
`calibredb remove {{id1}} {{id2}}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here
`calibredb remove {{id1}} {{id2}}` | |
`calibredb remove {{id1}} {{id2}} {{idN}}` |
- Scan a specific list of ports (use -p- for all ports 1-65535): | ||
|
||
`nmap -p {{port1,port2,…,portN}} {{address_or_addresses}}` | ||
`nmap -p {{port1,port2,port3}} {{address_or_addresses}}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should keep the portN here at least.
`nmap -p {{port1,port2,port3}} {{address_or_addresses}}` | |
`nmap -p {{port1,port2,portN}} {{address_or_addresses}}` |
- Check pathnames for validity on a wider range of POSIX compliant systems: | ||
|
||
`pathchk -p {{path1 path2 …}}` | ||
`pathchk -p {{path1}} {{path2}}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This can be an arbitrary number of items, which this edit is not expressing.
`pathchk -p {{path1}} {{path2}}` | |
`pathchk -p {{path1}} {{path2}} {{pathN}}` |
- Check pathnames for validity on all POSIX compliant systems: | ||
|
||
`pathchk --portability {{path1 path2 …}}` | ||
`pathchk --portability {{path1}} {{path2}}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here
`pathchk --portability {{path1}} {{path2}}` | |
`pathchk --portability {{path1}} {{path2}} {{pathN}}` |
- Only check for empty pathnames or leading dashes: | ||
|
||
`pathchk -P {{path1 path2 …}}` | ||
`pathchk -P {{path1}} {{path2}}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here
`pathchk -P {{path1}} {{path2}}` | |
`pathchk -P {{path1}} {{path2}} {{pathN}}` |
- Merge multiple files: | ||
|
||
`samtools merge {{output}} {{input1 input2 …}}` | ||
`samtools merge {{output}} {{input1}} {{input2}}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again with the changing the meaning.
`samtools merge {{output}} {{input1}} {{input2}}` | |
`samtools merge {{output}} {{input1}} {{input2}} {{inputN}}` |
- Show the history of specific files or directories: | ||
|
||
`tig {{path1 path2 …}}` | ||
`tig {{path1}} {{path2}}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`tig {{path1}} {{path2}}` | |
`tig {{path1}} {{path2}} {{pathN}}` |
Hi all! This thread has not had any recent activity. |
Hi all! This thread has not had any recent activity. |
I'm going to close this until I feel like I want to get back to it. |
'Appropriate' because there is only one occurence where I did not remove the non-ASCII character:
https://github.com/tldr-pages/tldr/blame/f72f348a0368676b52b3d5ccad4bcb70b1805343/pages/common/chars.md#L8
I also didn't touch the translations as the non-ASCII characters in them are (mostly) desired.