JavLibrary_python.yml, Better formatting keywords before sending request to source site #1301
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e, therefore Identifying step usually failed because media file is bad, use https://github.com/jvlflame/Javinizer/blob/master/src/Javinizer/jvSettings.json\#L45 from javinizer seem to be better
AndyHoang
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
javlibrary python is sending whole filename as scene title, therefore Identifying task usually have zero result just because media file naming is bad
use https://github.com/jvlflame/Javinizer/blob/master/src/Javinizer/jvSettings.json#L45 from javinizer seem to be better for guessing jav code
Some of testcase:
become
MEYD-799hhd800.com@JUQ-208.mp4become
JUQ-208