You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2017-01-16 11:43:16 +00:00 (in Redmine)
Currently when working with multiple people doing translations for the same module, you end up with a huuuuge GIT commit every time someone with a differing module_path translates just a single string. Fixing this would mean to strip the base path afterwards, as there seems to be no option but --no-location for this.
The text was updated successfully, but these errors were encountered:
lippserd
changed the title
[dev.icinga.com #14027] translation should not write absolute path to .po files
[dev.icinga.com #14027] Translation module should not write absolute path to .po files
Sep 20, 2017
This issue has been migrated from Redmine: https://dev.icinga.com/issues/14027
Created by tgelf on 2017-01-16 11:43:16 +00:00
Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2017-01-16 11:43:16 +00:00 (in Redmine)
Currently when working with multiple people doing translations for the same module, you end up with a huuuuge GIT commit every time someone with a differing module_path translates just a single string. Fixing this would mean to strip the base path afterwards, as there seems to be no option but --no-location for this.
The text was updated successfully, but these errors were encountered: