summaryrefslogtreecommitdiff
path: root/www
diff options
context:
space:
mode:
authorGary E. Miller <gem@rellim.com>2015-04-09 20:51:20 -0700
committerGary E. Miller <gem@rellim.com>2015-04-09 20:51:20 -0700
commit6741413044357fde32916bc444f648f62c5a30d5 (patch)
treedc3efb544ca89cf2bec75893162272b5ad59e304 /www
parent2fd7a1548f03904e51969246b3df027a1e5631bd (diff)
downloadgpsd-6741413044357fde32916bc444f648f62c5a30d5.tar.gz
Conver to html5 and utf-8, Add some SEO.
Diffstat (limited to 'www')
-rw-r--r--www/upstream-bugs.html14
1 files changed, 8 insertions, 6 deletions
diff --git a/www/upstream-bugs.html b/www/upstream-bugs.html
index 55fc01c1..92b96d45 100644
--- a/www/upstream-bugs.html
+++ b/www/upstream-bugs.html
@@ -1,10 +1,12 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<!DOCTYPE HTML>
<html>
<head>
- <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Author" content="Eric Raymond">
- <meta name="Keywords" content="GPS, translator, mxmap, GIS">
+ <meta name="Description" content="Links to Open User-Visible Problems in other software">
+ <meta name="Keywords" content="GPS, gpsd, bugs">
+ <meta name="Revised" content="9 April 2015">
+ <meta name="robots" content="index,follow">
<title>Bugs GPSD Exposes In Other Software</title>
<link rel="stylesheet" href="main.css" type="text/css">
</head>
@@ -175,9 +177,9 @@ that -b is an effective workaround and can finger bad Bluetooth
firmware as the cause of the problem.</p>
<p>A separate bug with less severe symptoms afflicts some USB devices.
-The probe strings <tt>gpsd</tt> sends in order to determine device
+The probe strings <code>gpsd</code> sends in order to determine device
type and subtype may be more than a device can handle, causing it to
-hang; power-cycling should fix this. Newer versions of <tt>gpsd</tt>
+hang; power-cycling should fix this. Newer versions of <code>gpsd</code>
break up the probe writes into smaller pieces, interleaving them with
the first few packet reads, so they are far less likely to trigger
this bug.</p>