The funny thing is that I did NOT edit any of the files (bs, it, fr, sk)
What I did what normal: 1. I used "svn up" to get the latest revision 2. I replaced da.po with my own updated version 3. I tried to make 4. I got errors with bs, it, fr, sk which I fixed by removing them from LINGUAS 5. There was NO errors with my own updated da.po It's not that big of a problem, I just wanted you to know about it. Since it sounds like you do, everything is great :P. And I'm 100% sure that the da.po I started to update was the latest version. And I did not get any errors with it, so I do not consider it a problem. Cheers, Ysangkok 2007/3/6, Eddy Petrișor <[EMAIL PROTECTED]>:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kyle wrote: > A quick fix for me when I get these problems is to delete the offending > files and svn up again to restore them. I don't know why this works, but it > does. This is a "correct" workaround if you haven't updated yourself (as in update the translation, not sync with code) the offending translation. PO files have a tendency to generate large diffs on updates or even conflicts due to the fact that a valid PO file can have any of the following formats and be correct: msgid "" "fhkdfs s" msgstr "translated" msgid "fdfsfds" msgstr "fdsfsfd" msgid "" "fdskjhgs dnf" msgstr "" "fdslfkh fsd" Different systems might reformat the layout and width of the strings thus leading to false big updates. Add to that comments and formatting specification for the string "c-format", "perl-format" etc, and you will figure out the answer to the initial question "why this works" since you are eliminating the need to merge such incompatible (from svn's POV) changes. - -- Regards, EddyP ============================================= "Imagination is more important than knowledge" A.Einstein -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF7egRY8Chqv3NRNoRAq9vAKDRJw9w68L7eb497AQX5Go/hFwByQCeMnUW qAVnQgYhX9Un7zZeiQkpclw= =4ioL -----END PGP SIGNATURE----- _______________________________________________ Wormux-dev mailing list Wormux-dev@gna.org https://mail.gna.org/listinfo/wormux-dev
-- KH Janus
_______________________________________________ Wormux-dev mailing list Wormux-dev@gna.org https://mail.gna.org/listinfo/wormux-dev
