view website/www/_static/style.css @ 5543:bc3e00a3d24b

MySQL backend fixes for Python 3. With Python 2, text sent to and from MySQL is treated as bytes in Python. The database may be recorded by MySQL as having some other encoding (latin1 being the default in some MySQL versions - Roundup does not set an encoding explicitly, unlike in back_postgresql), but as long as MySQL's notion of the connection encoding agrees with its notion of the database encoding, no conversions actually take place and the bytes are stored and returned as-is. With Python 3, text sent to and from MySQL is treated as Python Unicode strings. When the database and connection encoding is latin1, that means the bytes stored in the database under Python 2 are interpreted as latin1 and converted from that to Unicode, producing incorrect results for any non-ASCII characters; furthermore, if trying to store new non-ASCII data in the database under Python 3, any non-latin1 characters produce errors. This patch arranges for both the connection and database character sets to be UTF-8 when using Python 3, and documents a need to export and import the database when moving from Python 2 to Python 3 with this backend.
author Joseph Myers <jsm@polyomino.org.uk>
date Sun, 16 Sep 2018 16:19:20 +0000
parents c84dbc205b57
children c2fd254c9257
line wrap: on
line source

/* layout*/
body 
{
  font-family: sans-serif, Arial, Helvetica;
  background-color: white;
  color: #333;
  margin:0;
  padding: 0 3em 0 13em;
}
body > .header { margin: 0 0 0 -13em;}
body > .footer { margin: 1em 0 0 -13em; clear:both;}
body > .navigation 
{
  margin-left: -13em;
  width: 13em;
  float: left;
}
body > .content 
{
  width: 100%;
  margin: 0;
}
body > .header > #searchbox { position: absolute; right: 1em; top: 1em;}

/* style */

:link { color: #bb0000; text-decoration: none;}
:visited { color: #770000; text-decoration: none;}
a.toc-backref { color: #000000; }

.header h1 { margin-left: 1em; }

body
{
  font-family: sans-serif, Arial, Helvetica;
  background-color: #f5f5f5;
  color: #333;
}

.menu { padding: 0; margin-right: 1em;}
.menu ul 
{
  padding: 0;
  margin: 0;
}
.menu li
{
  margin: 5pt 0;
}
.menu > ul > li > *
{ 
  display: block;
  padding: 2pt 2pt 2pt 10pt;
  border: solid thin #dadada;
  background-color:#ffffff;
}
.menu > ul > li.current > *
{ 
  background-color:#dddddd;
}

.menu ul li:first-child { margin-top:0;}
.menu ul { list-style-type:none;}

/* sub-menus are indented */ 
.menu > ul > li > ul,
.menu > ul > li.current > ul
{
  border:none;
  background-color: inherit;
}
.menu ul ul 
{
  margin-left: 2em;
  font-size: smaller;
}

/* sub-menu items draw a separator */
.menu ul ul > li 
{  
  margin: 0;
  padding: 0;
  border: none;
  border-top: solid thin #dadada;
  background-color: inherit;
}
.menu ul ul > li:first-child
{  
  border-top: none;
}

.footer
{
  font-size: small;
  text-align: center;
  color: lightgrey;
}

.footer img {
  vertical-align: middle;
}

.content
{ 
  padding: 1em;
  border: solid thin #dadada;
  background-color: #ffffff;
}

/* This is a little hack to inject a 'news' block into the title
   page without having to set up a custom directive. */
#roundup-issue-tracker .note
{
  float: right;
  width: auto;
  border: solid thin #dadada;
  background-color:#f5f5f5;
  padding: 1em;
  margin: 1em;
}
#roundup-issue-tracker .note .admonition-title { display: none; }

table
{ 
  border-collapse: collapse;
  border-spacing: 1px;
  background-color: #fafafa;
}

input, textarea { border-width: 1px; }


/* Contact page */
div#contact table td {
  white-space: nowrap;
  padding: 1pt 1em;
}

Roundup Issue Tracker: http://roundup-tracker.org/