Mtext Indentation Issue

[TimTheriault]

I have a multi-column Mtext that has Indents for the different sections of specifications, numbering and lettering and such. We can change the indents to show however we want, but when we close the drawing and reopen it, a large portion of the text looses its indents. When we open the mtext to edit it, the spacing fixes itself in many of the areas, but not all. We do not want to have to fix this everytime we open the drawing to use it. Is there any way to fix this problem?

I attached 2 .pdfs to illustrate.

Corrected.pdf:
This is what the text looks like after we have tabbed it and moved the spacing to what we want it to look like.

After Reopen.pdf
This is the same drawing, after closing the drawing and reopening.
Upon repoen it looks like that.


The only thing I can think of is that the lines you see that says "Example: PDCS-101........." is somehow causing this to loose its formatting. When I erase that section, the problem goes away. I do not want to have to turn this sheetfull of notes into dtext to avoid this problem.

Thank you for any assistance.
Sorry if this is the wrong place to post this.
We are using the regular version of ACAD 2010.

- Tim

[jaberwok]

How about making each column a separate piece of mtext?

[TimTheriault]

I don't have the approval to split the columns.

But, it happens in the same column down the page a bit too.

[jaberwok]

I don't have the approval to split the columns.

But, it happens in the same column down the page a bit too.

Blast!

Can you strip everything else out of the drawing and post the file here?

[TimTheriault]

Here's the mtext that is giving me heartache

[jaberwok]

I've opened it in vanilla 2012, saved as 2007, closed, reopened, saved as 2010, closed and reopened and it always looks like your correct version.
I then saved it as 2004, closed and reopened it and it changed as your wrong version.

I see that you are saving it in 2004 version. IIRC, 2004 did not support tabs - or, at least, not with the same sophistication as 2007 and later versions.

So, stop saving as 2004, save as 2007 or later (if your workflow permits).

[TimTheriault]

something that easy gave us that much heartache.
I didnt even realize I was still saving to 2004.
Thank you so much!!!!!!!
Crisis averted