Correct me if I'm wrong, but the second image on this page is not portraying Sognefjorden, but the equally famous Geirangerfjorden some 100 km further north. There are images on http://www.norphoto.com/r/nor29.php, in particular no. 4127 is almost identical to this one.

Yes, that certainly looks like Geirangerfjord, so I removed the picture. Worldtraveller 12:55, 8 Jan 2005 (UTC)

Name of the article

edit

It's been moved to Sogne fjord from Sognefjorden. I wonder why? Searching on google.no for norwegian language results gives 10,000 for Sognefjorden and only 22 for Sogna fjord. English language results are not quite as one-sided but still give strong preference to Sognefjorden, so I'd suggest it should be moved back. I will do so in a few days time unless there are strong objections. Worldtraveller 12:55, 8 Jan 2005 (UTC)

OK, I got confused. Looks like in fact a duplicate article was created at Sogne fjord. I'll replace it with a redirect to the still-existing Sognefjorden article. Worldtraveller 13:45, 8 Jan 2005 (UTC)
This is a result of software bug in wiki. I've heard that they upgraded the system recently, so no big wonder. The history is the following. There is an article that lists all titles from Encyclopedia Britannica. It particular, it contained a red link from "Sogne Fjord". So I decided to create redirects from this one and from "Sogne fjord". Also Sogn og Fjordane didn't link to Sognefjorden. I added it. But when I tried to make redirects, the articles remained empty. Think "bug".
Being a smart-ass, I remembered that when you move a page, this auomatically creates a redirect. So I decided to move "Sognefjorden" to "Sogne fjord" and then back, hoping a new article (redirect) will appear. You see the result. Also, if you look at "what links here" from Sognefjorden, you see nothing, while I know at least 6 aricles that link there. But when I did my moves, at some moment the list of these backlinks contained like 5 articles with title "Sogne Fjord" and 4 ones titled "Sogne fjord"! (I tried to create them several times.) There were several other weird thins with redirects and article histories.
Go figure. I hope at the moment you read this, the problems will be gone. Mikkalai 16:29, 8 Jan 2005 (UTC)
Aha, I thought it might be something to do with software problems. I'd noticed the weird thing with 'what links here' not returning any results, that still seems to be the case unfortunately. Very strange, let's hope it works itself out soon. Worldtraveller 09:40, 9 Jan 2005 (UTC)
What's even weirder, even though it is now only a redirect, Sogne fjord is listed in the Geography stubs category (there is no template on the Sogne fjord page! I'm posting to the village pump to see what's going on here. Grutness|hello?   11:11, 16 Jan 2005 (UTC)

Just an FYI but Sognefjorden translates into English as "the Sogne fjord". Sognefjord is the actual name of the fjord in Norway. The "en" on the end add the word "the" to the title. So I think English speakers have redirected it to The Sogne Fjord because of the difference between Norwegian conjugation of words and how English works. — Preceding unsigned comment added by 166.129.240.22 (talk) 23:38, 10 September 2011 (UTC)Reply

You've got my number

edit

The article says the fjord extends 203km inland; I've seen 204.4. Anybody able to clear it up? Trekphiler 20:29, 12 October 2006 (UTC)Reply

Norwegian encyclopedias list 205, (Store Norske Leksikon and Caplex). I'll changed it. --Dittaeva (talk) 20:41, 11 June 2008 (UTC)Reply

PD photo

edit

New PD photo here. Badagnani (talk) 22:51, 10 January 2009 (UTC)Reply


Sognafjord contains more water than Tana and Glåma combined. — Preceding unsigned comment added by 46.147.176.221 (talk) 12:08, 19 August 2015 (UTC)Reply

A Commons file used on this page or its Wikidata item has been nominated for deletion

edit

The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for deletion:

Participate in the deletion discussion at the nomination page. —Community Tech bot (talk) 14:35, 23 January 2023 (UTC)Reply