2000 Lexus Rx300 Awd~only 92k Miles~peral W/tan Leather~dealer Serviced on 2040-cars

Auto blog

Ever wonder how to really pronounce Japanese automaker names?

People tend to get very set in their ways when it comes to the pronunciation of words. Just look at the endless debates over whether or not to say the final 'e' in Porsche (which you should in terms of correct German enunciation). Or the argument about whether to follow the British convention and give the 'u' in Jaguar a special delivery or to say the 'ua' diphthong as more of a 'w' sound, as usually happens in the US.
This short video doesn't answer either of those automotive questions, but it does allow a native Japanese speaker to demonstrate the accepted pronunciations for several, major automakers from the country. One benefit is that it clears up the occasional debate over whether Nissan should be said with a long or short 'i' sound. Also, listen closely to how the female host says Mazda as Matsuda, the way it's actually said in the language. Even if this doesn't change the way you enunciate these brands, at least now you know the accurate way in Japanese.

Lexus RC F Coupe puts on a brave face for Detroit

With less than a week to go until the 2015 Lexus RC F makes its debut at the Detroit Auto Show, Lexus has given us a sneak peek at its upcoming performance coupe. Earlier this week, Autoblog was granted were the opportunity for an intimate studio photo shoot with the RC F outside of the bright lights and big crowds sure to surround the coupe at Cobo Hall next week.
Compared to the hybrid version of the all-new RC we saw at the Tokyo Motor Show last year, the RC F has noticeably more aggressive styling. The cartoonishly oversized Lexus spindle grille gets a mesh insert pattern and is flanked by massive intakes in the lower fascia. To make room for what is expected to be a bigger V8 engine, the hood sits higher and is vented, but like many details about the RC F, Lexus is keeping the engine's size and output under wraps (although we have a sneaking suspicion it'll have 460 horsepower).
A trio of 19-inch wheel options will be available (including a set that is hand-polished), and the side sills and rear fascia have been modified for F duty. The biggest styling change on the RC F, however, is the LFA-inspired active rear wing that rises at speeds above 50 miles per hour for improved traction and stability. Carrying over cues from the current IS F, the RC F features air outlets behind the front wheel openings and angle-stacked exhaust outlets at the rear of the car.

Google shares more details on self-driving car accidents

Google has pledged to release monthly reports on the status of its self-driving car program, and says these updates will include information on accidents involving the vehicles. But the company won't release the actual accident reports, a sore point for activists who recently have clamored for the company to be more transparent in the way it tests this promising technology on public roads. "Google is dribbling out bits of information in the hope to silence legitimate calls for full transparency," said John Simpson, privacy director for Consumer Watchdog, a nonprofit that has asked Google to release reports from the 12 accidents the company says it has been involved in over the past six years. "They are testing on public roads, and the public has a right to know exactly what happened when something goes wrong." Under California law, the accident reports are not considered public records. Google has attributed all accidents to human error, and says drivers of the other cars involved caused 11 of the 12 accidents. In eight of those, the Google cars were rear-ended, and the autonomous vehicles were sideswiped in two other crashes. One of the accidents occurred at an intersection when a human driver failed to yield at a stop sign, and in one incident, a Google driver accidentally rear-ended another car while manually driving. Google had previously provided those details. The first monthly report installment sheds new light on which types of self-driving vehicles were involved, directions of travel, locations, and whether the cars were operating in autonomous or manual mode. Update: Google says this information comes directly from the OL 316 forms used to report accidents involving autonomous cars in California, though it has "edited the summaries lightly to protect other drivers' information." But Google still will not release the original OL 316 forms, nor the "traffic collision report" forms used in California to report accidents. Another company that has been involved in a single self-driving car accident, Delphi Automotive, has released this information, which verified its car was not at fault. Regarding Google, Simpson said, "We now know a few more details of what happened. The problem is that it's Google's version and they want us to take their word for it." The Google self-report adds information that goes beyond accidents, with further details on the company's overall program.