Today would have been my father's 87th birthday. In a change of tone from the usual Hooting Yard guff, here is a remembrance of him. Following Georges Perec's Je me souviens (1978) and Gilbert Adair's Memories (1986), I have written, in no particular order, a set of sentences each beginning “I remember…” There are fifty-eight in all, one for each year of his life. I wrote them at one sitting, as they bubbled to the surface. On another day I might write a different list of memories.
1. I remember he smoked a cheap brand of cigarettes called Carlton Premium.
2. I remember the Evening Standard ringing him up after he made disparaging remarks about Dr Rhodes Boyson, though I don't remember the context, or how the paper knew.
3. I remember his love of crime fiction.
4. I remember his love of football, and that—uniquely among aficionados of the game?—he did not support any particular team.
5. I remember his hip-flask of Scotch.
6. I remember seeing him cry only once, when talking about his father.
7. I remember him using the nickname “Brucie” for my mother.
8. I remember when his choice of hat convinced some of our neighbours that he was a Russian spy.
9. I remember he read The Guardian and the Morning Star.
10. I remember he always called The Guardian The Manchester Guardian
11. I remember him wandering around the house with a tea-towel over his shoulder calling out “Any more pots?”
12. I remember he called Ready-Brek Fairex.
13. I remember precisely the style of his spectacle-frames.
14. I remember the way he referred to Norman St John Stevas as “Ste-VASS”.
15. I remember that he subscribed to a Soviet propaganda magazine called Sputnik.
16. I remember him dusting individually the books on the bookshelves.
17. I remember his habit of cutting off the corners of dust-jackets where the price was shown.
18. I remember him saying “The whole point is…”
19. I remember his afternoon naps on the sofa.
20. I remember his loud snoring
21. I remember him saying “It's like Blackpool Illuminations” when a light was left on in an empty room.
22. I remember his psoriasis.
23. I remember him telling me that when he played football as a young man he was nicknamed “Twinkletoes”.
24. I remember his hatred of Reginald Maudling but also his insistence, when Maudling died, that one should never speak ill of the dead.
25. I remember his sentimentality.
26. I remember that Random Harvest (Mervyn LeRoy, 1942) was his favourite film.
27. I remember him taking me to a Manchester United match (at Upton Park?) and how his Manchester accent became unconsciously exaggerated when speaking to other fans.
28. I remember him saying “daft as a Toc H Lamp”.
29. I remember his puritanical streak.
30. I remember his dismissal of anything other than the plainest foods as “foreign muck”.
31. I remember him telling me how he had gone to the Chinese embassy to be given a free copy of Mao's Little Red Book (which I still have).
32. I remember his fierce attachment to his mother.
33. I remember him polishing his shoes.
34. I remember that the bottle of Guinness he drank with his evening meal was “medicinal”.
35. I remember kicking a football around in the garden with him.
36. I remember when he wore a shirt with a collar that made him look like a priest.
37. I remember his collection of cigarette cards.
38. I remember the time he bought a hideous plastic rose in a glass globe as a birthday gift for my mother.
39. I remember him as an educator.
40. I remember him taking me to summer garden parties at the home of his colleague Mike Gibbs.
41. I remember learning that he had been very ill and almost died shortly before I was born.
42. I remember his brilliantine.
43. I remember him mowing the lawn.
44. I remember learning that he had all his teeth extracted at the age of thirty and had dentures fitted.
45. I remember his friend Jim Spraggins.
46. I remember him pontificating.
47. I remember him showing me the “grooves” on his hands that were the first signs leading to a diagnosis of motor neurone disease.
48. I remember his uxoriousness.
49. I remember his infuriating habit of tidying that which was already tidy.
50. I remember his insistence that one should always have an up-to-date atlas.
51. I remember, when I boasted that I had dodged my bus fare, how he reprimanded me for my dishonesty, his clarity about right and wrong.
52. I remember his supper of boiled egg and bread mashed into a pulp.
53. I remember how he hated Monty Python but loved Fawlty Towers.
54. I remember how he loved the Carry On films.
55.I remember his postcard collection.
56. I remember his big florid curly handwriting.
57. I remember that he always wore a vest under his shirt.
58. I remember clearly the last time I saw him, sitting at his desk, reading the paper, drinking whisky, on the morning of Monday 16 May 1983. He died two days later.


WITNESS LIST County Affairs Committee April 4, 2001-8:00A HB 1148 For: Ratliff, Thomas (AT&T Wireless; Voicestream Wireless; Western Wireless; Texas Assoc. of Paging Services) HB 2212 For: Bacon, April (Texas Association of County Auditors; Travis County Auditor's Office) HB 2466 For: Larson, Lyle (Bexar County) HB 2477 For: Kirkpatrick, Zoe (Self and Garza County Hospital District Board of Directors) Travis, Michael (Self and Hospital Board of Directors: David Tyler, Zoe Kirkpatrick & Leon Miller) Against: Burnett, Wesley W. (Self) Ethridge, Daymon (Self) HB 2628 For: Humble, Monty (Greater Dallas Jewish Community Capital Campaign) HB 2818 For: Conner, J. C. (Self and Management and Training Corporation) On: Julian, Terry (Texas Commission on Jail Standards) HB 3073 For: Allison, Jim (County Judges & Commissioners Association of Texas) Wisenbaker, Beth (Self and Hopkins County Commissioners Court: Judge Cletis Milsap, H.W. Halcomb, Don Patterson, Calvin Prince) HB 3132 For: Endres, Jack R. (Muenster Hospital District) HB 3440 For: Brown, Dan W. (Self and Sheriff's Association) Painter, Gary (Self and Sheriff's Association of Texas) HB 3443 For: Brown, Dan W. (Self and Sheriff's Association) Painter, Gary (Sheriff's Association of Texas) HB 3475 For: McClendon, III, Sidney S. (Galveston County Beach Erosion Task Force; West Galveston Island POA) Against: Hallmark, Terry (Texas Chapter Surfrider Foundation) Mitchell, Jamie (Surfrider Foundation, Texas Chapter) On: Kewley, Wayne (Texas General Land Office) HB 3633 For: Marks, David (East Montgomery County Improvement District) HB 3634 For: Rash, Jeanette (Self) SB 201 For: Burke, Cecelia (Travis County Commissioners Court) Dahill, John (Dallas County) Harlow, Joe (Travis County) Nguyen, Tien (City of Houston)


--- layout: page title: About header-img: "img/about-bg.png" ---
I've always seen myself as broken to some degree; however, it's gotten much better over the years. After digging myself out of a pit of social phobia, depression, and other anxieties I'm now ready to start my first career... for real. It's a very gut-wrenching, cold-sweat-inducing move on my part, but I'm so very excited to start my coding/programming career!


CONTENTS | PREV | NEXT
The
javax.print.attribute.standard package enumerates all of the
standard attributes in the Java Print Service API. Most of these
standard attributes are taken from the attributes defined in the
IETF Internet Printing Protocol (IPP) 1.1 specification. This means
that each IPP-compliant attribute class(category) defined in
package javax.print.attribute.standard corresponds to an IPP
attribute category, and the name (as returned by getName) is the
actual IPP name for the category. The class names also usually
reflect the IPP name as closely as the coding conventions of the
Java programming language permit. Furthermore the values defined
for a category are the same as the IPP values. IPP compatibility of
each attribute category is documented in the API specification.
This section
describes the attributes that developers will probably use most
frequently. The more commonly-used attributes, including the ones
listed here, implement PrintRequestAttribute because printing
applications will usually specify how an entire print job should be
printed, which is the role of a PrintRequestAttribute.
OrientationRequested
The
OrientationRequested attribute category allows you to specify the
orientation of the imaging on the paper. The possible attribute
values are: PORTRAIT, LANDSCAPE, REVERSE_PORTRAIT, and
REVERSE_LANDSCAPE. OrientationRequested.PORTRAIT is usually the
default value. This code snippet demonstrates adding an
OrientationRequested attribute to a set:
aset.add(OrientationRequested.REVERSE_PORTRAIT);
The
OrientationRequested object is a type-safe enumeration
encapsulating String values, which correspond to the possible
orientations. These values are the actual IPP keywords.
Some pre-formatted
document types, such as "Postscript", might not be able to support
this attribute category because pre-formatted document types embed
printer language commands that are interpreted by the printer, and
these commands take precedence over a client request.
Clients can discover
the supported orientation values for a particular print service by
calling:
PrintService.getSupportedAttributeValues(OrientationRequested.class, ...).
This method returns an
array of type OrientationRequested enumerating the supported
values.
Copies
The Copies attribute
category allows you to specify the number of copies to print. The
Copies class encapsulates an integer representing the number of
copies requested. This code snippet demonstrates adding a Copies
attribute, set to five copies, to an attribute set:
aset.add(Copies(5));
Clients can discover
the range of copies that a print service supports by calling :
PrintService.getSupportedAttributeValues(Copies.class, ...)
This method returns a
CopiesSupported object, which encapsulates a range of integer
values representing the range of copies that the service can
handle. Calling getSupportedAttributeValues with CopiesSupported
instead of Copies always returns null because the CopiesSupported
object does not implement the PrintRequestAttribute interface, and
so a client cannot specify a CopiesSupported attribute in a print
request.
This code sample
demonstrates discovering if a print service supports printing 5
copies and adding a Copies attribute with a value of 5 copies to an
attribute set:
CopiesSupported copSupp =
(CopiesSupported) service.getSupportedAttributeValues(Copies.class, null,
null);
if (copSupp != null && copSupp.contains(5)) {
requestAttrSet.add(new Copies(5));
} else { ...
}
Media
Media is the IPP
attribute that identifies the medium on which to print. The Media
attribute is an important attribute to understand, butis relatively
complex.
The Java Print
Service API defines three subclasses of the abstract class Media to
reflect the overloaded Media attribute in the IPP specification:
MediaSizeName, MediaName and MediaTray. All the Media subclasses
have the Media category, for which each subclass defines different
standard attribute values. For example, a MediaTray object can
specify a value of MANUAL for the Media attribute to indicate that
the document must be printed on paper from the printer's manual
tray. This code snippet demonstrates adding a Media attribute to a
set:
aset.add(MediaTray.MANUAL);
The value of the
Media attribute is always a String, but because the attribute is
overloaded, its value determines the type of media to which the
attribute refers. For example, the IPP pre-defined set of attribute
values include the values "a4" and "top-tray". If
Media is set to the value "a4" then the Media attribute
refers to the size of paper, but if Media is set to
"top-tray" then the Media attribute refers to the paper
source. Because the String attribute value can refer to such
diverse types of media, an application can extend the attribute set
to include values such as "company-letterhead" or
"yellow letter paper". Of course, to extend the Media
attribute in this way, an application must discover a print service
that is configured to print with this media.
In most cases,
applications will use either MediaSizeName or MediaTray. The
MediaSizeName class enumerates the media by size. The MediaTray
class enumerates the paper trays on a printer, which usually
include a main tray and a manual feed tray. The IPP 1.1
specification does not provide for specifying both the media size
and the media tray at the same time, which means, for example, that
an application cannot request size A4 paper from the manual tray. A
future revision of the IPP specification might provide for a way to
request more than one type of media at a time, in which case the
JPS API will most likely be enhanced to implement this change.
The JPS API also
includes two additional media-related Attribute classes that are
not IPP attributes: MediaSize and MediaPrintableArea.
MediaSize
MediaSize is not a
request attribute; it is an enumeration of paper dimensions and a
mapping to MediaSizeName instances. Each MediaSizeName instance
usually has a MediaSize object associated with it so that clients
can obtain the dimensions of the paper that the MediaSizeName
instance defines. To determine the dimensions of the MediaSizeName
instance, call:
MediaSize size = MediaSizeName.getMediaSizeForName(paper);
MediaPrintableArea
MediaPrintableArea is
used in a print request in conjunction with a compatible Media to
specify the area of the paper on which to print. Printer hardware
usually defines the printable area of a page, which is rarely the
entire page. For this reason, an application needs to determine
what printable area a printer defines for a particular size media
to ensure that the print data can fit within this area.
For example, to
determine the supported printable area for 5" x 7" paper, the
application needs to choose a media size attribute value that
corresponds to this size paper and then query the print service
with the media size:
PrintRequestAttributeSet aset = new HashPrintRequestAttributeSet();
aset.add(MediaSizeName.NA_5X7);
MediaPrintableArea printableArea =
(MediaPrintableArea)service.
getSupportedAttributeValues(MediaPrintableArea.class, null, aset);
The returned value
indicates the largest printable area that can be supported by that
printer for that paper size.
Destination
The Destination
attribute allows you to redirect your print data to a file rather
than sending it to a printer device. The "print-to-file"
option is very common in user dialogs, but the spooled data is not
always usable because it might be a device-specific raster that can
only be interpreted by the device from which it was redirected. For
this reason, the Java Print Service API requires that the client
query the print service to determine if it can redirect the output
to a file. The service might not support the category at all, or it
might support only particular values. For example, since the JPS
API can be used in an network environment, in which the formatting
of print data does not occur on the host computer, specifying a
local file for output might not be possible because the service
formatting the data might not have access to the local filesystems
of the client. The Destination attribute takes a URL as the value
of the destination, which allows a network printer to use a
protocol such as ftp to upload formatted print data. However, most
printers that support this attribute will run as part of a local
environment and can accept the "file:" protocol URL. This
code snippet redirects the output to a file called out.prn on the
c: drive:
aset.add(new Destination("file:c:\out.prn"));
SheetCollate
The SheetCollate
attribute allows you to specify whether or not your print job is
collated when you are printing more than one copy of a multi-page
document. For example, the pages of a 3-page, 2-copy collated job
will print as (1,2,3,1,2,3), but the pages of the same document
submitted in a 2-copy uncollated job will be printed as
(1,1,2,2,3,3). This attribute is not in version 1.1 of the IPP
specification, but it is very useful and most printers support it.
This code snippet demonstrates specifying a collated job:
aset.add(SheetCollate.COLLATED);
Sides
Some printers,
particularly high-end printers, can print on both sides of the
paper. The Sides attribute allows applications to specify two-sided
printing instead of the usual default of single-sided printing.
Two-sided printing is sometimes referred to as "duplex" or "tumble"
printing. These two values are differentiated by the orientation of
the output. The Java Print Service API refers to duplex as "two
sided long edge" and tumble as "two sided short edge". Read the API
specification for Sides for further explanation. This code snippet
specifiesthat a job print the documents two-sided:
aset.add(Sides.DUPLEX);
Fidelity
The Fidelity attribute
is an IPP boolean attribute that represents whether or not a print
job should be rejected if the print service does not support any
attribute specified in the print request. Fidelity is not an
attribute many developers will need to consider, but it is an
important attribute in the context of the JPS API. The default
value is FIDELITY_FALSE, which indicates that a print job should
not be rejected if the print service does not support an attribute
specified in the print request. For example, if an application
specifies an orientation of reverse landscape, but the printer does
not support reverse landscape, the job is rejected if fidelity is
true, but if fidelity is false then the printer might substitute a
reasonable alternative, such as the landscape orientation. The
Fidelity attribute allows applications to decide whether to only
print the document exactly as specified or to print it even though
the printer might not support all attributes. This code snippet
specifies that a job should be rejected if the printer does not
support the requested attributes:
aset.add(Fidelity.FIDELITY_TRUE);
For the cases in which
fidelity is important, the Java Print Service API provides many
tools for applications to query exactly what can be supported for a
particular print request. See the various query methods on the
PrintService interface.
CONTENTS | PREV | NEXT


Toggle navigation
Yifan's Blog
Home
Books
Contact
Dropdown
Action
Another action
Something else here
Nav header
Separated link
One more separated link
Please sign in
Email address
Password
Remember me
Sign in
Here I come!
2017-04-12 22:45 by
Yifan
fadjhfahiuwehfushafkhsdf
read more
So what is next?
2017-04-12 23:45 by
Yifan
Not surprisingly, I should continue.
read more
Previous
Next


Activities
Return
- Golf: 18 different courses so you don't ever have to run into anyone
during your game.
- Bingo: nonstop 24/7 tournaments mean experienced players can walk away
with MILLIONS in cash.
- Birdwatching: from ferocious birds of prey to ferocious songbirds, Isla Paradisia where
every animal is highly territorial and carnivorous.


{% extends "base.html" %} {% block title %}AraPheno - Tutorials{% endblock title %} {% block content %}
You can retrive a list of all phenotypes for all studies by following this link: Show all Phenotypes or via the global navigation menu at the top.
In addition you can also use the AraPheno REST API. More information about the REST API can be found here: Information about the REST API
You can retrive a list of all studies by following this link: Show all Studies or via the global navigation menu at the top.
In addition you can also use the AraPheno REST API. More information about the REST API can be found here: Information about the REST API
At the AraPheno home view we provide a search form. Here, you can type in any phenotype or study name. An autocompletion will help you finding the correct phenotype or name. If you click on a entrie in the autocomplete form you will be directly redirected to the study/phenotype you searched for. If you press enter you will be redirected to a result view. This result view gives an overview about all phenotypes and studies that could have been found with your search query.
Each entry in the study table is clickable. Thus, you will be redirected to the study specific view with additional information and meta-information. You will see all phenotypes that are linked to this study. Furthermore, you can retrive additional information about trait ontologies, environment ontoloties and units.
In the detailed view of a phenotype, click on the "Show transformations" link above the histogram. This will show the histograms and Shapiro-Wilk scores of various transformations (log, sqrt, box-cox, ...).
Each entry in the phenotype table is clickable. Thus, you will be redirected to the phenotype specific view with additional information and meta-information. Here, you can see the geographic distribution of all accessions of this phentype, as well as dynamic visualisations about the measurment distribution.
You can compute phenotype-phenotype correlations for a list of up to ten phenotypes. We implemented a Phenotype Correlation tool that guides you through selecting available phenotypes via an autocompletion search field. In this field you just have to search for phenotypes by name. You can select up to ten phenotypes. After you submitted your selection AraPheno will compute the phenotype correlations on the fly. On the results page you can see a heatmap with all pairwise phenotype correlations. Hovering with the cursor over circles in the correlation plot will update the phenotype-phenotype scatter plot and the sample-overlap plot for this phenotype pair. Here, you can see a live demo of the result page: Demo.
Phenotypes can be annotated by various ontologies (Plant Trait Ontology, Plant Environmental Conditions and Unit of Measurement). This makes it possible to view all available phenotypes for a specific ontology term. To access this feature, first choose "Ontologies" from the "Data" menu in the top toolbar. This will display a list of available ontologies. By clicking on the "Show" button, the user will be navigated to the corresponding ontology detail view. On the left side a tree widget displays all ontology terms that are part of the selected ontology. By selecting an ontology term from the tree widget, detailed information about the selected term is displayed on the right side. Below that a table of phenotypes that are annotated by the selected term or any of its subterms will be shown.
You can upload a study by clicking on the "Submit Phenotypes" button on the landing page.
The data has to be provided in either ISA-TAB
(sample), PLINK (sample) or CSV format (sample).
Additionally you must provide contact information (email + name).
Once uploaded, the submission will be reviewed by one of our curators and you will be automatically redirected to a submission status page. Additionally an email containing the URL to the submission status page will be sent
to your specified email address, so you can check your submission at a later time. If the curators raise issues, you can view them there.
If there are no issues left, the curators will make the submission public and everyone will be able to access your submitted study.
PLINK format:
FID IID pheno1 pheno2 6909 1 24.5 100.2 6909 2 23.2 101.5 6909 3 25.2 99.4 6414 4 5.4 10.4 6414 5 11.2 6414 6 4.2 9.8 ...
CSV format:
accession_id,replicate_id,pheno1,pheno2 6909, 1, 24.5, 100.2 6909, 2, 23.2, 101.5 6909, 3, 25.2, 99.4 6414, 4, 5.4, 10.4 6414, 5, , 11.2 6414, 6, 4.2, 9.8 ...
Empty values are encoded as empty cells in both CSV and PLINK (see pheno1 for accession_id/FID: 6414 and replicate_id/IID: 5)
In case you submit a study with many phenotypes, it can be cumbersome to edit the meta-information (trait, environment and unit ontology, scoring, type, etc) of all the phenotypes manually. The submission detail view provides a feature to upload a CSV with meta-information for one or more phenotypes in the study. To do so open the submission detail page (link that was sent in the email), select the CSV file with the meta-information for the phenotypes in your study and save the study. The phenotypes for which the CSV file contains the meta-information are updated. The CSV has following format:
Phenotype, Scoring, growth_conditions, eo_term_id, to_term_id, uo_term_id, Type phenotype1, Scoring of phenotype1, Growth condition of phenotyp1, EO:0007256, TO:0000371, UO:0000005, binary phenotype2, Scoring of phenotype2, Growth condition of phenotyp1, EO:0007256, TO:0000202, UO:0000270, quantitative phenotype3, Scoring of phenotype3, Growth condition of phenotyp1, EO:0007256, TO:0000183, UO:0000304, categorical ...
The IDs for eo_term_id (environment ontology), to_term_id (trait ontology) and uo_term_id (unit ontology) can be found on the Ontologies page


Life is all about Happiness and Sorrow.... -MKS
Don't run behind success, Make success run behind you...." MKS
Always think abnormally as these abnormal thinking leads to famous invention.... -MKS
Life is just like sun, which arises and sets one day.... -MKS
Success is only a thought until you have a firm determination to achieve it.... -MKS
Goal is acheived by those you have strength to do hardwork otherwise else seing the ways gets off.... -MKS
Giving 100% is using your own full potential.... -MKS
Smarter persons do well in their future .... -MKS
One should not only rely on what he is seeing.... -MKS
If you are capable of doing charity then do as not everybody is capable of doing.... -MKS
Development has hypnotised us that we are not seeing our evironment....  -MKS
Don't trust on what is written trust when you do it.... -MKS
Think always like this which creates curiosity.... -MKS
Brand is not only the life, the disciple must be there.... -MKS


Suited
For the architecture and API docs see here
For the main demo see here
For the usage see this README
Suited's markdown plugin is based on markdown-it and so can use other markdown-it plugins for special mark-up.
Suited's Markdown plugin add special markdown syntax to allow you to easily add fif=gures and slides using markdown.
# Special markdown syntax for figures and slides
For figures surround with your markdown like so
~~: **your bold stuff** :~~
For slides surround your markdown like so
~~* **your bold stuff** *~~
NB that if the ~~: and :~~ is on one line it is an inline-figure.
NB for block level figures put ~~: on a line by itself and follow with :~~ on a line by itself.
I kind of want a **nested html evaluated to** here: so lets gie it a go
this is text in a paragraph
This is on new line
this is text in aanother paragraph
This is also on new line
# Check out figures
I kind of ~~:want a **bold figure** here:~~ so lets gie it a go
~~:
* l1
* l2
- l377777
* l4
:~~
# nested inline figures
~~:
* fig1
* fig2
- ~~:fig2a nested:~~
* l4
:~~
# nested block figures
~~:
* fig1
* fig2
~~:
- fig2a nested1
- fig2a nested2
:~~
* l4
:~~
# Check out slides
I kind of ~~*want a **inline** slide here*~~ so lets give it a go
~~*
* l1 in slide block
* l2
- l377777
* l4
*~~
# Slide wide nested inline figure
~~*
* slide1
* slide2
- ~~:fig2a nested:~~
* slide3
*~~
# nested list item
~~*
* slide1
* slide2
- nested
* slide3
*~~
# Slide wide nested inline slide
~~*
* slide1
* slide2
- ~~*slide2a nested*~~
* slide3
*~~
~~*
### Slide with image
![jackOfSpades](images/jackOfSpades.png)
*~~
~~*
### Slide with image and text
some text before
![jackOfSpades](images/jackOfSpades.png)
some text before
*~~
# block slide with nested block figures
~~*
* slide1
* slide2
~~:
- block fig2a nested1
- block fig2a nested2
:~~
* slide3
*~~
# block slide with nested block slide
~~*
* slide1
* slide2
~~*
- block slide2a nested1
- block slide2a nested2
*~~
* slide3
*~~
**Boldmarkdown** is cool
lists are cool
* ggg
* hhh
# Tables
| Option | Description |
| ------ | ----------- |
| data | path to data files to supply the data that will be passed into templates. |
| engine | engine to be used for processing templates. Handlebars is the default. |
| ext | extension to be used for dest files. |
Right aligned columns
| Option | Description |
| ------:| -----------:|
| data | path to data files to supply the data that will be passed into templates. |
| engine | engine to be used for processing templates. Handlebars is the default. |
| ext | extension to be used for dest files. |
---
__Advertisement :)__
- __[pica](https://nodeca.github.io/pica/demo/)__ - high quality and fast image
resize in browser.
- __[babelfish](https://github.com/nodeca/babelfish/)__ - developer friendly
i18n with plurals support and easy syntax.
You will like those projects!
---
# h1 Heading 8-)
## h2 Heading
### h3 Heading
#### h4 Heading
##### h5 Heading
###### h6 Heading
## Horizontal Rules
___
---
***
## Emphasis
**This is bold text**
__This is bold text__
*This is italic text*
_This is italic text_
~~Strikethrough~~
## Blockquotes
> Blockquotes can also be nested...
>> ...by using additional greater-than signs right next to each other...
> > > ...or with spaces between arrows.
## Lists
Unordered
+ Create a list by starting a line with `+`, `-`, or `*`
+ Sub-lists are made by indenting 2 spaces:
- Marker character change forces new list start:
* Ac tristique libero volutpat at
+ Facilisis in pretium nisl aliquet
- Nulla volutpat aliquam velit
+ Very easy!
Ordered
1. Lorem ipsum dolor sit amet
2. Consectetur adipiscing elit
3. Integer molestie lorem at massa
1. You can use sequential numbers...
1. ...or keep all the numbers as `1.`
Start numbering with offset:
57. foo
1. bar
## Code
Inline `code`
Indented code
// Some comments
line 1 of code
line 2 of code
line 3 of code
Block code "fences"
```
Sample text here...
```
Syntax highlighting
``` js
var foo = function (bar) {
return bar++;
};
console.log(foo(5));
```
## Tables
| Option | Description |
| ------ | ----------- |
| data | path to data files to supply the data that will be passed into templates. |
| engine | engine to be used for processing templates. Handlebars is the default. |
| ext | extension to be used for dest files. |
Right aligned columns
| Option | Description |
| ------:| -----------:|
| data | path to data files to supply the data that will be passed into templates. |
| engine | engine to be used for processing templates. Handlebars is the default. |
| ext | extension to be used for dest files. |
## Links
[link text](http://dev.nodeca.com)
[link with title](http://nodeca.github.io/pica/demo/ "title text!")
Autoconverted link https://github.com/nodeca/pica (enable linkify to see)
## Images
![Minion](https://octodex.github.com/images/minion.png)
![Stormtroopocat](https://octodex.github.com/images/stormtroopocat.jpg "The Stormtroopocat")
Like links, Images also have a footnote style syntax
![Alt text][id]
With a reference later in the document defining the URL location:
[id]: https://octodex.github.com/images/dojocat.jpg "The Dojocat"
just finnish


Java SE Desktop consists of several technologies used to create rich client applications and applets. The desktop tools and libraries provide an interface between the Java application and the core tools and libraries of the platform as shown in Figure 9-1.
For information on all desktop technologies available in Java SE, visit the Java SE Desktop Overview documentation.
This topic describes troubleshooting techniques for the following Java SE Desktop technologies:
Abstract Window Toolkit (AWT) provides a set of application programming interfaces (APIs) for constructing graphical user interface (GUI) components such as menus, buttons, text fields, dialog boxes, checkboxes, and for handling user input through those components. In addition, AWT allows for rendering of simple shapes such as ovals and polygons and enables developers to control the interface layout and fonts used by their applications. It also includes data transfer classes (including drag and drop) that allow cut and paste through the native platform clipboard.
The classes of this API are at the bottom of the software stack (closest to the underlying operating and desktop system).
AWT also provides a set of heavyweight components.
Purely AWT applications are usually not related to Swing. If an AWT application does custom rendering, it uses Java 2D.
For more information about AWT, see the AWT documentation.
Java 2D is a set of classes for advanced 2D graphics and imaging. It encompasses line art, text, and images in a single comprehensive model. The API provides extensive support for image compositing and alpha channel images, a set of classes to provide accurate color space definition and conversion, and a rich set of display-oriented imaging operators. These classes are provided as additions to the java.awt
and java.awt.image
packages.
Like AWT, Java 2D is also at the bottom of the software stack (closest to the underlying operating and desktop system).
For more information about Java 2D, see the Java 2D documentation.
Swing provides a comprehensive set of GUI components and services which enables the development of commercial-quality desktop and Internet/Intranet applications.
Swing is built on top of many of the other Java SE Desktop technologies, including AWT, Java2D and Internationalization. In most cases the Swing high-level components are recommended instead of those in AWT. However, there are many APIs in AWT that are important to understand when programming in Swing.
Since Swing is a lightweight toolkit, it has very little interaction with the native platform. Swing uses Java 2D for rendering, and AWT provides creation and manipulation of top-level components, such as Windows, Frames, and Dialogs.
For more information about Swing, see the Swing documentation.
Internationalization is the process of designing software so that it can be adapted (localized) to various languages and regions easily, cost-effectively, and in particular without engineering changes to the software. Localization is performed by simply adding locale-specific components, such as translated text, data describing locale-specific behavior, fonts, and input methods.
In Java SE, internationalization support is fully integrated into the classes and packages that provide language-dependent or culture-dependent functionality.
For more information about internationalization APIs and features of Java SE, see the Internationalization documentation.
Java Sound provides low-level support for audio operations such as audio playback and capture (recording), mixing, musical instrument digital interface (MIDI) sequencing, and MIDI synthesis in an extensible, flexible framework. This API is supported by an efficient sound engine which guarantees high-quality audio mixing and MIDI synthesis capabilities for the platform.
For more information about Java Sound, see the Java Sound documentation.
Java Plug-in extends the functionality of popular web browsers by connecting them to the Java platform. This connection enables Java applets on websites to be run within the web browser on the desktop.
For more information about Java Plug-in, see Java Plug-in and Applet Architecture documentation.
The better you understand the relationships between these technologies, the more quickly you can pinpoint the area your problem falls into.


05 January 2001
Disease Outbreak Reported
The onset of the outbreak of Ebola in Gulu, Uganda (see previous report) has heightened awareness of viral haemorrhagic fevers in the region. As a result, WHO has been investigating periodic rumours of similar outbreaks in the surrounding countries. In Democratic Republic of Congo (DRC), WHO has investigated rumours in Dungu, Bengadi, Isiro, Buta, Nyankunde and Bunia, and samples have been negative for Ebola.
As part of these ongoing operations, WHO is currently investigating unverified reports of 2 additional cases for which few clinical details have been reported, in Bunia, DRC. The WHO Outbreak Response Team in Gulu has been in contact with WHO Office, Goma, Médecins sans Frontières (MSF), Goma and the WHO sub-office in Bunia regarding these unverified rumours. A WHO surveillance officer at the Bunia sub-office is investigating the reports. In addition, a team from MSF and WHO will travel to Bunia early next week.
Previously 3 suspected cases were reported in Bunia, one in early August, one in mid-November and a third in late-November. WHO investigations demonstrated that these rumours were unfounded.