similar to: Rails, 1.9 & Encoding - does it work?

Hi, Windows Vista Home Premium ruby 1.9.2dev (2009-07-18 trunk 24186) [i386-mswin32_90] I noticed there was an ordinal bug in win32-security and Ruby 1.9.x. I fixed those easily enough, but now we''re left with this: 1) Error: test_string_to_sid(TC_Win32_Security_Sid): ArgumentError: invalid byte sequence in US-ASCII

Hola, No sé si esas funciones cuando te proporcionan los strings utilizan algún parámetro de configuración sobre el enconding. Si no lo tienen (en español, es conveniente utilizar UTF-8). Pero una vez en tu workspace, mira la función "iconv()" que te ayudará tanto a conocer el encoding que tienen las cadenas como a transformarlas. En un caso reciente, para poder tener en cuenta los

Buenas noches a todos, Estoy descarganado tweets a través del paquete twitteR en dos sistemas diferentes. La configuración del primero, un MacBook Pro, es R version 3.0.2 Patched (2013-12-11 r64449) Platform: x86_64-apple-darwin10.8.0 (64-bit) locale: [1] en_AU.UTF-8/en_AU.UTF-8/en_AU.UTF-8/C/en_AU.UTF-8/en_AU.UTF-8 attached base packages: [1] compiler stats graphics grDevices utils

Hola La codificación con uft-8 y etc., es un poco complicada, tendría que ser sencillo, pero siempre aparecen problemas. Por las dudas le comento que un inconveniente que tuve, es que al tener archivos en R, guardados como Rnw (aprovecho a colocar comentarios y cosas en latex), y cambiar la ubicación o la carpeta, la codificación de texto se rompía, es decir donde decía alguna palabra con

Hello, I am wondering if I am misinterpreting something from R/3.0.0 NEWS LONG VECTORS: This section applies only to 64-bit platforms. ... o serialize() to a raw vector is unlimited in size (except by resources). However when I try the following it fails: > foo <- raw(2500000000) > print(object.size(foo),units="auto") 2.3 Gb > bar <- serialize(foo, NULL)

Question: Hi, our company is using Ruby 1.8.6 with Rails 2.2.2. Does anyone know we can explicitly specify what encoding to use when calling to_json() or to_xml() methods? Problem: We have some multibyte characters in our database. For example we have a table with a name column that has this French accented e: Café Records. When we serialize this object using ActiveRecord''s to_xml()

Hello I'm using an OOTB RH80 with recent updates, and samba 227, french language when I access a samba share from a w98 box eveything works fine but with accented chars I just can't get the right filename under linux. whatever filename I use on w98, with accented chars, it works from the w98 side (I get write and read files with their right filenames) but when I try to access those

Hi all I've been getting some emails from the R package maintainers that I need to update some code in a CRAN packge that uses FORTRAN, to comply with (not so recent) changes. I've been a little busy... I'm having trouble adjusting my code. I hope someone can help. The package was working fine, and a few R functions in my package had lines like this: tmp <- .Fortran(

Hey all, Anyone got some quick advice on international character submission via Prototype''s Form.Serialize? The base scenario: I set the charset on my page to ISO-8859-1, which seems to be what everyone uses. If I submit a regular form with a standard webpage, I get international characters (like an accented "e", or and AE legature) encoded as 1-byte ascii code

Hi everyone, I have a very annoying character encoding problem. Have a look to this: # ls -l M*mo-1.* -rw-rw-rw- 1 root root 8417218 6 sept. 2013 Mémo-1.aif -rwxr--r-- 1 hope hope 8417218 6 sept. 2013 Mémo-1.aif -rw-rw-rw- 1 root root 363175 6 sept. 2013 Mémo-1.m4a -rwxr--r-- 1 hope hope 363175 6 sept. 2013 Mémo-1.m4a Yes, it looks like two files have exactly the same name, but

Hi, I''m a newcomer to Ruby and to Rails, and am having a problem with character encoding. Now, I know ruby doesn''t handle unicode...but, characters like ? (eacute) and ? (ccedil) are part of the iso-8859-1 charset, so it shouldn''t be a problem, right? But, for some reason, the string functions still seem to hang on those characters. As an example, in a brand new rails

On Thu, Apr 26, 2018 at 07:29:41PM +0200, Emmanuel Florac via samba wrote: > Hi everyone, > > I have a very annoying character encoding problem. Have a look to this: > > # ls -l M*mo-1.* > -rw-rw-rw- 1 root root 8417218 6 sept. 2013 Mémo-1.aif > -rwxr--r-- 1 hope hope 8417218 6 sept. 2013 Mémo-1.aif > -rw-rw-rw- 1 root root 363175 6 sept. 2013 Mémo-1.m4a >

I have kind of an interesting problem. I have a form wherein people enter information. Big surprise. If they enter any "weird" characters like ø or é or whatever, the form will submit and all is well. However, I have a select box for the state which, if you''re looking at Spain, has states like A Coruña, Cádiz and País Vasco. These are pulled from the database which is set to

Hello Because I want to use different true type fonts with latex, I''m using the XeTeX typesetting engine for my sweave-documents. I''m using Lyx with Sweave on a Windows 7 PC and have set up LyX to work with XeTeX according to the following instructions: http://wiki.lyx.org/LyX/XeTeX Because the input file for XeTeX is assumed to be in UTF-8 encoding, I set the encoding

Hello, I have some questions concerning encoding and package distribution. We develop the ade4 package. For some data sets included in the package, there are accentued character (e.g. ?,?...). The data sets have been saved using latin1 encoding, but some of us use utf-8 and can not see some data sets which contains accented chracters. e.g: librarry(ade4) data(rankrock) rankrock in this case,

Hi all I love Sweave; use it all the time. But I recently received a new computer, and ever since I have had a problem I've never seen before. For example, I place the following in my Snw file: <<>>= sms <- read.table("http://www.sci.usq.edu.au/staff/dunn/Datasets/applications/popular/smsspeed.dat", header=TRUE) attach(sms) sms.lm <- lm( Time ~ Age*Phone,

Hi as part of our setup we have erb templates that are SQL files, we parse then to add in some user details to the SQL (these come from a hiera json file created from PHP) before using that file to create the database. If that data includes UTF-8 characters (for example an e with an acute accent) we get the error: Failed to parse template Detail: incompatible character encodings: UTF-8 and

SUMMARY: -------- I tried to identify the general and root causes for these problems with 1.9, by taking into account non-utf encoding, current patches, comments and ideas. I used ticket #2188 as base for explanations. This is a long read. I wanted to include all the relevant information in one place. I also included information about related tickets in LH and their status. I decided that adding

So, man, character encoding is confusing. Worse, I''m talking to a vendor-supplied database (read-only) that I did not add the data too. At least this vendor-supplied database is MySQL. So this database has some accented charactars in it. For instance, something as simple as a lowercase o with an acute accent, for example. At first, this character was not being displayed correctly in my

Hello, my application controller defines before_filter :set_charset def set_charset @headers["Content-Type"] = "text/html; charset=ISO-8859-1" end Everything is fine and accents are rendered correctly in the browser. However, when I call a controller/action from Ajax (Prototype), the charset is not taken in account and accents are garbage displayed (''?''