Issue 11525 - META tag for cs project pages
Summary: META tag for cs project pages
Status: CLOSED FIXED
Alias: None
Product: Native-Lang
Classification: NLC
Component: www (show other issues)
Version: current
Hardware: PC Linux, all
: P3 Trivial
Target Milestone: ---
Assignee: lsuarezpotts
QA Contact: issues@native-lang
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-16 10:22 UTC by pavel
Modified: 2003-02-26 06:05 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description pavel 2003-02-16 10:22:16 UTC
Hi Louis,

Czech Native-Lang project pages need META tag containing iso-8859-2 charset.
Comment 1 lsuarezpotts 2003-02-18 19:11:59 UTC
thanks, accepting
louis
Comment 2 lsuarezpotts 2003-02-18 20:35:44 UTC
done. please test.
louis
Comment 3 pavel 2003-02-18 20:44:14 UTC
Thank you Louis,

it works in Mozilla, but the old TAG remains there and I wonder it it
would work in other browsers:

<html><head>
<meta http-equiv="content-type" content="text/html ; charset=iso-8859-2">
<meta HTTP-EQUIV="Content-Type" CONTENT="text/html;CHARSET=iso-8859-1">
  
Only the first one should be there. This is incorrect HTML.
Comment 4 lsuarezpotts 2003-02-19 05:27:48 UTC
Hi
I am aware it is incorrect html and i am aware the old tag remains
there. It has to, for the rest of the site. I can try w/ the
iso-8859-2 only but I cannot guarantee the rest of the site will work
well.
What I have done is a little hack: when the project is cs, then the
1s0-..-2 governs page display. At all other times it is either -1 (or
the japanese charset). (The double charsets don't, evidently, confuse
modern browsers. If they did, this project would be horrible: look at
the source of, say, Porting.)

 To further explain this essentially temporary hack, SC composes all
its web pages in parts: thereaer separate Head, Standard, Navbar,
Footer templates.  These are all put together as needed.  The Head
(where charset is set) is not peculiar to a project but general to all
projects.  What I did with Ja and now with cs was make a call to the
server to read, if the project is cs or ja, a particular charset. It
works. I tested it using several browsers.  The rest of the site, as I
explained, probably needs the standard iso.  

I'd be surprised if it doesn't work in all modern browsers.  I'm
concerned, of course, about IE5 for Win and Ntscp 4.7x, the banes of
any designer.  

the upgrade to the infrastructure has resources that allow language
specification, so this won't be necessary. :)

cheers, and good luck,
Louis
 
Comment 5 pavel 2003-02-25 21:48:31 UTC
Louis,

it stopped working today. I use Mozilla and it does not grok the
current header:

<meta HTTP-EQUIV="content-type" CONTENT="text/html; charset=ISO-8859-1">
 	<meta HTTP-EQUIV="content-type" CONTENT="text/html ;
charset=iso-8859-2">

Maybe it is a space before ;. I think it would be better to solve this
properly.
Comment 6 lsuarezpotts 2003-02-25 23:09:52 UTC
I'll fix. 
i was playing with the webmacros last night and thought i had fixed it.
-louis
Comment 7 lsuarezpotts 2003-02-25 23:25:44 UTC
I fixed it for cs.
I actually spent  a couple of  hours last night seeing if I could use
the webmacro commands to work for both.
am trying again
louis
Comment 8 lsuarezpotts 2003-02-25 23:42:06 UTC
fixed.
the code now reads... and it works, though is not perfectly pretty:

 #if ($currentProject.getName()=="ja"){
 	<META HTTP-EQUIV="content-type" CONTENT="text/html ; charset=EUC-JP">
 	}#else {
		#if ($currentProject.getName()=="cs"){
 	<META HTTP-EQUIV="content-type" CONTENT="text/html ;
charset=iso-8859-2">
  	}#else {
	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
	}
}
louis
Comment 9 pavel 2003-02-26 06:05:34 UTC
Works great. Thanks!