hancock4@bbs.cpcn.com wrote:   
   > In the old days, a standard convention in timetables was that a.m.   
   > times were in light face, while p.m. train times were in bold face.   
      
   When this came up back in 2008, I had a then-recent copy of Amtrak's   
   Pacific Surfliner timetable.  It used 12-hour times with a suffix 'a' or   
   'p', and the PM times were also in bold face.  The bold face was used   
   throughout the timetable for both trains and buses, and the "light for   
   AM, bold for PM" was noted in the key/legend.  Examples in HTML markup:   
      
   11:26a   
   11:36a   
   12:15p   
   12:30p   
      
   Some newer examples near me:   
      
   Looking at the PDF version of the current Amtrak timetable for their   
   Missouri and Illinois services, it uses pretty much the same   
   conventions (A and P, PM bold), except that the A and P are upper case.   
   http://www.amtrak.com/ccurl/666/370/Illinois-Missouri-Schedule-060914.pdf   
      
   MetroLink in St. Louis uses A and P, but doesn't put the PM times in   
   boldface.  Their Web site offers a document called a "schedule" for   
   each station, but this document calls itself a "stop card".  These use   
   different colors to distinguish which train a line is on, and a suffix   
   letter to note trains that stop short of the final station on that line   
   (I think).   
   http://www.metrostlouis.org/PlanYourTrip/MetroLinkPDFSchedules.aspx   
      
   MetroLink's main schedule doesn't put an A or P with each stop time;   
   there are section headings for "AM Service" and "PM Service".  The   
   times are in red or blue, depending on which line they are for.   
   http://www.metrostlouis.org/Libraries/System_Map_PDFs/MLWeekday112612.pdf   
      
   DART rail in Dallas uses A and P, but doesn't put the PM times in   
   boldface.   
   http://www.dart.org/schedules/schedules.asp   
      
   I wonder if perhaps there is sort of a "cultural" split here between   
   long-distance rail (PM bold) and metro services (PM indicated some   
   other way).   
      
   Personally I think using a 24-hour clock would be a better idea, but I   
   realize that's a much bigger change in the world than just printing some   
   new train schedules.   
      
   Matt Roberds   
      
   --- SoupGate/W32 v1.03   
    * Origin: LiveWire BBS -=*=- UseNet FTN Gateway (1:2320/1)