1) The current i18n branch is work-in-progress and the msgids are subject to change at my whim. I can and I will change msgids if I think it would improve translations or user experience. This is normal and recommended practice even for stable software. I'm giving you a warning since you would essentially be working on a moving target. This is not necessary a bad thing, it means that I'm open to suggestions too.
2) I recommend not to alter the dcpp/po/ files (even though they might be poor translations). They are pulled from upstream, and are maintained by upstream. This means that you'll have to contribute to DC++ directly to change these files. DC++ uses launchpad translations, where this dcpp directory is translated separately.
3ED: You are not extracting msgids properly. See the i18n.sh script.
I'm responding to bug mail, but I will not work with this until the start of February. I hope I will get some free time by then.
2 notices to all translators:
1) The current i18n branch is work-in-progress and the msgids are subject to change at my whim. I can and I will change msgids if I think it would improve translations or user experience. This is normal and recommended practice even for stable software. I'm giving you a warning since you would essentially be working on a moving target. This is not necessary a bad thing, it means that I'm open to suggestions too.
2) I recommend not to alter the dcpp/po/ files (even though they might be poor translations). They are pulled from upstream, and are maintained by upstream. This means that you'll have to contribute to DC++ directly to change these files. DC++ uses launchpad translations, where this dcpp directory is translated separately.
3ED: You are not extracting msgids properly. See the i18n.sh script.
I'm responding to bug mail, but I will not work with this until the start of February. I hope I will get some free time by then.