Click seems to have many empty *_en.properties files :(. Are they really required? Isn't there any other trick that Click could use to achieve the same effect/functionality but without using those empty *_en.properties files?
All advanced i18n tools (IDEs too) have nice key cross-language consistency checking, marking with red the groups that are not in sync. This is a very good, advanced and fast feature that makes the work with property files very productive. Due to these empty *_en.properties files in Click however, all groups are marked as errors, so the i18n tools that help translation and maintenance are useless here :(. thank you, George. -- View this message in context: http://click.1134972.n2.nabble.com/Why-empty-en-properties-files-tp5162183p5162183.html Sent from the click-user mailing list archive at Nabble.com.
