Re: [MSEide-MSEgui-talk] msei18n vs PO files

Hello fredvs, you wrote on Tue, 14 May 2019 06:07:06 -0700 (MST): > > I.e. you use Java for user interface only, which is just what I meant. > > Not sure to understand,but even on a "pure Android" machine (like a a > mobile-phone), compiling a Java-compatible library with fpc is working. If

Re: [MSEide-MSEgui-talk] msei18n vs PO files

Re-hello Sieghard. I forgot to note, for the Android-Java-native library in previous post, that it works if the library is compiled on a ARM machine. I use a Rpi + Raspbian. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___

Re: [MSEide-MSEgui-talk] msei18n vs PO files

Hello Sieghard. >> I do it for uos (United Openlibrary of Sound), compile with fpc a >> Java-native library and use that library with Java applets. > I.e. you use Java for user interface only, which is just what I meant. Not sure to understand,but even on a "pure Android" machine (like a a

Re: [MSEide-MSEgui-talk] msei18n vs PO files

Hello fredvs, you wrote on Mon, 13 May 2019 13:05:34 -0700 (MST): > Hello Sieghard and sorry for the long delay. No problem . > Hum, Android is Java, so, IMHO, fpc could only deal with Java via Well, it usually uses a Java virtual machine defined by Google, but it's kernel is - as yet -