Opened 9 years ago

Closed 6 years ago

#2494 closed defect (wontfix)

missing space in ui (zoom scale)

Reported by: Schusch Owned by: richard@…
Priority: minor Milestone:
Component: potlatch (flash editor) Version:
Keywords: Cc:

Description

it would be great to have a space between the number and the symbol ("517 m" and not "517m") in the scale in the lower left corner - the space is international standard (see http://en.wikipedia.org/wiki/International_System_of_Units for example with links to BIPM brochure etc.) (missing in potlatch 1.3 today)

Change History (11)

comment:1 Changed 9 years ago by Tom Hughes

Perhaps if you enlightened me as to which piece of software you were referring to then I might be able to do something with this bug.

You mention potlatch, but that doesn't have a scale in the lower left corner (or anywhere else) and neither does the web site.

comment:2 Changed 9 years ago by Schusch

Priority: majorminor

well - the editor of potlatch shows a (new?) scale on the left side beneath the editor window (only after a first edit) ... that scale has a distance under it like "33m (z12)" ... it should be "33 m" according to SI and I would prefer "Z 12" (but the latter is my personal opinion - spaces have their well defined reason in typography - they are for better readability)

(that's of course not a major defect - reducing it to minor)

comment:3 Changed 9 years ago by Tom Hughes

Component: adminpotlatch (flash editor)
Owner: changed from Tom Hughes to richard@…

Over to you Richard.

comment:4 Changed 9 years ago by Richard

Blimey.

I'm used to people criticising my programming style but this is a new one, especially considering my real proper job is actually not programming but, well, editing. Still, what do I know.

comment:5 in reply to:  4 Changed 9 years ago by Schusch

hm, sorry--my english is not good enough to exactly understand, what you mean ... but I hope the SI and typography (at least in times before computers and programs like MS-Word existed) are at least small arguments ... greetings and thanks for the good work :-)

comment:6 Changed 9 years ago by Richard

What I mean is that I work as a magazine editor; that's my profession. Stuff like this is my bread and butter.

I disagree absolutely that the SI has the right to tell anyone how to write units. Common usage is much more important than arbitrary 'rules', and if a missing space is good enough for the BBC (to take one example) it's good enough for me.

By analogy, the well-known UK newspaper, the Sunday Times, thinks that it is called The Sunday Times. That's their right, but I don't accede to their whims of capitalising the definite article. Similarly, I don't call British Midland's lowcost airline 'bmibaby'; it's a proper noun, so it should be capitalised.

So I don't see why I should accede to the SI's whims on spacing - particularly given that their guidelines also appear to insist that the units should never be italicised or emboldened, which is clearly bollocks.

comment:7 in reply to:  6 Changed 9 years ago by Schusch

no typographic argument up to now from you ... any rule beside the ones set up by google and ms-word? This is not a question of your personal opinion--if it is your daily bread and butter I'm really wondering you never heard of the space, because it is usual in technical writings.

ok, here my comment from #2495 ...

there is no reason for the lack of typgraphy here

The SI only specifies something which is usual for typography (before the times of MS-Word etc.). The space is for better readability, just take a look in books which are older than the word processor computer applications - it's not my illusion but a well known rule of typography.

Well and about the "downside" of the possible linebreak:

Without the space we have always a wrong typography, with the space only when the line is broken in the wrong place (which easily could be handled with a non breakable space).

and by the way, the rule that units should never be italicised or emboldened has a well defined reason--to differentiate unit symbol and the number - which should be considered in technical papers (whichs maps are ...). The typography is sometimes the only way to differentiate between a symbol of unit and variable.

comment:8 Changed 9 years ago by Richard

Er no, maps are not technical papers, they're maps.

Why on earth you keep mentioning MS Word I have no idea, given that I don't use it and never have done. I might have a bit of respect for your "I know about typography before 1995 argument and you evidently don't" argument... were it not for my degree which is partly in the paleography of the early Medieval period.

comment:9 Changed 9 years ago by Richard

To clarify... I'm not actually that fussed about the space or not. If you want to code and compile the change I won't object to it.

But I do object to you claiming that there is one true orthography. Maybe your language works like that but English doesn't.

comment:10 Changed 9 years ago by Schusch

ok :-) I didn't want to relate you to M$-Word. What I mean with that M$-Word (not the best but a well known wysiwyg program) argument is, that since the time that everybody is able to do the "typography" of a book or so, the lack of the space between number and unit seems to be exploding ... that's all. I don't know if I know typography better than you but I don't think so. It's your job as you say - mine is of technical nature. But I'm interested in that small detail (because it makes texts less readable) - and what I found out (but that's of course not a scientific research) is that in older books there are mostly spaces. That seems to change since the uprising of wysiwyg programs for everybody. Also in english books.

So - I like (better) readable text - that's all - maybe I'm becoming old ;-)

I don't know how to code it - otherwise I would have added a patch ... but up to now there was nearly always somebode who changed this small space thing ... maybe I've to get a bit older until then :-)

comment:11 Changed 6 years ago by iandees

Resolution: wontfix
Status: newclosed

Cleaning aging tickets.

Note: See TracTickets for help on using tickets.