Skip to content
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

Open
antonioalia7 opened this issue May 9, 2023 · 3 comments
Open

Unrecognized accents for internal versions of translations #93

antonioalia7 opened this issue May 9, 2023 · 3 comments

Comments

@antonioalia7
Copy link

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?

@maximurm
Copy link

maximurm commented May 11, 2023 via email

@antonioalia7
Copy link
Author

I did it. The file is there too. But same problem. When I search for letters with accents they are not found.

@yukuku
Copy link
Owner

yukuku commented May 17, 2023

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants