Comment 62 for bug 323041

As i have stated earlier, my evaluation of the buildability mishap is different, but it appears what you are saying is that i should not have added crh to configure.in relying on the following commit comment to reconcile w/ maintainer's earlier action:
"In particular, crh.po is not checked in this time, because it was one of Sergey's reasons for reverting, so until it's pulled from TP, something like `cp po/tr.po po/crh.po` is required prior to building from source."

Also, I personally would find it preferable to make a build w/ the newly supported localization before code freeze.

At this point, if everybody feels comfortable w/ changing configure.in on the day of the release, after pulling crh.po from TP, and everybody is sure that it won't be forgotten or left out (which i personally don't feel very confident about), then please feel free to undo po/crh.po addition, and addition of crh to ALL_LINGUAS in configure.in.

P.S. Frankly, i don't understand all this commotion about checking in a .po file. That's how many projects do it, and it's the only way to do it in many projects. I would also allow checking it in at least when it's tied to new changes that cannot be accomodated via TP, which is the case here. That said, .po file is probably the least significant piece here, and i will use TP to update it going forward as i was going to do anyway w/ May 11th check-in.