I figured it out! The "index.eng.html" part, I mean. The translator is
not in testing anymore, so I moved it to https://silling.org/translator
 I still don't know how to approach the other two problems. If anyone
could help, I would really appreciate it. :)
Greg 
-------- Wiadōmość przekazowano ----------Ôd: Grzegorz Kulik <
g.ku...@o2.pl>Do: apertium-stuff@lists.sourceforge.netTymat:
Implementing apertium-html-toolsData: Sat, 20 Jul 2019 14:06:38 +0200
> Hi, 
> I asked this question on #Apertium, but it might be better to do it
> here. I'm just implementing Apertium into my WordPress installation (
> https://silling.org/test-translatora) and I can't figure out two
> things: how to stop Apertium from adding anything after the slash
> (index.eng.html?dir=pol-szl#translation) and how to get the language
> names to work, because I'm just getting "szl" instead of the actual
> name. 
> The Wiki says that apertium-apy supports POST method but there's no
> more information. How do I turn it on in apertium-html-tools? And how
> to get rid of the "index.eng.html"? I tried to fiddle with all.js to
> the point where I deleted almost entire persistChoices function but
> it still adds the "index.eng.html" to the URL. What can I do about
> it?
> Would it be possible to just have permanent names for languages
> instead of them being loaded from an external source? I even tried to
> add:
> "LANGNAMES": {'pol': 'polskŏ','szl': 'ślōnskŏ'},
> since there is no documentation what that function does. Any ideas?
> Thank you in advance!
> Best,Greg
_______________________________________________
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Reply via email to