Translating Sigil

[meme]

Thanks for helping with the translations.

The list of roles are from the MARC relator list at http://www.loc.gov/marc/relators/ which is the complete list referenced by the EPUB spec (2.2.6).

It does have some odd entries in the list. And its possible some are missing. I should probably review the list and add any missing ones, as the intent is to support the full set of metadata from the EPUB spec.

The list of languages is also quite long, but again its what was in the code and is actually incomplete and needs expanding as well.

The list of entries has been in the code for a while, but its only now that I've exposed them for translation that you are seeing them. We knew it would be a lot of work to translate, and can understand if you don't want to translate everything. But we are trying to ensure everything can be translated. Anything that is not translated will just default to English.

[Griffel]

Meme,

Thanks for this clarifications!

I like well designed standards ...

Eckhard

[Jellby]

I'm having the hardest time with the legal terms (complainant, libelee-appellee, etc.), which I suspect don't have a direct translation in many languages, since they are dependent on the legal system of each country. I believe it was a mistake to include these in the standard.

[mmat1]

Originally Posted by Griffel

To make my theme more clear, please have a look to a screenshot I took from the translation program "Qt Linguist": Screenshot of "Qt Linguist"

ok, maybe there is some relevance to books for some of them. But many of them will fit into a movie as well.

You're probably right with your estimation, that nobody really uses/needs them.

So is it hard to decide, just so skip them ???

[Jellby]

I guess any one of them might be used if there is an ebook about a movie, an exhibition, a legal case, etc. and if the ebook creator wants to be exhaustive.

I have created some ebooks with illustrations that were originally etchings or engravings, and the etcher or engraver is known (and different from the artist who designed the illustrations), in some cases the illustrations are actually signed by the engraver. I could have added the names is the metadata, but I only added the "illustrator". The fact that I didn't do it doesn't mean that it shouldn't be possible to do it.

[user_none]

In regard to the metadata elements. Remember EPUB is short for electronic publication. While primarily used to produce books it is designed to be a flexible system for publishing things other than books. Hence the inclusion of audio and video in EPUB 3.

In an EPUB 3 document especially it makes sense to have things like "woodcutter" when the document contains a video with a woodcutter in it.

[windrose]

Just installed sigil 0.5.3 and noticed the translation of the user interface. I think it great and thank all the effort of every translator.

However, I also notice that the folder names inside a epub are also translated into different languages which I don't think it proper. To make it clear, I mean the folder names showing in the book browser pane which are Text, Styles, Images, Fonts and Misc. Users will be confused when they try to refer to the folder names because they are kept unchanged in the epub file but showed differently in sigil.

Let me make an example. In Czech language, Styles will be showed as Styly. If I refer to a file, say, style.css in that folder, should I use Styles/style.css or Styly/style.css ? This is very confusing.

So I suggest keep the folder names intact among different translations. As a workaround, what I do now is to delete the localized translation which is Chinese and stay with English interface.

[dimitris]

Hello,

I created a Greek user interface software (Sigil). I will upload the file to transifex (The file is uploaded here too).

There is an available short guide to the Greek language software here…

http://www.labschool.eu/lab-software...itor-epub.html

[meme]

Many thanks.

[Jellby]

What does "tokenise sequence" do? I'd like to know it to find the best translation. Does it just escape special characters? i.e. does it attempt to find the original input (if unmodified afterwards) as a literal string, but with the regexp engine?

[meme]

It changes multiple spaces to \s + and numbers to \d+

[kiwidude]

Originally Posted by Jellby

What does "tokenise sequence" do? I'd like to know it to find the best translation. Does it just escape special characters? i.e. does it attempt to find the original input (if unmodified afterwards) as a literal string, but with the regexp engine?

To expand on meme's reply as it is a little bit complicated

If you have the Auto-tokenise option on, then it means when you hit Ctrl+F on some text it will:
- Escape any regex characters in the selection, such as periods, parentheses, brackets etc
- Runs a regex replacement of ([\n\s]{2,}) with \s+ to ensure two or more spaces/newlines get substituted with \s+. This is to handle some of the funkiness of the Sigil/Qt editor, where it puts a unicode newline and spaces in as part of the Pretty Print operation. This is handy when you are doing multiline regex to save you typing \s+ in between all the time.

If you choose the "Tokenise selection" context menu option, then it will do the same as above (escape and tokenise spaces), but add a regex find/replace of (\d+) with \d+ in order to replace any numbers in the Find text. This is not done in the "auto tokenise" because it is something you are less likely to do. And it works on your selection in the Find box (the whole text if you have no selection) so if you want to keep a numerical style name intact but substituting for a numerical id you can do so.

Note the next 0.5.907 build adds a slight tweak to Tokenise Selection so that it does not escape the text if it sees a \ in there. This is to allow you to repeatedly apply (or do a Tokenise Selection to do just the numbers while having Auto Tokenise on) without ending up with double escaped \\s+ etc.

[meme]

Things are always changing in this beta

By the way, thanks to all the translators trying to keep up with all the text changes we've been making. Apologies for so many during the beta but so many things to improve. After the next beta it should be fairly static in preparation for release.

[Jellby]

Thanks to to the developers for improving Sigil, I may actually use it some day

[meme]

With the final version of 0.6.0 less than a week away, the text needing translation is effectively complete. Hopefully the translators can work on any remaining updates in time for the release.