Version: GIT (master) OS: Linux Please, change "New Message Publish" to "New Message Published" or "Publishing New Message...". I don't understand what "New Message Publish" means. Reproducible: Always
Or may be it should be "Publish New Message", if it's a description of an action.
Where do you see this string ?
./kcal/scheduler.cpp:89: return i18nc( "@item new message posting", "New Message Publish" ); ./kcalutils/stringify.cpp:344: return i18nc( "@item new message posting", "New Message Publish" );
Ok thanks
Git commit 1ab638e71a6b9feef2dbe3532ce23a736acf2d3b by Montel Laurent. Committed on 07/09/2011 at 15:24. Pushed by mlaurent into branch 'master'. Fix Bug 268364 - strange message "New Message Publish" FIXED-IN: 4.8 BUG: 268364 M +1 -1 kcal/scheduler.cpp M +1 -1 kcalutils/stringify.cpp http://commits.kde.org/kdepimlibs/1ab638e71a6b9feef2dbe3532ce23a736acf2d3b
i still don't get it. can somebody show the screenshot with this text? it's not possible to understand the context from the msgctxt
this string is currently only used in debug print statements so there is no screenshot to show. I will attempt to give you a more descriptive context -- maybe that will help you.
Git commit 53b286a1ee40ccc96fea206a993b7a93a56ec835 by Allen Winter. Committed on 05/12/2011 at 19:50. Pushed by winterz into branch 'master'. in scheduleMessageStatus(), improve the i18n strings and context to help out the translators. BUG: 268364 FIXED-IN: 4.8 MERGE: no M +8 -4 kcal/scheduler.cpp M +8 -4 kcalutils/stringify.cpp http://commits.kde.org/kdepimlibs/53b286a1ee40ccc96fea206a993b7a93a56ec835
Please, just change "@item" to "@info:status" where applicable. What is a "scheduling message"? Who or what makes "requests" that are mentioned in the i18n strings "New Scheduling Message Request" and "Updated Scheduling Message Request"?
and, if these strings dont appear to the user, why should they be translated?
would it help if we replace "scheduling message" with "invitation"? we don't have to translate these strings at this time since they don't seem to be user-visible. but, the minute we do that someone will use them in a user-visible way. so this is mainly future-proofing.
Looks like everyone is happy.