
http://example.com/foo/bar
)'),
'proto-rel' => t('Protocol relative URL (//example.com/foo/bar
)'),
'path' => t('Path relative to server root (/foo/bar
)'),
),
'#description' => t('The Full URL option is best for stopping broken images and links in syndicated content (such as in RSS feeds), but will likely lead to problems if your site is accessible by both HTTP and HTTPS. Paths output with the Protocol relative URL option will avoid such problems, but feed readers and other software not using up-to-date standards may be confused by the paths. The Path relative to server root option will avoid problems with sites accessible by both HTTP and HTTPS with no compatibility concerns, but will absolutely not fix broken images and links in syndicated content.'),
'#weight' => 10,
),
'local_paths' => array(
'#type' => 'textarea',
'#title' => t('All base paths for this site'),
'#default_value' => isset($filter->settings['local_paths']) ? $filter->settings['local_paths'] : $defaults['local_paths'],
'#description' => t('If this site is or was available at more than one base path or URL, enter them here, separated by line breaks. For example, if this site is live at http://example.com/
but has a staging version at http://dev.example.org/staging/
, you would enter both those URLs here. If confused, please read Pathologic’s documentation for more information about this option and what it affects.', array('!docs' => 'http://drupal.org/node/257026')),
'#weight' => 20,
),
);
}
/**
* Pathologic filter callback.
*
* Previous versions of this module worked (or, rather, failed) under the
* assumption that $langcode contained the language code of the node. Sadly,
* this isn't the case.
* @see http://drupal.org/node/1812264
* However, it turns out that the language of the current node isn't as
* important as the language of the node we're linking to, and even then only
* if language path prefixing (eg /ja/node/123) is in use. REMEMBER THIS IN THE
* FUTURE, ALBRIGHT.
*
* The below code uses the @ operator before parse_url() calls because in PHP
* 5.3.2 and earlier, parse_url() causes a warning of parsing fails. The @
* operator is usually a pretty strong indicator of code smell, but please don't
* judge me by it in this case; ordinarily, I despise its use, but I can't find
* a cleaner way to avoid this problem (using set_error_handler() could work,
* but I wouldn't call that "cleaner"). Fortunately, Drupal 8 will require at
* least PHP 5.3.5, so this mess doesn't have to spread into the D8 branch of
* Pathologic.
* @see https://drupal.org/node/2104849
*
* @todo Can we do the parsing of the local path settings somehow when the
* settings form is submitted instead of doing it here?
*/
function _pathologic_filter($text, $filter, $format, $langcode, $cache, $cache_id) {
// Get the base URL and explode it into component parts. We add these parts
// to the exploded local paths settings later.
global $base_url;
$base_url_parts = @parse_url($base_url . '/');
// Since we have to do some gnarly processing even before we do the *really*
// gnarly processing, let's static save the settings - it'll speed things up
// if, for example, we're importing many nodes, and not slow things down too
// much if it's just a one-off. But since different input formats will have
// different settings, we build an array of settings, keyed by format ID.
$cached_settings = &drupal_static(__FUNCTION__, array());
if (!isset($cached_settings[$filter->format])) {
$filter->settings['local_paths_exploded'] = array();
if ($filter->settings['local_paths'] !== '') {
// Build an array of the exploded local paths for this format's settings.
// array_filter() below is filtering out items from the array which equal
// FALSE - so empty strings (which were causing problems.
// @see http://drupal.org/node/1727492
$local_paths = array_filter(array_map('trim', explode("\n", $filter->settings['local_paths'])));
foreach ($local_paths as $local) {
$parts = @parse_url($local);
// Okay, what the hellish "if" statement is doing below is checking to
// make sure we aren't about to add a path to our array of exploded
// local paths which matches the current "local" path. We consider it
// not a match, if…
// @todo: This is pretty horrible. Can this be simplified?
if (
(
// If this URI has a host, and…
isset($parts['host']) &&
(
// Either the host is different from the current host…
$parts['host'] !== $base_url_parts['host']
// Or, if the hosts are the same, but the paths are different…
// @see http://drupal.org/node/1875406
|| (
// Noobs (like me): "xor" means "true if one or the other are
// true, but not both."
(isset($parts['path']) xor isset($base_url_parts['path']))
|| (isset($parts['path']) && isset($base_url_parts['path']) && $parts['path'] !== $base_url_parts['path'])
)
)
) ||
// Or…
(
// The URI doesn't have a host…
!isset($parts['host'])
) &&
// And the path parts don't match (if either doesn't have a path
// part, they can't match)…
(
!isset($parts['path']) ||
!isset($base_url_parts['path']) ||
$parts['path'] !== $base_url_parts['path']
)
) {
// Add it to the list.
$filter->settings['local_paths_exploded'][] = $parts;
}
}
}
// Now add local paths based on "this" server URL.
$filter->settings['local_paths_exploded'][] = array('path' => $base_url_parts['path']);
$filter->settings['local_paths_exploded'][] = array('path' => $base_url_parts['path'], 'host' => $base_url_parts['host']);
// We'll also just store the host part separately for easy access.
$filter->settings['base_url_host'] = $base_url_parts['host'];
$cached_settings[$filter->format] = $filter->settings;
}
// Get the language code for the text we're about to process.
$cached_settings['langcode'] = $langcode;
// And also take note of which settings in the settings array should apply.
$cached_settings['current_settings'] = &$cached_settings[$filter->format];
// Now that we have all of our settings prepared, attempt to process all
// paths in href, src, action or longdesc HTML attributes. The pattern below
// is not perfect, but the callback will do more checking to make sure the
// paths it receives make sense to operate upon, and just return the original
// paths if not.
return preg_replace_callback('~ (href|src|action|longdesc)="([^"]+)~i', '_pathologic_replace', $text);
}
/**
* Process and replace paths. preg_replace_callback() callback.
*/
function _pathologic_replace($matches) {
// Get the base path.
global $base_path;
// Get the settings for the filter. Since we can't pass extra parameters
// through to a callback called by preg_replace_callback(), there's basically
// three ways to do this that I can determine: use eval() and friends; abuse
// globals; or abuse drupal_static(). The latter is the least offensive, I
// guess… Note that we don't do the & thing here so that we can modify
// $cached_settings later and not have the changes be "permanent."
$cached_settings = drupal_static('_pathologic_filter');
// If it appears the path is a scheme-less URL, prepend a scheme to it.
// parse_url() cannot properly parse scheme-less URLs. Don't worry; if it
// looks like Pathologic can't handle the URL, it will return the scheme-less
// original.
// @see https://drupal.org/node/1617944
// @see https://drupal.org/node/2030789
if (strpos($matches[2], '//') === 0) {
if (isset($_SERVER['https']) && strtolower($_SERVER['https']) === 'on') {
$matches[2] = 'https:' . $matches[2];
}
else {
$matches[2] = 'http:' . $matches[2];
}
}
// Now parse the URL after reverting HTML character encoding.
// @see http://drupal.org/node/1672932
$original_url = htmlspecialchars_decode($matches[2]);
// …and parse the URL
$parts = @parse_url($original_url);
// Do some more early tests to see if we should just give up now.
if (
// If parse_url() failed, give up.
$parts === FALSE
|| (
// If there's a scheme part and it doesn't look useful, bail out.
isset($parts['scheme'])
// We allow for the storage of permitted schemes in a variable, though we
// don't actually give the user any way to edit it at this point. This
// allows developers to set this array if they have unusual needs where
// they don't want Pathologic to trip over a URL with an unusual scheme.
// @see http://drupal.org/node/1834308
// "files" and "internal" are for Path Filter compatibility.
&& !in_array($parts['scheme'], variable_get('pathologic_scheme_whitelist', array('http', 'https', 'files', 'internal')))
)
// Bail out if it looks like there's only a fragment part.
|| (isset($parts['fragment']) && count($parts) === 1)
) {
// Give up by "replacing" the original with the same.
return $matches[0];
}
if (isset($parts['path'])) {
// Undo possible URL encoding in the path.
// @see http://drupal.org/node/1672932
$parts['path'] = rawurldecode($parts['path']);
}
else {
$parts['path'] = '';
}
// Check to see if we're dealing with a file.
// @todo Should we still try to do path correction on these files too?
if (isset($parts['scheme']) && $parts['scheme'] === 'files') {
// Path Filter "files:" support. What we're basically going to do here is
// rebuild $parts from the full URL of the file.
$new_parts = @parse_url(file_create_url(file_default_scheme() . '://' . $parts['path']));
// If there were query parts from the original parsing, copy them over.
if (!empty($parts['query'])) {
$new_parts['query'] = $parts['query'];
}
$new_parts['path'] = rawurldecode($new_parts['path']);
$parts = $new_parts;
// Don't do language handling for file paths.
$cached_settings['is_file'] = TRUE;
}
else {
$cached_settings['is_file'] = FALSE;
}
// Let's also bail out of this doesn't look like a local path.
$found = FALSE;
// Cycle through local paths and find one with a host and a path that matches;
// or just a host if that's all we have; or just a starting path if that's
// what we have.
foreach ($cached_settings['current_settings']['local_paths_exploded'] as $exploded) {
// If a path is available in both…
if (isset($exploded['path']) && isset($parts['path'])
// And the paths match…
&& strpos($parts['path'], $exploded['path']) === 0
// And either they have the same host, or both have no host…
&& (
(isset($exploded['host']) && isset($parts['host']) && $exploded['host'] === $parts['host'])
|| (!isset($exploded['host']) && !isset($parts['host']))
)
) {
// Remove the shared path from the path. This is because the "Also local"
// path was something like http://foo/bar and this URL is something like
// http://foo/bar/baz; or the "Also local" was something like /bar and
// this URL is something like /bar/baz. And we only care about the /baz
// part.
$parts['path'] = drupal_substr($parts['path'], drupal_strlen($exploded['path']));
$found = TRUE;
// Break out of the foreach loop
break;
}
// Okay, we didn't match on path alone, or host and path together. Can we
// match on just host? Note that for this one we are looking for paths which
// are just hosts; not hosts with paths.
elseif ((isset($parts['host']) && !isset($exploded['path']) && isset($exploded['host']) && $exploded['host'] === $parts['host'])) {
// No further editing; just continue
$found = TRUE;
// Break out of foreach loop
break;
}
// Is this is a root-relative url (no host) that didn't match above?
// Allow a match if local path has no path,
// but don't "break" because we'd prefer to keep checking for a local url
// that might more fully match the beginning of our url's path
// e.g.: if our url is /foo/bar we'll mark this as a match for
// http://example.com but want to keep searching and would prefer a match
// to http://example.com/foo if that's configured as a local path
elseif (!isset($parts['host']) && (!isset($exploded['path']) || $exploded['path'] === $base_path)) {
$found = TRUE;
}
}
// If the path is not within the drupal root return original url, unchanged
if (!$found) {
return $matches[0];
}
// Okay, format the URL.
// If there's still a slash lingering at the start of the path, chop it off.
$parts['path'] = ltrim($parts['path'],'/');
// Examine the query part of the URL. Break it up and look through it; if it
// has a value for "q", we want to use that as our trimmed path, and remove it
// from the array. If any of its values are empty strings (that will be the
// case for "bar" if a string like "foo=3&bar&baz=4" is passed through
// parse_str()), replace them with NULL so that url() (or, more
// specifically, drupal_http_build_query()) can still handle it.
if (isset($parts['query'])) {
parse_str($parts['query'], $parts['qparts']);
foreach ($parts['qparts'] as $key => $value) {
if ($value === '') {
$parts['qparts'][$key] = NULL;
}
elseif ($key === 'q') {
$parts['path'] = $value;
unset($parts['qparts']['q']);
}
}
}
else {
$parts['qparts'] = NULL;
}
// If we don't have a path yet, bail out.
if (!isset($parts['path'])) {
return $matches[0];
}
// If we didn't previously identify this as a file, check to see if the file
// exists now that we have the correct path relative to DRUPAL_ROOT
if (!$cached_settings['is_file']) {
$cached_settings['is_file'] = !empty($parts['path']) && is_file(DRUPAL_ROOT . '/'. $parts['path']);
}
// Okay, deal with language stuff.
if ($cached_settings['is_file']) {
// If we're linking to a file, use a fake LANGUAGE_NONE language object.
// Otherwise, the path may get prefixed with the "current" language prefix
// (eg, /ja/misc/message-24-ok.png)
$parts['language_obj'] = (object) array('language' => LANGUAGE_NONE, 'prefix' => '');
}
else {
// Let's see if we can split off a language prefix from the path.
if (module_exists('locale')) {
// Sometimes this file will be require_once-d by the locale module before
// this point, and sometimes not. We require_once it ourselves to be sure.
require_once DRUPAL_ROOT . '/includes/language.inc';
list($language_obj, $path) = language_url_split_prefix($parts['path'], language_list());
if ($language_obj) {
$parts['path'] = $path;
$parts['language_obj'] = $language_obj;
}
}
}
// If we get to this point and $parts['path'] is now an empty string (which
// will be the case if the path was originally just "/"), then we
// want to link to La Fundación Gilberto Alzate Avendaño y su proyecto Plataforma Bogotá: Laboratorio interactivo de arte, ciencia y tecnología los invitan a participar en el Laboratorio Composiciones, a cargo de Jonathan Ramírez, ganador de la “Residencia en Buenos Aires en cooperación con la Universidad de Buenos Aires (FADU/UBA) 2012”.
Este laboratorio busca explorar y entender las características del sonido a partir de diferentes prácticas como registro sonoro, edición, notaciones, dibujo, manipulación por código y caminatas auditivas. A través de estas prácticas se busca entender las características del sonido como sustento plástico al aislarlo de su entorno natural, transformarlo y usarlo como material para crear paisajes e instalaciones sonoras. En cada sesión se llevará a cabo un ejercicio que permitirá el entendimiento de los problemas y/o características del sonido.
Se hará uso de herramientas Open-Source como Audacity y Procesing que permitan editar y transformar el material. La materia prima del laboratorio (el sonido) se recolectará por medio de sesiones de registro sonoro, donde se realizarán capturas y, posteriormente, clasificaciones de material. El desarrollo teórico/práctico de las sesiones permitirá trabajar el material de diversas maneras, con el fin de construir y desarrollar una pieza sonora propia.
El laboratorio se llevará a cabo el 22,23,25,29 y 30 de abril y 2,6,7 y 9 de mayo de 2014, las inscripciones cierran el 16 de abril. Serán en total 20 personas participantes.
Sesión 1 - El sonido
En esta sesión se realizará una introducción a las propiedades y la naturaleza del sonido.
Ejercicio. Sesión de dibujo de sonidos. Se enviará con anticipación una lista de sonidos para que cada uno de los asistentes pueda escucharlos. Cada sonido tiene una característica particular que será interpretada y posteriormente representada por medio de dibujos.
Referentes:
Nigel Peake “Dibujos de cantos de pájaros”, “In the Wilds”
Video: Resonance https://vimeo.com/25186640 Exploración de la relación entre la geometría y el audio.
Carstei Nicolai “Bitwave” 2001, Dibujo en pared
Sesión 2 - Notaciones musicales contemporáneas
En esta sesión se estudiarán las diferentes prácticas de notación musical contemporánea y las ideas detrás de las mismas. Para esto se verán ejemplos de notaciones de John Cage, Stockhausen, Walter Mays, entre otros.
Ejercicio. Se seleccionarán espacios fuera del taller en los cuales se realizarán notaciones del lugar por tiempos cortos.
* Texto opcional en inglés para la sesión: OnListening, Perspective of New Music, vol 48, No 2 (Verano 2010), pg. 152 – 179.
Sesión 3 - Captura y edición de sonido
Se realizará una sesión de captura de sonido en grupo en diferentes lugares cercanos al lugar del laboratorio. Los sonidos recolectados serán parte del material para experimentar en la representación del entorno de manera sonora. Se utilizará la herramienta de edición de sonido Audacity para llevar a cabo esta práctica.
Sesión 4 - Ejemplos de obras sonoras
Parte de esta sesión estará dedicada a estudiar y ver casos de obras sonoras como “Sinfonía de las sirenas” de Arseeny Avraamov, “PigeonSoundings” y “RiverSoundings” de Bill Fontana, “L’escalier des aveugles” de Luc Ferrari, entre otros.
Ejercicio. Intercambio sonoro. Cada asistente hará la mitad de un paisaje sonoro de un minuto. Luego intercambiará con otra persona. Ambos deben completar el minuto restante del paisaje.
Sesión 5 - Espacio – Ruido
Esta sesión abordará el ruido y su relación con el espacio, a partir de ejercicios de multiplicación de los mismos. Se verán como ejemplo las obras de: Zimoun (http://www.zimoun.net/2013-318.html) y podcast de 99% Percent Invisible sobre el ruido (http://bit.ly/1fXx6ta).
Ejercicio. Seleccionar una serie de sonidos y utilizarlos para generar ruido y alterar un espacio. El ruido debe ser pensado para reproducirse en diferentes parlantes distribuidos en un espacio buscando alterarlo de la mejor manera posible.
Sesiones 6 y 7 - Processing
Las siguientes dos sesiones estarán dedicadas a aprender a usar la herramienta de programación Processing para manipular el sonido de manera interactiva. La primera sesión dará a conocer el programa a través de ejercicios cortos para familiarizarse con los conceptos básicos de programación, mientras que la segunda hará uso de variables que puedan modificar el comportamiento del sonido de manera interactiva.
Sesiones 8 y 9 Proyecto final 1-2
Estas dos últimas sesiones del laboratorio están dedicadas al desarrollo de un proyecto personal. Se ensamblarán los proyectos.
*Es opcional traer grabadora de sonido y computador para editar, no es necesario conocer los softwares que serán utilizados: Processing y Audacity.
Envíe un documento PDF en el que argumente en máximo dos párrafos su interés en este laboratorio, adjunte su hoja de vida y fotografías de los principales proyectos relacionados con el tema, también en formato PDF, al correo electrónico plataformaconvocatoria@gmail.com escribiendo en el asunto Laboratorio composiciones.
Inscripciones hasta el 16 de abril de 2014.
Se publicaran los seleccionados el 18 de abril del 2014 a través de www.plataformabogota.org. La selección de los participantes será realizada por Jonathan Ramírez y dependerá de la motivación, los aportes de las investigaciones y formación en relación a las problemáticas del laboratorio de cada persona.
Artista plástico con énfasis en medios electrónicos egresado de la Universidad de los Andes. Interesado en entablar relaciones entre el sonido y la imagen a través de diferentes prácticas como video y dibujo. Vive y trabaja en Bogotá.