View Bug Activity | Format For Printing
I'm attaching a diff of some minor changes to the mk_MK locale. The summary of the changes follows: - Update my email address since the old has not been used and is probably unfunctional. - Change contact address to bug-glibc-locales@gnu.org (a new alias for the libc-locales mailing list). [BZ #337] - Update date_fmt, I haven't noticed it was added to the locale, and it was incorrect. - Add first_weekday and first_workday in LC_TIME (Monday here). - Add "week 7;19971201;4" in LC_TIME, I have no idea what that is for.
Created an attachment (id=1113) Patch for the mk_MK locale data
Before the patch is applied, I have doubts about "first_weekday", "first_workday" and it's corelation to "week" in LC_TIME. Monday should be the first day here, so what are the correct values? What's the most up-to-date locale that I can consult?
One more thing, I see the glibc locales can now be encoded in UTF-8 and not in the ugly <U0xxx> encoding. Should I convert the mk_MK locale to utf? UTF-8 would be easier for debuging and future generations.
Read http://std.dkuug.dk/jtc1/SC22/WG20/docs/n690.pdf to learn about the week definition.
So, if I set weekday to 19971201 (a Monday) I should also change day and abday to start from Monday - right? And in that case first_weekday and first_workday should be 1 (also Moday)? I also don't understand the meaning of the third operand in weekday but I guess it ok like it is. (the text ISO/IEC PDTR 14652:1999(E)) ------------------------------------------------------------- weekday: Shall be used to define the number of days in a week, and which weekday is the first weekday (the first weekday has the value 1), and which week is to be considered the first in a year. The first operand is an integer specifying the number of days in the week. The second operand is an integer specifying the Gregorian date in the format YYYYMMDD. The third operand is an integer specifying the weekday number to be contained in the first week of the year. If the keyword is not specified the values are taken as 7, 19971130 (a Sunday), and 7 (Saturday), respectively. ISO 8601 conforming applications should use the values 7, 19971201 (a Monday), and 4 (Thursday), respectively. This keyword is optional.
(From update of attachment 1113) I'll be preparing a new patch...
I was reading http://std.dkuug.dk/jtc1/SC22/WG20/docs/n690.pdf but I got confused... The documentation about *abday* seems to suggest that the fist day of the week is considered according the *week* keyword. So if *week* is setup to start with a Monday, abday should also start with a Monday. The practise shows different though (in glibc 2.4). I guess I'm reading too much in the PDF.
Created an attachment (id=1280) latest mk_MK locale I've updated the locale with the correct changes, and I've converted it to UTF-8. Because of the conversion the diff is bigger than the whole file, so I'm sending the whole locale (gzip-ed to protect it from accidental mangling).
Have you even looked at any other locale? All strings must use the <U....> format for each character. No UTF-8 encoded strings. And next time when you reply, change the status away from WAITING.
> Have you even looked at any other locale? All strings must use the <U....> > format for each character. No UTF-8 encoded strings. Sorry, I don't know where I got the idea... I guess I've found that it works and thought it's ok. > And next time when you reply, change the status away from WAITING. I don't understand, should I change the status to NEW?
Created an attachment (id=1293) Patch for the mk_MK locale data Here's the latest patch for mk_MK. Corrected my mistakes in the first patch, and reverted back to <U....> escaped Unicode representation.
Patch applied in cvs.