Hi Jogi,
Joerg Sievers schrieb:
André Schnabel wrote:
So .. we might be save in functionality testen even without the
localized strings and I'd like to remove thoses strings from places
where they are not needed (or at least don't want to add more strings
if not necessary for testing of functionality).
Yes, but we have an office application and without correct filter
names it makes absolutely no sense to test a L10N. Why did you made
the L10N? To get your local names into the application.
FMPOV (from my point of view) it makes sense to document what to do
and to centralize the strings. The fallback should be English US to
test functionality if it's not translated but a warning should also be
thrown if language code <> en_US and there is the Enlish string included.
What do you think about that?
I see a reason to test, that the localized strings are *there*.
(Testtool came across missing names for legacy file filters in vi
localization .. so it does the job very well ;-) ).
The best solution was to have this centralized - the current
dezentralized strings are hard to maintain.
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
