Category Archives: web sites

website to jekyll

While my research diary has stalled out because I haven’t been researching (other than some administrative tasks like collecting and organizing article PDFs, and typing notes into Mendeley), I have made some progress on updating my website.

Specifically, I have switched over to using Jekyll, which is software that converts markdown/HTML and SASS/CSS to static web pages. Why do I want to do it? Because I want to have a consistent header and footer (navigation and that blurb at the bottom of every page) across the whole site, but don’t want to manually edit every single file every time I update one of those, or update the site structure/design. I also didn’t want to use PHP because then all my files will be .php and on top of it, it feels messier. I like static HTML a lot.

I’m just writing down my notes here for others who might want to use it too. I’ve only found tutorials that talk about how to publish your site to GitHub Pages. Obviously, I have my own hosting. I also already had a full static site coded in HTML and CSS, so I didn’t want to start all over again with markdown. (Markdown is just a different markup language from HTML; from what I can tell, you can’t get nearly the flexibility or semantic markup into your markup documents that you can with HTML, so I’m sticking with the latter.) I wondered: all these tutorials show you how to do it from scratch, but will it be difficult to convert an existing HTML/CSS site into a Jekyll-powered site?

The answer is: no. It’s really really easy. Just copy and paste from your old site into some broken-up files in the Jekyll directory, serve, and go.

I recommend following the beginning of this tutorial by Tania Rascia. This will help you get Jekyll installed and set up.

Then, if you want a website — not a blog — what you want to do is just start making “index.html”, “about.html”, folders with more .html files (or .md if you prefer), etc., in your Jekyll folder. These will all be generated as regular .html pages in the _site directory when you start the server, and will be updated as long as the server is running. It’ll all be structured how you set it up in the Jekyll folder. For my site, that means I have folders like “projects” and “guides” in addition to top-level pages (such as “index.html”).

Finally, start your server and generate all those static pages. Put your CSS file wherever the head element wants it to be on your web server. (I have to use its full URL, starting with http://, because I have multiple folders and if I just put “mollydesjardin.css” the non-top-level files will not know where to find it.) Then upload all the files from _site into your server and voilà, you have your static website.

I do not “get” Git enough yet to follow some more complicated instructions I found for automatically pushing my site to my hosting. What I’m doing, and is probably the simplest but just a little cumbersome solution, is to just manually SFTP those files to my web server as I modify them. Obviously, I do not have to upload and overwrite every file every time; I just select the ones I created or modified from the _site directory and upload those.

Hope this is helpful for someone starting out with Jekyll, converting an existing HTML/CSS site.

#dayofDH Japanese digital resource research guides

Another “digital” thing I’ve been doing that relates to the “humanities” (but is it even remotely DH? I don’t know), is the creation of research guides for digital resources in Japanese studies of all kinds, with a focus on Japanese-language free websites and databases, and open-access publications.

So far, I’ve been working hard on creating guides for electronic Japanese studies resources, and mobile apps easily accessible in the US for both Android and iOS that relate to Japanese research or language study. The digital resources guide covers everything from general digital archives and citation indexes to literature, art, history, pop culture, and kuzushiji resources (for reading handwritten pre- and early modern documents). They range from text and image databases to dictionaries and even YouTube videos and online courseware for learning classical Japanese and how to read manuscripts.

This has been a real challenge, as you can imagine. Creating lists of stuff is one thing (and is one thing I’ve done for Japanese text analysis resources), but actually curating them and creating the equivalent of annotated bibliographies is quite another. It’s been a huge amount of research and writing – both in discovery of sources, and also in investigating and evaluating them, then describing them in plain terms to my community. I spent hours on end surfing the App and Play Stores and downloading/trying countless awful free apps – so you don’t have to!

It’s especially hard to find digital resources in ways other than word of mouth. I find that I end up linking to other librarians’ LibGuides (i.e. research guides) often because they’ve done such a fantastic job curating their own lists already. I wonder sometimes if we’re all just duplicating each other’s efforts! The NCC has a database of research guides, yes, but would it be better if we all collaboratively edited just one? Would it get overwhelming? Would there be serious disagreements about how to organize, whether to include paid resources (and which ones), and where to file things?

The answer to all these questions is probably yes, which creates problems. Logistically, we can’t have every Japanese librarian in the English-speaking world editing the same guide anyway. So it’s hard to say what the solution is – keep working in our silos? Specialize and tell our students and faculty to Google “LibGuide Japanese” + topic? (Which is what I’ve done in the past with art and art history.) Search the master NCC database? Some combination is probably the right path.

Until then, I will keep working on accumulating as many kuzushiji resources as I can for Penn’s reading group, and updating my mobile app guide if I ever find a decent まとめ!

ruins – the past, the real, the monumental, the personal

Did I ever tell you about one of my favorite buildings in the world? It’s a public housing project named Kaigan-dori Danchi 海岸通り団地 (not to be confused with the type of projects one finds in the US, it was perfectly desirable housing in its time). This particular danchi (“community housing” or – generally public – housing project) was located smack in the middle of the richest section of Yokohama, between Kannai and Minato Mirai, perhaps one of the richest areas of the Tokyo region. Here it is in all its dirty, dirty glory, with Landmark Tower in the background.

Yes. This is Kaigan-dori Danchi, one of the grossest “ruins” (haikyo 廃墟) I had ever seen. Or, I thought it was a ruin. You know, an abandoned building. Because it looked too much like a shell to be anything else.

Then I got a message on Flickr.

In it, the messager wrote that he grew up in Kaigan-dori Danchi and now lives in New York City. He advised me that yes, it’s still inhabited, and thanked me for putting so many photos of it on Flickr. (Yes, I went for a photo shoot of this complex, more than once – hey, it was on my walk home from school!) He felt nostalgic at seeing his boyhood home and was interested to see what it looked like now.

In other words, what I’d felt vaguely strange about as some kind of ruins voyeurism – the same kind of ruins porn that takes hold of nearly everyone who wants to take photos of Detroit, for example – turned out to be a two-way street. It wasn’t pure voyeurism; it was a way to connect with someone who had a direct experience of the past of this place, a place that was still alive and had a memory and a history, rather than being some monstrosity out of time – as I’d been thinking of it. I saw it as a monument, not an artifact.

So this was in 2008, a half year after I’d become obsessed with Japanese urban exploration photography, which was enjoying a boom in the form of guidebooks, a glossy monthly magazine, calendars, DVDs, tours, photo books, and more, in Japan at the time. (Shortly thereafter, and I CALLED IT, came the public housing complex boom. I do have some of the photo books related to this boom too, because there’s nothing I love more than a good danchi.)

As part of the research for a presentation I gave on the topic for my Japanese class at IUC that year, I’d done some research into websites about ruins in Japan (all in Japanese of course). These were fascinating: some of them were just about the photography, but others were about reconnecting with the past, posting pictures of old schools and letting former classmates write on the guestbooks of the sites. There was a mixi (like myspace) group for the Shime Coal Mine (the only landmark of the first town I’d lived in in Japan). The photo books, on the other hand, profoundly decontextualized their objects and presented them as aesthetic monuments, much the way I’d first viewed Kaidan-dori Danchi.

So I wonder, with ruins porn a genre in the United States and Europe as well, do we have the same yearning for a concrete, real past that some of these sites and photographers exhibit, and not just vague nostalgia for the ruins of something that never existed? How much of ruins photography and guidebooks are about the site in context – the end point of a history – and how much is just about “hey I found this thing”? How much of this past is invented, never existed, purely fantasy, and how much of it is real, at least in the minds of those who remember it?

These are answers I don’t yet have, but I’ve just begun on this project. In the meantime, I’m happy to share Kaigan-dori Danchi with you.

fans, collectors, and archives

In the course of my research, I’ve been studying the connection between the first “complete works” anthology of writer Ihara Saikaku, his canonization, and the collectors and fans who created the anthology – a very archival anthology. (I say this because it has information about the contemporary provenance of the texts that make it up, among other things. It names the collector that contributed the text to the project on every title page!)

It’s struck me throughout this project that the role of fans – which these people were – and their connection with collectors, as well as their overlap, is of crucial importance in preserving, in creating archives and maintaining them, in creating resources that make study or access possible in the first place. They do the hard work of searching, finding, discovering, buying, arranging, preserving, and if we’re lucky, disseminating – through reprinting or, now, through making digital resources.

As I’ve become more acquainted with digital humanities and the range of projects out there, I can’t help but notice the role of collectors and fans here too. It’s not so much in the realm of academic projects, but in the numbers of Web sites out there that provide images or other surrogates for documents and objects that would otherwise be inaccessible. These are people who have built up personal collections over years, and who have created what would otherwise be called authoritative guides and resources without qualification – but who are not academics. They occupy a gray area of a combination of expertise and lack of academic affiliation or degree, but they are the ones who have provided massive amounts of information and documentation – including digital copies of otherwise-inaccessible primary sources.

I think we can see this in action with fandoms surrounding contemporary media, in particular – just look at how much information is available on Wikipedia about current video games and TV shows. Check out the Unofficial Elder Scrolls Pages and other similar wikis. (Note that UESP began as a Web site, not a wiki; it’s a little time capsule that reflects how fan pages have moved from individual labors of love to collective ones, with the spread of wikis for fan sites. A history of the site itself – “much of the early details and dates are vague as there are no records available anymore” – can be found here.)

I’m not a researcher of contemporary media or fan culture, but I can’t help but notice this and how little it’s talked about in the context of digital humanities, creating digital resources, and looking at the preservation of information over time.

Without collectors like Awashima Kangetsu and fans like Ozaki Kōyō and Ōhashi Otowa, we may not have Ihara Saikaku here today – and yet he is now among the most famous Japanese authors, read in survey courses as the representative Edo (1600-1867) author. He was unknown at the time, an underground obsession of a handful of literary youths. It was their collecting work, and their dedication (and connections to a major publisher) that produced The Complete Works of Saikaku in 1894, a reprinted two-volume set of those combined fans’ collections of used books. Who will we be saying this about in a hundred years?

For my readers out there who have their feet more in fandom and fan culture than I do, what do you think?

new magazine: yū

I came across a new magazine online recently that, as always, makes me wish I were still in Japan so I could grab a copy of myself. It’s called Yū 幽, or spirit in my translation – and by spirit I mean the supernatural.

In case you can’t guess, it’s all about the supernatural and ghostly, and is your typical “literary” magazine in Japan – some fiction (short enough for a single issue, usually), plus essays and other relevant short non-fiction. When in Japan (and now, through my sizeable collection of back issues) I consumed these kinds of magazines regularly. I would say voraciously, but it makes for some somewhat slow reading given that it’s literary fiction not in my native language. Still, I love magazines, and I love this type in particular. (Some of my favorites in Japan are Bungakkai and Yom Yom.)

Best of all, Yū has a fantastic web site: Web Yoo. It has a number of blogs, including by authors that write for the magazine, about related books, and ones that have news about current and upcoming issues. They even have their own supernatural fiction prize, 幽怪談文学賞. (Never quite sure how to translate that one; I like to use “weird” as in “weird tales” of the early 20th century here in the US.)

Please check it out, especially if you’re in Japan and can get ahold of it. At the very least, you’ll be treated to great content and some seriously fantastic images and typography on the web site.

android slashdot reader: 和英コメントで言語学び!

Now that I have an Android phone and have found some pretty great things on the Android Market for getting ahold of Japanese content, I would like to start sharing with you all what I’ve been using and whether it’s worth downloading.

First up is my favorite new find: Slashdot Reader. Yeah. It’s an RSS feed reader for Slashdot. Why so great?

Well, can you imagine my reaction when I read its description and saw images of posts from slashdot.org and slashdot.jp showing up all mixed in together? Then I read the description: “just a feed reader, nothing more” – for both Japanese and English Slashdot.

It’s like I found an app made by my doppelganger. Really.

If you don’t want one or the other of the languages, it allows you to toggle both, Japanese only, and English only.

Because it’s a feed reader, you only get the headlines and leads from Slashdot, but can easily click through to the full story, and therein lies the amazing language learning tool that somehow never really occurred to me.

All of these years, I could have been learning Japanese through Slashdot comments! That’s right. Of course it’s not textbook Japanese. I already know how trolls (荒らし) talk after just a minute or two of reading. How nerds talk. (They always use が and never けど, although they do use ね sparingly for emphasis. A certain language teacher from several years ago who forbid us from using けど in class for an entire semester would be proud.) And how random users talk.

I also know how they’re basically saying exactly the same things that commenters do on Slashdot in English, only they’re saying it in Japanese. (open source != free as in beer, anyone? I seriously just read this. 無償 is free as in beer, and note that it’s not the same as the widely-used word for “free” 無料 – so I just learned something new about software licensing.) So if you’re a Slashdot reader, this is going to help you immensely. It’s all about context.

Yes, so there are people out there who would disparage the idea of learning language from internet comments. But I counter that with: it’s real language! And this is a specific forum where you know what is coming: some nerdspeak, some posturing, some trolls, some reasonable people, talking about a rather limited set of topics. So you are going to learn voices, not just “Japanese.” You are going to learn what people say in a certain situation, and also what not to say. I can’t think of anything more helpful than that!

And here you go: Slashdot Reader for Android (this takes you to Android Market).

in which I acquire typographical empathy

Guys. I humbly apologize for forcing you to read monospace font of your browser’s (or OS’s) choice for the past year. I’ve learned the error of my ways.

From now on it’s serif all the way.

And I now supply Linux font defaults just in case, which I didn’t before out of ignorance. At least there’s something to try to fall back on before font-family: serif now.

mac woe update: adobe drops flash for PPC

Sigh.

This article talks about much of my last post, with the focus not on Google Apps but on Adobe Flash: “Adobe Flash Has Left PowerPC Macs Behind

The reason I’m linking to this piece is that it makes an excellent point about “obsolete” PowerPC Macs (and even Intel Macs) not being so obsolete relative to their PC counterparts, but made so by Apple’s hardware decisions. Given that I haven’t owned a PC for at least 9 years, I had nothing to compare to, but this author points out that Apple dropping support for its older hardware sends perfectly good Macs to an early grave despite having the same or even better performance for still-supported older PCs.

On the Power Mac G5 and PowerBook G4:

While these highly capable PowerPC machines meet or exceed the Windows-based minimum hardware specifications required for the latest release of Flash Player, it matters not. Progress in the world of Mac OS X tends to make Apple hardware obsolete much faster than comparable Windows computers released in the same time frame.”

“I’m simply dumbfounded that fully capable PowerPC Macs continue to lose support and functionality with so many things that similarly aged (and often far older) Intel machines still receive” – as am I! Because I did not know that older Intel machines were supported for so long. Then again, this author makes the excellent point that support is being dropped for OS 10.4 but still retained for Windows XP.

It also makes me remember my general policy of “if it’s old and getting too slow, put Linux on it” because a Linux install will usually make most of the problems of an older Windows box magically go away. Indeed, Linux on older hardware is a good thing: but where is the support for older PowerPC platforms? In comparison, it isn’t really there.

It’s really too bad to see the end of this era. First the Dreamcast (an excellent RISC console that also runs Linux), now the Mac PPC line. It’s not that Intel/AMD architecture is superior: it’s just so common that it’s simpler to drop support for anything else. Unless there is another explanation?

google dropping app support; molly has PPC angst

A decision I made over five years ago has ended up making me quite unlucky these days.

iBook G4 photo

I intentionally bought a PowerPC Mac, the iBook G4, when my iBook G3 succumbed to the infamous logic board defect a year or so after Apple stopped fixing it for free. My first winter semester at Michigan had just started, so I was stuck: I needed the data from my G3’s hard drive even more than I needed a computer, and I knew that Apple would soon drop PowerPC in favor of Intel. Like the idealist I can be, I went for the PowerPC instead of waiting a while for the new hardware, because after taking some computer architecture courses and having done a little assembly programming, I had come to the conclusion that RISC architecture is superior to CISC – meaning that I favored PowerPC over Intel.

Little did I know how ghettoized the PowerPC is out there in the real world. Naive, I had no idea that most operating systems and software are not ported to PowerPC – not even Linux.** In the first few years this wasn’t a problem and wasn’t anything I noticed beyond having a matte screen instead of a shiny one. I still love my G4, with its plucky reliability and long battery life.

Starting about last year, however, more and more software makers dropped PowerPC completely, as OS X only went up to version 10.4.x on PowerPC and many required 10.5, which is Intel-only. Even the software that is still released for 10.4 stopped supporting my laptop, including OpenOffice.***

I resigned myself to having a laptop that is circa 2009 in terms of what it runs. I am okay with running a Japanese version of OpenOffice 3 that will open .docx files for me, and running Adobe CS3 and Word 2004. Honestly, I don’t need the newer versions of these programs for a base model iBook that only has 40GB of hard drive space. What I need is the reliability, toughness, and 5 hour battery life (with the ability to buy new batteries) that my 5 year old friend provides. I have a desktop for everything else!

I have a sinking feeling about it now, though. We have a problem. Google is going to gradually drop support for older browsers, which includes pretty much every browser that I can download for my PPC Mac. While I applaud their strict use of HTML5 (I use it too!) and refusal to cater to legacy browsers that don’t understand it, I realize that I am basically screwed. And how much I rely on Google, frankly.

Here are things I would like to use a laptop for: Web browsing, Gmail, Google Docs, a little word processing, PDF reading and editing, writing, and possibly a little Photoshop. And some Twitter. If I suddenly can’t access or use Gmail or Google Docs, that is a huge blow to using my laptop to be productive – it’s the point of carrying something around that will let me access my files remotely to begin with!

“Get a MacBook,” a voice pleads in my head. They are so shiny, fast, small, and nice. They’re still only 13″ but have a wide screen that makes it seem so much bigger than the 12″ iBook. They have long battery life. I’m kind of in love with them despite myself. Admittedly, I resent the non-removable battery that will allegedly last for the average life of a laptop. But if I wasn’t suddenly losing all software support for my peculiar architecture, I wouldn’t even consider a new laptop.

I just bought the laptop a new battery. It has 5 hours of battery life, does everything I need it to, and is very hardy. It’s relatively small, light, and convenient. It has some very expensive software on it. Most importantly, it simply still works fine and has nothing wrong with it. I abhor wasting things. I am fond of this laptop. If it weren’t for the uncertain nature of old hard drives and impossibility of replacing that without breaking the case, I’d argue that it probably has many years of good life left in it. It’s the Volvo of laptops.

So even if I bought a new laptop (which I can’t exactly afford now), I’d want to keep using the iBook for as long as I can. Why waste it? But why have two laptops, one running Linux?^ (Seriously, I already have a netbook running Linux.) They’re the same size. It makes no sense to keep the iBook around for anything other than preserving my installation of many pieces of CS3. And because I heart the damn thing.

I’m at a crossroads: my PPC laptop is soon not going to just be dated, but unsupported. I don’t want to waste a perfectly wonderful laptop that has seen me through an entire PhD program. I have good software on it. Why buy a laptop the exact same size and type? Because it will save me from Google no longer supporting my laptop, and Web browsers that are actually implementing new W3C standards from not running on it.

Lesson learned: Even though I want superior architecture and don’t jump at trends (like oh, x86?) that I think are not worth it, I have to just go with the crowd, because sooner or later it will leave me behind. I am still not getting an iPad though. How long do you think I can scorn touch screens before I become officially old?

* (Yes, that is how old the G3 was. About three and a half years. Not bad for a laptop with a manufacturing defect that I was very hard on.)
** There are a number of PPC Linux distributions, but specific software may or may not be ported. Usually not.
*** Weirdly, there are a few local language versions of OpenOffice that do still support PowerPC architecture. Since one of those is the Japanese-language version, I now happily use a Japanese word processor and try to keep my language skills current, at least in terms of menu choices.
^ If I could get it to run for the newest AmigaOS I would run to it without hesitation, but I have only gotten reports of it running on a Mac Mini. Don’t think I haven’t considered getting a Mac Mini solely for this purpose. The lack of a monitor is mostly what’s stopping me.

multilingual laziness

I’ve come across a few sites lately – commercial and academic – that offer “translation” into several languages. I click on them out of curiosity. The link does not take me to a translation.

It takes me to Google Translate!

I have a few things to say about this:

  1. It’s unprofessional. It looks unprofessional too. That bar at the top of the site that says it’s being translated by Google? Kind of ruins the effect.
  2. If you’re just sending your site text to Google, why not offer all languages? I just visited a site that offers about 7; another (Rakuten) offers a handful. Google can handle more than 7 languages.
  3. It’s deceptive. Listing only a few languages makes it look like you’re offering actual human translations that you made or commissioned yourself. In fact, this is what I thought about all of the sites that I’ve visited recently that “offer” translations via Google. There’s no button that says “powered by Google Translate,” only a few flags that the user assumes lead to a real translation. They don’t. They lead to Google.
  4. Last but not least – it’s laughable. The translations aren’t so much inaccurate as hilarious. The only reason I can use the English Rakuten.jp is that I know Japanese and can guess at the original phrasing that produced such funny English. I have to double-check everything with the original Japanese text that it helpfully supplies a link to.*

This is the impression that your “serious” commercial or academic site is leaving: you’re naive about machine translation; you’re too cheap or unimaginative to get your own local translations; you’re out to deceive your users; and you’re an Engrish generator.

Is this the impression you want to leave?

Machine translation isn’t here yet. It may never be. Machine translation is hard. At the very least, get a native speaker of each language to read each end of the translation. You can identify the parts that need to be fixed simply by watching them making funny faces.

Google Translate may be okay in a pinch if you need to, for example, order something from a storefront or service that isn’t in your language. If you want to be taken seriously, find a human.

—-

* The reason I use Rakuten’s international English site is to narrow down the stores to ones that ship internationally. I wish I could use the Japanese site with this filtering.