Can't type accented characters into song entry window about quelea HOT 19 CLOSED

I can confirm that.
I tried launching Quelea like this (with the original Launch.sh file)
/usr/bin/java -Xms1200m -Dfile.encoding=UTF-8 -Djavafx.embed.singleThread=true -Dprism.dirtyopts=false -jar Quelea.jar
And I tried it directly like this in the installation folder
java -jar Quelea.jar

That does't change anything. In both cases everything works just fine, but the accented characters in the song editor just don't work...

Using Linux Mint 19, Java version 8 and Quelea 2018.1

(I tried the 2019 snap version for linux too, but it does't work either)

from quelea.

Can't seem to reproduce this - @ArvidNy , are you having any luck? You're probably better placed to test accented characters than me...!

from quelea.

I can reproduce this as well. For instance, writing 'é' just results in 'e'. Don't know how to get this character with the English keyboard layout, so I've only tried this with the Swedish keyboard layout where you need to press two characters in a sequence to make this character.

from quelea.

from quelea.

Just did a quick test in Window 10 and it seemed to work as expected with both Spanish and Swedish keyboard layout, so my guess is that this is another Linux bug since we both get this behaviour in Linux Mint. I wasn't able to use Alt Gr + the non-accented key in Linux Mint, so I'm still not sure if this also applies to English keyboard layout. However, I remember someone in my church saying this was a problem when they were adding a song in Spanish and we use Window 10 there. I'm about 1000 km from my church at the moment, so it might be a while before I can try it there again to verify it though. Either way, I get the feeling this might be a bug in the library we're using since it works in the title text field but not in the lyrics field. Perhaps it has something to do with the fact that you need to press a key sequence using a 'dead key' (as in ' + e) and not two keys together (as in alt gr + e).

from quelea.

from quelea.

Sounds like a good plan. However, RichTextFX doesn't seem to be maintained anymore, so we might have to resolve it ourselves either way. Can't say for sure when I'll be able to look at this a bit more thoroughly, so feel free to have a stab at it if you end up having some spare time.

from quelea.

I did a quick test s well, seems like you found the problem. I can use the dead keys like ~+a in the title fields, but not in the lyric field. I'm using portuguese keyboard layout, and we have a lot of accented characteres, but I have no access to them via AltGr. The special characters designed for the AltGr key are functional like AltGr + ] gives me º just as shown on my keyboard, and they all work on the lyrics field. (¹²³£¢¬§€®ŧ←↓→øþªæßðđŋħłº«»©nµ°) but none of these are the ones I need, like (ã á à é ó ü)

from quelea.

Had another quick look at RichTextFX and found this issue where they conclude it's a JDK bug in Linux. I suppose there's no good way around it then at the moment.

from quelea.

Yup, a JDK bug it seems, so we're blocked on this:

https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8172867

Not much we can do aside from wait for that to be fixed unfortunately.

from quelea.

What do you think about swapping the lyrics area for a regular TextArea if Quelea is run on a Linux system as a temporary fix? To me it feels like it's more important being able to spell correctly than for the chords and the labels to be properly styled.

from quelea.

from quelea.

Sounds good to me! Well, either that or it's just a bug report lost in the "silent user" ratio. =)

from quelea.

@hosios, do you still use a Linux system? I've just found a workaround for Japanese characters and I started thinking it might have resolved this issue as well, and on my keyboard layout I can now type accented characters. Would you mind testing the CI release and see if you notice any difference with the characters you need?

from quelea.

I can test it for you, (will do it tonight) but apart from this issue, and some others, I moved to OpenLP. Sorry guys. I can manage a lot of problems, but most of the users in our church just need a working system. And Quelea didn't deliver just yet. But I'm still open. I realy like the concept.

from quelea.

That's kind of you, thanks! Sorry that Quelea hasn't been working out for your church, but I'm happy to hear that you've found another software that suits your needs.

What were the other issues that made you give up on Quelea? If there are deal-breaking issues that keep users from using the software, we want to try to resolve them if possible.

from quelea.

Hi,

About the issues: (will test the software later)
Issue Nr. 1 is/was the lyrics typing
Issue Nr. 2 (not a deal breaker) but I could not make the video work properly on Linux
Issue Nr. 3 (very Important to us) no cloud sharing of the database (for Dropbox or Nextcloud). We have 4 worship leaders, and we prepare the songs at home, and everybody has access to the same songs. We used OpenSong before, and we could define the database's path (songs, themes, etc) to one common shared place. At the time of my testing it wasn't possible (not even planed) for Quelea. Don't know how its now.
Issue Nr. 4 I really can't remember right now, but I know there was something else. I think it had something to do with the resolution of the projector. I don't know.

from quelea.

Well, after the usual battle to make Quelea even run (Issue Nr. 5?) I finally tested the lyrics entry text, and I can confirm: Accented characters do work with the dead keys on my Keyboard, the same way they work on other software, like LibreOffice.
Problem solved.

from quelea.

Brilliant, many thanks for verifying it! In that case I'll just close this issue for now, and in case anyone else would experience similar issues, they could just open it again.

As for the other issues, the big deal breaker seems to be the missing cloud synchronization. That's on our to-do list, but we still haven't tackled that issue. I've had some ideas about possible ways to go about it to avoid corrupting the database if many users use it simultaneously, but none of us have had the time to really try to solve it yet.

If the other issues still are present, I'd advice you to open issues for them if you were planning on using Quelea, but I suppose you'll stick with OpenLP until Quelea can offer cloud synchronization. Either way, many thanks for sharing your experiences with Quelea and for helping me confirm that this issue now is resolved!

from quelea.