by Luc Saffre · in Developers · assigned to Sharif Mehedi

Kurzbeschreibung

Kinder

Kommentare

• 4 Jahre, 1 Monat ago von Luc Saffre Antwort auf Sharif Mehedi about #4642 (Rename "Problem" to "Message" in checkdata) : The test case fails because the translation was now marked as fuzzy.
• 4 Jahre, 1 Monat ago von Luc Saffre Antwort auf Sharif Mehedi about #4642 (Rename "Problem" to "Message" in checkdata) : Sharif and I fixed it together with shared screen.
• 4 Jahre, 1 Monat ago von Sharif Mehedi about #4642 (Rename "Problem" to "Message" in checkdata) (2 Antworten) : The translation strings in bn still holds the meaning right. We do not need to change them. But I am wondering why the test case fails.
• 4 Jahre, 1 Monat ago von Luc Saffre about #4642 (Rename "Problem" to "Message" in checkdata) : I committed my work. Sharif, please und "inv mm" in lino to adapt the translation, and then run "doctest docs/specs/cosi5/index.rst" in book.
• 4 Jahre, 1 Monat ago von Luc Saffre about #4642 (Rename "Problem" to "Message" in checkdata) : Sharif will need to run poedit in lino/locale/bn/... to translate thte new word "data problem message" into Bengali. The messages created by checkdata are *messages*, not *problems*.
• 4 Jahre, 1 Monat ago von Luc Saffre about #4642 (Rename "Problem" to "Message" in checkdata) : I made all changes in source code and docs. Now started the test suite, which will require changes.
• 4 Jahre, 1 Monat ago von Luc Saffre Antwort auf Luc Saffre about #4642 (Rename "Problem" to "Message" in checkdata) : But that name clash is not a real one. When local code removes the "checkdata." prefix, it must of course take care for name clashes. So this is not a reason to keep saying "problems" when actually meaning "messages". A different thing is when we speak about fixing a data problem. We don't "fix" the...
• 4 Jahre, 1 Monat ago von Luc Saffre about #4642 (Rename "Problem" to "Message" in checkdata) (1 Antwort) : Simply checkdata.Message has the disadvantage of causing a name clash with e.g. notify.Message in situations where both models are used. To avoid this, we might rename it to "CheckerMessage" or something similar. But talking about "checker messages" feels like a kind of nonsense expression.