strange..
If I were You, I just delete Tags (head tag and tail tag) part only at target segment

Unknown said:

"Externalize" is clearly a serious design mistake.
It should be placed inside of it (segments).

You're so wrong!  Moving unwanted tags outside benefits users far more than the other way around.  But I can see the value in having an option to prepare files with the tags internalised if you want.

"Wrong"
Wooo, you could be Right

Now, Look at the fact, the Wrong guy solved problem. Right ?

What is good at this place be Problematic Right ? I am fully satisfied with Problemless Wrong as you mentioned.

Unknown said:

If you do not like this silly tedious procedure, make your own PlugIn

You still don't seem to understand that not everybody (especially not linguists!) can code, especially not using the crazy .Net hell, requiring dozens of megabytes of libraries just for Hello World :(
And that your way of making a separate plugin for every little one-off sh*tty task is especially crazy...

Plus, I remember very well your beginnings in the forum, when you flooded (under your previous account) the forum by dozens of, well, pretty lame, coder-beginner's questions to which you would find answer if you would actually read the documentation and use some basic programming knowledge.
So playing a big "make your own plugin" hero just a few months after you didn't even know yourself what plugin is and how to make it is kinda funny...

Okay, I just felt the need to express my opinion, this is not meant as flamewar and I will not take part in one.

Wooo

I would like to give you the same wordings minutes ago Paul gave to me. OK ?
"You're so wrong !!! "

In my personal and very smart opinion.
The Powershell is a really sh*t.
That is the degenerated mutation of the great .NET

Unknown said:

the trick is complete it first at EndTag, and then at StartTag
that means, copy StartTag into EndTag first.

This "solution" just pollutes the file with additional huge number of tags! These tags then get into the target file.

Unfortuantely, this is typical "solution" by people who don't see the potential technical consequences and all they care about is what they can see on the screen :(
There is one big "but": what you see is not what you get...

Unknown said:

I do not understand clearly what do you mean by "Option" here ?

Hi  I mean enhance our filetypes to make it possible for a project to be created with the tags internalised rather than externalised by ticking a box.  So it would be optional.  I'm pretty sure that most users would not want this.  So it would be an optional thing for working with projects where you wanted to change the formattting of the target.

I guess creating a plugin as you have done to handle it after the event is another option.  But I think it's neater as an enhancement to the filetype.

Unknown said:

I do not understand clearly what do you mean by "Option" here ?

Hi  I mean enhance our filetypes to make it possible for a project to be created with the tags internalised rather than externalised by ticking a box.  So it would be optional.  I'm pretty sure that most users would not want this.  So it would be an optional thing for working with projects where you wanted to change the formattting of the target.

I guess creating a plugin as you have done to handle it after the event is another option.  But I think it's neater as an enhancement to the filetype.

hmmmm

Thanks for the detailed comment.