12345678901234567890
I installed the font XB Kayhan and then open your document and it seems OK. The same when I changed the font to Scheherazade or Scheherazade New.
But for KFGQPC Uthman Taha Naskh, Amiri and Noto Naskh Arabic it showed “kashidas”, but always for different words. I’m not sure, but maybe it is related to the ligatures in the font.
Win10x64 Libre 7.5.0.3
Like I suspected. Please report an issue on bugzilla. On the meantime, I suggest using different fonts. XB fonts are probably the only third-party Arabic AAT fonts.
12345678901234567890
“If” your documents are based on the same template (so that the styles confer a uniform layout to all of them), all you need to do is to modify one or a few styles in the template. The documents are automatically updated next time you open them.
When you maintain a collection of several hundreds document, a strict methodology is mandatory. Not using template is equivalent to direct formatting text but on a much larger scale.
Even if it is tedious and boring, it might be time to adopt a “professional” approach to document management.
12345678901234567890
Which is the wrong way of using it.
Are you sure this can’t be solved with a judicious collection of styles. There are surely not several hundreds different layouts. If they number less than ten, it can be handled elegantly with styles. Not all people will use all styles but they’ll find what they need in the collection.
12345678901234567890
Omg. Yes, reading is hard.
You had been asked to file a bug. Twice. By two (!) actual developers who happened to read this: myself and @khaledhosny2 (who is the expert in fonts and layout and CTL (using CTL, and being one of principal contributors both to LibreOffice and to Harfbuzz). Asking for a bug means we agree that the issue exists. Khaled also suggested you a workaround in the meanwhile, knowing the root cause, and in the impression that people who ask here usually need some solutions that would work now. All that you replied was rudeness.
12345678901234567890
I read it, and I didn’t see why anyone would need to wait, but it’s your decision. It just feels sick when someone asking for help gets a suggestion to file a bug report (with a note that the version is new an regressions are expected), then tells that they will wait, then gets another reply describing the problem in depth (which mentioned that the problem is specific to very few fonts), and then posts a series of comments blaming people trying to help.
12345678901234567890
You can always ask for a refund.
1 Like
FWIW, I did extensive testing and I did encounter this issue and even considered a possible solution, but there wasn’t enough time to implement it so I took a calculated decision that the benefits of the new approach greatly outweighs the negatives. The fact the old code worked for this particular font is accidental, and the new code correctly handles much more fonts. Also the breakage is recoverable since it has no effect on the proper rendering of the text (no gaps) and it doesn’t affect line breaking either (so no document reflow). The new code is more cautious and prefers no Kashida to insering Kadhida at bad positions, while the old code would happily insert Kashida where it shouldn’t (as evidenced by the multitudes of bugs that have been fixed).
Only a days? It doesn’t seem so terrible 
/joke, and I hope not the offensive joke for you . For example I make one project nearly 7 years and I repaired more times some changes that took me a days/.
I understand it is very unpleasant for you - to downgrade to older version or repair the hundreds of documents.
But is it possible to automate the fix of hundreds documents? I think yes.
ODT files are only renamed ZIP, and if you rename ODT to ZIP and unpack, there are the XML files. And it is possible to replace the string XB Kayhan to OtherFont. It is not problem to rename the ODT files to ZIP, and I saw some webs there was the procedure how to Find&Replace in ZIP files. But it was under Linux. Maybe you will able to find some program under Windows or Mac or what you use.
Or it is possible to write the macro that will unpack the ODT files in some directory, or pack the directories to the ODT files. And use some program for batch Find&Replace to change the strings.
Or write a macro that will generate the Shell commands for some ZIP program to unzip/zip the files.
So if you have some font instead XB Kayhan, I think it could not be problem for many days. I don’t write it could be easy, but it could not be impossible or so hard .
But of course, these “hand” editation could be danger 
, but I don’t see the problem if only the name of font is replaced. I did this operation for some Templates before few days, and succesfully.
But if you have some complicated formatting and it need also to change some Enters or positions for new font, probably it is not possible to automate it .
Given the text on the fontlibrary.org page, is it possible that the font has both technologies built-in, and so the library possibly could use the other when there’s no data in the first?
a bit error-prone…isn’t it ?
The better way seems to adapt the styles of one writer-doc, and in any target.odt if you need:
→Styles→Load Styles→→From File....
and of course the whole job for 100+ files can be done by few lines of code!
As you have discovered a serious bug, it is wise to keep this topic, at least as a reminder or an incentive whip for developers. Also, many visitors have already seen and read your question. Being able to search for it has a high value for people needing Arabic writing, at least to be cautious with LO 7.5 and keep an eye on future releases.
Please, restore your question.
PS: I don’t know if deleting your account also deletes your posts. Anyway, no user here, even with high privileges, can delete your account. You should ask site maintainers through the Feedback category.
HarfBuzz does not currently offer a way to control whether AAT or OpenType will be used if the font has both, it will choose one or another based on some heuristics that try to replicate what CoreText does with such fonts.
That is all moot anyway, the OP got so upset and deleted everything they wrote crippling the discussion. Until more people complain about this, it is a low priority issue AFAIC.