Welcome to SaveAny-Bot Discussions!

[krau]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[homuzer]

Hello! I want to thank the developer for his creation, I have wanted this for a long time, thank you very much for your work!
but I have two questions:

1. can the bot save a file with the name as in the message header, look at the screenshot
2. Is it possible to convert the bot’s interface language to another, say Russian, if so, how difficult is it?

[krau]

1. You can use the /config command to change the filename strategy.
2. Adding support for other languages is easy, but requires some go development experience. We currently support English(en) and Chinese(zh-CN), see the common/i18n folder for details.You can switch languages by specifying the lang field in the bot's configuration file.

[homuzer]

I added the line lang = "en" to configuration file, but the language does not change What am I doing wrong?

[krau]

The lang field is a global configurable option which should be placed at the top of the configuration file, not below the telegram section. Alternatively, you can specify the language using the command-line argument -l.

[homuzer]

could you give an example of a command?

[krau]

could you give an example of a command?

see the readme for config file example, i updated it for lang configuration

[homuzer]

I noticed an imperfection in saving file names

[krau]

Try using a custom filename template if you want to retain the full original text of the message.

[homuzer]

Why doesn't this function work correctly by default? What's the reason? Can you provide an example of a custom template, and how and where it's embedded?

[krau]

The default filename generation strategy processes the message content to produce more standard filenames.
If you want to retain all the original message text in the filename, use the {{.msgraw}} variable in the /fnametmpl command (although I don't recommend doing so).