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

Amphetype asks for untypable input #13

Open
GoogleCodeExporter opened this issue Mar 22, 2015 · 7 comments
Open

Amphetype asks for untypable input #13

GoogleCodeExporter opened this issue Mar 22, 2015 · 7 comments

Comments

@GoogleCodeExporter
Copy link

I use a wide variety of e-book texts, and the formatting conventions differ
greatly over them all. The most annoying single thing about this is that
often a extract will contain untypable input.

An example: My keyboard only has '-'; it doesn't have ‒, –, —, or ― (or,
for that matter, many of the characters listed in
https://secure.wikimedia.org/wikipedia/en/wiki/Hyphen or
https://secure.wikimedia.org/wikipedia/en/wiki/Dash )

So if Amphetype gives me a text selection containing any of those, I might
type satisfactorily up to the offending character and be stopped.

It'd be best for Amphetype to do something like translate everything into
ASCII which I can actually type.

Original issue reported on code.google.com by gwe...@gmail.com on 13 Feb 2009 at 5:12

@GoogleCodeExporter
Copy link
Author

+screenshot of example uncompletable text

Original comment by gwe...@gmail.com on 13 Feb 2009 at 5:21

Attachments:

@GoogleCodeExporter
Copy link
Author

I would suggest offering it as an option to convert Hyphens etc, cause I use a 
keyboard layout which has a key for every hyphen. So I wouldnt want them to be 
converted

Original comment by quietdeath@gmail.com on 13 Feb 2009 at 7:36

@GoogleCodeExporter
Copy link
Author

quietdeath: the hyphens were just an example. The issue also arises with 
Unicode'fyed
ellipses and quotation marks. I doubt your keyboard layout has keys for all of 
those
as well!

Original comment by gwe...@gmail.com on 22 Feb 2009 at 6:31

@GoogleCodeExporter
Copy link
Author

Untypable input in general is very hard to get rid of automatically since I 
don't
know how your keyboard setup is (personally I can type both the ellipsis and 
emphasis
hyphen). And when you say "translate into ASCII", hmm, I will look into it, but 
I
guess I would have to make my own translation table like "ß" -> "ss", "å" -> 
"aa",
"—" -> "--" because I am unaware of anything standard that does this 
automatically. I
could *strip* all non-ASCII characters (or replace them all with some arbitrary 
char)
very easily, but I am guessing that's not what you want. :) But yeah.. I want a
better text edititing / import too.

Original comment by tristesse on 10 Mar 2009 at 9:58

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

> I
could *strip* all non-ASCII characters (or replace them all with some arbitrary 
char)
very easily, but I am guessing that's not what you want.

That actually might work pretty well. I'm using ebooks, so I'm used to strange
formatting in them - blank spaces or no replacement at all wouldn't be 
particularly
odd. And the odder it is, the better a typing challenge, I suppose.

Original comment by gwe...@gmail.com on 11 Mar 2009 at 3:16

@GoogleCodeExporter
Copy link
Author

Maybe there could be some sort of interaction with the actual layout used, so 
that
Amphetype can check the text and replace all untypable chars by a star or an 
underscore…

This would have to be handled either by keeping a folder of keymaps and letting 
the
user specify which one he use, or by interacting with the system directly…

Original comment by joan.cha...@gmail.com on 3 Jul 2009 at 7:40

@GoogleCodeExporter
Copy link
Author

any updates regarding this issue?

and also could you put an option to disable "backspace",  
so our pinky won't get used in pressing the backspace key whenever we make 
typing mistakes.


by the way this is a great project, the best i have tried.
i hope this project is not abandoned.

Original comment by wohlstan...@gmail.com on 4 Sep 2012 at 2:23

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

1 participant