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

It would be nice if GINJ accepted inverted commas. I am pretty sure that Jing did. #53

Closed
DennisPolack opened this issue Dec 16, 2021 · 8 comments
Labels
bug Something isn't working

Comments

@DennisPolack
Copy link

It would be nice if GINJ accepted inverted commas. I am pretty sure that Jing did.

@DennisPolack
Copy link
Author

It would be nice if GINJ accepted inverted commas. I am pretty sure that Jing did.
I have tried using arrows >>Text<< it is cumbersome and doesn't mean the same as "Inverted Commas" (>>Inverted Commas<<)

@vicnevicne
Copy link
Contributor

vicnevicne commented Dec 16, 2021

Mmmh, I admit I don't understand what you mean by "inverted commas"...
Do you mean quotes ? As far as I can tell, all are supported :
2021-12-16_22-51-39
Now some of them are not available on all keyboards, but you can get them using copy/paste or (on Windows at least) by typing their codes, e.g. Alt 0171 and Alt 0187 for « »

In any case I don't think it really is a Ginj issue.

If you mean something else, just tell me or type the chars in question in a comment here...

Vicne

Edit: oh, there's also this kind:
2021-12-16_22-58-30

@DennisPolack
Copy link
Author

DennisPolack commented Dec 17, 2021 via email

@vicnevicne
Copy link
Contributor

vicnevicne commented Dec 18, 2021

Err, maybe I didn't understand what you mean by "accept".
I thought you meant you weren't able to type double quotes in a text box.
Now I understand you meant using double quotes in the name of the capture under the image, and indeed that name is used as the default filename, which cannot contain double quotes on Windows:
https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file

When looking at the log, Ginj indeed does not perform any "cleanup" on the capture name before passing it to the filename selection box, and that causes an error:

Encountered an error while saving image as
'D:\TEMP\2021-12-18_23-02-21 "test".png'
Can't create an ImageOutputStream!
More info is available on the Java console
javax.imageio.IIOException: Can't create an ImageOutputStream!
	at java.desktop/javax.imageio.ImageIO.write(ImageIO.java:1551)
	at info.ginj.export.disk.DiskExporter.exportCapture(DiskExporter.java:240)
	at info.ginj.ui.CaptureEditingFrame.lambda$onExport$10(CaptureEditingFrame.java:642)
	at java.base/java.lang.Thread.run(Thread.java:832) 

I'll add a "cleanup" phase to make sure forbidden characters are replaced before saving.

Thanks.

@vicnevicne vicnevicne added the bug Something isn't working label Dec 18, 2021
@DennisPolack
Copy link
Author

DennisPolack commented Dec 19, 2021 via email

@vicnevicne
Copy link
Contributor

Hi Dennis,

Can you try the latest (0.4.8) version to see if it solves the issue ?

Also, please reply on the Github website and not by e-mail, because Github only imports basic text from e-mails (no attachments, no font color etc.)

Kind regards,
Vincent

@DennisPolack
Copy link
Author

Hi Vicne, Thank you - Works perfectly now after restart.

Thanks again

Best Wishes for a Merry Christmas and a Healthy and Rewarding New Year.

@vicnevicne
Copy link
Contributor

Thanks for reporting the issue, testing and confirming it's now OK.

Best wishes to you and your loved ones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants