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

[Feature Request]: .eml email file #1363

Closed
1 task done
ilyasch199 opened this issue Jul 3, 2024 · 8 comments
Closed
1 task done

[Feature Request]: .eml email file #1363

ilyasch199 opened this issue Jul 3, 2024 · 8 comments
Labels

Comments

@ilyasch199
Copy link

Is there an existing issue for the same feature request?

  • I have checked the existing issues.

Is your feature request related to a problem?

No response

Describe the feature you'd like

can you add the support for .eml files

Describe implementation you've considered

a parser for email files

Documentation, adoption, use case

No response

Additional information

No response

This was referenced Aug 6, 2024
KevinHuSh added a commit that referenced this issue Aug 6, 2024
### What problem does this PR solve?

add support for eml file parser
#1363

### Type of change

- [x] New Feature (non-breaking change which adds functionality)

---------

Co-authored-by: Zhedong Cen <cenzhedong2@126.com>
Co-authored-by: Kevin Hu <kevinhu.sh@gmail.com>
@peizimo
Copy link

peizimo commented Oct 14, 2024

The presentation parsing method does not support "Enhancing RAPTOR strategy with Recalls",ask for help,if thus,pptx file will lose context after parsing .
84cdc8f8d56c40104830f8dc8d32e6f7

@KevinHuSh
Copy link
Collaborator

fixed.

@peizimo
Copy link

peizimo commented Oct 17, 2024

fixed.

Thanks for your reply !
Today I found another bug , When I run the App and RAGFlow at the same time , the App will refer to the recent history reply of the API Key Token session window used , I don't know if you understand what I'm saying , Looking forward to communicating with you !

@KevinHuSh
Copy link
Collaborator

The API and server share the same data source.

@peizimo
Copy link

peizimo commented Oct 21, 2024

The API and server share the same data source.

Thanks for your reply ! Even if it's not the same conversation id, one on ragflow and one newly created conversation id through the API call interface .

I'll follow up on that one.

I'm looking forward to feeding my voice to ragflow, I wonder when it will be available .

I also hope that chat module can support translation into multiple languages for retrieval. Is there any plan to launch it .

Thank you very much!

@peizimo
Copy link

peizimo commented Oct 21, 2024

image
I don't see this parsing method on the front end anymore

@peizimo
Copy link

peizimo commented Oct 21, 2024

image
The audio file was parsed successfully, but no block was parsed

KevinHuSh added a commit that referenced this issue Oct 22, 2024
### What problem does this PR solve?

#1363

### Type of change

- [x] Bug Fix (non-breaking change which fixes an issue)
@peizimo
Copy link

peizimo commented Oct 22, 2024

thanks for your reply , this is the current scene
image

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

No branches or pull requests

3 participants