Re: [poedit-users] keep obsolete strings when updating from pot file
Vaclav Slavik <[email protected]>
| Newsgroups | gmane.editors.poedit.user |
|---|---|
| Message-ID | <[email protected]> |
Claudia Kosny wrote: > Vaclav Slavik wrote: > > Normally, poedit should preserve them (since 1.3.2) in the .po > > file using the standard #~ pseudo-comment format (they're not > > visible in the GUI, but are not deleted from the file). What > > exactly are you doing when they're lost? > > I have checked the resulting po file in a text editor - the > obsolete strings are definitely not there anymore. Once again: how _exactly_ did you do the merge? > Closely related to this - as the obsolete strings are commented out > they are not part of the mo file that is created by poedit. Is > there a way to make these strings 'unobsolete' (apart from editing > the text file directly) so that they are included in the mo file? I think you misunderstand the way gettext works -- if a string is not present in .pot file, it means it's not used by the program you're translating at all and so it *makes absolutely no sense* to include obsolete strings in the .mo file, they would never be used for anything. But if you insist, you can easily uncomment them using any half-decent text editor. Vaclav -- PGP key: 0x465264C9, available from http://pgp.mit.edu/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Poedit-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/poedit-users
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.6 (GNU/Linux) iD8DBQBG3WO5xDYa/UZSZMkRAqRiAJ40CokL+SRBDZkMr40w9GqKgnyH5QCdE/Np iA9rr23URZl8Srx7BAxbvfY= =bbWp -----END PGP SIGNATURE-----