Skip to content

Conversation

bl-ue
Copy link
Contributor

@bl-ue bl-ue commented Apr 15, 2021

'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.

@bl-ue bl-ue added page edit Changes to an existing page(s). mass changes Changes that affect multiple pages. labels Apr 15, 2021
@bl-ue bl-ue marked this pull request as draft April 15, 2021 19:08
@bl-ue
Copy link
Contributor Author

bl-ue commented Apr 15, 2021

I'll search for the characters that I've removed here in the translation pages.

@bl-ue bl-ue added the translation Issues requesting translating pages from English to other languages. label Apr 15, 2021
@bl-ue bl-ue marked this pull request as ready for review April 15, 2021 21:16
- Check pathames for validity in the current system:

`pathchk {{path1 path2}}`
`pathchk {{path1}} {{path2}}`
Copy link
Contributor Author

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?

Copy link
Contributor

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.

Copy link
Contributor Author

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.

Copy link
Member

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

@bl-ue bl-ue marked this pull request as draft April 19, 2021 15:31
Copy link
Member

@sbrl sbrl left a 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}}`
Copy link
Member

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.

Suggested change
`calibredb add {{file1}} {{file2}}`
`calibredb add {{file1}} {{file2}} {{fileN}}`

Copy link
Contributor

@marchersimon marchersimon Apr 20, 2021

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.

Copy link
Contributor Author

@bl-ue bl-ue Apr 20, 2021

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.

Copy link
Member

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}}`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

Suggested change
`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}}`
Copy link
Member

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.

Suggested change
`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}}`
Copy link
Member

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.

Suggested change
`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}}`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

Suggested change
`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}}`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here

Suggested change
`pathchk -P {{path1}} {{path2}}`
`pathchk -P {{path1}} {{path2}} {{pathN}}`

- Merge multiple files:

`samtools merge {{output}} {{input1 input2}}`
`samtools merge {{output}} {{input1}} {{input2}}`
Copy link
Member

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.

Suggested change
`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}}`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
`tig {{path1}} {{path2}}`
`tig {{path1}} {{path2}} {{pathN}}`

@github-actions
Copy link

Hi all! This thread has not had any recent activity.
Are there any updates? Thanks!

@github-actions github-actions bot added the waiting Issues/PRs with Pending response by the author. label May 17, 2021
@bl-ue bl-ue removed the waiting Issues/PRs with Pending response by the author. label May 17, 2021
@github-actions
Copy link

github-actions bot commented Jun 1, 2021

Hi all! This thread has not had any recent activity.
Are there any updates? Thanks!

@github-actions github-actions bot added the waiting Issues/PRs with Pending response by the author. label Jun 1, 2021
@bl-ue
Copy link
Contributor Author

bl-ue commented Jun 9, 2021

I'm going to close this until I feel like I want to get back to it.

@bl-ue bl-ue closed this Jun 9, 2021
@bl-ue bl-ue deleted the pure-ascii branch June 9, 2021 15:30
@bl-ue bl-ue restored the pure-ascii branch June 9, 2021 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mass changes Changes that affect multiple pages. page edit Changes to an existing page(s). translation Issues requesting translating pages from English to other languages. waiting Issues/PRs with Pending response by the author.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants