My HTC Nexus One Car Dock broke only a few months after I got it. I searched the Internet about this, and found that I was not alone. One man suggested a way to handle it with care and I am now following his advice with my replacement dock. I am providing this video to give you a visual tutorial about how to baby your fragile car dock. Hope it works for you!
In case your car dock breaks, I recommend that you do what I did: call HTC Repair and tell them that your Nexus One Car Dock broke and you want them to send you a replacement under the one-year warranty. If they give you any trouble, tell them that you know of other people whose car docks broke and who received replacements. They should email you an RMA label. You will have to box up your broken car dock and drop it off at a FedEx with the provided shipping label. HTC Repair should receive it within a couple of days, process the replacement in a couple of days, and ship it back to you via FedEx in a couple of days; i.e., you “should” have a new one in your hands within a week.
I tried installing Typekit fonts on this blog, and I almost gave up because the complexity of it reminded me of why I moved my blogs from WordPress.org to WordPress.com. I suppose it would have been easier if Typekit had built-in support for the Twenty Ten theme, but when I tried it a couple of weeks ago, they didn’t. So I had to open one of my blog pages in Safari, select Develop from the menu (because I installed the optional developer tools), select Show Web Inspector, and study the CSS to suss out what the “selectors” were for the masthead and other sections of the pages I wanted to set the new fonts to. Even knowing CSS, it took some searching through the code to see what was styling what, since Classes and IDs are arbitrarily created by each CSS author.
Once I found the Classes and IDs, I had to go back to the Typekit editor (which always took a long time to load, as did everything else on the Typekit site) and manually enter the “selectors” I wanted to apply the fonts to. I found that I had to do it with periods in front rather than hashmarks, or maybe it was the other way around— I would have to be writing CSS on a regular basis to get it right, and who does? (If you do, then you wouldn’t find it complicated at all, but then you might as well have a WordPress.org site and not a WordPress.com site, eh?)
Reflections on my recent experience at the RID Region V conference, the benefits of the policy of using ASL at all times during the conference (except in a few of the workshops that were interpreted), and the great contribution of deaf interpreters to the field. I also discuss my experience as a workshop presenter and my thoughts on how to make my discussions of interpreting less hearing-interpreter-centric, and more inclusive of all interpreters, especially deaf interpreters.
I finally got the Froyo (Android 2.2) update pushed to my Nexus One today, and I noticed digital zoom as an option in the new Camera app. I ran an experiment by placing this ad down on the counter, and standing in the same place taking photos at 2x, 1.5x, and 1x digital zoom.
I finally got tired of the hassle and hours it took me to update my WordPress.org-powered self-hosted versions of two different blogs–danielgreene.com and smithersgreene.net. Trying to upgrade my blogs to WordPress 3.0 was the last straw.
I’m a guy who started writing his own HTML and CSS in 1996; in fact, I was one of the first handful of brave ones on the Internet to style valid HTML with CSS knowing that most browsers couldn’t handle it. After all, what did I have to lose? Little old me with his personal website.
This was a decade before Flickr and YouTube and Facebook and Twitter allowed you to post content with ease and let them take care of the code, and years before every major website was written in structural HTML and styled with CSS. This was back when you had to either have a self-hosted website or something like AOL Hometown Web pages. This was when “Web Designers” would charge you an arm-and-a-leg for a page and a couple of links. I was okay with the idea that, if I wanted a site that used proper HTML (without proprietary structural markup) and CSS, I had to get an ISP to host my own website. And I had to write all my own HTML & CSS.
Things have changed in the past few years. Even with WordPress.org, I had more freedom to blog without worrying about the coding. When I didn’t have to worry about updating WordPress and editing .htaccess pages and PHP files, it worked great. But I hated it when I would break my site when trying unsuccessfully to upload new versions of the blogging platform software. I thought, “Why can’t it be more like posting content to Facebook, Flickr, Twitter, or YouTube? I can’t break those sites. There must be an easier way.”
I recently reviewed all the fonts on my computer that had embedded descriptions, and I typeset the descriptions in their respective typefaces. The result is a demonstration of the typefaces and their history, features, and uses. To view these font descriptions in their proper typefaces you must have the fonts installed and enabled on your computer. To see the ligatures you will have to use a browser that supports them (Firefox 3.5 and later does). For the truest view, see Fonts with Descriptions (PDF). Below is the document in HTML format.
“Andale Monospaced is a highly legible monospaced font.” Regular only.
Arial: “Monotype Drawing Office 1982. A contemporary sans serif design, Arial contains more humanist characteristics than many of its predecessors and as such is more in tune with the mood of the last decades of the twentieth century. The overall treatment of curves is softer and fuller than in most industrial-style sans serif faces. Terminal strokes are cut on the diagonal which helps to give the face a less mechanical appearance. Arial is an extremely versatile family of typefaces which can be used with equal success for text setting in reports, presentations, magazines etc, and for display use in newspapers, advertising and promotions.” Regular, Italic, Bold, and Bold Italic. Contains common ligatures that are not apparent in the phrase “File systems for affluent field offices.”
Arial Black: “…display use in newspapers, advertising and promotions.” Regular only.
Before I compare websites where you can download e-books in the EPUB format, I should tell you that I just got a Sony Reader Pocket Edition (Model PRS300SC) from my husband on Valentine’s Day. I’ve spent a bit less than a week with my new e-book Reader, but I’ve crammed a lot of reading and researching into the past five days. I’m pretty well versed in typography, and I have been disappointed with the readability of some of the e-books I’ve put on the Reader. Having viewed various books on the Reader, I don’t blame the Reader; I blame the formatting of some e-books. In an effort to find more readable e-book formats, or styles, I went a-searching, and these are the results of my trials.
PDF was not designed for e-books
First off, I found that PDFs are difficult to read on the Pocket Edition. I discovered this when I went to my local library’s digital download site and downloaded four books by Nicholas Sparks — all formatted in the same way by Warner Books in PDF. The margins were huge, the font size small, and the font face’s x-heights very small. (To oversimplify, x-height is the difference in size between capital letters and lowercase letters. Fonts with small x-heights look classy, but are not readable at smaller sizes.) These books were impossible to read at the default “small” size on the Pocket Edition. Not only that; the printer’s crop marks were visible, which made the margins even bigger since what I saw on my screen included extra margins that shouldn’t be visible to the consumer.
WordPress for Android was released on February 2, and I downloaded it from the Android Market today for my Nexus One. Now I’m posting a blog entry with it. It looked like it hung just now when I tried to select Categories, but other than that, it’s pretty nifty. Oh– I just realized I just had to click the refresh button to the right of Categories and I got a list to choose from. Not bad!
I haven’t felt like writing a blog entry in a long time, but I have been updating my friends, colleagues, and the world about my life in other ways. This morning, I feel moved to recap the previous year and look forward to the next.
I continue to take photographs and share them on Flickr. Some of my recent adventures include hiking Camelback Mountain for the first time, a weekend getaway to Jerome, going to the Arizona State Fair for the first time in the five years that I’ve lived here, going “full frame” by trading in my Canon Digital Rebel XTi and EF-S lenses for a used Canon 5D, and meeting a longtime Flickr friend from Brooklyn who visited me and my husband with his husband. It was great to bring the online life and real life together, and we all really hit it off. There are several other photo sets I’ve posted in months since my last blog post as well. The best way to keep up with what I’m up to in a visual way is to follow my Flickr photostream.
I’ve also really gotten into Facebook this year. I don’t add people I don’t know as Friends, and I don’t have a Fan Page, but I do enjoy keeping up with my friends through status updates, photos, videos, links, etc. I am sort of the designated photographer at gatherings of friends and coworkers, so it’s always fun to upload an album from a shared event and tag everyone in it who’s on Facebook– which is most of them. For a while there, I was spending a couple/three hours a day on Facebook, but I’ve cut back because I have so many other priorities. I felt I was neglecting my photography and Flickr social circle for a while there, so I’ve returned to spending a bit more time on that. One thing I love that Flickr added in the last couple of months is People in Photos, which allows you to tag your Flickr friends in photos the way you can tag your friends in photos on Facebook. Those friends have to be Flickr members in order to be tagged, so it’s most useful for photos from FlickrMeets; that is, when a group of photo geeks get together to go on a shooting spree. Not necessarily good for your neighbor’s family’s Thanksgiving party unless they’re all Flickrites themselves. Thanks to this new feature and my general hamminess, I can now point you to photos of me on Flickr. As of this writing, there are over 900, though I’m not sure they are all public!
I was honored that a participant in my Vague Language (VL) workshop for ASL interpreters was moved to write this review for our local chapter of the Registry of Interpreters for the Deaf (Arizona RID). The writer wishes to remain anonymous, but I found out who they are and got their permission to publish their review on my website. I assure you that this review was entirely unsolicited and is reprinted here in the writer’s original words. Here it is!
Hi everyone. I was able to attend the workshop this past Saturday by Daniel Greene entitled, “Just What They Said: Retaining Ambiguity When Interpreting Vague Language.” This was an excellent workshop for a number of reasons and I’m thrilled that Daniel has taken it up to present this topic because it is one thing I know I have struggled with and it hasn’t been addressed enough in regards to the work we do as interpreters. There was so much that I learned.
It was all about vague language of course which has really been brought to light, I think, by video relay interpreting but certainly applies to the work we do in education. It is a fairly new topic in linguistic studies too. It is the concept that people do use vague and unspecific language in their everyday interactions and often it is for a purpose that they are being vague. This brings up the question, do we as interpreters then clean it up and make it clear, do we interrupt the conversation to get clarification, or do we just render the message as vague as it was given? Keep in mind it might be the person’s goal to be vague.
For example: a teenager might wish to cover up the truth to avoid getting in trouble; a teacher might wish to protect a student’s feeling when giving feedback about work; a person might just be trying to be polite in their use of words; a doctor might wish to be less direct about a person’s life expectancy; a counselor might purposely need to ask an open ended question without leading the client with examples. How much of this can and should an interpreter try to clarify?
