Comment 4 for bug 1373578

We have not came across the second problem since 2.8 upgrade. Just for a case I randomly tested some language strings in question in Evergreen 2.10 and I can confirm the problem is positively solved.
Thanks a lot :-)