mscore_ar.ts update

• Jul 11, 2009 - 17:14

I've done 535 items out of 2047.

Hosam Adeeb Nashed

Attachment Size
mscore_ar.ts 256.46 KB

Comments

• Jul 15, 2009 - 04:28

Hi,
Sorry for not doing as much as I would hope to do; I did a bit of travelling during the past three weeks.

Well, regardless of the bits flagged as "Do not translate", I can't understand why the About box never appears as translated; it even has two html blocks (which I translated both), neither of which is displayed!

Apart from that, the only other thing that feels rather frustrating is that almost one dialogue box seems to appear complete with Arabic text, although, by now, I had completed more than 530 items!!!

Anyway, I can't wait until all is finished, so the item "Arabic" can appear on the "Languages" list on the website...

Oh, by the way, as the version currently under development approaches its final stage, is there any chance something is added to (or omitted from) the file I'm working on? I trust I'll receive an alert if this ever happens, won't I?

Hosam Adeeb Nashed

Reply

• Jul 17, 2009 - 18:41

Hi Hosam,

I could reproduce your problem that some translated strings were not displayed in the interface but this issue was going above my level. Lasconic took a look but it was eventually Werner who did some magic with lupdate which solved the issue. Building the SVN trunk returned a fully functional translation. See the attached screenshot.

Attachment Size
1247852065-clip-25kb.jpg 24.67 KB

Reply

• Jul 18, 2009 - 11:57

OK, but let me just draw your attention to this:
The Arabic strings are right, but the whole passage should have been rendered Right-to-Left, I'm going to try to embed a "dir='rtl'" into the html code (the translation, of course).

I suppose I should re-compile the whole thing, too, but currently I'm using a measly Pentium V for this, and it takes the better part of a whole day (!!!) to finish the compilation (Uuuurrrrghghghghgh) ...

Hosam Adeeb Nashed

Reply

• Jul 20, 2009 - 08:52

Well, I'm not sure what is happening, but even after doing a full compile with the most up-to-date trunk not all Arabic text is showing, notably the html in the About box! But the code itself is rightly done, as evidenced by testing it in a browser.

Releasing from within Linguist, I suppose, is no different from "make lrelease", right?

I've so far finished a bit more than 700 elements.

Although I currently don't think it would be wise to add more on my head (!), but do you think we shall need an Arabic translation of the Manual? I'm just curious how this is handled...

Regards.

Hosam Adeeb Nashed

Attachment Size
mscore_ar.ts 256.34 KB

Reply

• Jul 20, 2009 - 11:46

The update has been committed. It's not clear to me why the arabic translation is still giving issues in the interface, even wit the latest trunk. I'll try to track it down.

Regarding translating the manual: there are two main reasons why it can be so beneficial to MuseScore to have a manual translated in Arabic. First of all for the users (no-brainer) and second because the manual will be indexed by search engines and draw Arabic visitors to musescore.org/ar . The more visitors we can draw to MuseScore, the more chances you'll get help translating the manual.

How does it work? The best way to dive in is with a small example how to translate a typical page on musescore.org.

  1. Go to the translate tab of the teaser page
  2. Click on the link to add the Arabic translation
  3. Replace all English text with the translation, while leaving in the html markup
  4. Finally submit the page and go to http://musescore.org/ar where you will see your translation

These steps are the same for all other pages on musescore.org.

Reply

• Jul 22, 2009 - 21:45

Dear Thomas,
The Arabic translation is awful, I'm afraid... I never take for granted software translators! What Google gave you in fact means, word for word: music free formation & the marking the programmes!!!!
Please copy and paste the following string:
"البرنامج الحرّ لتدوين وتاليف الموسيقى" for the slogan, and then "تحميل مجانى" for Free Download, and lastly "اﻹصدار 0.9.4" for the version number.

The page now looks half-way right. Only the bullets are not quite right! The line has to start from the far right. But the first line and the image are now perfect, in contrast to how they looked when I edited the page.

As for the editor, it did not recognise the

tag, which should have put everything to rights in one go.

Regards.

Hosam Adeeb Nashed

Reply

• Jul 23, 2009 - 07:56

Thanks a lot for your review Hosam. All strings are updated.

Regarding the editor and the website: I will have to investigate how to end up with a good rtl layout for musescore.org. As you may know, musescore.org is build on Drupal, a free and open source content management system. This means we could try to find a good open source right to left layout and work it out. I will take up this task together with the rebranding of musescore.org with the new logo etc. So, don't expect changes in the coming weeks, but rather months. In the meantime, don't hesitate to translate more pages which will draw more visitors to the site.

Reply

• Jul 23, 2009 - 08:34

Dear Thomas,
I noticed something: the page does NOT look the same within the editing section as when just browsing! Please take a look.

I haven't used Drupal myself, but heard about it quite often. I noticed that, although the proper tags are indeed embedded when I insert them, they are not effective on display!! So, the

is effectively there, but is not displayed properly!! The same code, though, gets displayed the right way when I test it in a separate browser window (I use FireFox and SeaMonkey most of the time).

About the Manual: Do you prepare it using a word processor? If so, could you send me a copy to start alongside the software arabisation?

Regards.

Reply

• Jul 23, 2009 - 08:44

You're right. I didn't look into this yet, but indeed I will try to sort this out.

For the menu or handbook (manual) pages, I don't use a word processor but rather the spartan on site text editor. However, considering there is a rtl issue with the editor, it could be good for you to copy paste the English text into your word processor. Tip: use a non markup one, like windows notepad so when you copy-paste your translation back to musescore.org, there is no new markup copied over and all the existing markup remains in place.

Reply

• Jul 23, 2009 - 08:54

It's new to me, but let's solve it step by step:

      As you noticed, http://musescore.org/ar/node/2067 as well as the editor are different from http://musescore.org/ar . So, there appears to be some RtL support in the theme, but not completely implemented
    • I found many references for Drupal + RtL: [1], [2], [3]

      • I'll try to sort this out on short term because otherwise it's not very rewarding to translate musescore.org to Arabic.

    Reply

    • Jul 24, 2009 - 00:18

    Yes!!!! It's already much, much better!! Bravo!!! The title is simply right. Thanks, folks!

    I have to say that apparently some blame has to go to the Gecko rendering engine; because, you see, the page, as is or even before, looked satisfactorily right in Opera, though not in FireFox or SeaMonkey. The bullets read just right in Opera, although the bullet symbols were rendered on the very left (!!!) even under the floating image...

    I'll try to concentrate on the pragramme messages translation, then start on the Handbook, so you have ample time!

    Regards.

    Hosam Adeeb Nashed

    Reply

    • Jul 26, 2009 - 15:00

    By the way, I have translated one page in Arabic:
    Features ("خصائص ومميزات");
    It will need to be added to the menu in the Arabic section.

    Regards.

    Hosam Adeeb Nashed

    Attachment Size
    mscore_ar.ts 258.85 KB

    Reply

    • Jul 26, 2009 - 21:12

    Dear Thomas,
    Qt Linguist shows you all the time how many strings are already translated in each section, as well as globally.

    Regards.

    Hosam Adeeb Nashed

    Reply

    • Jul 26, 2009 - 22:37

    Look, realising that I have started rather late in the cycle, I'm starting to worry that there will be a potential conflict: I need to finish early so I can start translating the handbook, but in the same time I might need a bit more time to revise the translation from within the compiled code...

    I'll just make every effort possible to finish within the running week, since I'll have to travel for six days starting next Sat.

    Hosam Adeeb Nashed

    Attachment Size
    mscore_ar.ts 259.83 KB

    Reply

    • Jul 27, 2009 - 06:55

    Hi Hosam,

    From the 2047 strings in total, there are normally only 1615 strings which needs translation since the rest is common over all languages such as A B C etc. At least for all languages using the characters from the latin alphabet. I don't know whether that's the case as well for Arabic, but if it is than 1615 will be your end point.

    Regarding the handbook: having the Arabic handbook pdf included in the software would be nice, but it's not a must since one day, when it's finished, it will be available for download on musescore.org. I guess we can target on MuseScore 1.0 to have an Arabic handbook pdf included. After all, there is some effort going on to add Mac shortcuts to the handbook and I believe this job isn't over yet. So the handbook is being worked on currently. So no hurry.

    Reply

    • Jul 27, 2009 - 11:12

    Dear Thomas,
    I'm not sure if the option is available in Arabic to omit anything! The notes' names are not ABC, rather Do Re Mi written in Arabic letters. So, I'll just have to keep going...

    On another, positive, note: I finally could visualise the whole set of arabised strings! It seems that just updating the .qm files is not enough; I had to recompile the whole thing. I noted that the culprit, that prevented this to happen previously, was a file named gen-qt-projectfile which should be marked executable, but isn't just after tar decompression. Once this is manually done, everything seems to work like a charm, and the full gamut of arabised strings came to appear in all their glory :-)

    Regards.

    Hosam Adeeb Nashed

    N.B.: Re handbook, point taken, but just for curiosity's sake, will it be easy to make the RTL pdf from the HTML version? Or shall we need the services of oo.org, for example?

    Reply

    • Jul 27, 2009 - 11:26

    Good question about the RTL handbook; I'm quite confident that it will work with the HTML version but for sure it will need some tweaking just like I've done with the website.

    Thanks for the update concerning gen-qt-projectfile as executable.

    Reply

    • Jul 29, 2009 - 11:08

    But I've already translated the Features tab of the menu. Could you try with that? I'll have to wait for a week since I'm going to travel for a one-week job.

    On the other hand, I could always copy and paste into OpenOffice.org Writer and export to PDF from there, taking the English version for a guide line.

    Regards.

    Hosam Adeeb Nashed

    Reply

    • Jul 29, 2009 - 22:24

    That is, as far as HTML goes, of course.

    On another note, I had had to insert at

    element within the arabised teaser page to make up for something a bit strange with the layout, but it's gone now :-( leaving the page absolutely unreadable!

    Thanks.

    Hosam Adeeb Nashed

    Reply

    • Jul 30, 2009 - 06:39

    Hi Hosam,

    Regarding the teaser page: I noticed you used a table for changing the layout. I reverted this since it's got good web coding (css vs tables). However, in order to solve the readability problem: can you point me to the layout problem, perhaps by attaching a screenshot? I can solve it for you I guess in a proper way.

    Thanks!
    Thomas

    Reply

    • Jul 31, 2009 - 08:35

    I know that table are generally frowned at, but the table I used was for a good cause, and in good intention.

    Anyway, attached is how the page should look. As it is, it does look right in Opera, but for some reason it doesn't in the version of SeaMonkey that I'm using (not the very latest). But to be honest, it does look business as usual in the most recent version of FireFox, but I always take into account that all people do not usually upgrade every time there is an upgrade available...

    Thanks.

    Hosam Adeeb Nashed

    Attachment Size
    MuseScore Teaser.pdf 99.57 KB

    Reply

    • Aug 1, 2009 - 09:02

    Well, apparently I'm giving you and myself an unnecessarily hard time... I have three machines, each with a different browser generation. I usually work on the version in the middle (SeaMonkey 1.1.1). When I was a Web programmer I always made it a point not to follow the most up-to-date trends, to ensure that our customers could visualise our pages whatever version they happened to be using. Perhaps I should change this habit...

    Otherwise, on present day versions of the browsers, CSS support seems to have been solid enough, and the page is rightly rendered.

    I had started on the very first page of the Handbook ("الكتيّب") but shall continue with it after I come back from my week in Sudan which should start today at midnight.

    CU.

    Hosam Adeeb Nashed

    N.B.: I might have done a very minor spelling mistake in the Slogan Arabic translation; it should be "البرنامج الحرّ لتدوين وتأليف الموسيقى". Could you please mend it? I know, it's just one letter, but well...

    Reply

    • Jul 28, 2009 - 02:38

    Please follow with me what happened step by step:
    1) The last time I sent an update of the mscore_ar.ts it had 2047 items all in all.
    2) I had intended to recompile the whole thing, so I thought I'd better get the most recent code, the release candidate.
    3) Before I extracted the contents of the tar ball I made a copy of the file I had uploaded just in case the last update had not been committed yet.
    4) I decompressed the tar ball, and then re-put my saved copy in place, over-writing what had been in the tar ball.
    5) I recompiled, and made sure all my efforts are being displayed in the executable, and then ...
    6) I opened the .ts file in linguist only to find that it now contained about 2035, that is around 12 strings less than the original!!!

    Now, should I conclude that lupdate found out that, by comparison to the other language files, my file contains more than is now necessary, and so took out redundant material??!
    Even more, I thought I should compare the two versions I now have, so I opened the older copy (the one I sent last), but I noticed that linguist did not open it in a separate window, or even instead of the currently opened one! It simply showed their respective contents concurrently... With a global number of around 2053!!!

    So, what do you make of all this????

    Hosam Adeeb Nashed

    Reply

    • Jul 28, 2009 - 10:28

    There are two questions in your post. One about lupdate and one about linguist.
    I don't know how linguist works. So I can't answer.
    Regarding lupdate, as far as I understand, it scans the source code for strings to translate and update the ts language files accordingly. So if some strings are removed from the source code, they will be removed from the ts file.

    Source : lupdate man page

    Reply

    • Jul 28, 2009 - 12:27

    I'm at 1747 out of 2032.

    But I didn't understand what an SLine is, so please advise. And, is there a difference between mm (millimetre) and MM in capitals (segments)?

    Regards.

    Hosam Adeeb Nashed

    Attachment Size
    mscore_ar.ts 257.39 KB

    Reply

    • Jul 28, 2009 - 13:14

    Sline is related to a type in the code. I don't think it needs to be translated. Some strings in the ts file don't appear in the UI or appear in developpers "reserved area" like the Object inspector and if not translated will not hurt the average user experience.

    Reply

    • Jul 29, 2009 - 11:04

    If you have some time to spare, give me a couple of days to recompile and check for inconsistency and/or errors. You see, some elements need a slightly different translation according to the context, but within linguist things are not always clearly understood...

    Regards.

    Hosam Adeeb Nashed

    Attachment Size
    mscore_ar.ts 256.16 KB

    Reply

    • Jul 29, 2009 - 22:28

    After recompiling and re-installing I did spot a couple of silly translations. Attached is my very best, final version, except that I found out that the programme used the tool-tip "Accidental" for all types of accidentals in the relevant palette... Is this intentional?

    Hosam Adeeb Nashed

    Attachment Size
    mscore_ar.ts 256.23 KB

    Reply

    • Jul 30, 2009 - 12:39

    A comment by the NL translator suggested to me that although some strings are tagged as "Do Not Translate", they perhaps should be translated. That's what I did in fact, and found out that they did appear in many dialogue boxes, while some other, already translated, strings are not...

    Hence, find attached a newer, amended version...

    I also found some obscure abbreviations:
    CPos
    TPC
    S-Channel
    HGrp (Horizontal Group?)
    SLine

    Anyway, regards.

    Hosam Adeeb Nashed

    Attachment Size
    mscore_ar.ts 256.78 KB

    Reply

    • Aug 10, 2009 - 07:26

    I keep revising for inconsistencies, or listen to friends' suggestions. Or simply discover that what is meant by a phrase isn't exactly its face value...

    On another note, has anyone read my last two replies (to admin and to David Bolton) regarding the arabisation of the Handbook?

    Regards.

    Hosam Adeeb Nashed

    Attachment Size
    mscore_ar.ts 257.31 KB

    Reply

    • Aug 10, 2009 - 07:57

    I have read your replies and have spent quite a bit of time over the past several days looking into the problem. The current HTML to PDF conversion software we are using does not support right-to-left languages.

    I have been looking at Flying Saucer which uses iText to create PDFs. iText supports right-to-left languages as does the XHTML renderer for Flying Saucer, unfortunately the PDFs it creates do not support right-to-left languages. It might be possible to write the code that addresses this issue. However I do not know the depth of coding it would require to fix this issue and integrate it with the current system.

    You mentioned OpenOffice. This was something I investigated before we went with the current system. Unfortunately its HTML support is very poor quality so it would be difficult to integrate it with the website.

    Probably the best solution for now is to have the Arabic handbook in HTML only.

    Reply

    • Aug 10, 2009 - 08:56

    In my comment //www.musescore.org/en/node/2023#comment-5406 I had asked the admin to mend a small mistake and whether it would be appropriate to add the link to the arabised Handbook.

    As far as this last issue is concerned, I suppose the HTML approach is indeed vital for the time being, but later on I could simply convert the whole thing manually, using OOo, just to be incorporated in the downloadable package as well as a separate download.

    Which reminds me: later on, when the thing is completely arabised, shouldn't the link to the on-line Handbook be revised accordingly? Hence, shouldn't it be included in the .ts file as a string to be translated according to each supported language? What do you think?

    Regards.

    Hosam Adeeb Nashed

    Reply

    • Aug 10, 2009 - 18:56

    I updated the slogan with your proposed correction and added the handbook link to the menu.

    The HTML way is indeed the best way and hopefully it works out without using OOo.

    I'm not sure I understand what you mean regarding the Handbook link. But don't worry if it's not a problem yet. We'll tackle it on the right time.

    BTW I managed the admin account as well. It has more right to control the website and so, now and then, I comment in name of admin bc otherwise I need to switch from accounts continuously.

    Reply

    • Aug 10, 2009 - 18:24

    Thomas, If we went with FlyingSaucer then the website would need to use XHTML strict. Currently the MuseScore website has some HTML markup mixed in with the XHTML. However I don't know if this is the method we'll end up using yet or not.

    Reply

    • Sep 2, 2009 - 03:16

    I got the HTML to produce a satisfactory handbook via OpenOffice.org. It takes a couple manual steps at the moment but there is probably a way to automate this later with macros, etc. This is probably the way to go for now (until one of the opensource HTML2PDF converters supports bidirectional text).

    I practiced using the Spanish handbook, but I will show you the results once there is a couple Arabic pages in the handbook to work from and check that everything is OK.

    Reply

    Do you still have an unanswered question? Please log in first to post your question.