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

Not detecting invalid character in title #515

Closed
aantiix opened this issue Jan 13, 2017 · 1 comment
Closed

Not detecting invalid character in title #515

aantiix opened this issue Jan 13, 2017 · 1 comment
Assignees
Labels
Milestone

Comments

@aantiix
Copy link

aantiix commented Jan 13, 2017

Please describe the problem or feature request in detail:

When entering a title with invalid characters, normally they are detected and a message pops up, however, a colon (:) is not being reported as such so the job fails when a title is detected with one. The file appears to encode, taking the expected amount of time. The name of the file is in the correct output directory with the file name truncated at the : (with no extension). However, the file size is 0KB and even manually adding the extension back on again, its not recognized as a valid file. The log name is the opposite in that the name begins after the colon.

What are the steps to reproduce this problem:

Enter a file name containing a : (colon).

What version of HandBrake you are running:

1.0.1 (2016122900) - 64bit (though this issue existed in previous versions as well). Downloaded from handbrake.fr.

What operating system and version and you running (e.g. OSX 10.11, Windows 7, Ubuntu 14):

Windows 10 - 64bit (Version 1607 build 14393.576)

Was there any error message or error dialog, if so please detail or provide screenshots:

Please provide the full activity log for the encode or scan attempt. You may attach the log as a file, post a pastebin URL to the log, or place the log inline below:

Vol. 1.mp4 01-13-2017 11-27-54.txt

@sr55 sr55 self-assigned this Jan 14, 2017
@sr55 sr55 added the Bug label Jan 14, 2017
@sr55 sr55 added this to the 1.0.2 milestone Jan 14, 2017
@sr55
Copy link
Contributor

sr55 commented Jan 14, 2017

Corrected the checker, so it should now prevent erroneous file names in the destination box from being accepted. Will be available in the next nightly build.

Thanks for reporting.

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

No branches or pull requests

2 participants