Writer: Page Number/Page Count problem.

I have a document with 3 pages and I have a footer in it and I want to see the pagenumber/pagecount there.

I select the footer and I insert the page number and page count like this

Insert -> Fields -> Page Number , I type "/" , Insert -> Fields -> Page Number

When I do a print preview it looks ok.

But when I save the document and open it again I see -1-3 , -2-3 , -3-3 instead.

I use the current version : LibreOffice 3.3.1 Build:8

The file extension is docx

Arda Tunccekic wrote:

I have a document with 3 pages and I have a footer in it and I want to
see the pagenumber/pagecount there.

I select the footer and I insert the page number and page count like this

Insert -> Fields -> Page Number , I type "/" , Insert -> Fields ->
Page Number

When I do a print preview it looks ok.

But when I save the document and open it again I see -1-3 , -2-3 , -3-3
instead.

I use the current version : LibreOffice 3.3.1 Build:8

The file extension is docx

Hi

I can confirm this behaviour. Seems like you've hit upon a bug within the
.docx format. All works as expected in .odf

Regards

Dave

Do yourself a favor. If you must have your documents readable in Word, use the ".doc" format instead of that bloated/complex ".docx" format. I really wonder what MS people was thinking about when they created that XML based format. I know a lot of MSO people who do not touch .docx and .xltx formats. They stick with .doc and .xlt since it is able to be used my more MS Office versions. Since I do not use MSO, I stick with ODF formats like .odt and .ods. But try to avoid MSO's "x" file formats. See if you can get all the people you know that use MSO to stop using "x" file formats.

If the "x format" is the default format in the leading&mainstream office product, you can't escape from it unfortunately.
It is useful for me because the documents are smaller in size.
I know it's so much pain for the development team but LO should be compatible in every possible way.
If someday LO market takes over, LO can set the rules.

I haven't had a chance to check out the various options, but there are some free conversion tools and some
tools for pay that translate docx to doc and, I think, vice versa.

Does anyone have any experience with these?

If the "x format" is the default format in the leading&mainstream office product, you can't escape from it unfortunately.
It is useful for me because the documents are smaller in size.
I know it's so much pain for the development team but LO should be compatible in every possible way.
If someday LO market takes over, LO can set the rules.

Arda Tunccekic wrote:

I have a document with 3 pages and I have a footer in it and I want to
see the pagenumber/pagecount there.

I select the footer and I insert the page number and page count like this

Insert -> Fields -> Page Number , I type "/" , Insert -> Fields ->
Page Number

When I do a print preview it looks ok.

But when I save the document and open it again I see -1-3 , -2-3 , -3-3
instead.

I use the current version : LibreOffice 3.3.1 Build:8

The file extension is docx

Hi

I can confirm this behaviour. Seems like you've hit upon a bug within the
.docx format. All works as expected in .odf

Regards

Dave

Do yourself a favor. If you must have your documents readable in Word, use the ".doc" format instead of that bloated/complex ".docx" format. I really wonder what MS people was thinking about when they created that XML based format. I know a lot of MSO people who do not touch .docx and .xltx formats. They stick with .doc and .xlt since it is able to be used my more MS Office versions. Since I do not use MSO, I stick with ODF formats like .odt and .ods. But try to avoid MSO's "x" file formats. See if you can get all the people you know that use MSO to stop using "x" file formats.

--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***

Glenn
glennst01@gmail.com

I haven't had a chance to check out the various options, but there are some free conversion tools and some
tools for pay that translate docx to doc and, I think, vice versa.

Does anyone have any experience with these?

If the "x format" is the default format in the leading&mainstream office product, you can't escape from it unfortunately.
It is useful for me because the documents are smaller in size.
I know it's so much pain for the development team but LO should be compatible in every possible way.
If someday LO market takes over, LO can set the rules.

MSO tried to add the ODF formats to their package, but did not try hard enough.
Yes MS sets the rules since it has the most market share. It bought the votes to have its XML format made a "second" ISO "international standard" after ODF was made THE "international standard", and there should not be two
"standards" for the same "item" by regulations of the ISO group. He who had the biggest stick [or most money] makes the rules and gets away will not obeying court rulings for years, since the fines for doing so is just "pocket change" for MS. But since more and more Governments are moving to Open Source, then that should mean also that a single company should not control the file formats as well. So ODF is the way they should go unless you use MS's non-XML formats.

I can use any format, it's not a problem for me, but you or I cannot tell using other formats to any computer illiterate who only know ms office which they learn in school.
And I think, if there is an option in any software, it should work.
If it cannot work in the supposed way, that option should be fixed or dropped.
And in this case, I think this is a trivial feature and it should be fixed.

Is standard here to top or bottom post?

In any event, @AT, it is one thing to offer input filter, quite another to offer export filter. If a MSO user wants to access an odt doc he should be turning to Microsoft, not Sun, Oracle, Foundation, etc IMHO. docx is an unmitigated disaster, as arguably the new iWorks format is (folder based) but that is not the real issue here.

If the "x format" is the default format in the leading&mainstream office
product, you can't escape from it unfortunately.

Sure you can, especially when the "leading [for $] & mainstream"
office product supports both formats: just change your default format
to .doc (.xls, etc) and your output documents will be 100% compatible
with the .???x formats (if you're using MSO), or 95+% compatible if
you're using OO or LO.

It is useful for me because the documents are smaller in size.

Better to use .odf formats for this, and they work even in MSO 2007+.

I know it's so much pain for the development team but LO should be
compatible in every possible way.

They are and do, but there are limits when you don't have the
resources of a market giant with monopoly power (so far) and a
proprietary format that no one likes.

If someday LO market takes over, LO can set the rules.

It's coming, sooner than you might think.

I don't really care about the extension but *many* people use docx.
It's not something specific to me.
Thank you for your advice but you get funny when you say "It's coming, sooner than you might think."
I like LO, I appreciate the developers and I'm so willing to install LO everywhere I can and I'm fighting in my company with people but i'm nearly alone with this here.
There are 200 pc users, I can't control who receive what document in which format.
But I know they want it working good, they want it to be compatible with doc and docx format and they don't want to face bugs like I told yesterday.
When anything goes wrong, they want to give up, they want to go back to mso.

The documents I talk about is being used in contracts with pfizer , novartis, etc which are imporant documents here.
LO have "office" in it's name, so I can presume it's targeted for the office use.
If you have success over convincing people to use an office application which can't do page numbering while they need it, I wan't to know how you manage it.
Users here really don't want to spend time with bugs or any conversions and memorize every workaround for every situation.
And most of the problems I face here is about compatibility.
This is nothing personal, nothing emotional and I am sure there are many other companies in a similar profile.
If you think docx can be avoided and it's unnecessary, propose dropping it from the distro.
But I wish it can do page numbering instead.

I don't really care about the extension but *many* people use docx.
It's not something specific to me.

I hear you.

Thank you for your advice but you get funny when you say "It's coming,
sooner than you might think."
I like LO, I appreciate the developers and I'm so willing to install LO
everywhere I can and I'm fighting in my company with people but i'm nearly
alone with this here.

I take it from your email address that you are in Turkey - the LO
change is beginning more in Europe than elsewhere, but I truly believe
that the days of proprietary software are numbered, and MS had raised
more than a few hackles all over the world, although they are also
very good at providing international support - that's what happens
when you have billions to spend on such efforts.

I'm not denigrating any OSS efforts at all by this, especially not LO
since TDF has performed what could well be considered a miracle in
getting LO out in less than six months (!). I'm just saying.... The
for-profit mega-corporation will fight going down every millimeter of
the way.

But I know they want it working good, they want it to be compatible with doc
and docx format and they don't want to face bugs like I told yesterday.
When anything goes wrong, they want to give up, they want to go back to mso.

MSO is for wimps. We just need to make all OSS a little
wimp-friendlier while also educating the timid and weak.

I think your efforts to persuade others to move to LO are quite heroic
given your situation. Don't give up - bugs like the one you hit will
go away, probably faster here than elsewhere.

Thanks for your perspective.

PS: Please don't top-post.... :slight_smile:

[Oh, crap! I used a smiley! I'm doomed now.... ]-;

Hi,

David Griffiths wrote:

Arda Tunccekic wrote:

I have a document with 3 pages and I have a footer in it and I want to
see the pagenumber/pagecount there.

I select the footer and I insert the page number and page count like this

Insert -> Fields -> Page Number , I type "/" , Insert -> Fields ->
Page Number

When I do a print preview it looks ok.

But when I save the document and open it again I see -1-3 , -2-3 , -3-3
instead.

I use the current version : LibreOffice 3.3.1 Build:8

The file extension is docx

Hi

I can confirm this behaviour. Seems like you've hit upon a bug within the
.docx format. All works as expected in .odf

I can also confirm this using LibreOffice 3.3.1 (Build:8) on Ubuntu 10.04.

One thing which might be of interest is that opening the saved document with Microsoft word viewer (sic!) the expected result is shown, so if you are saving in docx format just to share with someone with MS office they should view the document ok.

As for the doc(x) and MS office 'dominance' in the work environment I feel and share your pain (especially on the presentation side here).

Another thing (untested)... I think nothing prevents you from saving from LO to .doc format (which seems to be better supported) and simply rename the file to .docx ... Ok I know this sounds a bit mean.. but hey I bet no one would know it and do you really use the docx features? :wink:

Lorenzo.

I don't really care about the extension but *many* people use docx.
It's not something specific to me.

Much of the work being done to make the "x" formats work, outside the Microsoft product line, is done by reverse engineering. MS does not share the documentation that defines their XML "x" formats. Even when they wanted it to be "the" ISO standard, the would not hand over all the needed definitions needed to develop the "codes" so non-MS packages could read/write those files properly. So dedicated people are working on figuring out what the internal definitions are so LibreOffice [and others] can support MS's XML file formats.

Thank you for your advice but you get funny when you say "It's coming, sooner than you might think."
I like LO, I appreciate the developers and I'm so willing to install LO everywhere I can and I'm fighting in my company with people but i'm nearly alone with this here.
There are 200 pc users, I can't control who receive what document in which format.
But I know they want it working good, they want it to be compatible with doc and docx format and they don't want to face bugs like I told yesterday.
When anything goes wrong, they want to give up, they want to go back to mso.

The documents I talk about is being used in contracts with pfizer , novartis, etc which are imporant documents here.
LO have "office" in it's name, so I can presume it's targeted for the office use.
If you have success over convincing people to use an office application which can't do page numbering while they need it, I wan't to know how you manage it.
Users here really don't want to spend time with bugs or any conversions and memorize every workaround for every situation.
And most of the problems I face here is about compatibility.
This is nothing personal, nothing emotional and I am sure there are many other companies in a similar profile.
If you think docx can be avoided and it's unnecessary, propose dropping it from the distro.
But I wish it can do page numbering instead.

If the "x format" is the default format in the leading&mainstream office
product, you can't escape from it unfortunately.

Sure you can, especially when the "leading [for $]& mainstream"
office product supports both formats: just change your default format
to .doc (.xls, etc) and your output documents will be 100% compatible
with the .???x formats (if you're using MSO), or 95+% compatible if
you're using OO or LO.

It is useful for me because the documents are smaller in size.

Better to use .odf formats for this, and they work even in MSO 2007+.

Last time I knew, MSO did not do a good job at supporting ODF. Sun [now Oracle] had an extension that you could add to MSO that worked, somewhat, to allow MSO to read/write ODF, but MSO had stated that they planned on doing this natively in their next version. That was in 2010 [I think], and I was told that MSO did not do a good job natively supporting ODF. I could be wrong, since I have not updated MSO beyond 2003, and I rely on others who have tested this "native support".