Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#2007 closed defect (wontfix)

Namefinder's format_direction should support directions like W, WNW, NW, NNW, N instead of just W, NW, N

Reported by: avarab@… Owned by: tom@…
Priority: major Milestone:
Component: website Version:
Keywords: Cc:

Description

Here's a diagram of cardinal directions:

http://upload.wikimedia.org/wikipedia/commons/1/1a/Brosen_windrose.svg

Perhaps even more accurate directions like "North by North-East" should be supported:

http://upload.wikimedia.org/wikipedia/commons/8/8e/Compass_Card.png

Change History (2)

comment:1 follow-up: Changed 9 years ago by tom@…

  • Resolution set to wontfix
  • Status changed from new to closed

Thanks for the lesson in sucking eggs.

I'm actually perfectly well aware of how to infinitely subdivide the compass rose however so I didn't really need the lesson.

What you failed to provide, which would actually have been useful is any justification for your use of the word "should" in the title of this bug. Why should it? It's just supposed to be a helpful indication of the general direction, not a precise indication of the exact bearing.

comment:2 in reply to: ↑ 1 Changed 9 years ago by avarab@…

Replying to tom@compton.nu:

Thanks for the lesson in sucking eggs.

As a non-native speaker of English I have no idea what this apparent euphemism for sucking on testicles means exactly. Could you elaborate?

I'm actually perfectly well aware of how to infinitely subdivide the compass rose however so I didn't really need the lesson.

The reason I attached compass card references was that I thought they might be useful for anyone willing to implement this. Not because I thought you, Tom Hughes, personally needed a lesson in compass subdivision.

When I file bugs against the "website" component I'm filing them against the site/rails_port source code, not against you personally. That tom@… is the assignee for the "website" component as opposed to some general bug E-Mail list isn't something I have control over.

What you failed to provide, which would actually have been useful is any justification for your use of the word "should" in the title of this bug. Why should it? It's just supposed to be a helpful indication of the general direction, not a precise indication of the exact bearing.

Why should helpful indications be restricted to the accuracy of 45 degree intervals?

The reason I think it should be done is to help localization efforts (as is the case with almost anything I commit to sites/rails_port). In some languages, such as Icelandic no name one example, directions are almost universally split at 22.5 degree intervals when referring to point orientations.

Since we're using a customizable i18n system it's quite easy for languages that don't want this much accuracy to simply not use it, e.g.:

north: North
north_north_east: North-North East
north_east: North-East
east_north_east: East-North East
east: East

Another key could then be set to indicate the amount of accuracy the language in question wanted to use, e.g.:

# Set this to 90, 45, 22.5, 11.25 depending on the accuracy you want
compass_accuracy: 45

Would this be acceptable?

Note: See TracTickets for help on using tickets.