name mode size
README 100644 1.8kB
blog-recent.wmi 100644 732B
dlhead.wmi 100644 9.32kB
donatefoot.wmi 100644 373B
donatehead.wmi 100644 1.39kB
foot.wmi 100644 4.83kB
functions.wmi 100644 2.14kB
head.wmi 100644 5.65kB
info.wmi 100644 310B
lang.wmi 100644 1.34kB
links.wmi 100644 2.67kB
mirrors-table.wmi 100644 22.06kB
navigation.wmi 100644 884B
perl-globals.wmi 100644 1.49kB
side.wmi 100644 3.4kB
thankyou-head.wmi 100644 6.09kB
tor-mirrors.csv 100644 27.69kB
versions.wmi 100644 2.51kB
Here's a brief overview of how our wml set-up works. ---------------------------------------------------- Here's a typical wml file: The top of the file has: ## translation metadata # Revision: $Revision$ # Translation-Priority: 1-high #include "head.wmi" TITLE="Tor: Bridges" <div class="main-column"> and the bottom of the file has: </div><!-- #main --> #include <foot.wmi> and the middle is standard html, plus a few extra tags like <page> that we've added to automatically link to the translated pages when they exist. So that wml page produces this html page: aka Then head.wmi and foot.wmi are just other mostly-html files you import to handle the repeat parts of each page (well, that plus some embedded perl scripts to generate some of the static content). You can basically ignore the wml part of them, and to a first approximation just think of them as more html. So in summary, wml is like html with a bit more markup. ---------------------------------------------------- Where it gets interesting is the download page: It has the standard header and footer section, but in the body of the page it includes links like <a href="<package-osx-bundle-stable>". Rather than putting URLs and Tor versions into every wml page, and then requiring the translators to update their page whenever we bump a version number, we instead define each URL and version as a new wml element: