-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
Labels
Area: UXIssues related to user experience.Issues related to user experience.Waiting for: DemandLow priority for development. Pull requests welcome. Can be prioritized by sponsorship.Low priority for development. Pull requests welcome. Can be prioritized by sponsorship.
Description
Describe the problem
For each localization component in a git project
- I need to fill out the "add new component" form.
- That scans my repo and suggests the potential candidates.
- For this I first have to enter stuff which later gets partially ignored, since I selected the discovered component.
- Then I need to fill out the rest of the form which contains defaults I don't want.
- Then I need to store it.
- Then I need to enter the component settings again, to edit settings which weren't shown to me before.
- Then I need to go to the project root.
- Then I hit the "components" tab.
- Finally I can start with the next component.
- I need to repeat all these steps for every component I want to add.
This is completely upside down to how it actually should be.
(And btw. you're seriously wasting user's time and annoy them with that procedure.)
Solution brainstorm
What it should look like: Have a wizard which lets me add all or some components of a git project.
- Enter Git URL.
- Weblate scans, shows potential components.
- I select all components I want.
- I choose all settings which apply to all component types once.
- I step through settings which only apply for a specific component.
- I hit "Finish". Everything is setup up. All done.
Side note: Defaults I constantly have to change:
- Manage strings, edit base file: Noooo, no translators should be able to mess with the source strings. The source code is the source of truth, not the other way around.
- Push on commit: No, I don't want pull requests every day.
- Merge style: Rebase is too error-prone.
- Lock on error: Errors all the time, would lead to too much lock time. (See my other issue Apple strings files: Weblate is constantly fighting with BartyCrouch over the existence of non-comments #18241)
- Adding new translation: Random people should not be able to induce a PR which creates files in my project. Which then typically are empty. (And would be unused anyway, since I would also have to edit the project configuration to enable the new languege). I have to decline these PRs, but then Weblate is angry at me again.
Describe alternatives you have considered
No response
Screenshots
No response
Additional context
I created this issue after I had a conversation with @orangesunny.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Area: UXIssues related to user experience.Issues related to user experience.Waiting for: DemandLow priority for development. Pull requests welcome. Can be prioritized by sponsorship.Low priority for development. Pull requests welcome. Can be prioritized by sponsorship.