# Revision history [back]

LibreOffice does not contain an extra RegEx engine, but one provided by ICU. If there is a bug it is most likely one of the "third-party-software".

As \b in ICU Regex is an abbreviated lookbehind assertion, but a lookahead assertion at the same time, it may be that the enginge cannot recognize the two-sided \b compliance of a single . at the same time: between two \w characters. This, however, should affect many cases where the point is replaced by different \W charachers - but it doesn't in some cases I tested.

Thus the best I can do for you without a lot of reseaech is to suggest the workaround (\b|(?<=\W))hey(\b|(?=\W)) or a similar one.

LibreOffice does not contain an extra RegEx engine, but one provided by ICU. If there is a bug it is most likely one of the "third-party-software".

As \b in ICU Regex is an abbreviated lookbehind assertion, but a lookahead assertion at the same time, it may be that the enginge cannot recognize the two-sided \b compliance of a single . at the same time: between two \w characters. This, however, should affect many cases where the point is replaced by different \W charachers - but it doesn't in some cases I tested.

Thus the best I can do for you without a lot of reseaech is to suggest to use the workaround
(\b|(?<=\W))hey(\b|(?=\W)) or a similar one.

LibreOffice does not contain an extra RegEx engine, but one provided by ICU. If there is a bug it is most likely one of the "third-party-software".

As \b in ICU Regex is an abbreviated lookbehind assertion, but a lookahead assertion at the same time, it may be that the enginge cannot recognize the two-sided \b compliance of a single . point (\.) at the same time: between two \w characters. This, however, should affect many cases where the point is replaced by different \W charachers - but it doesn't in some cases I tested.

Thus the best I can do for you without a lot of reseaech is to suggest to use the workaround
(\b|(?<=\W))hey(\b|(?=\W)) or a similar one.

LibreOffice does not contain an extra RegEx engine, but one provided by ICU. If there is a bug it is most likely one of the "third-party-software".

As \b in ICU Regex is an abbreviated lookbehind assertion, but a lookahead assertion at the same time, it may be that the enginge cannot recognize the two-sided \b compliance of a single point (\.) at the same time: between two \w \w characters. This, however, should affect many cases where the point is replaced by different \W charachers \W characters - but it doesn't in some cases I tested.

Thus the best I can do for you without a lot of reseaech is to suggest to use the workaround
(\b|(?<=\W))hey(\b|(?=\W)) or a similar one.