Mobileread
Translating Sigil
#1  user_none 10-08-2011, 07:41 PM
One of the the new features that has been implemented for 0.5 (release date yet to be determined) is support for Translations. For Sigil's first supported language Grzegorz Wolszczak has provided a Polish translation. Currently translations are loaded based upon the current system locale. There no support for choosing the language via preferences. This may come at a later time but for now I believe that using the system locale will handle the majority of user needs.

I've put together a wiki page with instructions for creating translations. This first revision is a bit basic but as people have questions I plan to update it to make it more robust.

If anyone is interested in translating Sigil into their native (or second, third, fourth...) language it's now possible.
Reply 

#2  Pinguin 10-09-2011, 01:53 AM
That's great! Many thanks! Karma for you.
Reply 

#3  daubnet 10-09-2011, 09:53 AM
For those who wish to help with translations and don't want to install the quite large Qt SDK (a few hundred MB), there is a 6.4MB Download of the necessary tools available here.

There is one caveat, though: Since binaries for V0.50 haven't been released, you cannot check your translations inside Sigil yet - above tools don't allow you to create your own build.

As a sidenote: On Windows, you'll have to use "lupdate ../../ -ts out.ts" to produce the TS file. Note the missing asterisk. I believe this command line should also work on Linux, but haven't tried.

BTW, I think it makes sense to include the sigil_en.ts file in the GIT repository so that translators don't have to pull the whole source and create the TS file individually. This could also be part of a "string freeze" process.

P.S. I'm working on a german translation. If somebody else is doing the same, please contact me via PM.
Reply 

#4  user_none 10-09-2011, 08:30 PM
Quote daubnet
There is one caveat, though: Since binaries for V0.50 haven't been released, you cannot check your translations inside Sigil yet - above tools don't allow you to create your own build.
Very true but this will not be an issue once 0.5 is out.

Quote daubnet
BTW, I think it makes sense to include the sigil_en.ts file in the GIT repository so that translators don't have to pull the whole source and create the TS file individually. This could also be part of a "string freeze" process.
Agreed. My plan is to do a "string freezing" when betas are ready. I plan to put out a generic .ts file for translators to use at this time too.
Reply 

#5  daubnet 10-10-2011, 05:05 PM
Just in case anybody wants to play with it: Attached is my first version of the german translation. Please note that I currently don't have a 0.50 binary, so things might still be a bit odd at places.

I haven't created a GIT account and committed the file because it is just a first translation, but I thought it might be helpful in development because german text tends to be a bit longer than the english original.
[zip] sigil_de.zip (23.4 KB, 1004 views)
Reply 

#6  user_none 10-10-2011, 08:03 PM
@daubnet, I've pushed a number of changes to the menus that change the text in a number of places. This is why I'm putting off a string freeze until I'm ready to do betas. At least this gives a good head start for later.
Reply 

#7  daubnet 10-11-2011, 03:13 PM
No worries, my translation wasn't meant to be final in any way, but just a quick patch to help testing etc. I assume half (if not all) of the work will have to be redone when 0.50 is ready.

Something that might be a good idea to discuss before everybody heads off and translates stuff is the current wording in english, because it isn't using a consistent terminology right now. For novice users of Sigil it may become confusing that the same thing is sometimes called "chapter", "file", "document", "item" or "HTML".

Current usage of terms (incomplete):

Those are overlapping somewhat. My personal vote would be for:The sections and stylesheets also need a heading for the book browser, currenty those are "Text" and "Styles" - please discuss if it should be "Sections"/"Chapters", and "Stylesheets" instead.

Rules (I just made these up, please discuss)
Additionally, the UI sometimes mentiones HTML, sometimes it mentions XHTML. I know that for validation and similar tasks, the difference between XHTML and HTML is important, while it is otherwise common to use just "HTML", even if it is in fact XHTML. So it may or may not make sense to unify these terms, but nevertheless is probably worth looking at.

Lastly, do you think it should be "EPUB" or "ePUB"? The logo features a lowercase "e", while the www.ipdf.org seems to use mostly "EPUB".
Reply 

#8  user_none 10-11-2011, 03:38 PM
I like:

I'm going to use EPUB.

HTML should be used in place of XHTML. Simply because EPUB 3 will use HTML 5 and HTML can also apply to XHTML.

File should be used in place of Item to refer to any or all things inside of an EPUB. E.G. add existing file.
Reply 

#9  theducks 10-11-2011, 05:18 PM
Chapter is not equal file in many cases.

A "Section" can contain many Chapters (total should be < 260K for compatibility with portable readers). A huge chapter may span sections.

(x)HTML is the coding used for All Sections, be they Cover page,Chapters or Contents Page.

Text can only be added i Book View. (x)HTML can only be added in Code View or added as a file (New section).
Reply 

#10  Heathside Boy 11-01-2011, 03:04 PM
Hi,

I am a complete novice and do not understand Sigil quite yet, so bear with me. All I know is, that it is an editor of some sort and that you can piece several bits of separate books together in it.

Am I correct so far?

This can only be accomplished if the contents are in EPUB format. Is this correct also?

Now you are mentioning being able to change the language. By this, do you mean the actual Sigil content having a different language or the content you put in it can be changed?

Firstly, where can I download the Sigil e-book editing program?

If I explain this task, can you tell me whether or not I can do the things in it that I want to?

To explain:

I have a complete book in .docx format (or if you like, Microsoft Word). The complete book is in Spanish. I have taken out each page separately from the original document.

I would like to change the language in it from Spanish to English.

At the moment, I have taken each page separately and translated it from Spanish to English using an online translator.

This as you can imagine, is very time-consuming. I know at the end of the exercise, I can change the format of the pages from docx to PDF.

What I would like to know is, can Sigil perform this operation much quicker for me somehow?

Or am I barking up the completely proverbial wrong tree in summarising how Sigil works?

Any help on this issue and if it can be solved will be truly appreciated.

Thank you

HB
Reply 

  Next »  Last »  (1/13)
Today's Posts | Search this Thread | Login | Register