Vancouver Airport to Westin Hotel Travel Info
Hi: I did some investigation on getting from the Vancouver Airport to the Hotel, thinking most of us need to do this, hence sharing my results in this E-Mail. Airporter Bus company runs a shuttle from YVR Airport to the hotels, $12CAD/1way, $18CAD/RT, Route 1 goes to the Westin (Marriott and Renaissance also, but you should double check). Please see http://www.yvrairporter.com/. This takes about 40 minutes YVR -> Westin. Vancouver Public Transportation costs $2.25CAD/1way in the weekend ($3.25 weekdays). Public buses requires 2 transfers for the Westin (1 transfer for Marriott and Renaissance). There is a routing tool (a public transport network device) that gives you the details at: http://www.translink.bc.ca/ under the "Trip Planning" tab on the top. This takes about 45-60 minutes YVR -> Westin. And there are more info from the Transportation links off of the Vancouver Airport web site: http://www.yvr.ca/ Vancouver Weather Info: http://www.intellicast.com/Local/IntlLocalStd.asp?loc=cyvr&seg=LocalWeather&prodgrp=Forecast&product=Forecast&prodnav=none&pid=none See you in Vancouver -- Kwok Ho Chan -- ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Faux Pas -- web publication in proprietary formats at ietf.org
As of Wed Nov 2 22:47:14 PST 2005 the "Restaurant Guide" in http://www.ietf.org/meetings/IETF-64.html points to http://www.ietf.org/meetings/Restaurant_Guide_Map.ppt This information is provided in Microsoft PowerPoint, a vendor-specific proprietary format. This is the only format in which this information is available on the IETF website. It is wildly inappropriate for IETF to be using a proprietary format on its web page. For years we have been fighting this. Attached below is the form letter that I send back each time I receive a Microsoft Word document. The same concept applies to Microsoft's PowerPoint. This is particularly bad for an entity that claims to be a standards organization. Fix it quick. ---Subject: I Prefer Not to Receive Informaton in Proprietary Formats This is an automatic message: You sent the document in Microsoft Word format, a secret proprietary format, so it is hard for me to read. If you send me plain text, HTML, or PDF, then I will read it. Please recognize that this note is not about what you may have wished to communicate in that document. You have made the implicit assumption that I would be able to easily read the document in that format. That assumption is a mistake. Distributing documents in Word format is bad for you and for others. Receiving Word attachments is bad for you because they can carry viruses (see http://www.viruslist.com/eng/viruslist.html?id=7). Sending Word attachments is bad for you, because a Word document normally includes hidden information about the author, enabling those in the know to pry into the author's activities (maybe yours). Text that you think you deleted may still be embarrassingly present. See http://news.bbc.co.uk/2/hi/technology/3154479.stm for more info. But above all, sending people Word documents puts pressure on them to use Microsoft software and helps to deny them any other choice. In effect, you become a buttress of the Microsoft monopoly. This pressure is a major obstacle to the broader adoption of free software. Would you please reconsider the use of Word format for communication with other people? To convert the file to HTML using Word is simple. Open the document, click on File, then Save As, and in the Save As Type strip box at the bottom of the box, choose HTML Document or Web Page. Then choose Save. You can then attach the new HTML document instead of your Word document. Note that Word changes in inconsistent ways--if you see slightly different menu item names, please try them. To convert to plain text is almost the same--instead of HTML Document, choose Text Only or Text Document as the Save As Type. Your computer may also have a program to convert to pdf format. Select File => Print. Scroll through available printers and select the pdf converter. Click on the Print button and enter a name for the pdf file when requested. Regards, ...Mohsen http://www.neda.com PS: For further reasons why .doc should not be the format of choice when exchanging information electronically, I invite you to read http://www.gnu.org/philosophy/no-word-attachments.html It may be long, but it certainly exposes the compromises both you, as the sender, and I, as the receiver, are making by exchanging Microsoft Word documents. ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Re: Faux Pas -- web publication in proprietary formats at ietf.org
Mohsen Next time, don't mince your words. Be bold and say what you mean. Take a stand and voice an opinion, why don't you sheesh! At 07:16 PM 11/3/2005 -0800, [EMAIL PROTECTED] wrote: As of Wed Nov 2 22:47:14 PST 2005 the "Restaurant Guide" in http://www.ietf.org/meetings/IETF-64.html points to http://www.ietf.org/meetings/Restaurant_Guide_Map.ppt This information is provided in Microsoft PowerPoint, a vendor-specific proprietary format. This is the only format in which this information is available on the IETF website. It is wildly inappropriate for IETF to be using a proprietary format on its web page. For years we have been fighting this. Attached below is the form letter that I send back each time I receive a Microsoft Word document. The same concept applies to Microsoft's PowerPoint. This is particularly bad for an entity that claims to be a standards organization. Fix it quick. ---Subject: I Prefer Not to Receive Informaton in Proprietary Formats This is an automatic message: You sent the document in Microsoft Word format, a secret proprietary format, so it is hard for me to read. If you send me plain text, HTML, or PDF, then I will read it. Please recognize that this note is not about what you may have wished to communicate in that document. You have made the implicit assumption that I would be able to easily read the document in that format. That assumption is a mistake. Distributing documents in Word format is bad for you and for others. Receiving Word attachments is bad for you because they can carry viruses (see http://www.viruslist.com/eng/viruslist.html?id=7). Sending Word attachments is bad for you, because a Word document normally includes hidden information about the author, enabling those in the know to pry into the author's activities (maybe yours). Text that you think you deleted may still be embarrassingly present. See http://news.bbc.co.uk/2/hi/technology/3154479.stm for more info. But above all, sending people Word documents puts pressure on them to use Microsoft software and helps to deny them any other choice. In effect, you become a buttress of the Microsoft monopoly. This pressure is a major obstacle to the broader adoption of free software. Would you please reconsider the use of Word format for communication with other people? To convert the file to HTML using Word is simple. Open the document, click on File, then Save As, and in the Save As Type strip box at the bottom of the box, choose HTML Document or Web Page. Then choose Save. You can then attach the new HTML document instead of your Word document. Note that Word changes in inconsistent ways--if you see slightly different menu item names, please try them. To convert to plain text is almost the same--instead of HTML Document, choose Text Only or Text Document as the Save As Type. Your computer may also have a program to convert to pdf format. Select File => Print. Scroll through available printers and select the pdf converter. Click on the Print button and enter a name for the pdf file when requested. Regards, ...Mohsen http://www.neda.com PS: For further reasons why .doc should not be the format of choice when exchanging information electronically, I invite you to read http://www.gnu.org/philosophy/no-word-attachments.html It may be long, but it certainly exposes the compromises both you, as the sender, and I, as the receiver, are making by exchanging Microsoft Word documents. ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Re: Faux Pas -- web publication in proprietary formats at ietf.org
Hello, [EMAIL PROTECTED] wrote: > As of > Wed Nov 2 22:47:14 PST 2005 > the "Restaurant Guide" in > http://www.ietf.org/meetings/IETF-64.html > points to > http://www.ietf.org/meetings/Restaurant_Guide_Map.ppt > > This information is provided in Microsoft > PowerPoint, a vendor-specific proprietary format. > This is the only format in which this information > is available on the IETF website. > > It is wildly inappropriate for IETF to be using a > proprietary format on its web page. > > For years we have been fighting this. Attached > below is the form letter that I send back each > time I receive a Microsoft Word document. The same > concept applies to Microsoft's PowerPoint. > > This is particularly bad for an entity that claims > to be a standards organization. Fix it quick. > ---Subject: I Prefer Not to Receive Informaton in Proprietary Formats > > This is an automatic message: > > You sent the document in Microsoft Word format, a secret > proprietary format, so it is hard for me to read. If you > send me plain text, HTML, or PDF, then I will read it. PDF is *very* vendor-specific and proprietary. Who sets the standards for PDF? I remember there used to be discussions here if the RFC's should be published in PDF also. It's always rejected of course, even if PDF is probably the best standard you can get for a formated document (better than postscript that it was derrived from). So you may want to ask people for Postscript there if you are really that centric about open standards. :-) > Please recognize that this note is not about what you > may have wished to communicate in that document. You > have made the implicit assumption that I would be able > to easily read the document in that format. That > assumption is a mistake. > [..] blah blah [..] > But above all, sending people Word documents puts > pressure on them to use Microsoft software and helps to > deny them any other choice. In effect, you become a > buttress of the Microsoft monopoly. This pressure is a > major obstacle to the broader adoption of free > software. Would you please reconsider the use of Word > format for communication with other people? I think you are just against Microsoft formats, thats all. You don't really care about using other proprietary formats or not. But that doesn't concern this issue, so why you add this? Concerning this "Restaurant_Guide_Map.ppt", I agree it really should be in HTML (its not even a Presentation but just one page with one picture). The use of standards in this world is shyzophrene, I used to be against HTML emails too, but I got used to it and consider it very practical to mark words in diffrent colors in long replies. But I imagine if I send a html mail to this list I will get flamed (depends on the list police of html email though). I wonder actually, given that HTML is a open standard, if all the ID's, RFC, Std's couldn't be spiced up a little with some bold tags and colors :-) One side effect of open standards is of course that they change all time cause developpers like to play with them... and it becomes messy (like the Web). Best Regards, Thomas ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Streaming efforts for IETF64 redux
Folks, The IETF 64 audio-streaming webpage is available here: http://videolab.uoregon.edu/events/ietf/ The detailed schedule is now available. It is still subject to change. Streaming Begins at 0800 PST (UTC/GMT -7) Monday November 7th. I would invite any feedback or suggestions be sent to myself, or [EMAIL PROTECTED] Some notes for attendees to the IETF meeting. It is our intention to again run a local streaming server to provide attendees access to meetings they aren't presently in. All 8 parallel rooms are being recorded. Using the provided microphones will vastly assist the remote participants follow the working group meetings, and increase the utility of recordings. regards joelja -- -- Joel Jaeggli Unix Consulting [EMAIL PROTECTED] GPG Key Fingerprint: 5C6E 0104 BAF0 40B0 5BD3 C38B F000 35AB B67F 56B2 ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
