images in the pdf file cannot show
Self Checks
- [x] I have searched for existing issues search for existing issues, including closed ones.
- [x] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
- [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
- [x] Please do not modify this template :) and fill in all the required fields.
1. Is this request related to a challenge you're experiencing? Tell me about your story.
I was using the knowledge base,and I uploaded a pdf file with some images.Then I searched ,the Dify just showed the text context,but no images related to the text context. I was confused , and Dify cannot be used . I give you a suggestion ,you can see the TencentCloud,it has done.
2. Additional context or comments
No response
3. Can you help us with this feature?
- [ ] I am interested in contributing to this feature.
This is a known issue, as you can see in the code, we only extract texts out of the PDF files and ignore the images, this requires a something like Extract Flow to do this. We are gonna to do this later. :)
thanks ,i hope you can solve it ,we have many customers
---Original--- From: @.> Date: Wed, Feb 26, 2025 22:39 PM To: @.>; Cc: @.@.>; Subject: Re: [langgenius/dify] images in the pdf file cannot show (Issue#14422)
This is a known issue, as you can see in the code, we only extract texts out of the PDF files and ignore the images, this requires a something like Extract Flow to do this. We are gonna to do this later. :)
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***> crazywoola left a comment (langgenius/dify#14422)
This is a known issue, as you can see in the code, we only extract texts out of the PDF files and ignore the images, this requires a something like Extract Flow to do this. We are gonna to do this later. :)
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
you have solved the problem in the v1.0.0, do you?
The latest version still hasn't resolved this issue. Is there a plan to address it?