Feature Request: time format for day "2nd"
Erik Unger
generate:
1st
2nd
3rd
4th
5th
....
Jan Mercl
David Symonds
I'm sure English would be sufficient, given the weekday and month
names are only in English.
It's pretty easy to write it yourself. Something like this:
// only works for 1-31.
func ordinal(x int) string {
suffix := "th"
switch x {
case 1, 21, 31: suffix = "st"
case 2, 22: suffix = "nd"
case 3, 23: suffix = "rd"
}
return strconv.Itoa(x) + suffix
}
Dave.
Dmytro Shteflyuk
On Tuesday, 14 February, 2012 at 7:37 AM, David Symonds wrote:
It's pretty easy to write it yourself. Something like this:// only works for 1-31.func ordinal(x int) string {suffix := "th"switch x {case 1, 21, 31: suffix = "st"case 2, 22: suffix = "nd"case 3, 23: suffix = "rd"}return strconv.Itoa(x) + suffix}
Kyle Lemons
// only works for 1-31.func ordinal(x int) string {suffix := "th"switch x {case 1, 21, 31: suffix = "st"case 2, 22: suffix = "nd"case 3, 23: suffix = "rd"}return strconv.Itoa(x) + suffix}
Kyle Lemons
12nd?
Dmytro Shteflyuk
Dustin
Dmytro Shteflyuk
Dustin
On Tuesday, February 14, 2012 12:49:57 PM UTC-8, Dmytro Shteflyuk wrote:
Of course no, go ahead.
Guillaume Lescure
I'm sure English would be sufficient, given the weekday and month
names are only in English.
It's pretty easy to write it yourself. Something like this:
// only works for 1-31.
func ordinal(x int) string {
suffix := "th"
switch x {
case 1, 21, 31: suffix = "st"
case 2, 22: suffix = "nd"
case 3, 23: suffix = "rd"
}
return strconv.Itoa(x) + suffix
}
Dave.
In my point of view , begin with english is obviously a pretty good choice but stay stuck on only one language is a terrible mistake.
Dustin
On Tuesday, February 14, 2012 2:29:18 PM UTC-8, Guillaume Lescure wrote:
I'm not so sure of that ... Go is the first UTF8-based language.
In my point of view , begin with english is obviously a pretty good choice but stay stuck on only one language is a terrible mistake.So no 1st, 2nd, 3rd, etc ... is not sufficient for everyone because names are not only in English. But that's a good start ...
David Symonds
<guil.l...@gmail.com> wrote:
> So no 1st, 2nd, 3rd, etc ... is not sufficient for everyone because names
> are not only in English. But that's a good start ...
You missed my point. If you're trying to use this with the "time"
package in the standard library then you're already being stuck with
English names for weekdays and months, so just doing English ordinals
isn't making the situation worse.
Dave.
Rémy Oudompheng
> I'm not so sure of that ... Go is the first UTF8-based language. That means
> it can be used by everyone with almost every characters. A chinese guy can
> use their own symbols to write code. And that's a so cool feature because
> that shows Go is opening up to the whole world. ASCII was enought for the
> beginning but now people have to considere that english is not the only
> spoken language. Everyone don't want to speak english and Go lets that
> choice :)
Haskell supports Unicode too.
main = do
let ωmega = 3
print ωmega
is valid, whereas
main = do
let Ωmega = 3
print Ωmega
is not (variables/functions are lowercase, type names are uppercase).uppercase.
Rémy.
Guillaume Lescure
Le mardi 14 février 2012 17:32:58 UTC-5, Dustin a écrit :
On Tuesday, February 14, 2012 2:29:18 PM UTC-8, Guillaume Lescure wrote:I'm not so sure of that ... Go is the first UTF8-based language.I don't believe this to be true.
In my point of view , begin with english is obviously a pretty good choice but stay stuck on only one language is a terrible mistake.So no 1st, 2nd, 3rd, etc ... is not sufficient for everyone because names are not only in English. But that's a good start ...I'd welcome an internationalization effort of github.com/dustin/go-humanize. :)
Guillaume Lescure
Haskell supports Unicode too.
main = do
let ωmega = 3
print ωmegais valid, whereas
main = do
let Ωmega = 3
print Ωmegais not (variables/functions are lowercase, type names are uppercase).uppercase.
Rémy.
Guillaume Lescure
You missed my point. If you're trying to use this with the "time"
package in the standard library then you're already being stuck with
English names for weekdays and months, so just doing English ordinals
isn't making the situation worse.
Dave.
For exemple, C/C++ are ASCII-based languages so it's impossible to be multilingual. For that, you have to use, for exemple, Qt to translate and produce a UTF8 string. I think with Go, we can do that in the standard librairies themselft.
I repeat, it's not that for now, but I truly think that where we should lead to.