Right now, the tool assumes all strings should go into a .strings file. This isn't necessarily true. Plural strings need added to a .stringsdict plist. It should be possible to allow some sort of flagging that a desired function is plural (not sure the most elegant way to do this). Furthermore, the tool will need to parse out existing .stringsdicts and do the same sort of behaviors that it does for plain .strings files.
Right now, the tool assumes all strings should go into a .strings file. This isn't necessarily true. Plural strings need added to a .stringsdict plist. It should be possible to allow some sort of flagging that a desired function is plural (not sure the most elegant way to do this). Furthermore, the tool will need to parse out existing .stringsdicts and do the same sort of behaviors that it does for plain .strings files.