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

Path unusable for copy #51

Open
Akaizoku opened this issue Jun 27, 2018 · 4 comments
Open

Path unusable for copy #51

Akaizoku opened this issue Jun 27, 2018 · 4 comments
Assignees

Comments

@Akaizoku
Copy link

While the use of menukeys is great visually, it makes it impossible to re-use a path by selecting and copying it.

It would be great if it was possible to change the actual text behind the visual separators to re-use the same separator that was used to break the path appart.

@tweh
Copy link
Owner

tweh commented Jul 3, 2018

This is a pretty nice idea, however at the moment unfortunately I don’t have the time to work on the packe, but I’ll keep it in mind!

@Skillmon
Copy link
Collaborator

Skillmon commented Nov 5, 2020

This could be possible with the accsupp package. The result would depend on the used PDF viewer (I tested the accsupp package with a few a while ago and while some pick up on the ActualText others ignore it).

Maybe we could provide a package option to switch on/off the use of accsupp. The output routine would have to be changed for this to use something like

\BeginAccSupp{ActualText=<string>}%
  <original output routine>%
\EndAccSupp{}

We'd have to make sure that there is no page break between \BeginAccSupp and \EndAccSupp. Maybe we could even only apply it to the separator, which should be more stable (but a bit more work).

@Skillmon Skillmon self-assigned this Nov 5, 2020
@tweh
Copy link
Owner

tweh commented Nov 6, 2020

If we apply it only to the separator I fear it could happen that some viewers add extra spaces (from bevor after the separator) which would circumvent the whole effort of making the path copy-able.

@Skillmon
Copy link
Collaborator

Skillmon commented Nov 6, 2020

Yes, this could happen indeed. I'll have to try things, maybe I can come up with something that works well across a bunch of viewers.

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

No branches or pull requests

3 participants