Core: Provide more configuration options for customizing the translation process

[skytin1004]

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Description

It would be helpful to provide users with more control over the translation process by adding specific features like:

• The ability to skip image translation.
• The option to select folders or files to exclude from the translation process.
• The ability to adjust the criteria or rules when verifying translations for accuracy.

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

azd version?

run azd version and copy paste here.

Versions

Mention any other details that might be useful

---

Thanks! We'll be in touch soon.

Once the plan is more concrete, I intend to break this issue down into separate issues for each feature (e.g., skipping image translation, folder exclusion, and adjustable translation verification criteria).

Thank you, @Shardakaur2624, for providing feedback on this issue!

[Shardakaur2624]

1. Create separate issues for each feature, as outlined above.
2. Assign priority levels to each issue based on user needs and technical complexity.
3. Begin gathering requirements and technical details for each issue.
4. Develop a plan for implementing each feature, including timelines and resource allocation.

[skytin1004]

Hi @Shardakaur2624,

As you suggested, I'm going to create sub-issues within this main issue to address each specific feature - skip image translation, customization of folder exclusion, and customization of translation validation criteria.

Prioritizing these issues is definitely a good idea. I'm considering looking at other open source projects for best practices that can guide us in discussing concrete solutions going forward.

Creating a detailed implementation plan is crucial, especially to get this project to a solid 1.0.0 release. We'll need to systematically outline the required features and their implementation steps to ensure that we support all target languages flawlessly.

I look forward to working on these steps to take this project to the next level.

Thanks again for your insightful feedback!