Many ‘Old-School’ companies cling to the — of intellectual property like a security blanket. In the digital age, consumers are sick of it and have all the tools available to get what they want for free when they want it. That’s why it just makes sense to ‘give away’ software to the people that want it. There’s always the consumer who wants more, therefore the Upgrade model will always work.

For those who don’t know, open source software is the tech industry’s real version of the free trial. It allows consumers and businesses to use software that a company creates for free through a general public license (http://ping.fm/rYmnK). That means anyone who wants to can use the product for their own personal or commercial use. The business model usually attached to it is that a company offers a free version of its software and provides paid upgrade options that include more features. Usually the free version has all you’ll ever need to create a great website or program, but every now and then the upgrades are REALLY COOL!

I use open-source software on a regular basis for my business. We create website based on open-source software like Joomla!, WordPress, and Drupal all the time because it SAVES CLIENTS MONEY!! It’s easier for me to sell a client on a $5,000 website that uses much of the same technology as thousands of other websites out there than to create a completely custom app every time (would cost well over $30,000 for even the cheapest of sites).

Not only can I get more bang for my clients’ bucks, but I can also provide them with low cost security and usability upgrades in the future without spending my company resources to build them. It allows us to focus on what makes us valuable to consumers and focus on web design and marketing. Leave the software development to the, well, software developers!

I’ve only described why it works for me (selfish I know). There are many reasons why it can work for the software developers as well. Let’s talk awareness – give something away for free and people find out. They post it all around the web, blogs and news sites pick it up and talk about it. It can even show up on Tech TV shows, the local news, and huge conferences attended by many of the industry’s elite. People love the ‘generosity’ of developers who offer open source, and the more demanding consumer will always pay for the upgrade.

As a business model it makes sense for the developer, the re-seller, and ultimately the end user. It saves money for the latter two and provides good will (and free marketing) for the former. With the amazing amount of choices in the market today, it just makes sense to let the product speak for itself. After all, “if you build it [and give it away for free] they will come”!

Ghi lại để nhớ cái tội ngu cả buổi chiều ngồi đọc code để tìm ra cái điều mà nó đã được mô tả trong hướng dẫn sử dụng của nó. Ngu vãi!!!!

1. Dùng module Pathauto

2. Bật tính năng Transliterate prior to creating alias

3. Hiệu chỉnh nội dung tập tin i18n-ascii.txt chứa trong thư mục module pathauto – thêm vào các nguyên âm mang dấu tiếng Việt

——– bắt đầu ———

à = “a”
á = “a”
ả = “a”
ã = “a”
ạ = “a”

ă = “a”
ằ = “a”
ắ = “a”
ẳ = “a”
ẵ = “a”
ặ = “a”

â = “a”
ầ = “a”
ấ = “a”
ẩ = “a”
ẫ = “a”
ậ = “a”

À = “a”
Á = “a”
Ả = “a”
à = “a”
Ạ = “a”

Ă = “a”
Ằ = “a”
Ắ = “a”
Ẳ = “a”
Ẵ = “a”
Ặ = “a”

 = “a”
Ầ = “a”
Ấ = “a”
Ẩ = “a”
Ẫ = “a”
Ậ = “a”

đ = “d”
Đ = “d”

è = “e”
é = “e”
ẻ = “e”
ẽ = “e”
ẹ = “e”

ê = “e”
ề = “e”
ế = “e”
ể = “e”
ễ = “e”
ệ = “e”

È = “e”
É = “e”
Ẻ = “e”
Ẽ = “e”
Ẹ = “e”

Ê = “e”
Ề = “e”
Ế = “e”
Ể = “e”
Ễ = “e”
Ệ = “e”

ì = “i”
í = “i”
ỉ = “i”
ĩ = “i”
ị = “i”

Ì = “i”
Í = “i”
Ỉ = “i”
Ĩ = “i”
Ị = “i”

ò = “o”
ó = “o”
ỏ = “o”
õ = “o”
ọ = “o”

ô = “o”
ồ = “o”
ố = “o”
ổ = “o”
ỗ = “o”
ộ = “o”

ơ = “o”
ờ = “o”
ớ = “o”
ở = “o”
ỡ = “o”
ợ = “o”

Ò = “o”
Ó = “o”
Ỏ = “o”
Õ = “o”
Ọ = “o”

Ô = “o”
Ồ = “o”
Ố = “o”
Ổ = “o”
Ỗ = “o”
Ộ = “o”

Ơ = “o”
Ờ = “o”
Ớ = “o”
Ở = “o”
Ỡ = “o”
Ợ = “o”

ù = “u”
ú = “u”
ủ = “u”
ũ = “u”
ụ = “u”

ư = “u”
ừ = “u”
ứ = “u”
ử = “u”
ữ = “u”
ự = “u”

Ù = “u”
Ú = “u”
Ủ = “u”
Ũ = “u”
Ụ = “u”

Ư = “u”
Ừ = “u”
Ứ = “u”
Ử = “u”
Ữ = “u”
Ự = “u”

ỳ = “y”
ý = “y”
ỷ = “y”
ỹ = “y”
ỵ = “y”

Y = “y”
Ỳ = “y”
Ý = “y”
Ỷ = “y”
Ỹ = “y”
Ỵ = “y”

———————– kết thúc ———————–

I maintain a drupal codebase that hosts multiple sites. I’ve been shamefully lax in getting regular backups of those files and databases, until today. Here is a pretty basic bash script that will create a bzip2 archive of the drupal codebase (including site-specific dirs), and then create mysqldump exports of each site’s database and gzip those files. This particular script requires that the drupal install directory be named “drupal”, but you can change this easily enough to suit your needs.

This does require a ~/.drupalsites file that contains the needed database login info (suggest chmod 600). Like I said, nothing too clever.

#!/bin/bash
DATESTAMP=`date +%Y%m%d`
SITESFILE=${HOME}/.drupalsites
# SITESFILE contents are in the following format:
# SITENAME:DBNAME:DBUSER:DBPASSWD
DRUPALDIR=/path/to/drupal
BACKUPDIR=${HOME}/backups/${DATESTAMP}

mkdir -p ${BACKUPDIR}

# Backup the drupal codebase
echo -n "Backing up ${DRUPALDIR} ... "
cd ${DRUPALDIR}/../
tar -cjpf ${BACKUPDIR}/drupal_${DATESTAMP}.tar.bz2 drupal
echo "Done."

cd ${BACKUPDIR}

# Backup MySQL Databases
cat $SITESFILE | while read line; do
        #echo $line
        line=(${line//:/ })
        echo -n "Backing up MySQL db ${line[1]} ... "
        DUMPFILE=${line[0]}_${DATESTAMP}.sql
        mysqldump -u ${line[2]} -p${line[3]} ${line[1]} > ${DUMPFILE}
        gzip ${DUMPFILE}
        echo "Done."
done

echo "Backup completed, all files are in ${BACKUPDIR}."

This script runs fine from cron, I have it scheduled for a weekly run. I then plan to rsync this to my home server for an offsite copy, even though the hosting service provides backups as well.

PHPTemplate : <?php print $whatever; ?>

Smarty: <li>{$link}</li>

Người viết CSS ko cần biết PHPTemplate, sử dụng Smarty đòi hỏi người viết CSS phải biết Smarty

Drupal é um Sistema de Gerenciamento de Conteúdo (CMS, de Content Management System) rápido e com muitos recursos. Já vem com módulos para criação de Blog, Fórum de discussão, matérias (com feeds RSS criados automaticamente) e páginas de internet. Ainda é possível criar sites de comércio eletrônico, classificados, bate-papo, wikis, leitores de RSS e muitas outras ferramentas, bastando apenas usar as dezenas de módulos gratuitos disponibilizados no sítio. Temas para mudar o visual e traduções também estão disponíveis gratuitamente pela comunidade.

A ferramenta Drupal é escrita em PHP e funciona em qualquer sistema operacional (Windows, Linux, entre outros) e servidores web (Apache, IIS).

O nome Drupal deriva da palavra “druppel” do holandês, que significa cair (“drop” em inglês). O criador Dries Buytaert pensou no cair da chuva, gotas. Dries na verdade queria a palavra “dorp” (“vila” em holandês, numa referência a comunidade de usuários), mas quando foi procurar o domínio, digitou errado e achou que soava melhor ainda. O projeto começou em 2000. O mascote azul em forma de gota chama-se Drupalicon.

DOWNLOAD:

http://ftp.drupal.org/files/projects/drupal-6.3.tar.gz

DEMO:

Portal: http://www.opensourcecms.com/cms/drupal/

Administrador: http://www.opensourcecms.com/cms/drupal/admin.html
Usuário: admin
Senha: demo

Módulos:

O core do Drupal foi bem projetado com um sistema de ganchos conhecido como hooks, ou callbacks, que permite que módulos insiram funcionalidades dentro do Drupal.

Módulos incluídos no core do Drupal liberam usuário para:

* Criar, revisar e categorizar conteúdo
* Buscar conteúdo
* Postar comentários
* Participar de fóruns
* Votar em enquetes
* Trabalhar em colaboração escrevendo projetos
* Criar e visualizar páginas de perfil pessoal
* Comunicar entre si ou com outros administrados de websites
* Mudar o visual do site através do gerenciador de temas
* Construir menus de navegação de vários níveis
* Usuários do mesmo site podem navegar com seus idiomas locais
* Prove leitor de notícias RSS feeds
* Registrar e gerenciar contas de usuários
* Criar granularmente regras para usuários dando permissão para funcionalidades específicas do site
* Usar regras de acesso para proibir acessos específicos através dos usuários, emails, e endereços IPs.
* Prove estatísticas e relatórios para administração
* Gerenciamento de cache e throttling, técnica utilizada para desabilitar recursos quando o site estiver com alto tráfego
* Construir específicas regras para filtros de conteúdo
* Sistema de URL amigável que permite lembrar facilmente (ex: “www.mysite.com/products” melhor que “www.mysite.com/?q=node/432)

O Drupal possui centenas de módulos gratuitos escritos pela própria comunidade, como:

* e-commerce systems
* Workflow features
* Photo galleries
* Organic groups
* Google sitemaps
* Amazon Items
* Mailing list management
* Integration with CVS

Fonte: Plugmasters

If your web site contain a huge number of pages and corresponding level of difficulty in keeping track of all of them, your organization rely on constant and regular web site changes, often with several people working on it and your web site contributors lack sufficient knowledge in HTML and also you need to editorially review each new page before publication. When you are using a CMS will save a lot of time, hassle and money in the long run.

A Content Management System, or CMS for short, is a collection of procedures used to manage work flow in a collaborative environment. These procedures can be manual or computer based. Or in other word, CMS is an administrative software system that allows its users, often unskilled in HTML and web development, to update, edit and create new pages on their website.

In a CMS data can be defined as almost anything – documents, movies, pictures, phone number, scientific data, etc. CMSs are frequently used for storing, controlling, revising, and publishing documentation. Content that is controlled is industry-specific. (Entertainment content differs from the design of a fighter jet). There are various terms for systems (related processes) that do this. Examples include: Web Content Management, Digital Asset Management, Digital Records Management, Electronic Content Management (and others). Synchronization of intermediate steps, and collation into a final product are common goals of each.
Basic of a CMS

A typical CMS works like these; a web design layout is designed and developed. Usually this entails a logo/banner at the top, standard navigation menus across the top, down the left side, and/or at the foot of the page, and a ‘blank’ area where content is inserted, this layout format is then converted into a master template for all subsequent pages. During the process of this conversion, the CMS admin backend is integrated and tested. Web content producers are given access and instructions on how to add text and images to web pages automatically. Most CMS are usually very intuitive and easy to operate. and each generated page is saved onto a database, for future editing or deletion. More elaborate CMS can perform unique functions (such as archiving, built-in search engines, and mod rewrites), but basic functionality is still related to easy creation and editing of web pages.

Types of CMS

• Proprietary CMS
  These systems are usually very expensive to purchase such as the $500,000 and up Vignette system. These high end systems however come loaded with full features and usually have excellent customer and technical support. Common uses of these systems involve very large organizations with departments that require unique functionality.
• Open source
  These systems are typically free and relatively easy to install. Some of the better known open source systems include Mambo and Drupal. Because of its open source nature however, you will find a dearth of customer and technical support, however there exists a huge following and forums dedicated to the popular systems. Customization capabilities vary from system to system. Be sure to do all the necessary research before deciding on one.
• Custom CMS
  These types of systems are usually preferred as they allow you to develop from scratch, your preferred functionality. Debugging is also less of an issue as your web developer, having written the codes, can easily isolate and fix problems. Bear in mind there are literally hundreds of CMS to choose from. Ranging in costs from free to over $500,000. What you do need to do, is firstly figuring out exactly what functionality your organization needs, your development budget and finally find a system that suits those needs best.The downside to installing a CMS is of course, the amount of web development needed initially. While you are able to obtain free open source CMS programs, you still need to hire someone experienced and capable enough to integrate it correctly. This initial expense however, is usually a necessary evil and is justified as you avoid the need of hiring or outsourcing your webmastering needs down the road.

Ultimately a CMS is meant to make life easier, not creating new rigid standards that require stop gap hacks or workaround solutions.

copas from Globaltor – About Content Management System And Relation With Your Business Needs

Attendees: Tony, Will, Yu-Ching and Danny

Issue:

1. Tony talked to Duran Goodyear from UArts Communications Office. They are working on an University level digital assets archive program. Possible collaboration opportunity with them. Perhaps using ID dept. as the first test group!
2. Will and Jeff (MID 2) are building an onsite ‘project work server’ system based upon a web-based creative community resources project of Will MID graduate thesis “OKWagon” using Drupal, a web-based content management platform. Drupal can be a possible platform to build our archive system, and further incorporated in OKWagon.
3. Yu-Ching asked whether we should include PDF’s or just images to our archive. We shall find out after our meeting with Duran about their project.

To Do:

1. Faculty charrette: Sit down and go through all material to decide what to keep and what to toss.
2. Conduct interview/survey for faculty and students to find out what service they want the archive system to provide.
3. Start digitize the slides.

Next Meeting:

12/3/2009 1pm @ ID faculty Office with Sara McDonald (Library) and Duran Goodyear (Communications)

Drupal 6 node.save uses different methods for saving taxonomy for different taxonomy types.

For multiple select based taxonomy:

(php)

$nodeObj->taxonomy = array(2=>array(15,19));

(python)

nodeOb['taxonomy']['2'] = [15,19]

For tags based taxonomy:

(php)

$nodeObj->taxonomy = array(
  'tags' => array(
         2=>'military,navy'
   )
);

Vandaag zijn we ook begonnen aan de derde opdracht.

Vooraleer je drupal kan installeren moet je eerst een webserver hebben. Omdat wij dit niet hebben is er nog een alternatief. Er zijn namelijk enkele mogelijkheden om een soort server lokaal op je pc of mac te laten lopen. Voor mac kan je grbuik maken van MAMP of XAMP en voor pc XAMP. Aangezien 3 van de 4 groepsleden een mac heeft hebben we gekozen voor te werken met MAMP.

Zoals de titel wel duidelijk maakt hebben we dus MAMP gedownload en geïnstalleerd. Ook hebben we al de recentste versie van drupal gedownload, uitgepakt en op de juiste locatie op onze lokale server geplaatst.

De opdracht voor dit onderdeel wordt duidelijk beschreven in de opdachten-bundel van de lector.
Extra informatie kan je terug vinden in de samenvatting die ik verstuurd heb.

Ik stel voor dat zeker tegen 04/12 de opdracht afgerond wordt zodat de voorbereidingen kunnen beginnen voor de voorstelling. Vroeger is natuurlijk nog beter.

Aliquam aliquet, est a ullamcorper condimentum, tellus nulla fringilla elit, a iaculis nulla turpis sed wisi. Fusce volutpat. Etiam sodales ante id nunc. Proin ornare dignissim lacus. Nunc porttitor nunc a sem. Sed sollicitudin velit eu magna. Aliquam erat volutpat. Vivamus ornare est non wisi. Proin vel quam. Vivamus egestas. Nunc tempor diam vehicula mauris. Nullam sapien eros, facilisis vel, eleifend non, auctor dapibus, pede.

A few weeks ago I took a one day course on Drupal development.  Drupal is an open source software package for developing content management systems and websites.  I had come across it several months ago and installed it on my home computer just to try it out, and when I saw that I had access to this course I figured that it was a good skill to add to my list.

The course was really good, and it covered a lot of ground, which I appreciated.  I feel like any continuing education that I pursue needs to be really concentrated, and it needs to deliver.  I want to walk out with ideas for things, but also with the skills to implement them.  Theory is great, but I want to do things.

A colleague and I have also installed Drupal on a server at work and we’re looking at it as an internal solution for our workgroup.  We are looking for ways to self-publish, collaborate, and create a repository that others can also use.  We do research within a large organization and we’re trying to refine the way we deliver our work.  Email is fine, but it’s a limited channel that excludes people who aren’t on the address line.  Also, email tends to get deleted, and we think a content management system would solve some of those problems.  We are also hopeful that it will encourage the exchange of ideas across departments, since people can post comments and questions via the Drupal platform.

The aspect of Drupal that I am most interested in is its taxonomy module.  Using the taxonomy module enables the site administrator to create categories with which users can classify the information they publish.  It’s certainly nice to allow some free tagging, and in a large department it’s difficult to predict all of the possible descriptive terms that your users might employ.  But creating some broad subject areas at the outset is a good way to encourage consistency, and consistency makes it easier on the content creator (since they don’t have to come up with terms from scratch), and it makes information retrieval easier because it presents the searcher with topic areas that should look familiar.

Right now we are just using Drupal across a very small user group which makes it much easier to manage.  I hope we can roll it out to a few more people and get their feedback on the site, as well as the taxonomy.  In many ways the organization is lax on the ways it classifies information, and if I can demonstrate the benefit of a solid taxonomy in this one area, it’s possible that I can then advocate for refinement in other areas.  I don’t think that it’s very easy for people to see the benefit of a good scheme of information classification in its absence, so I think it’s my job to demonstrate the good it can do.  Plus, if I want to pursue taxonomy consulting, it will be good to get some experience in my current job that I can point to.  An added benefit is that it will diversity my workday.  Now if they would just let me bring my dog to work…

Community News | Css Globe

สำหรับ drupal นะ

• อย่าสร้าง file ชื่อ install.php หรือไฟล์อื่นๆที่ชื่อซ้ำกับในระบบ ไม่งั้นปัญหาที่ไม่รู้สาเหตุจะตามมา
• เวลาเขียน sql ถ้าไปกอปจาก phpmyadmin มันจะได้เครื่องหมายฟันหนูแบบเอียงๆ `membership`  อย่างนี้  ถ้าเราไปใช้บางทีก็ฟันหนูเอียง บางทีก็ฟันหนูตรง จะมีปัญหาบ้าบอคอแตก รันได้ ไร้ error แต่ผลออกมาผิด

ที่จริงสาระก็ไม่ได้มีมาก แค่โวยวายที่เสียเวลาสามชั่วโมงกว่าเพื่ออะไรเนี่ยะ

Whoohoo – upgraded to Karmic (ubuntu 9.10 (pronouced nine point ten not, one), and I can get the latest eclipse (3.51) by doing a:

sudo apt-get install eclipse

But what about all those eclipse plugins I hear you say – has anybody gone to the trouble of packaging them?

Thanks to Yogarine you can now do this:

Here’s the line to add to your software sources list:
deb http://ppa.launchpad.net/yogarine/eclipse/ubuntu karmic main

And then run the following on the terminal to add my gpg key:
wget http://www2.yogarine.com/eclipse-ppa.key -O- | sudo apt-key add - && sudo apt-get update

Update: Now according to Zoresvit in #1 below – it’s as easy as:

sudo add-apt-repository ppa:yogarine/eclipse/ubuntu


Now you can install the Eclipse plugins like you would any other application in Ubuntu, e.g.:
sudo apt-get install eclipse-pdt eclipse-subclipse

And hey presto you have an IDE that can develop drupal modules without too much hassle.

Info File Details

name (Required)

The displayed name of your module. It should follow the Drupal 6 capitalization standard: only the first letter of the first word is capitalized (“Example module”, not “example module” or “Example Module”).
name = On this date

description (Required)

A short, preferably one line description that will tell the administrator what this module does on the module administration page. Remember, overly long descriptions can make this page difficult to work with, so please try to be concise. This field is limited to 255 characters.

description = A block module that lists links to content such as blog entries or forum discussions that were created one week ago.

Note that special characters in this description must be substituted with the HTML entity values. For example, use description = This is my "crazy@email.com" email address instead of description = This is my "crazy@email.com" email address
If the description has single quotes or apostrophes in it then you can simply put the entire string inside double quotes. For example, description = "Please don't use this unless you know what you are doing."

core (Required)

As of version 6.x, Drupal core will refuse to enable or run modules that aren’t explicitly written for the right version of core. The .info file must specify which Drupal core compatiblity any module or theme has been ported to. This is accomplished by means of the new core attribute in the .info files.

core = 6.x

Note: the drupal.org packaging script automatically sets this value based on the Drupal core compatibility setting on each release node, so users downloading packaged releases from drupal.org will always get the right thing. However, for sites that deploy Drupal directly from CVS, it helps if this value is added to the .info files for the module. This is also a good way to indicate to users of each module what version of core the HEAD of CVS is compatibile with at any given time.

dependencies (Optional)

There are a couple of extra options that may appear in the .info file, one of which are module dependencies. If a module requires another module to be enabled, list each module (filename) required in the following syntax:

dependencies[] = taxonomy
dependencies[] = comment

For the example module, these don’t apply and we will simply omit them. If dependencies are assigned for a module, Drupal will not allow it to be activated until the required dependencies are met.

package (Optional)

If a module has a package string, on the admin/build/modules page it will be listed with other modules with the same category. If a package string is not assigned, it will simply be listed in the ‘Other’. Not assigning a package for your module is perfectly ok; in general packages are best used for modules that are distributed together or are meant to be used together. If in doubt, leave this field blank.

package = "Your arbitrary grouping string"

Suggested examples of appropriate items for the package field:

• Audio
• Bot
• CCK
• Chat
• E-Commerce
• Event
• Feed Parser
• Organic groups
• Station
• Video
• Views
• Voting (if it uses/requires VotingAPI)

The files use the ini format and can include a ; $Id$ to have CVS insert the file ID information.

For more information on ini file formatting, see the PHP.net parse_ini_file documentation.

It is with great pleasure that we welcome our newest partner, Blink Reaction, to MPW. We will launch and oversee Blink’s social media strategy, website content management, web development marketing and PR projects. This summer, we created content for their new website and we are thrilled that our relationship has evolved into something much bigger.

Blink develops cutting edge websites for mid to large companies. They create clean and fluid electronic media presentations supported by Drupal, the best non-proprietary, open source content management and ecommerce platform available today.

Here’s a toast to great victories on the horizon. Welcome aboard!

We deal in “LAMP” Technologies.

We are expert in Application development & Customization of Open Source platforms.

Our coding teams have a lot of experience in building web applications for e-learning, e-commerce, content management, realty, CRM and other domains. We are also skilled in modifying and integrating popular open source applications .

Our work Specialty:

1- PHP and Mysql .
2- Full Joomla Customization (Theme ,Component,Module,Plugins).
3- Full Drupal Customization (Theme,Modules).
4- Full Moodle Customization (Theme, Modules).
5- Full Magento Cutomization.
6- Joomla + Moodle Integration.
7- Drupal + Moodle Integration.

For development work we put in a lot of effort to work together with clients to understand and clarify scope. Thereafter, we adhere to a transparent, process-driven development methodology:-

- Analysis
- Construction
- QA
- UAT

Url : www.maantech.com

We are always ready for working with you.

Welcome To My Blog

Ovvero come insegnare ad un computer a leggere opere di narrativa. E a farci dire a quale genere letterario appartiene. I’m sorry, Dave. I’m afraid I can’t read this: it’s another boring Gothic Novel.

Parto dall’articolo “Style versus expression in literary narratives” di Ozlem Uzuner e Boris Katz. Lo potete trovare in CiteSeer, la Scientific Literature Digital Library.

Qui vengono date due definizioni:

Stile: le scelte linguistiche che un autore fa lungo tutta la sua opera, indipendentemente dal contenuto.
Espressione: le scelte linguistiche che un autore fa per veicolare un particolare contenuto (nello specifico, per una particolare opera).

Stile ed espressione si differenziano quindi da un punto di vista qualitativo (uno fa riferimento al contesto, l’altro no), ma loro propongono un esperimento interessante: per identificare lo stile analizzano le diverse traduzioni fatte di una stessa opera. In questo modo si concentrano sullo stile (indipendente dal contenuto) dei traduttori, confidando nel fatto che le differenze di contenuto siano nulle o poco più (ogni traduttore lavora sulla stessa opera).

In questo modo la loro ricerca evidenzia come sia possibile riconoscere lo stile mediante l’identificazione di parole funzionali e l’espressione mediante l’analisi della sintassi.

Per fare questo tipo di analisi, quindi, non è necessario identificare parole specifiche, prese dal contesto. Non importa sapere se l’autore ha usato o meno la parola “pianeta”, perché il suo stile e la sua forma espressiva non dipendono dal contesto di cui sta parlando.

Quando si pensa al genere letterario, invece, si presume che “pianeta” aiuti, eccome: fa subito venire in mente la fantascienza, i viaggi nello spazio. Com’è possibile immaginare il genere gotico senza almeno un castello, o il romanzo rosa senza un fremito al cuore?

Eppure pare che i più recenti tentativi di determinare/attribuire in automatico i generi letterari di un testo possano funzionare anche senza cercare parole note a priori, ovvero senza crearsi un elenco di tutte quelle parole specifiche che la macchina deve individuare, contare e dunque valutare per decidere di che genere sia l’opera in analisi.

Secondo l’articolo “Machine-Classifying Novels and Plays by Genre” (https://www.stanford.edu/~mjockers/cgi-bin/drupal/node/27) il gotico, la fantascienza e il romanzo rosa (e tutti gli altri generi letterari, ovviamente) sono riconoscibili

• per il loro uso della punteggiatura,
• per la costruzione delle frasi tramite congiunzioni e subordinate,
• per l’utilizzo di aggettivi pronominali (interrogativi, numerali, indefiniti, possessivi…)
• per l’utilizzo dei pronomi personali.

Elencando insieme punteggiatura, congiunzioni, subordinate, interrogativi, numerali eccetera di un’opera siamo in grado di fare calcoli statistici su quanto spesso (e in che posizione) questi elementi ricorrono, così da associare tra di loro opere di narrativa (che la macchina ci restituisce raggruppate in insiemi). E questi insiemi corrispondono a quelli che noi intendiamo essere generi letterari.

Strumenti che si possono utilizzare per analizzare la narrativa:
Docuscope: http://betterwriting.net/projects/fed01/dsc_fed01.html
R: http://www.r-project.org/
Eseguire R in PHP: https://www.stanford.edu/~mjockers/cgi-bin/drupal/node/25