Bad IMG SRC URLs
Robert A. Rosenberg
run into a problem with the IMG tags generated via
Markup->Inline->Image. My page has a charset of UTF-8 and I am
attempting to add an IMG tag pointing at a JPG whose name contains
accented letters. Instead of the file name showing up using these
letters, they are showing up as %XX%XX (ie: The Encoded UTF-8 version
of the character's ISO-8859-1 Codepoint). My problem is that when I
try to use the image from the Web Site (where the character occurs in
the file name) the browser does not find it (I get the ALT string not
the image). I have to manually replace the %XX%XX with the character
in the tag for it to work. Is this a known problem and if so is there
a fix/setting so the SRC parm is created with the character not the
encoded value?
Thanks.
LuKreme
> Is this a known problem and if so is there a fix/setting so the SRC parm is created with the character not the encoded value?
I don't have access to v9 anymore (easily(, but is this a document encoding issue? That is, are you editing a UTF-8 document or does BBEdit have it marked as ISO-8859-1?
--
Your letters they all say that you're beside me now. Then why do I feel
alone? I'm standing on a ledge and your fine spider web Is fastening my
ankle to a stone.
Robert A. Rosenberg
On 07 Apr 2012, at 12:42 , Robert A. Rosenberg wrote:
> Is this a known problem and if so is there a fix/setting so the SRC parm is created with the character not the encoded value?
I don't have access to v9 anymore (easily(, but is this a document encoding issue? That is, are you editing a UTF-8 document or does BBEdit have it marked as ISO-8859-1?
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
LuKreme
On 07 Apr 2012, at 20:03 , Robert A. Rosenberg wrote:
> It is marked and saved as ISO-8859-1.
[snip]
> Even though the file name is xxxxêxxx.jpg the src shows up as xxxx%CC%82xxx.jpg. As I noted this causes problems since when the browser looks for xxxx%CC%82xxx.jpg is does not find it since the image has been uploaded as xxxxêxxx.jpg.
Probably because your server is sending UTF-8. Try changing the document type to UTF-8 and see if that helps?
--
Not every flower can say love, but a rose can. Not every plant
survives thirst, but a cactus can. Not every vegetable can read, but
bless it, look at you, having a little go.
Miers David
On Apr 8, 2012, at 3:11 PM, LuKreme wrote:
>> Even though the file name is xxxxêxxx.jpg the src shows up as xxxx%CC%82xxx.jpg. As I noted this causes problems since when the browser looks for xxxx%CC%82xxx.jpg is does not find it since the image has been uploaded as xxxxêxxx.jpg.
>
> Probably because your server is sending UTF-8. Try changing the document type to UTF-8 and see if that helps?
Seems like using accented characters is akin to using spaces in file names, something you just shouldn't do...I'd just rename the images
LuKreme
That's 1990's thinking. This 2011 and apps that don't work well and play with UTF-8 and spaces are simply broken.
And for the record, I use spaces in filenames all the time and have for 30 years.
--
Oh, he's just like any other man, only more so.
Fritz Anderson
On 8 Apr 2012, at 10:06 PM, LuKreme wrote:
> On 08 Apr 2012, at 17:59 , Miers David wrote:
>
>> Seems like using accented characters is akin to using spaces in file names, something you just shouldn't do...I'd just rename the images
>
> That's 1990's thinking. This 2011 and apps that don't work well and play with UTF-8 and spaces are simply broken.
That's very satisfying.
If my file names don't work on the server my client is committed to, can I tell him he should pay me anyway, because I'm right and he should be ashamed of his broken server?
> And for the record, I use spaces in filenames all the time and have for 30 years.
I go back only to 1984 with spaces, but they broke one part or another of the Xcode/GNU toolchain as recently as a couple of years ago. I could have denounced Xcode (Project Builder, CodeWarrior, THINK C, MPW) as simply broken, but given the choice between going on strike 1984-2009, and producing something I could get paid for, I took the spaces out.
— F
Charlie Garrison
On 7/04/12 at 10:03 PM -0400, Robert A. Rosenberg
<rar...@banet.net> wrote:
>It is marked and saved as ISO-8859-1.
Have you tried changing the encoding to utf8 and then adding an
image? I've either missed something in this thread or BBEdit is
doing the right thing; the document isn't set to utf8 so it's
not inserting unicode characters; it's encoding characters based
on the document's encoding.
Charlie
--
Ꮚ Charlie Garrison ♊ <garr...@zeta.org.au>
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
〠 http://www.ietf.org/rfc/rfc1855.txt
Miers David
Watts Martin
That's 1990's thinking. This 2011 and apps that don't work well and play with UTF-8 and spaces are simply broken.
And for the record, I use spaces in filenames all the time and have for 30 years.
LuKreme
On 09 Apr 2012, at 11:24 , Watts Martin wrote:
> On Apr 8, 2012, at 20:06 , LuKreme wrote:
>
>> That's 1990's thinking. This 2011 and apps that don't work well and play with UTF-8 and spaces are simply broken.
>>
>> And for the record, I use spaces in filenames all the time and have for 30 years.
>
> Well, I don't think the question was about apps dealing with filenames, but rather about browsers dealing with URIs, right?
If the webserver is set to serve UTF-8 pages and you have a page that should be UTF-8 but is encoded in IOS-859-1, strange things can happen. Also, it is not a URI that is the issue, but a link inside an HTML document, and how it is encoded.
There is a difference between typing www.åpple.com into a web browser and having an href in an HTML document.
> I might use any acceptable filename on a Mac, like "Writing blogging ideas" with spaces and no (visible) extension, but if I was going to put that on a web server, I'd definitely change that to "writing_blogging_ideas.html" to avoid confusion. If I didn't, I'd be relying on browsers and web servers to figure out how to handle those spaces. They probably would, sure -- but most browser will also handle horribly broken HTML. As developers, though, we probably shouldn't just say, "Your browser should be smart enough to figure out what I mean even when I'm violating the spec, because the spec is old and stupid."
But the browsers ARE smart enough to figure it out. If I type into Safari
macupdate.com/web browsers
it loads <http://macupdate.com/web%20browsers>, just as it should.
--
If the #2 pencil is the most popular, why is it still #2?