Problem translating certain strings on the website
Some strings on the homepage don't retain their translation after I've clicked the blue tick mark. All of them has two words without a space between them.
Example: 
between music and notation there is a line break on the page itself.
I suspect that I should enter a "line break" character between the words, but I don't know where to find it. The "enter" key doesn't work. Am I missing something? What should I do?
PS Should I post similar posts about translation problems here in the support and bug report forum or in the translation forum in the future?
Louis
| Attachment | Size |
|---|---|
| Vertaling.JPG | 10.95 KB |
Comments
Thank you for reporting this Louis. I didn't hit this issue myself, but I will try to reproduce in the coming days.
I moved your post to the translation forum.
In reply to Thank you for reporting this… by Thomas
Thanks!
In reply to Thanks! by Louis Cloete
This?
Professional music
notation software
I see that < br / > is 'absorbed'
In reply to This?… by Shoichi
I am not quite following you. Does it mean I should insert "< br / >" between "music" and "notation"?
In reply to I am not quite following you… by Louis Cloete
to me it appears as in the attached image...
but I saved the translation some time ago
In reply to to me it appears as in the… by Shoichi
Thanks, now I understand, but still no joy for me. The top row of the six reasons "Why MuseScore?" doesn't want to translate, as well as other places where there are line breaks which are missing.
Interesting though that your string to be translated (the English string) also contains the "
" tag. Mine doesn't, so it's a good bet that's the problem.
Thanks for trying to help, I think it has cleared the problem up somewhat for me.
In reply to to me it appears as in the… by Shoichi
The "" in my post above actually contains "br /" between <>, so it is disappearing here in forum posts too.
In reply to The "" in my post above… by Louis Cloete
< br > without spaces should interrupt the line;
/ (slash) delete the previous command.
Try to delete '/'
In reply to < br > without spaces should… by Shoichi
Still no joy without the slash.
Could you remind me which browser you are using and on which platform?
In reply to Could you remind me which… by Thomas
Windows 7 32 bit and edit: Internet Explorer 11
@Shoichi, Thomas
Figured it out. I was clicking on the blue block (see screenshot) with a link reading "Translate page" in the lower right corner of the Afrikaans homepage (musescore.org/af) to access the strings. That gives you an interface containing only the strings on the page you are currently on. In that interface this bug or fault is present.
When I went to this page musescore.org/af/admin/config/regional/translate, I found the string and translated it without problem. So there is some problem with the interface accessed via the blue block in the lower right corner of the page, but not at the main interface translation page. Hope this helps.
Louis
In reply to @Shoichi, Thomas… by Louis Cloete
A good track!
Thank you for your contribution and, if I can afford, in your spare time take a look at this page that I had entered with the help of Google translator: https://af.wikipedia.org/wiki/MuseScore ;-)
In reply to A good track!… by Shoichi
Thanks for the Wikipedia page! I just want to know, from what did you translate it with Google Translate? I would like to see the source (if it is English ;-) - I can't understand Italian) to help me.
In reply to Thanks for the Wikipedia… by Louis Cloete
Edit the suffix (en/en/it/af) to reach the page you are interested in
(my ways are a bit rough)
In reply to Edit the suffix (en/en/it/af… by Shoichi
Thanks!
In reply to Thanks! by Louis Cloete
@Louis, I would like to take advantage of your availability ...
Tell Thomas about the translation in Afrikaans of some forums title (eg Support and bug reports / General discussion / Made with MuseScore) to have them available on your page.
(excuse the impudence)
We found the root cause of this issue. A fix for it will be deployed on Monday next week. Thanks again for reporting.