dotnet / dotnet/ResXResourceManager

Don't run translation on all untranslated strings

Open
#374 7 comments 0 reactions 0 assignees View on GitHub
Feature request Up for grabs
Dominant language
C#
Stars
1.5k
Forks
251
Avg merge
1d 1h
Merged PRs (30d)
1

Description

I have a project where not all strings are going to need translated. This is happening because we are changing our UI technology from being MVC/Razor based to being Vue based. As a result there are a lot of strings in our resource file that don't need to be translated.

But as I just started using ResX for translation, I am seeing that it is trying to translate every one of our 3000 strings in the background before I can even see the result of any translation. This design makes it impossible to translate on a budget.

A much better approach would be to have the user first pre-select the strings that need to be translated, then hit start to start the background translation. Then let the process flow as it is currently designed,

The key change is not to translate everything at once. Let the user choose what strings to send to the translation service.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.