Comment 1:

I suggest to use any other mechanism (template func, feeding a plain func result) to
resolve this. Making the template package support/be aware of one specific language
conventions is IMO not a good approach.

Comment 2 by krolaw:

Actually, this request has nothing to do with the templates package.  It's the time
package's Format function (.Date is a time.Time object).  I used the template example as
that was how I was calling it.
Perhaps I should have gone with:
fmt.Println(time.Date(2014,6,10,0,0,0,0,time.Local).Format("Monday 2nd January 2006"))
In terms of language conventions, the package does support days of the week, etc.

Comment 3:

This kind of thing varies widely by language.  The right place to support it in Go will
be in the go.text packages.  We don't want to try to cover every language in the time
package, and we don't want to just support one language there either.

Labels changed: added repo-text, release-none.

This kind of thing varies widely by language. The right place to support it in Go will
be in the go.text packages. We don't want to try to cover every language in the time
package, and we don't want to just support one language there either.

The time package's format functionality is already completely tied to English (see all the hardcoded English in nextStdChunk(): https://github.com/golang/go/blob/master/src/time/format.go#L120). This would be a useful addition without making the localisation situation any worse.
Are you saying a change which implements this in the time package wouldn't be welcome?

CL https://golang.org/cl/16010 mentions this issue.

Yes, I think this change would not be welcome in the standard time package. Sorry.

@usedbytes Maybe file a follow-up proposal issue for the change on the time package.
I would like to see some more discussion why or why not to add in order to achieve consensus for the problem. Only my opinion.