Julian Bäume af94d8ff5e restore previous behaviour with \n in strings ... An incompatible change (that actually breaks po parsing after writing) had been introduced with commit e164fcfe9d. If _process returned an array (which is the case for strings containing \n character), array.toString will return a comma separated list, which is not valid po syntax. Added a test to restore the behaviour from before the e164fcfe9d.		2014-06-23 12:30:04 +02:00
..
fixtures	handle empty comments correctly	2014-06-19 17:04:03 +02:00
comments.js	Update test header.	2013-12-17 14:44:18 +01:00
headers.js	Start adding a real unit test framework.	2013-12-17 14:37:17 +01:00
parse.js	handle empty comments correctly	2014-06-19 17:04:03 +02:00
write.js	restore previous behaviour with \n in strings	2014-06-23 12:30:04 +02:00