A while back, I adopted the Firefox (technically, the Mozilla) versioning system. Namely three integers, separated by dots (1.2.3).
They will use four, to include a build number, but I don't think that I will. This is used specifically in the auto-update feature, so the Bloglines Toolkit, at least, needed to support it. And since we all know that I'm so anal about those things, I couldn't have the toolkit supporting it while the other software didn't.
Is it only in the US that we can't deal with the words small, medium and large? Or, to be more specific, that we can't deal with the words small and medium? We have to start at large and work our way up - tall, grande, venti or large, extra large and super-duper large. They mean the same thing - you've got three sizes, one of them is the smallest. One is the largest. The other one is in the middle. Why is it that we care what word is used? Are we really so dense that we believe that ordering a large off of a menu where large is the smallest size makes any difference over ordering a small of the same actual capacity?
More to the point, I don't really mind what you want to call your sizes. Call them Larry, Curly and Moe for all I care. But the simple fact is, one is the smallest and one is the largest. If I order a "small", don't look at me like I'm a moron and say "we don't have a small, sir". You have at least one. Perhaps another, that's no one's business but your own. Get over it and fill my order.
So while we're arguing about having a small size (or not), other people around the world have developed a language where they can communicate great distances - up to 6 miles (10 kilometers) - by whistling! Now these aren't new languages by any means, so try to stick with me. What I'm getting at is that if those people had been hung up on what to call the distance they were able to whistle, they'd never have accomplished anything...
Goat herder Doug: "I can't whistle more than 3 miles if I don't try very hard. That's easily my smallest whistle. I know what I'll do - instead of calling that my "short" whistle, I'll give it another name. Hmm... "medium"? Still not big enough, but if I call it "large", how will I let people know what I mean when I use my longer whistles? What am I going to do? I just can't call that my "small" whistle. Guess I'll just send a carrier goat. I know, I'll send Barney, the short-haul carrier. He can make it the 3 miles. But then they'll think that I don't measure up, because he's my short-haul goat. Maybe I'll call him my medium-haul goat. No, that's not going to do either. I'll just have some goat beer and forget about this mess."
Can't we just call a small a small?
I'm not exactly certain of who did this translation, or even if it is correct, but I have found a translation of the Bloglines Toolkit into Japanese, courtesy of someone named Norah.
I received a comment from her a while back that someone had done it, but I asked if they could let me know some more info and I'd pack it up in to the main distribution, but I never heard anything from them. So I decided to go looking.
The site above had a link to a downloadable version, so I figured i'd check it out. Sure enough, it had the Japanese translation (jp-JP) contained within. So I repacked it into my distribution archive, and now the toolkit is delivered in three languages. Woo-hoo!
Happy to distribute more if there is any interest. I don't have the know-how to do the translations, however. If you'd like to localize the toolkit into your language - or even a language you happen to know and would like to assist with - please let me know that you're interested and I'll get you hooked up with everything you need. There are only a dozen or so lines that need translating, and I'll show you just where they are. Thanks!
I understand the need for object permissions. I really do. But man can they be a pain. Apparently at some point in the recent past, I managed to assign Everyone (a special Microsoft group, meaning, well, everyone) deny permission to an access list in Exchange. To make it worse, it was the Default Global Access List. What makes that so bad are two things.
One: I'm in this list, as is every other user. If they can't be found in that list, then they are unable to make an Exchange (RPC) connection to the server. You get a terribly useful message: The action could not be completed. The bookmark is not valid. What do bookmarks have to do with anything? I have no idea.
So now that I resolved the issue about the bookmark not being valid, I made may way carefully (and rather suddenly) to the next error: "The name could not be matched to a name in the address list". I swear there are days that I wish I had never even heard the name of Microsoft. Regardless, I have, so off I went again. This search was rather quick.
I had a pretty hefty spreadsheet of contacts that I wanted to post into Outlook. The problem is that the phone numbers were stored in Excel as numbers and Outlook doesn't like importing numbers into that field. Not sure what the folks at Microsoft expected, perhaps they are still living in the days when people used letters for the first digits of the phone number.
In any case, I needed to switch those number fields to text fields. And it was a royal pain to do it manually. So I came up with this little macro that did the trick.
