different font size in different files

I have tried to standardize on freesans 10 point for most ss uses. I just came on a file with very small type size, yet when I selected the cell and the format -> font, I got freesans 10 point. Not wanting to diagnose myself as blind and/or crazy, I brought up another file with the same freesans 10 point, and they are clearly different.

why?,

john

​Just a guess: the zoom level is stored in the file. Have you checked that?​

​It is visible in the bottom right corner of LO window, or in the
Display/Zoom menu.​

Hi :slight_smile:
Or from the View menu go to the last item = "Zoom"
Regards from
Tom :slight_smile:

No idea, but I used to copy and paste from a terminal window (Mac) to a calc sheet with no problem, until the latest release. Now, what I paste gets blown up to a much larger size. I have to enter the numbers by hand and then they are okay. I have no idea why this is happening or what to do about it.

This may or may not be a related problem.

​Maybe your terminal now copy as rich text. Try "paste special" (it's in
the edit menu, or with ctrl+shift+v on a PC... probably something similar
on a mac). I don't know if it will help you with the weird size
discrepancies, but at least you won't have to input your data by hand...​

I wrote about this a while back, but I was unable to find the two files with differing size text. I just found them. They are both freesans 10 point, there are no embedded fonts per the properties selection, I found no differences except for the text size. The only thing I can think of, is, some files may have been opened with freesans/10, while others were opened the the Microsoft mermaid font (arial), and then changed.

Thoughts?

John

oh yes: ubuntu 14.04, LO 4.2.4.2

Hi :slight_smile:
How about selecting the misbehaving text doing going up to the "Format"
menu to do "Remove direct formatting"? Then maybe apply styles.

I dunno why it mis-reports what the font really is. I've had that problem
with text pasted from various weird places such as from MS Office documents
and in each case it seems likely there is some hidden coding making things
go wrong like that.
Regards from
Tom :slight_smile: