On 4/5/2012 3:21 PM, Richard Ash wrote: > Looking at the site in SVN, a lot of new files have been committed.
Thanks for doing that, Richard. > Unfortunately despite being PHP files, they were committed with CRLF > line endings, and without setting the svn:eol-style property to > "native". This meant the files were being checked back out with DOS line > endings onto the Linux server where xgettext was being run. Must be a bug in TortoiseSVN. I think all of those files were renamed and modified copies of existing files. But I used TortoiseSVN to Add then Commit them. I don't think I've ever had this problem with it before, so they must have introduced it. > > I think this was probably the cause of the stray \r sequences in > the .pot files Yes, most likely. > > I have fixed the vast majority of the files in the site, but because > some files were different on the server to in SVN (really different, not > just white space), I haven't got them all yet. Thanks, but probably some of that effort could have been avoided. There are a number of files that should probably just be removed. A lot of the PHP in them was more complicated than what's being used now, so I thought it might be good to have them around in case we ever wanted to reuse that code. But a lot of them are not currently linked to, so shouldn't be translated. I think there may be older ones that don't need to be translated. I'll go through and delete them both from SVN and the server. > > So the audacity_website.pot file is not fixed yet, but should be closer > to being fixed. Thanks! - V ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Audacity-translation mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/audacity-translation
