Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
litehtml does not handle CSS font family fallbacks. Consider the fragment:
The call to "create_font" gets faceName = "Georgia, serif". Which suggests that font family selection is an exercise for the user, and I am fine with that, but consider the following:
The exact same font would be created since NoFont does not exist, but it would register as a different font in the document::get_font function because the map key is built from the strings.
Further, the following:
Would create yet another font containing the same data if Georgia was not found in the original fragment.
I would suggest that litehtml should try the options in order and call a new document function that takes the single font family name and returns if it can be created. Then the init_font function could call get_font with the successful name, which would make the map key string work better.
Background: I am writing an OpenGL ES 2.0 container to run on an embedded device. I am using freetype to deal with fonts and not an operating system that would deal directly with the passed string.