-
Notifications
You must be signed in to change notification settings - Fork 107
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
Are you able to generate handwriting for special symbols such as @,✓, +, $ and £? #23
Comments
Hi @AIMLAPP, unfortunately all of those symbols where not present in training dataset (except I'm not sure about quality of uppercase letters (I think those are rather rare) but they are present in dataset so it should be possible to generate them. :) |
Hi @Grzego, I hope you're well. Ah OK, I understand. Thank you very much for your reply, I really appreciate it. :) I have an additional question I would like to ask please. In your "ReadMe" section, I see that you have used the On-Line dataset. The xml files contain the handwriting data. Do you know how to convert these into a .jpg/.png such that I can visualise the handwriting (i.e. convert the On-Line dataset into "Offline")? I'm thinking of creating my own dataset like the xml files, but would like to also visualise and verify them through this conversion. Thank you and have a good weekend! |
@AIMLAPP so it seems there is a ready off-line dataset available at "data/lineImages-all.tar.gz". According to this page where you can download and example from it, it contains EDIT: Sorry, I missed your part about visualizing own dataset. So in this case you can look at this short script I posted in other issue. The parts with plotting should be the most interesting in your case. :) |
Hello,
I've been exploring different handwriting generators and would like to ask a question about this one.
May I please ask if your model, given the data you used to train it, is able to generate special symbols such as @, +, $ and £, ✓, as well as uppercase Q and Z?
Many thanks! :)
The text was updated successfully, but these errors were encountered: