-
Notifications
You must be signed in to change notification settings - Fork 181
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
Unrecognized accents for internal versions of translations #93
Comments
When converting to INTERNAL, there is a file ddd_revindex.bt (or not "ddd"
if you specify a prefix)
Make sure you include that file in the assets/internal folder, so that
search is consistent.
…On Wed, May 10, 2023 at 2:14 AM antonioalia7 ***@***.***> wrote:
I changed my translation from yet to internal version.
I made sure the format was as described UTF-8 encoding without BOM and
UNIX format.
Now when there is in the internal version therefore in the biblical text a
word with an accent, example: "creò"
If I write this word with an accent in the search, it is not found. On the
contrary, if I write "creo", the verse where this word exists is found. The
problem is that in both cases it doesn't highlight it and in the first case
it doesn't find it, but it actually exists in the biblical text.
This doesn't happen if I transform the .yet version and import it into the
.yes version in the app.
At that point the search works perfectly. Do you know how this problem can
be solved?
—
Reply to this email directly, view it on GitHub
<#93>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFIIXU5CQZJ6JBX24GPA2BTXFLFXHANCNFSM6AAAAAAX36FLYY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
I did it. The file is there too. But same problem. When I search for letters with accents they are not found. |
I removed the revindex functionality: 08aa25c Letters with accents are not modified/normalized before searching. Therefore, "creò" only matches "creò" and not "creo". |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I changed my translation from yet to internal version.
I made sure the format was as described UTF-8 encoding without BOM and UNIX format.
Now when there is in the internal version therefore in the biblical text a word with an accent, example: "creò"
If I write this word with an accent in the search, it is not found. On the contrary, if I write "creo", the verse where this word exists is found. The problem is that in both cases it doesn't highlight it and in the first case it doesn't find it, but it actually exists in the biblical text.
This doesn't happen if I transform the .yet version and import it into the .yes version in the app.
At that point the search works perfectly. Do you know how this problem can be solved?
The text was updated successfully, but these errors were encountered: