Summary: | Translation template are not updated on Transifex | ||
---|---|---|---|
Product: | PulseAudio | Reporter: | Cheng-Chia Tseng <pswo10680> |
Component: | misc | Assignee: | pulseaudio-bugs |
Status: | RESOLVED FIXED | QA Contact: | pulseaudio-bugs |
Severity: | normal | ||
Priority: | medium | CC: | colin, fitojb, lennart, piotrdrag |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Cheng-Chia Tseng
2012-02-01 22:44:12 UTC
We disabled the Transifex hookup when Tx stopped to apply changes in separate commits to git. We need proper attribution of translation changes, and that also means we need proper commits to git for that, with the right author filled in, and not all merged into one. Until the point that Tx doesn't supply that we will not be able to hook up the project with Tx again. Quite frankly I don't understand how any open source project can currently live without proper attribution of the translations. Could you please advise how translators can contribute their translation to PulseAudio? The wiki page said that "Please note that translations submitted by other means (bug tickets, mailed patches) will be ignored (or closed as "wontfix" in the case of bug tickets)." Can we translators submit po files via freedesktop bug tracker instead now? Hi Guys, Please do submit patches for translations via this bug tracker. I ran an update-po a while ago so fingers crossed it's fairly up-to-date and ready for translations! I'd appreciate it if you could add "i18n" to the keywords section of bugs you submit. We've just migrated wiki to freedesktop.org (the link in comment 1 should redirect) so I've made sure to update the section regarding translations with a different description until a more automated system can be enabled again. I guess that means this bug is "solved" now, so I'll close it, but I'll definitely try and get a proper system hooked up. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.