How to have bullet points in an error message?

[wmayer]

If you like you can make your first PR so that it can be merged into master. Before doing so there are two other features with a similar meaningless error message: FeatureHole.cpp in line 952 and FeatureGroove.cpp in line 102.

[DeepSOIC]

But the real important question: what does cheese have to do with face creation?

FaceMakerCheese is adapted face-making code of Part Extrude and PartDesign (same code was repeated in about three places I think). I called it "cheese" because it supports making faces with holes, but doesn't support islands inside holes. If you take a slice of cheese, it can have holes but can't have islands inside holes... That's why!

[DeepSOIC]

Use html, maybe?

html-in-qmessagebox.PNG (28 KiB) Viewed 268 times

[NormandC]

Use html, maybe?

Thanks, creative, but not working for me. C++ may not be directly recognizing html, seems like Python does?

FC018_PD_error_message_enhancement_03.png (36.92 KiB) Viewed 237 times

I guess it's related to what wmayer mentioned in his next to last reply.

So, because QString::fromLatin1 instead of QString::fromUtf8 is used the characters are not properly decoded.

Thanks, I'm very much tempted to change it to utf8. I'm guessing it shouldn't affect other errors that use this routine.

If you like you can make your first PR so that it can be merged into master. Before doing so there are two other features with a similar meaningless error message: FeatureHole.cpp in line 952 and FeatureGroove.cpp in line 102.

I'd like to try, if I can figure out the PR process with Git (so far I've only created a local branch - maybe I'll make things easier on myself and redo everything on Github's web UI!). I had already made the same change in FeatureHole.cpp, I hadn't thought of looking in FeatureGroove.cpp.

I called it "cheese" because it supports making faces with holes, but doesn't support islands inside holes.

Ha! Thanks for the explanation, the Swiss cheese analogy did pass through my mind.

[NormandC]

Success:

FC018_PD_error_message_enhancement_04.png (33.49 KiB) Viewed 236 times

But it does not look nice without indentation, and with the text right beneath the bullet. I wanted to avoid forcing carriage returns because I thought the window could be resized by then end user, but it looks like its width is fixed.

[NormandC]

Better, but missing an empty line before the bullet list! Line breaks are not to my liking either.

[NormandC]

I think this is it.

What do you guys think?

FC018_PD_error_message_enhancement_06.png (32.82 KiB) Viewed 232 times

Now, the big question is, how will this text string be translated? I mean, how will it appear on Crowdin: as it's shown above, or will the bullet points be shown as \xe2\x80\xa2

[chrisb]

That looks good. It is good to see that you have similar high aesthetic standards as I have. How does it look with another space (half a line would be nice, haha) between the bullet paragraphs?

[wmayer]

Now, the big question is, how will this text string be translated?

Not at all because Qt's lupdate tool won't pick up the string because it's not marked accordingly. The string must be put inside the QT_TR_NOOP macro and then when it is about to be displayed QApplication::translate must be used.

I mean, how will it appear on Crowdin: as it's shown above, or will the bullet points be shown as \xe2\x80\xa2

I guess that it will show the \xe2\x80\xa2. However, it's always a bit problematic if technical stuff is part of a string because some translators don't know what to do and simply omit it.
IMO, the best practise to avoid such cases is that it's up to the programmers to split the whole string into two parts. The technical part that won't be marked for translation and the actual content that will be marked.

Code: Select all

/* TRANSLATOR PartDesign::Pocket */

Code: Select all

std::string message = QT_TR_NOOP("The requested feature cannot be created. The reason may be that:");
message += "\n\xe2\x80\xa2";
message += QT_TR_NOOP("the active Body does not contain a base shape, so there is no material to be removed");
message += "\n\xe2\x80\xa2";
message += QT_TR_NOOP("the selected sketch does not belong to the active Body.");

On crowdin the translator will see three strings within the context "PartDesign::Pocket". So, the likelihood that he messes things up should be rather low.
The code to display the error message should then be changed to (TaskDlgFeatureParameters::accept()):

Code: Select all

QMessageBox::warning(Gui::getMainWindow(), tr("Input error"), QApplication::translate(feature->getTypeId().getName(), e.what()));

[DeepSOIC]

Code: Select all

std::string message = QT_TR_NOOP("The requested feature cannot be created. The reason may be that:");
message += "\n\xe2\x80\xa2";
message += QT_TR_NOOP("the active Body does not contain a base shape, so there is no material to be removed");
message += "\n\xe2\x80\xa2";
message += QT_TR_NOOP("the selected sketch does not belong to the active Body.");

...
The code to display the error message should then be changed to (TaskDlgFeatureParameters::accept()):

Code: Select all

QMessageBox::warning(..., QApplication::translate(..., e.what()));

But will it work at all? I thought, Qt looks up the whole string in the translation library, but will not find it because only pieces are in the library?