russian and other locales support #584
Comments
stamepicmorg
changed the title
|
Same trouble |
|
@Aleks-Z, please refrain from "me too"-style comments. They pollute the issue tracker, add nothing to the discussion and actually do not affect the motivation of those who are able to fix things -- quite contrary, they might make them angry. |
|
@stamepicmorg, were #496, #403, #378 not enough to cover this problem? What warranted creating another issue? |
|
sorry but the problem is not solved.. In one issue, the author refers to the lightweight installer. So the final decision and has not followed. |
|
What prevents the installer to create a second with only localizations? Or, as has been previously suggested to make two versions of the installer - portable (current) and complete? At each issues a new answer. And yes - a can manually install locales. I know it.. |
|
hmmm. ok. can i try to create standalone installer of languages and if it will be work fine i will add it as pull request at "build-extra" repository? |
|
These questions have been answered already, with If you truly care about this issue, here is the way to go forward:
I am curious to see your progress. |
|
@dscho Thank you for answer! I will really try it. Sorry for my bad English, Merry Christmas and Happy New Year! |
Migrate applicable secrets to a new 'release' workflow environment. This is a security measure to help ensure secrets cannot be accessed by those without proper permissions. An example of a passing `build-git-installers` workflow with these changes can be found [here](https://github.com/ldennington/git/actions/runs/5182147378) (I set up my fork with the same migrated secret values as this repo). Note that the old actions secrets will be left in this repo until the next successful release, at which point they can be safely removed.
Migrate applicable secrets to a new 'release' workflow environment. This is a security measure to help ensure secrets cannot be accessed by those without proper permissions. An example of a passing `build-git-installers` workflow with these changes can be found [here](https://github.com/ldennington/git/actions/runs/5182147378) (I set up my fork with the same migrated secret values as this repo). Note that the old actions secrets will be left in this repo until the next successful release, at which point they can be safely removed.
Migrate applicable secrets to a new 'release' workflow environment. This is a security measure to help ensure secrets cannot be accessed by those without proper permissions. An example of a passing `build-git-installers` workflow with these changes can be found [here](https://github.com/ldennington/git/actions/runs/5182147378) (I set up my fork with the same migrated secret values as this repo). Note that the old actions secrets will be left in this repo until the next successful release, at which point they can be safely removed.
Hello.
Is it possible to add language support for the Russian language in the new version?
It was at all "msysgit" pre-releases, and it exists in the current SDK.
Thanks.
The text was updated successfully, but these errors were encountered: