On 17 April 2013 14:34, F Wolff <frie...@translate.org.za> wrote: > On Wed, Apr 17, 2013 at 1:57 PM, Dwayne Bailey <dwa...@translate.org.za> > wrote: > > > > > > > > On 17 April 2013 12:06, F Wolff <frie...@translate.org.za> wrote: > >> > >> On Wed, Apr 17, 2013 at 10:19 AM, Julen Ruiz Aizpuru <jul...@gmail.com> > >> wrote: > >> > Hi Jason, > >> > > >> > az., 2013.eko apiren 17a 05:27(e)an, Jason Pickering(e)k idatzi zuen: > >> >> I am seeing an error message each time a string is translated. It > >> >> appears > >> >> in the browser as "Unknown error". After looking at the JavaScript > >> >> console, > >> >> I see something like the error message display below. > >> >> Is there a way to disable this feature completely or do I need to > setup > >> >> my > >> >> own server for this? > >> > > >> > To disable this feature altogether you can set `AMAGAMA_URL = ''` in > the > >> > server settings (this can only be disabled by a server admin). > >> > > >> >> > >> >> 1. Request URL: > >> >> > >> >> > >> >> > http://amagama.locamotion.org/tmserver/en_GB/id_ID/unit/?source=Back%20to%20search&jsoncallback=_jsonp569633 > >> >> 2. Request Method: > >> >> GET > >> >> 3. Status Code: > >> >> 404 NOT FOUND > >> > > >> > This sounds like the provided language-pair is not properly > >> > detected/supported by amagama. So it's probably a bug on either > amaGama > >> > or Translate Toolkit. > >> > > >> > Friedel, is this a known issue? Sounds like a similar situation to > >> > script variants (bug 2556[1]). > >> > > >> > HTH, > >> > Julen. > >> > > >> > [1] http://bugs.locamotion.org/show_bug.cgi?id=2556 > >> > >> A 404 from Amagama mostly means that the language pair is not > >> supported/available. In this case we could simply pretend that "en_GB" > >> is "en", and serve the request as such. > > > > > > We seem to fallback like that on the target, but not the source, was > that by > > design? > > I think so. I think it has more to do with the fact that certain > varieties are registered in the Toolkit as existing on their own (like > en_GB, pt_BR), and in that case we don't simplify the code further. > > >> I think Pootle's client should > >> not show the 404 as an error, but just silently supress it. Also, it > >> shouldn't ask again for that language pair. > >> > > > > I think we haven't hit this as we send back an empty list if we don't get > > anything for an unkown target language. So it is only hitting us on > source. > > Yes, we just haven't gotten to that yet. I would like to do it for an > unknown target language as well. I would also like the server to be > able to supply a list of the pairs it supports so that clients never > need to ask for something that isn't supported. >
Are you able to turn some of those into bugs? There is some amagama work I'd like to schedule and it would be nice to have them on file. -- Dwayne *Translate* +27 12 460 1095 ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
