Translating Sigil

[BeckyEbook]

Here.

[User_Z]

Контекст
QObject
Подробности
Размер
1 слово
Вхождения
../../Importers/ImportEPUB.cpp:675
Ресурс
base.ts
Хэш строки
db2af4afe0890fa9ae06dbcbc2a81755

[User_Z]

Thanks, BeckyEbook.

This is the text in the program window.
Where is the line in Transifex?

[KevinH]

Check out: ../../Importers/ImportEPUB.cpp:675
(ie. Importers/ImportEpub.cpp line 675)

https://github.com/Sigil-Ebook/Sigil...tEPUB.cpp#L675

And the opf error message itself comes from Qt's QXMLStreamReader which is internal to Qt. Since these are error messages from an XMLParser, I would guess they are in English only. There is an error() enum value but that list is short and comes back with CustomErrorMessage which is no help for Translators.

[User_Z]

Hello BeckyEbook.

What do I need to do to get a message like the one in your screenshot?

Thanks.

[BeckyEbook]

Outside of Sigil, edit the OPF file and remove the attributes from the metadata tag so that only <metadata> remains.

[User_Z]

Hello KevinH.

What do the numbers at the end of the line in the screenshot mean? They represent the position in the OPF file—the line and column.

If so, what does "near" have to do with it?

[DiapDealer]

It means that might not be the exact location of the error. The error is likely near that location.

[KevinH]

Remember, the OPF being processed here by the QXmlStreamReader is exactly what the original epub was created with, likely no xml header, possible lead comments, misused prefixes, etc. Sigil normally auto fixes and cleans all of this but then the book was never set as Modified properly (as only the opf was repaired). Now we detect when the opf is malformed on load and alert you. We still auto fix it but now the Modified flag can be properly set since we can now detect a repair was needed.

Line numbers and columns in the QXMLStreamReader may differ slightly now from the fully fixed version now in Sigil, thus the use of the word "near".

[User_Z]

Originally Posted by KevinH

Check out: ../../Importers/ImportEPUB.cpp:675
(ie. Importers/ImportEpub.cpp line 675)

https://github.com/Sigil-Ebook/Sigil...tEPUB.cpp#L675

And the opf error message itself comes from Qt's QXMLStreamReader which is internal to Qt. Since these are error messages from an XMLParser, I would guess they are in English only. There is an error() enum value but that list is short and comes back with CustomErrorMessage which is no help for Translators.

Judging by your code and comment, you are assembling the phrase from various parts. However, the translation would apply to only one word out of the entire—rather long—phrase.
What will the result actually look like?

I searched the Qt source code for the phrase "Namespace prefix opf for scheme on identifier is not defined" and parts of it, but the search yielded no results.

Perhaps the string "opferror.message" or "error_message" in the code could be made more natural?

[KevinH]

You need to talk to Qt about that. As I said we do not create the error message, we just add location info to the end. And there are many different possible OPF parsing error messages created by QXmlStreamReader.

[User_Z]

I’ve already spoken to them about updating the current translation in general.
I have never seen a more idiotic localization system—especially for a commercial product.

Some time ago, I mentioned here that I had fully translated Qt into two languages ​​and fixed various errors and inaccuracies (quite a job, let me tell you). I then submitted the complete set of translation files to Qt Gerrit. It turned out, however, that no one but me cared about it. The current localization manager told me that Qt management couldn't care less about localization.

So now, whenever Sigil spits out some nonsense from the standard Qt translation, I replace the `qtbase` file with the one from my own set and use the more accurate translation instead.

[DiapDealer]

I'm not seeing this particular instance rising to the level of "nonsense". I find it hard to believe there's no suitable substitute for "near" that would fit the context of "near this line:column number" in any language.

[User_Z]

You misunderstood; please read carefully.

"nonsense" refers to the "standard Qt translation," not to your word "near".
Everything is fine with "near" now; the translation is ready.