It's very strange that Spanish isn't one of the reference translation languages...

See user_none's post above with pre-translated Dublin Core text. Edit: which as he just posted, doesn't help at all :(

German translation
 

Dear all,

For some while I follow this forum in some areas by reading.
Today I decided to participate by becoming a member.

I'm working on the German Sigil translation.

And I'm wondering about the amount of metadata entries: 454, this means 227 pairs of metadata fields.

As far as I understood, the Dublin Core Metadata set consists of 15 fields, according to several sources.

The links to translations I saw handle only 15 fields.

Are the other fields really part of the standard?
Or are they non-standard and optional?
I'm speaking of the amount of the fields, not of the entries.
If the fields are non-standard and if the field names are free, wouldn't it be a better idea to let the users decide to add field names by themselves?

A lot of the fields seem to be related to movie business, like "dancer", "woodcutter", "wood-engraver" and so on. They don't make sense in an ebook.

Are all these fields really needed? They will cause a lot of work (and may be frustration) for all translaters.

I couldn't find any list of all this fields of "Dublin Core Metadata" in a German translation. And I assume, other translators to other languages will have a similar problem.

For all who are interested in the German translations, here are some hints:
SELFHTML
Wikipedia
http://www.community-of-knowledge.de...ta-initiative/

Cheers,

Griffel

Hello,
I would guess, they are standard. Of course, usage is optional.

They make sense in some very rare situations. I.E. Woodcutter is defined as a person who cuts an image into wood (see definition in Sigil). This reminds me on the the way, how pictures are produce until ~1850/60. I.E. the early works of W. Busch are painted on a shelf, engraved by a woodcutter and then printed. Well, who remembers the name of the woodcutter today ? :)

As user_none says, there are some translations (i guess, just the 15 basic attributes).

German translation
 

@mmat1

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"

It's only a small extract of the 454 entries in the section "Metadata".

Are you aware of all these 227 categories?

From my point of view none of the entries of the screenshot is related to books or ebooks. These entries are typical for movie business.

Only a subset of few categories in the Metadata section makes sense in an ebook.

We all know the multiple and annoying kinds of categories from the end credits of movies.
But, in book business, these categories are not in use.

For example "woodcutter". No one in book business uses this category. Typical for book business is the category "illustrator". No one cares about the technique an illustrator uses. But the category "illustrator" is not part of the core. Therefore it makes sense to provide "illustrator" as additional field, but not "woodcutter".

I showed the screenshot to my girl friend. She is involved in book business for a long time. Her answer was: "It looks like an alien speech."

Only few categories of metadata are in use in book business. Most of them are described in the core. But some other additional categories make sense. The challenge is, to identify these categories and to shorten the long list to an appropriate subset.

I highly recommend to do so. Even if it's not easy. I would appreciate to support this action.

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.

Meme,

Thanks for this clarifications!

I like well designed standards ... ;)

Eckhard

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.

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 ???

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.

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.

folder names should not be translated
 

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.

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

Many thanks.

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?

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

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.

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.

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

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.

The Spanish translation is complete :)

I am currently working on the German translation. I have a small problem with short cuts for words where I don’t have an equivalent character:

'Save A &Copy…' will come to 'Sichere eine &Kopie…'

Can I make a new shortcut &K or will this end in a problem?

You can put the & in front of any letter in the menu as long as that letter is unique for the entire menu (e.g. K is fine if no other word in the File menu has an & before the K). Most people use the keyboard shortcuts anyway, but its nice to have the menu letter shortcuts available too.

Thanks for your answer, meme. So I'll try to do some translations for the main window today.

Up to yesterday I completed a lot other areas and update the file at Transiflex. For user who want to take a first look on it can download the attached file and copy it in the translation folder (don’t forget to save the original file). It's completed up to 61%.

Meme,
I've done some more of the german translation (excluding dublin core).

I found maybe one minor problem in the code of Language section. There are two entries with the same code:
"new" << tr( "Nepal Bhasa" ) <<
"new" << tr( "Newari" ) <<

I guess, the first one have to be
"nep" << tr( "Nepal Bhasa" ) <<

Users who want to take a look on it can download the attached file and copy it in the translation folder (don’t forget to save the original file). It's completed up to 80%.

Thanks. I've corrected it (merging it into "Nepal Bhasa/Newari"), although it might not make it into the translations string for this release.

That dublin core list is pretty long :)

"That dublin core list is pretty long - Yes, it is killing me :)

Due to the merging, if I'm looking in the documentation of ISO 639-2b, there are 2 entries, so it's better to have it separate:
"nep" = "Nepal Bhasa"
"new" = "Newari"

Some nice findings:
"lol" = "Mongo-Nkundu" and "tlh" = Klingon (Artificial language). I like to see a Klingon star trek version of Sigil :2thumbsup

By the way, I made a update at transiflex. The de-File for the translation folder is attached below.

Nice WE

Well from http://www.loc.gov/standards/iso639-...glish_list.php we're using the 639-1 code if it exists, and if not then the 639-2 code. So "ne" is "Nepali" (with "nep" the 639-2 code) and "new" is "Nepal Bhasa" and "Newari". Until someone actually using the code comments that a different code is needed, I think we'll leave it as is for now:)

Think of the Dublin Core as a challenge :)

You should have more time now as I think it will be frozen imminently for 0.6.0 and the next updates won't be seen until 0.6.1.

I made a update at transiflex. The de-File for the translation folder is attached below.

I am looking for some missing translation strings:

From menu:
Format -> Heading -> next window has no translation strings (pic Aufzeichnen)

Tools -> Metadata editor -> Metadata editor window: right click in field Title, Author or Save as open context menu in English, no translation strings found (pic Aufzeichnen 4)

Tools -> Index -> Index Editor -> Index editor window: right click in field Filter open context menu in English, no translation strings found (pic Aufzeichnen 4)

Tools -> Reports -> Report window: right click in field Filter open context menu in English, no translation strings found (pic Aufzeichnen 4)

Insert -> Picture -> next Window: right click in field Filter open context menu in English, no translation strings found (pic Aufzeichnen 4)

Insert -> ID -> next Window: right click in field Filter open context menu in English, no translation strings found (pic Aufzeichnen 4)

Insert -> Hyperlink -> next Window: right click in field Filter open context menu in English, no translation strings found (pic Aufzeichnen 4)

Search -> Go to line -> next Window: right click in field line number open context menu in English, no translation strings found (pic Aufzeichnen 5)

In code view:
Right click in window open context menu in English, no translation strings found (pic Aufzeichnen 2)

Right click in search or replace field open context menu in English, no translation strings found (pic Aufzeichnen 3)

In book view:
Right click in search or replace field open context menu in English, no translation strings found (pic Aufzeichnen 3)

Thanks for the new before chrismas version :)

Divingduck

Can you please check the translation of "short-cut-strings"?

I think it is not correct to translate "Ctrl" to "Strg"

With GUI Language set to German goto Bearbeiten - Einstellungen - Tasterturkürzel and press button "Alle zurücksetzen"

All shortcuts former prefixed with Ctrl will loose this. E.g. it will become impossible to type square brackets.

Reset Language to English. Restart Sigil, reset keyboard shortcuts once again, you will see the difference.

Thanks.

I see the point. The correct translation is [Strg] because all German keyboards layout have a [Strg] instead of [Ctrl] key since the last 30 years I use keyboards.

Wikipedia: German keyboard layout and Wikipedia: Keyboard layout

I just recognize that unfortunately an international keyboard layout seems to be not supported in Sigil. That's the problem with language and translations. Surprises came up where you do not expect it. :thumbsup:

Your point is correct and I think I need to change this back to Ctrl as long as there is no difference of international keyboard layouts in Sigil. By the way you are the first one who have recognize (ore let me say use) this. I had made the change some when mid October.

Thanks for your comment.

@User_none and meme
I will change this back but it is a problem for translation and documentation. People who a working with IT will have no problem to understand that [Ctrl] is the same as [Strg] but there is still the point that this key do not exist in a keyboard layout for Germany and Austria. As this isn't a common standard for these countries. My guess is to describe this in the documentation and may be in the shortcut editor window. Then there is no misunderstanding.
When I look into other programs like MS Windows, MS Office, Adobe products etc. this key will be translated and used as [Strg]. This is common standard. Maybe this is something you can implement some when in the future.

Have a nice sunday.

I did an update at Transiflex. Here is the update german language file. Replace file sigil_de.qm in subdirectory of Silgil translation files ( ...\Sigil\translations\) restart Sigil and reset the shortcuts in preferences.

Comments are welcome. :)

What? Is the code to actually process the shortcuts using the translated strings? If that's the case, I think it's a bug (or a misfeature).

If the translation system is currently intended to allow adapting shortcuts for different languages, then I suggest adding strings for the different key names, so the code can compare the shortcut strings with them, and set the right shortcut.

(I've been using "Mayús" as a translation for "Shift" in the Spanish translation, and that's what non-computer-savvy people are most likely to understand.)

The problem accrued by changing the translation from Crtl+key to STRG+keys in the MainWindow translation source text. Pls. see attached file.

There appears to be an option notr for no translation for strings that probably should be used in the ui files for all the shortcut strings. It was being used mistakenly for the heading formats - which is good because now I know what to change for the shortcuts :)

But we want to translate the way the shortcuts are displayed (Ctrl = Srtg in German, Shift = Mayús in Spanish) ;)

You're right. Just before doing an update I realized that changing the characters might mean they won't work. So not sure how to address this if at all.

Can't you regex the (untranslated) shortcut string before displaying? That way we would only need to provide translations for the key names.

Hi meme,

Thanks for updating the template. We did an update in Transiflex and in addition the new member penZig did a lot improvements and corrections in the actual translation.

I have 4 translation strings in the FindReplace section that are not working. I can make a translation but 2 of them won't be updated by upload and two have a problem with parameter for Singular / Plural translation strings.

Is it possible to take a look on that? Please take a look on attached the pictures.

The first two are:
"Search wrapped around" and "No replacement found". In linguist window for Sources and Forms is a message "File ... not readable"

The last two are:
"%1 matches found" in source code "QString message = tr("%1 matches found", 0, count);"
and
"%1 replacements made" in source code "QString message = tr("%1 replacements made", 0, count);"
I am using the source code from version 0.6.2 and the actual ts file

Ah... those damned strings :D

The first two, I can translate in Spanish, but they always appear as untranslated in the next update, so they probably are not working somehow.

The other two (with plural forms) cannot be done, as far as I know, with QTlinguist. You have to edit the file with a text editor and fill the <numerusform> or whatever is called. Download the file for a language with 100% done and copy the syntax.