-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
charset_table #16
Comments
+1 |
It would be better if this charset_table would detect if your using UTF8 or not. If using UTF-8 it should build a charset safe for UTF-8. |
@Yariksat and @realdigger Can you guys try the following in your configs. See if this gets support working.
|
Thank. |
It could worth to have a look at phpbb/phpbb#5815. Just note that the phpBB implementation is using the older SphinxAPI instead of SphinxQL. |
Just to clarify, they have a different licensing model which means we can't borrow any code from them without it being noncompliant with the GPL and 3 Clause BSD. However the configuration of the Sphinx is not something that would be considered licensable. The difference between the API and QL usage doesn't matter here as this is more how Sphinx is setup to process the data. Looking at what they set, the charset looks very familiar with some different options elsewhere that we are not setting. If we are finding those options are needed or fix other issues, they should be added. I think the requested test for the updated charset should get things rolling properly. |
@realdigger Here is good config for sphinxserach indexes creation: |
So after looking into this and thinking. I think the best solution is to
The config is supposed to be hints to get things working, not be a OOB solution. http://sphinxsearch.com/docs/current/conf-charset-table.html |
charset_table = 0..9, A..Z->a..z, _, a..z
Would be better to remove this line or make it optional, because it limit index to latin charset only.
Default value for charset_table are latin and cyrillic characters.
The text was updated successfully, but these errors were encountered: