Jefferson's Newspaper » Reference http://jeffersonsnewspaper.org A blog about information, education, and the (digital) humanities... Tue, 01 May 2012 12:38:31 +0000 en hourly 1 http://wordpress.org/?v=3.3.2 Tips for Using the WordPress Admin Bar with BuddyPress http://jeffersonsnewspaper.org/2012/tips-for-using-the-wordpress-admin-bar-with-buddypress/ http://jeffersonsnewspaper.org/2012/tips-for-using-the-wordpress-admin-bar-with-buddypress/#comments Fri, 20 Jan 2012 15:47:18 +0000 E. Bell http://jeffersonsnewspaper.org/?p=1227
If you run a WordPress Network that uses BuddyPress, you are probably aware of the distinctions between the WordPress and BuddyPress admin bars (or in the latter case, the “buddy bar”), so we can jump right to the point: You are no longer using the buddy bar, and are now using the core admin bar; there is something you don’t like about this arrangement and you need to change it. Well, here are a few quick tricks.

Each of these snippets (with one noted exception) can be added to functions.php of your main blog theme or you can create a simple plugin.

Swap the BuddyBar for the Admin Bar

If you somehow are still using the buddy bar, try one of the following methods. (You may also need to adjust your CSS slightly to accommodate the differences between the two admin bars.)

Here is the preferred BuddyPress method, which is simply added to wp-config.php:

/*
** Add the following to wp-config.php
** Removes BP admin bar and replaces it with the WP admin bar
*/
define( ‘BP_USE_WP_ADMIN_BAR’, true );

If for some reason you find that the above method does not work, you may try adding the following to functions.php

<?php
/*
** The following removes BP admin bar and replaces it with the WP admin bar
*/
 
function remove_bp_adminbar(){
     remove_action( 'wp_footer', 'bp_core_admin_bar', 8 );
     remove_action( 'admin_footer', 'bp_core_admin_bar');
     show_admin_bar(true);
}
add_action('after_setup_theme','remove_bp_adminbar');
?>

Remove something from the Admin Bar

To remove a menu item, you just need to know its HTML div id. This example removes the WordPress logo and menu. See remove_node().

<?php
/*
** The following removes the WordPress menu and logo
** wp-admin-bar-wp-logo is the div id in the menu HTML but we just use wp-logo 
** see http://codex.wordpress.org/Function_Reference/remove_node
*/
 
function admin_bar_remove_this(){
     global $wp_admin_bar;
     $wp_admin_bar->remove_node('wp-logo');
     }
     add_action('wp_before_admin_bar_render','admin_bar_remove_this');
?>

Adding something to the Admin Bar

Similarly, you can add a new menu item to an existing HTML div id. Here we are adding a link to create a new category within the +New menu. See add_node().

<?php
/*
** The following adds a link item to create a new "Category" within the "+New" menu
** wp-admin-bar-new-content is the div id in the menu HTML but we just use new-content 
** see http://codex.wordpress.org/Function_Reference/add_node
*/
 
function admin_bar_add_this(){
     global $wp_admin_bar;
     $newcat=get_site_url( BP_ROOT_BLOG ).'/wp-admin/edit-tags.php?taxonomy=category';
     $wp_admin_bar->add_node( array(
          'parent' => 'new-content',
          'title' => 'Category',
          'href' => $newcat) );
     }
add_action('wp_before_admin_bar_render','admin_bar_add_this');
?>

Make it Easier for Network Users to Create New Blogs

The BuddyPress dev team has added Notifications and some other BP-specific features to the admin bar, but the link to “Create a new site” is still missing as of v. 1.5.3 (UPDATE: actually, this would be a WP issue, not BP; track this issue here). If you have a very active community, especially one that routinely creates new sites (e.g. a university course blog network), they will notice this absence. To add another complication, BuddyPress redirects wp-signup.php to the network homepage, meaning the default WordPress Network mode method for creating a new site is broken (UPDATE: track this issue here). Luckily both of these are easy to fix.

<?php
/*
** The following adds a link to "Create a new site" under "My Sites" menu
*/
function admin_bar_create_blog_link(){
     global $wp_admin_bar;
     $create=get_site_url( BP_ROOT_BLOG ).'/blogs/create/';
     $wp_admin_bar->add_node( array(
          'parent' => 'my-sites',
          'title' => 'Create a new site',
          'href' => $create) );
}
add_action('wp_before_admin_bar_render','admin_bar_create_blog_link');
 
/*
** The following fixes the dashboard link for "Create a new site"
** By default, WordPress sends the user to wp-signup.php to create a site
** But wp-signup.php is redirected to the network homepage by BuddyPress as of 3.1+ and 1.5.3+ respectively
** This just filters that core behavior to use the BuddyPress link instead
*/
add_filter('wp_signup_location', 'bp_blog_creation_link');
function bp_blog_creation_link($old) {
     if (function_exists('bp_include'))
     return get_site_url( BP_ROOT_BLOG ).'/blogs/create/';
}
?>

Feel free to make additional suggestions in the comments.

]]> http://jeffersonsnewspaper.org/2012/tips-for-using-the-wordpress-admin-bar-with-buddypress/feed/ 6 Migrating from ContentDM to Omeka http://jeffersonsnewspaper.org/2011/migrating-from-contentdm-to-omeka/ http://jeffersonsnewspaper.org/2011/migrating-from-contentdm-to-omeka/#comments Wed, 14 Sep 2011 13:47:46 +0000 E. Bell http://jeffersonsnewspaper.org/?p=423
Seems like the Omeka forums get a lot of traffic from people looking to migrate from ContentDM to Omeka. I, personally, get inquiries about this all the time (for some unknown reason). So I figured I may as well share what I know about the process here so I can just send a link or you can find it on Google or whatever.

It’s worth noting at the outset that I don’t know anything about generating ContentDM export files (partially because even the ContentDM documentation is proprietary, or at least hidden behind a login). But I do know that every time someone has sent me a cDM export file, it is in tab-delimited format (UPDATE: here is the Tab-delimited export documentation), which is basically a plain text spreadsheet. I gather these spreadsheets can be produced pretty easily so I think we can start by assuming you already have the spreadsheet and need to prep it for import into Omeka, which will be done in this tutorial using the CSV Import plugin. If you are not already familiar with how that plugin works, check out the documentation page at Omeka.org before continuing.

You probably need to use Excel

First, open the tab-delimited spreadsheet in Microsoft Excel. You will later save this file in CSV format. If you prefer using non-MS spreadsheet software, you are probably out of luck. As far as I know, neither OpenOffice/LibreOffice nor Apple’s Numbers have an equivalent ‘Text-to-Columns…’ functionality, which will be used in this process.

Remove unwanted and problematic rows/columns, Rename column headers

Once you have your spreadsheet open in Excel, go ahead and remove any ContentDM-specific administrative metadata, or anything else you don’t wish to carry over to Omeka during the migration. At this point, you should probably rename the column headings to something meaningful. This will help with the crosswalk step later.

Breaking out semicolon-delimited values

Next, you will want to check for columns having multiple entries within a single cell. At the very least, this will probably include the Subjects column (because archivists/librarians are never satisfied with assigning just one subject term… subject classification being the Lay’s potato chip of librarianship). By default, these multiple subjects will be separated by a semicolon (e.g. “Librarianship — Potato Chip Analogies; Librarianship — Puns; Librarianship — Personality Disorders;” ). Instead of copying each one of these entries into a new Subjects column, you can just use the “Data > Text to Columns…” feature in Excel. I recommend using a separate worksheet for this step as the new columns will overwrite your existing ones if you are not careful.

Getting the File Path URLs

So you’ve shaped up all the metadata on the spreadsheet. Now you need to define the path to the item file in ContentDM. This is probably the trickiest part to come up with on your own, especially if you are not so familiar with ContentDM. Basically, our starting point will be the cDM “Reference URL.” Those look something like this: http://images.ulib.csuohio.edu/u?/press,59. Assuming you have a whole column of Reference URLs, you need to run a Find and Replace to create your file path (again, I recommend doing this in a separate worksheet so you don’t accidentally overwrite important data). Let’s begin.

UPDATE: in ContentDM version 6+, ShowFile is replaced by GetFile. Adjust the following instructions as needed (i.e. in the first Find and Replace, swap out showfile.exe with getfile.exe).

Start with something like:
http://images.ulib.csuohio.edu/u?/press,59

FIND this:
u?/
… and REPLACE with this:
cgi-bin/showfile.exe?CISOROOT=/

Next, FIND this:
,
…and REPLACE with:
&CISOPTR=

So now we have something that looks like:
http://images.ulib.csuohio.edu/cgi-bin/showfile.exe?CISOROOT=/press&CISOPTR=59

This is a working file path that can be used by the CSV Import plugin to ingest the item file along with the metadata record.

In some instances, you might need to tweak this process. For example, if your ContentDM installation includes JP2 or TIF files (or some other unfriendly image format) but you don’t want the hassle of building a custom display wrapper into your Omeka theme, you can append some additional query string parameters to your file URL.

So if you want ContentDM to serve up a JPG instead of a JP2 (or other…) file, add this to your file column
&DMSCALE=100.00000&DMWIDTH=1600&DMHEIGHT=1600&DMX=0&DMY=0&DMTEXT=&REC=1&DMTHUMB=0&DMROTATE=0
…using this Excel function (where A2 is the first column/cell in need of appending):
=CONCATENATE(A2,"&DMSCALE=100.00000&DMWIDTH=1600&DMHEIGHT=1600&DMX=0&DMY=0&DMTEXT=&REC=1&DMTHUMB=0&DMROTATE=0")

Finally, you need to swap showfile with getimage in the file URL above by running one more find and replace in Excel.

So now, your file path looks like:
http://images.ulib.csuohio.edu/cgi-bin/getimage.exe?CISOROOT=/press&CISOPTR=59&DMSCALE=100.00000&DMWIDTH=1600&DMHEIGHT=1600&DMX=0&DMY=0&DMTEXT=&REC=1&DMTHUMB=0&DMROTATE=0

This will return a JPG file, which is pretty handy. These additional parameters will vary by installation and file type. I don’t know what all of the parameters are or even what each one does; only that this usually works. Again, this is a case where actual ContentDM documentation would be really handy. UPDATE: Keep in mind that this only works with image file types. For more details, check out the GetImage documentation.

Metadata Crosswalk

It’s usually a good idea to plan out your metadata crosswalk in advance, especially if you have multiple export files (and you should if your collection is bigger than a few hundred items; more on that later). Remember that Omeka – out of the box – only uses the first 15 Dublin Core elements. You may need to add a new Item Type or install Dublin Core Extended in order to find/create an appropriate home for your legacy/custom metadata in Omeka.

Batching

To avoid server timeouts, you should consider breaking your spreadsheets into manageable batches. I try not to import more than a few hundred items at a time, and even then one of the two servers involved is likely to timeout or throw an error or something. Keeping the batches small makes it easier to isolate problems, avoid import errors, and undo problematic imports.

Using the CSV Import Plugin

From here, just follow the standard instructions for using the CSV Import plugin.

Bugs, Known Issues, and Limitations

As of version 1.3, there are still some quirks. For example, your file path – that hideous long URL you worked so hard to create – will become the actual name of your imported/migrated file. In some instances, your files may be ingested sans file extension (e.g. .pdf, .jpg, .mp3), which can cause various headaches (though it’s worth noting that these files will generally display inline on your site, due to the way most Omeka themes handle media files, and will only break down when someone tries to download the file, in which case they would need to manually add the file extension). From time to time, you could have an import that hangs indefinitely, never finishing and never failing — and thus not easily “undo-able” (at least, the “Undo Import” button will not be visible). In such a case, you can manually create that button by entering the following URL pattern into your address bar:

http://[PATH TO YOUR OMEKA INSTALLATION]/admin/csv-import/index/undo-import/id/[IMPORT ID]

– this is on the plugin documentation page by the way, as are several other points in this tutorial.

One of the biggest limitations of the CSV import strategy is that you will probably have issues migrating compound objects and other multi-file items, primarily because of the way ContentDM formats the export file and serves compound objects online and partially due to limitations in the way the plugin works with Omeka. Basically, you need all the files for an item to be in the same row as all of the other item-level metadata (e.g. in columns like “File 1,” “File 2,” “File 3,” etc). And there is currently no way to use the CSV Import plugin to assign file-level metadata. For example, if you had a postcard in your ContentDM collection and it had distinct metadata for each side (say, for front.jpg and verso.jpg), along with general metadata for the object as whole, something is going to be lost in the migration without some serious elbow grease.

The Omeka Dev forums are the best place to report bugs, inquire about error messages, discuss workarounds, and submit patches. The general Omeka Forums are also great for more basic questions; happily, most questions get answered in fairly short order. Please do not post support questions here. Please do, however, feel free to leave general comments, suggestions for improvement, requests for clarification, etc.

IMAGE NOTE: poorly Photoshopped post image contains assets by multiple artists and designers, including the amazing “Bob” sketch from Matt Haley’s unreleased but totally awesome sounding Twin Peaks: Season 3 graphic novel.

]]> http://jeffersonsnewspaper.org/2011/migrating-from-contentdm-to-omeka/feed/ 4 Acronyms and Initialisms My Library Degree Failed to Teach http://jeffersonsnewspaper.org/2011/acronyms-and-initialisms-my-library-degree-failed-to-teach/ http://jeffersonsnewspaper.org/2011/acronyms-and-initialisms-my-library-degree-failed-to-teach/#comments Sat, 26 Mar 2011 08:38:21 +0000 E. Bell http://jeffersonsnewspaper.org/?p=886 I’ve been told many times since completing my M.L.I.S. that most skills related to library and archival work are developed on the job.  In fact, I realized about halfway through my degree program that my professional training would continue well after grad school. Not unlike other professional-academic hybrid programs, library school provided a sufficient foundation, but the bigger challenges and learning experiences came during my practicum and in my daily work, as well as in the various (un)conferences and workshops I’ve attended and professional development courses I’ve elected to take since graduation.  In many ways, this suits the overall learning style and personality of the “typical” librarian or archivist (without getting onto a tangent, I think it’s safe to assume that most librarians would consider themselves to be relatively eclectic and prolific learners).  Generally, this approach to learning is indeed a very comfortable one for me.  While I enjoyed the rich academic world of the humanities as an undergrad – exploring ideas through research, reading and writing – library and information science requires a higher degree of  hands-on experience and purposeful technical training.  Sure, LIS programs include conventional graduate reading seminars, research papers, etc. But unlike, say, history, where a historian-in-training may expect to use and hone these skills over the course of a long career in scholarly research and writing, the average librarian or archivist will not be publishing books, writing for academic journals, or conducting original research.  Information professionals certainly need an academic, scholarly background, but I’m not sure I consider them (us) to be academics or scholars in the usual sense.  We have too many responsibilities, too many constituencies, too many rules and protocols, and too many acronyms and abbreviations.

Though we know information work is highly technical, it seems most library and information science programs are not — even when the faculty are involved in cutting edge technical research.  The programs are relatively short, culminating after just 1-2 years — not much time, especially considering that, unlike most other graduate programs, LIS students are generally starting from scratch with degrees in unrelated fields.  As such, the curriculum is broad but mostly shallow, save for some specialized tracks and doctoral programs. The following is my shortlist of abbreviations and acronyms that I’ve come to view as important to my work in public/digital history, digital humanities, and educational technology.  I don’t work in a library exactly, but I know firsthand that many of these are also important in that setting as well.

 

API
Application Programming Interface
APIs connect different platforms and programs, most often via established functions and methods.  Twitter, Facebook, Flickr, Google and many other web services provide open APIs that allow you to embed, feed, and connect with their services on your own site or application.  Operating systems, content management systems (WordPress, Drupal, dSpace, etc.), game engines, and programming languages (Ruby on Rails, jQuery, etc.) all have APIs that allow programmers to tap into, customize and extend functionality.

 

XML
eXtensible Markup Language
XML is the core of several languages, tool, and protocols used in digital archives, digital humanities, and general web development.  In my experience, it is kind of a bear to work with, but is nonetheless worth investigating as it is the basis of RSS, EAD, and TEI, among others familiar to M.L.I.S.s.

 

JSON
JavaScript Object Notation
JSON is a lightweight, language-independent data interchange format, billed as “The Fat Free Alternative to XML.” I’ve never worked with it, but probably will at some point.

 

OOP
Object Oriented Programming
Okay, well, I’m listing OOP here as a placeholder for various programming languages, some of which are not, strictly speaking, object-oriented by definition. The point is that, while I was introduced to HTML and CSS for the first time in an elective grad school workshop, there’s really not that much you can do with those tools alone. Static webpages have limited use these days. Most libraries, archives, and digital humanities projects need someone who understands – or better, can do – programming/scripting on some level. The languages listed below are probably the most commonly used in the field, though as more projects start to involve mobile app development, Objective-C (iPhone) and Java (Android) will also be in demand.

 

LAMP
Linux Apache MySQL Perl/PHP/Python
Basically, a LAMP server is composed of several open source components, including MySQL for database service, Apache as the HTTP server, and pre-installed “P” programming languages (Perl/PHP/Python) running on some variety of Linux operating system. This LAMP “stack” is the basis of most sites on the web today.

 

SQL
Structured Query Language
SQL, and particularly MySQL, is one of the most common relational database platforms in use on the web today. As part of the open source LAMP stack, it is available on nearly all web servers by default and forms the underlying data structure for most open source content management systems.  In recent years, a variety of alternative platforms have emerged under the banner of NoSQL, sparking some amusing yet mostly incomprehensible (to me) debate.

 

DCMI
Dublin Core Metadata Initiative
A metadata schema for describing “physical resources such as books, digital materials such as video, sound, image, or text files, and composite media like web pages.” It is often said that Dublin Core is “capable of describing anything, though not particularly well.” Still, a good place to start.  Like the two metadata standards that follow, it is often used in conjunction with some type of XML. I’m listing just a few here but there are many others one might add to this list.

 

METS
Metadata Encoding and Transmission Standard
Another metadata standard “for encoding descriptive, administrative, and structural metadata regarding objects within a digital library” using XML.

 

DACS
Describing Archives: A Content Standards
And another metadata standard “for describing archives, personal papers, and manuscript collections.”

 

DMCA
Digital Millennium Copyright Act
Understanding copyright legislation is essential for many projects in libraries, archives, education and digital publishing.  I name DMCA here mainly because it’s an abbreviation and thus fits into the scope of this post. It is difficult to imagine a web consisting only of the publisher’s own original content. Today we share, link, quote, and remix content created by others as part of our daily routines. Scholars post research material for students; archivists post manuscripts for researchers; librarians share book reviews; students and other user communities contribute to projects by uploading content. While most institutions have a copyright policy, it’s important that it be kept up to date, both for the organization’s protection, but also for the protection of our collective legal rights. If we take a casual view of copyright, we risk legal action on one end and the forfeiture of our power on the other. A large part of DMCA applies specifically to Digital Rights Management software (DRM) and the legality of circumventing it. Archivists of film, videogames, music and other commonly DRM’ed material obviously have something at stake here.

 

General Resources

 

This list may seem overwhelming.  I wrote it and it overwhelms me, even two years out of grad school. And it’s not even comprehensive. But you have to start somewhere.

My progression from HTML newb only a couple years ago to, well, a newb of several additional, more difficult things, came by way of hacking WordPress.  I’m sure this is quite common. There are plenty of other ways to learn a programming language, but from what I can tell the key factors are always going to be necessity and specificity. If your motivation is to complete a specific project (regardless of languages involved), you will be far more likely to succeed and learn something than if you are simply trying to grasp the language itself in an abstract, academic way. I have a book on Objective C sitting on my shelf, but until I need to complete a real life project with Objective C, I probably won’t get much further than “Hello World!.” Find an actual need to develop these skills and you will probably make some progress. If nothing else, you will discover along the way all the things you don’t know, which is also helpful.

Another important thing to remember is that you will almost never be working from scratch. When you plan out a project, find something to serve as a solid foundation.  It may be a document to use as an example, a description of an existing project, an open source code base, or  some other fundamental element that almost fits your needs perfectly, and then figure out what needs to change to make it your own. As you go deeper and begin to produce your own content, this will seem less like copying and more like learning from and contributing to a community of practice.

Just to be clear, I want to close in defense of my education and alma mater (to which I will always be true or whatever). I was taught of these things (well, some of them), but not in any great detail; something that would be near impossible in the context of a broad-based 1-2 year LIS program.  It’s worth noting that I was in a generic public library track and may have learned more about these issues in a more specialized setting.  I also should clarify that I’m hardly an expert in most if any of these topics and languages; there may be some better resources and explanations out there so please share in the comments and/or via twitter.

What was/has been your experience with your MLIS program?  Did/do you feel prepared for a professional position coming out of grad school?  What would you add to this list?

]]> http://jeffersonsnewspaper.org/2011/acronyms-and-initialisms-my-library-degree-failed-to-teach/feed/ 3 The Brief Etymology of a Gay Bash http://jeffersonsnewspaper.org/2009/the-brief-etymology-of-a-gay-bash/ http://jeffersonsnewspaper.org/2009/the-brief-etymology-of-a-gay-bash/#comments Thu, 21 May 2009 21:55:19 +0000 E. Bell http://jeffersonsnewspaper.org/?p=179 I went to library school because I am what some people call “intellectually restless” – constantly moving from one interest to the next.  Honest people call this phenomenon by other names, such as “uncommitted,” “easily distracted” or “lazy,” but I prefer the more aristocratic “intellectually restless.” In any case, given my training and varied interests, I will occasionally pose imaginary questions on this site to give myself micro-research and reference problems. Please feel free to submit a real question and I’ll do my best to answer, and provide citations to any relevant digital sources (sorry, I will not read or find books in your library).

The inaugural Jefferson’s Newspaper Reference question was submitted by the curious 13 year old Latino boy that lives in my subconscious.  His name is Martin.  Martin asks, “What’s the deal with the word maricón?  Why does it mean gay?”

Martin, let me tell you right now, I will be using Wiktionary.  Deal with it.

Maricón is derived from marica, the Spanish language word for magpie – an Australian bird.  The base of the word is Maria or Mary (the English word magpie is derived from another variation of Mary, Margaret), with the addition of the suffix -ica, which is diminutive and often derogotory.  In other words, maricón translates into both “littly Mary” and “little bird.”

If you’re into gay bashing and/or Spanish language insults, this may come as no surprise.  Mary is another slang word used to describe gay men — most often used by gay men.  Gay men are also often referred to in terms that suggest aviation — fairy, for example, or another Spanish language word, pajarito, which has a couple connotations.  Pajarito is a diminutive form of pájaro, meaning bird or sometimes parrot.  In Spain, Guatemala, Mexico, and Venezuela, pájaro also means penis.  Thus, pajarito means both little bird and little penis.  Another double whammy.

Now, why are homosexuals so often equated to tiny virginal flying peckers?  I have no idea.  It’s very uncool and someone should get to the bottom of it.

But back to the question.  I promised a solid source to Martin, and my Wiktionary-gleamed musings are not going to cut it.

In Marginalization of alternative gender and sexual identities: The role of normative discursive practices in Chilean society (2005), linguist Sara Balder describes use of the term as such:

A diachronic approach shows that maricón is derived from the proper name Maria. Accordingly, this female origin qualifies the term to connotatively recall feminine gender attributes such as weakness and submissiveness.  Another parallel is that the term indicates submission not only in the social sense, but also in the sense of sexual passivity.  In practice, this term is polysemous, and is primarily used to denote an effeminate and/or homosexual male, making it roughly synonymous with ‘effeminate sodomite’.  I will refer to this primary meaning as (maricón 1).

Additionally, this term can also be used secondarily in reference to a bad, wretched, or harmful person (maricón 2).    The relationship between these two senses can be best explained by the chaining approach (see Lakoff 1987), whereby maricón2  developed as a derivative of some of the characteristics of maricón 1.  The characteristics, specifically, are those that give maricón 1 its negative connotation: maricón 1, which denotes an effeminate homosexual male, is connotatively negative in that homosexuals are considered bad, wrong, weak, deviant, and contemptible by dominant society.  The chaining involved in the relationship of maricón 1 to
maricón 2 can be conceptualized as such:

maricón 1: effeminate passive
homosexual male
↓
effeminacy, passivity, and homosexuality
are bad, deviant, and wrong
↓
a maricón is a bad, deviant person
who commits wrongful acts
↓
maricón 2: a bad, wretched,
or harmful person

The resultant polysemous outcome is that a term used for homosexuals can also be used for other people who are disreputable, odious wrongdoers (maricón 2), even if they have normative gender and sexual orientation.

Read the full text here [PDF].  No mention of magpies, though.

Maricón In the News:  Bill Richardson uses the term on the Don Imus Show, hampering his presidential bid and dampening his reputation as a strong supporter of gay and lesbian rights (2007): link

Maricón In the History: Fidel Castro, preeminent among gay-bashing jerks, allegedley sent his pal, writer Gabriel Garcia Marquez, to leaders of both Panama and Spain with one brief spoken message: “Dice Fidel que usted es un maricón” (“Fidel says you are a faggot”): link (hover for citation)

]]> http://jeffersonsnewspaper.org/2009/the-brief-etymology-of-a-gay-bash/feed/ 10