Thanks Atul, It is working well and fine -John
On Jan 29, 9:47 pm, Atul Varma <[email protected]> wrote: > Betas are super easy to push, so I just made a new one. :) You can get > it here: > > http://ubiquity.mozilla.com/xpi/ubiquity-latest-beta.xpi > > Let us know if the problem still persists! > > - Atul > > On 1/29/09 7:13 AM, John wrote: > > > That's fine Atul. But when will be the next beta release? Can I get to > > know where this change has to be made so that I can continue my > > experiments? Or can you help me with an intermediate release? > > > Thanks once again to Blair and Atul for taking up this issue. > > > -John > > > On Jan 29, 7:20 pm, Atul Varma<[email protected]> wrote: > > >> Thanks for reporting this, John. This breakage was my fault; I've just > >> fixed, so it should show up in the next beta release. Sorry about that! > > >> - Atul > > >> On 1/29/09 2:37 AM, John wrote: > > >>> Hi Blair, > > >>> I think I have finally found out the reason which can be useful in > >>> solving up the issue. In Windows, I had ubiquity version 0.1.4 and > >>> the command correctly worked. But in Linux, I had version 0.1.5. But > >>> today I updated ubiquity to 0.1.5 in Windows also and the same problem > >>> which was seen in Linux also propped up in windows. The command is now > >>> displayed in 'Your commands' as '%u092D%u093E%u0930%u0924' in Windows. > > >>> So if you see the diffs between the two versions, you may be able to > >>> figure out the issue. Since Now it is clear that it is not OS specific > >>> issue, but rather the issue is with ubiquity. > > >>> -John > > >>> On Jan 29, 1:03 pm, John<[email protected]> wrote: > > >>>> Thanks for filing the bug. > > >>>> -John > > >>>> On Jan 29, 12:20 pm, Blair McBride<[email protected]> wrote: > > >>>>> I asked a couple of the other Ubiquity devs to take a look at this, and > >>>>> it has them stumped too. Apparently it has issues on OSX Leopard too. > > >>>>> However, we did come to a general consensus, in that we *think* its not > >>>>> Ubiquity's fault. But, of course, that's not very helpful. > > >>>>> Until this is fixed, I've added a bug report > >>>>> here:http://ubiquity.mozilla.com/trac/ticket/544 > > >>>>> - Blair > > >>>>> On 29/01/2009 4:35 PM, John wrote: > > >>>>>> After writing the command, I checked the 'Your Commands' Tab. The > >>>>>> particular command appears as '%u092D%u093E%u0930%u0924 > >>>>>> ' in Linux whereas in Windows it appears as 'भारत'. > > >>>>>> The command appears in suggestion as '%u092D%u093E%u0930%u0924'. But > >>>>>> I feel that such an appearance will make no meaning with respect to a > >>>>>> user. > >>>>>> This is not a font issue, since the word 'भारत' appears in the command > >>>>>> editor. > > >>>>>> Is this some locale issue with respect to Linux? > > >>>>>> -John > > >>>>>> On Jan 29, 3:11 am, Blair McBride<[email protected]> wrote: > > >>>>>>> Hmm, if this is working on Windows but not Linux, then this has me > >>>>>>> stumped. I'll see if I can get someone else to look at this issue as > >>>>>>> well. > > >>>>>>> How does it break? Does it just not show up in the suggestion list? > >>>>>>> Does > >>>>>>> it show, but not preview/execute? Or is it displaying the wrong glyphs > >>>>>>> (characters/symbols) for the same? (The later would indicate a just a > >>>>>>> font issue.) > > >>>>>>> - Blair > > >>>>>>> On 28/01/2009 8:33 AM, John wrote: > > >>>>>>>> Hi Blair > >>>>>>>> This is the command I have written > >>>>>>>> CmdUtils.CreateCommand ({ > >>>>>>>> name: "भारत", > >>>>>>>> execute: function() { > >>>>>>>> displayMessage("Testing Ubiquity with utf-8"); > >>>>>>>> } > >>>>>>>> } > >>>>>>>> ) > >>>>>>>> The command name is in Hindi(Devanagari) Language. This command works > >>>>>>>> well in Windows. But it is not working with Linux (Ubuntu). Am I > >>>>>>>> missing anything? > >>>>>>>> -John > >>>>>>>> On Jan 27, 2:59 pm, Blair McBride<[email protected]> wrote: > > >>>>>>>>> Hi John, > >>>>>>>>> I would have expected UTF-8 to work - there are many commands feeds > >>>>>>>>> in > >>>>>>>>> different languages that use various different encodings. JavaScript > >>>>>>>>> itself is natively in Unicode. Could you provide a sample command > >>>>>>>>> that > >>>>>>>>> uses UTF-8 that Ubiquity doesn't handle correctly? > >>>>>>>>> Its possible that this is just an issue of what encoding the server > >>>>>>>>> is > >>>>>>>>> sending the file as, or possibly the encoding of the HTML page that > >>>>>>>>> links to the file. > >>>>>>>>> - Blair > >>>>>>>>> On 26/01/2009 11:17 PM, John wrote: > > >>>>>>>>>> Is there any possibility of supporting UTF-8 for the name field? > >>>>>>>>>> I was trying to create some commands other than English but that > >>>>>>>>>> didn't work. Is there any possibility to include that in the future > >>>>>>>>>> releases? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ubiquity-firefox" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ubiquity-firefox?hl=en -~----------~----~----~----~------~----~------~--~---
