Thanks Matthew. Great suggestions. Yes, we did add the check to
parsekey and I just ran everything through the check and fixed the
remaining errors.
for i in `grep "^Name=" /usr/share/sword/locales.d/*.conf|cut -f2
-d=|sort|uniq`; do ./parsekey jn.1.1 $i; done
I'm building with ICU so I only have UTF-8 locales exposed by my build.
Someone building without ICU should probably try this and see how we
do with the non-UTF-8 locales.
Thanks for the suggestion.
-Troy.
Matthew Talbert wrote:
Data changes (as in .conf files and so forth), sure (it would be nice if
there was a .conf file validator though). Touch a .h or .cpp file and
you're probably looking at another RC, to be safe :)
I'm not sure I understand the locales .conf files at this point well
enough to help out with validation. However, it would be very nice to
have. We had a problem in Xiphos with one language that we hunted and
and hunted for. We didn't suspect the locale because ./parsekey (I
think) did the right thing. In the end, it was the locale that was
causing the problem. The locales can make frontends navigation
unusable or worse, so they are very important.
Now that I'm writing this, I believe locale validation was added to
parsekey. Perhaps someone can remind me. If so, perhaps it should be
used to validate all the locales during the test run?
Matthew
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
