搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Problem with search engine added with GPO (Qwant Lite) and accent

  • 6 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 Izanagi52

more options

Hello,

I want to add Qwant Lite as default search engine in Firefox 60.3.0 ESR with GPO. I have succefully done it, but there is a problem when I make a research with any character with accent (é, è, à, ...) Example : "testé" become "test%E9"

I have tested with the Qwant Lite Extension, which have exactly the same parameters than my GPO, and there is no problem, so I don't understand why...

Hello, I want to add Qwant Lite as default search engine in Firefox 60.3.0 ESR with GPO. I have succefully done it, but there is a problem when I make a research with any character with accent (é, è, à, ...) Example : "testé" become "test%E9" I have tested with the Qwant Lite Extension, which have exactly the same parameters than my GPO, and there is no problem, so I don't understand why...

被采纳的解决方案

This is fixed in Firefox 60.4.0 ESR.

Thanks !

https://github.com/mozilla/policy-templates/issues/305

定位到答案原位置 👍 0

所有回复 (6)

more options

Hmm, I think "testé" should be URL-encoded as

%22test%C3%A9%22

Could this be a utf-8 vs. Latin encoding difference?

What are you adding -- is it an OpenSource .xml search plugin file?

more options

I have add it with this GPO

more options

Hi Izanagi52, thank you for the screenshot.

In a conventional OpenSearch XML plugin file, there's usually a line like the following:

<InputEncoding>UTF-8</InputEncoding>

It seems there's no space in your form for that.

I don't know whether the search engine plugins you define through GPO have a default character set of UTF-8 or something else.

Could you post a new issue on the following and see whether they can sort out the problem:

https://github.com/mozilla/policy-templates/issues

more options
more options

Thanks for your answers.

Else, can I add a new search engine for all users without this GPO?

more options

选择的解决方案

This is fixed in Firefox 60.4.0 ESR.

Thanks !

https://github.com/mozilla/policy-templates/issues/305