Adding semantics to ePub 2.0: where are "Notes"?

[roger64]

Hi

Using Archlinux. Sigil 0.9.10

I tried to add the semantics value "Notes" to an ePub2 and failed to find it (see screenshot). I had to do it with the Calibre editor.

[BetterRed]

Has Notes been translated as Remarques ?

BR

[DiapDealer]

Originally Posted by BetterRed

Has Notes been translated as Remarques ?

BR

"Remarques" does indeed insert a guide item of type "notes".

[roger64]

OK Thanks.

"Remarques" may be a bit overzealous, "Notes" is quite good even in French and probably more helpful.

[DiapDealer]

Originally Posted by roger64

OK Thanks.

"Remarques" may be a bit overzealous, "Notes" is quite good even in French and probably more helpful.

We don't do the translations. You'll have to take that up with the Transifex team. The only decision we could make would be to translate NONE of the semantic titles. And that would affect all languages.

[Doitsu]

Originally Posted by DiapDealer

We don't do the translations. You'll have to take that up with the Transifex team. The only decision we could make would be to translate NONE of the semantic titles. And that would affect all languages.

Theoretically, Sigil should also be able to display metadata entries in English, if the user selects English as the Default Language For Metadata value (Edit > Preferences > Language), however, changing the Default Language For Metadata value doesn't seem to have any effect.

Could you please have a look at the code and check whether changes to the Default Language For Metadata value are actually detected by the Sigil GUI code?

[DiapDealer]

Originally Posted by Doitsu

Could you please have a look at the code and check whether changes to the Default Language For Metadata value are actually detected by the Sigil GUI code?

So far as I know, Default Language For Metadata isn't used by GUI code (nor was it intended to). It merely sets the dc:language metadata element in the opf to the default selected by the user. It's not used to translate the metadata gui editor strings differently from the main UI language.

[Doitsu]

Originally Posted by DiapDealer

So far as I know, Default Language For Metadata isn't used by GUI code (nor was it intended to). It merely sets the dc:language metadata element in the opf to the default selected by the user. It's not used to translate the metadata gui editor strings differently from the main UI language.

Thanks for the clarification!

[DiapDealer]

No problem.
I can see the advantage of wishing to see the list of semantic elements in English regardless of the UI language setting, but I don't know how that could easily be accomplished without forcing them to be untranslated for everyone.

[BeckyEbook]

Idea: Use English abbreviated names in brackets after translation.

[BetterRed]

Originally Posted by roger64

OK Thanks.

"Remarques" may be a bit overzealous, "Notes" is quite good even in French and probably more helpful.

Blame Sergey Brin's Alphabet Soup

Originally Posted by BeckyEbook

Idea: Use English abbreviated names in brackets after translation.

Good one, too. But that's up to the translators.

BR

[DiapDealer]

Originally Posted by BetterRed

Good one, too. But that's up to the translators.

Actually, we could pull it off without involving them. We could just build the string and leave the parenthetical English portion out of the tr function. The translators would never see it.

The doubled entries would look a little weird whenever English was the selected UI language, however:

Text (text)
Notes (notes)
Table of Contents (toc)
Glossary (glossary)

[Notjohn]

Originally Posted by roger64

"Notes" is quite good even in French and probably more helpful.

Some years ago I was skiing in Argentiere, and I met a Canadian in the B&B's parking lot who was in shock at the sad state of the French language as practiced the Haute-Savoie. We were standing beneath a sign for Parking! And people went skiing on the Weekend!

[un_pogaz]

Originally Posted by BeckyEbook

Idea: Use English abbreviated names in brackets after translation.

That's a great idea. A translation is very practical but the English terms are the ones used internally in the ePub, it can be useful to have them some here.

Originally Posted by DiapDealer

The doubled entries would look a little weird whenever English was the selected UI language

Since you will (probably) modify the code, you could add an exclusion condition for the English.