moderncv 0.2

Milestone information

Project:
moderncv
Series:
trunk
Version:
0.2
Released:
 
Registrant:
Xavier Danaux
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon moderncv-0.2.zip (md5) moderncv v0.2 55
last downloaded 44 weeks ago
Total downloads: 55

Release notes 

This release does not have release notes.

Changelog 

View the full changelog

version 0.2 (6 March 2006)
  - rewrite of the code to have the styles (fonts, colours, headers and footers) be defined in different files than the class. The styles are now defined in a separate file per style, named moderncvstyle<style_name>. It should now be easy to write your own style, starting from moderncvstyleempty.sty. If you feel you have created a nice style, just email it to me and I'll include it in the next version.
  - due to the previous point, styles are now loaded by the command \moderncvstyle{style_name}. I couldn't figure out a way to preserve the old "casual" and "classic" class options, so these are now broken! Use \moderncvstyle{casual} or \moderncvstyle{classic} at the beginning of your document. This should be the only incompatibility with version 0.1.
  - added class option "nolmodern" for people without the latin modern fonts.
  - corrected some English mistakes in the examples. Thanks to Machael H. Prager for pointing them out.
  - added a \cvlistitem to produce items with a bullet (controlled by \listitemsymbol), and renamed \cvresume to \cvlistdoubleitem for consistency purpose. For compatibility reasons, the command \cvresume still works, but should be avoided.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.