Bug: When renaming a culture, existing translations must be renamed accordingly #44

Closed
opened 2022-10-30 13:27:55 +00:00 by thorsten · 3 comments
thorsten commented 2022-10-30 13:27:55 +00:00 (Migrated from devops.tsommer.org)

When renaming a culture, existing translations must be renamed accordingly

When renaming a culture, existing translations must be renamed accordingly
thorsten commented 2022-11-01 18:56:09 +00:00 (Migrated from devops.tsommer.org)
created branch [`44-bug-when-renaming-a-culture-existing-translations-must-be-renamed-accordingly`](/open-source/dotnet/i18n-commander/-/compare/main...44-bug-when-renaming-a-culture-existing-translations-must-be-renamed-accordingly) to address this issue
thorsten commented 2022-11-01 18:56:13 +00:00 (Migrated from devops.tsommer.org)

mentioned in merge request !23

mentioned in merge request !23
thorsten commented 2022-11-01 19:41:39 +00:00 (Migrated from devops.tsommer.org)

mentioned in commit d9ba6eeb59

mentioned in commit d9ba6eeb596ae6fb13c66a836f5196b090d62077
thorsten (Migrated from devops.tsommer.org) closed this issue 2022-11-01 19:41:39 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Dotnet/I18NCommander#44
No description provided.