Source files of fsfe.org, pdfreaders.org, freeyourandroid.org, ilovefs.org, drm.info, and test.fsfe.org. Contribute: https://fsfe.org/contribute/web/ https://fsfe.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Björn Schießle 99f199e2e0 german translation added 15 years ago
..
2001 Added back an article hat has a lot of external links. 15 years ago
2002 Moved news-releated articles into the correct news directory. 15 years ago
2003 Enconding matters definitely solved ! (Well I hope so) 17 years ago
2004 Some cleanup. No content changes. 15 years ago
2005 Initial Spanish translation 16 years ago
2006 german translation added 15 years ago
nl Spanish newsletter. 15 years ago
.cvsignore Corrected bug on the detection of translations system that wouldn't recognize a new translation. Added *.lang to all .cvsignore files. 19 years ago
.symlinks Added back an article hat has a lot of external links. 15 years ago
fsfe-news.png icons for FSFE news & events RSS streams 17 years ago
news.ca.xhtml Initial translation 15 years ago
news.da.xhtml Translations to Danish 15 years ago
news.de.xhtml German translation. 17 years ago
news.en.xhtml Added links for RSS feeds. 17 years ago
news.es.xhtml fixed typos, translated title 16 years ago
news.fr.xhtml French updates. 15 years ago
news.hu.xhtml Added some more Hungarian translations. 16 years ago
news.it.xhtml RSS stuff 17 years ago
news.nl.xhtml Update 17 years ago
news.ro.xhtml corrected the project.ro , and move the translator tag out of the body tag 16 years ago
news.rss.xsl Fixed bug in RSS generation with https:// links. 15 years ago
news.sources Include newsletters in RSS feed. 15 years ago
news.sq.xhtml Added lots of Albanian translations, thanks to Besnik Bleta. 16 years ago
news.sv.xhtml Added swedish translations. 17 years ago
news.xsl Attempt to fix news listing without newsletters. 15 years ago
newsletter.ca.xhtml Initial translation 15 years ago
newsletter.da.xhtml Translations to Danish 15 years ago
newsletter.de.xhtml Translation timestamp updates. 17 years ago
newsletter.en.xhtml English revisions 17 years ago
newsletter.es.xhtml Initial translation thanks to 'cinturapartida' 15 years ago
newsletter.hu.xhtml Added some more Hungarian translations. 16 years ago
newsletter.it.xhtml Fixed a typo 17 years ago
newsletter.sources Own page for archiving newsletters. 17 years ago
newsletter.sv.xhtml Added swedish translations. 17 years ago
newsletter.xsl Fixed xsl. 17 years ago
readme Added file readme as requested 17 years ago

readme

From: "Georg C. F. Greve" <testroundup-issues@fsfeurope.org>
Subject: [issue19] Add Events to Web Page
Date: Thu, 01 Jul 2004 09:31:58 +0000
Message-Id: <1088674318.72.0.041272067427.issue19@fsfeurope.org>


[...]
It occurs to me that currently I'd have problems going there. I'm asking myself
among other things:

- WHERE exactly is it?
- WHAT do I have to pay to get in?
- WHEN exactly will be Reinhards speech and WHEN will it end?

We should try to come up with a way of providing that information consistently.

My suggestion as immediate improvement would be that every event entry title
should contain
<NAME>, <LOCATION>, <CITY>, <COUNTRY>

And the description should always contain a word about possible admission fees.

In the medium perspective, we might want to consider how we actually map the
individual speeches and tasks inside one larger event. If several people speak,
I would like to be able to supply that information.

So we may either want to discipline ourselves strongly or add another subset of
tags for this. Information I would like to have as someone who's planning to
attend is:

- Speaker(s) (mandatory, maybe as link)
- Title/Summary of speech/conference (mandatory)
- Language of speech/conference (mandatory)
- Start and end time of speech/conference (mandatory)
- Expected audience (optional)
- Possible link to preparatory/additional information (optional)

Until we have better ways of providing this info, we should try to put it in
text into the event descriptions, I think.
[...]