PI being moved by XML Stream filter

[Former user]

Original [issue 145](https://code.google.com/p/okapi/issues/detail?id=145) created by @ysavourel on 2010-09-29T22:30:12.000Z:

In the attached file we have:

<entry id="v944944\_fr-fr" colname="col1"><ph id="v944945\_fr-fr" translate="no">4500<ph id="v944946\_fr-fr"><?xm-replace\_text Phrase?></ph>-30 </ph> </entry>

after processing it becomes:

<entry id="v944944\_fr-fr" colname="col1"><?xm-replace\_text Phrase?><ph id="v944945\_fr-fr" translate="no">4500<ph id="v944946\_fr-fr"></ph>-30 </ph></entry>

The <?xm-replace\_text Phrase?> get moved to the start of the entry content.

Note: it's Ok for M9, but would be nice to fix for M10.

[Former user]

Comment [1.](https://code.google.com/p/okapi/issues/detail?id=145#c1) originally posted by @ysavourel on 2010-09-29T22:30:58.000Z:

[Former user]

Comment [2.](https://code.google.com/p/okapi/issues/detail?id=145#c2) originally posted by @ysavourel on 2010-09-29T22:35:28.000Z:

We also have files with PI in them - I'll make this a priority for early M10.

[Former user]

Comment [3.](https://code.google.com/p/okapi/issues/detail?id=145#c3) originally posted by @ysavourel on 2010-10-25T19:50:46.000Z:

This bug has to do with the tricky INLINE\_EXCLUDED\_ELEMENT support we added for translate=no cases. Looking at it now.

[Former user]

Comment [5.](https://code.google.com/p/okapi/issues/detail?id=145#c5) originally posted by @ysavourel on 2010-10-25T22:50:07.000Z:

Fixed by making sure inline PI's (and comments) obey inline exclusion rules