aspx language settings and FP2K

  • Thread starter Thread starter Dennis Blondell
  • Start date Start date
D

Dennis Blondell

Hi, I have translated a clients site into Japanese and used the language
settings in FP2K page properties to set the page to Japanese and everything
is working fine for the htm pages but the aspx pages only retrieve Japanese
text from the database and won't display Japanese text in the page itself.
Are there other language tags I need to put in for aspx? I have asked my
aspx guy and tried adding "<%@ import Namespace= " tags to include global
language settings with no luck. He has no idea about what is causing the
problem. Any suggestions? Roll on Oct 21st and FP2003
Try http://www.leisuretours.co.nz/nihongo/j_booking.aspx?id=clt01 for an
example.

Thanks heaps
 
I don't know if this is part of it, but if you look at the actual code for
the page there are at least three complete document headers including <body>
tags. You can only have one and it must be at the beginning. Also, your page
has lots of extra closing tags for the document (</body></html>). This could
also be causing problems as the browser may not be able to figure out what
part of the page can be Japanese.

For ASPX, it's not just a matter of importing the globalization namespaces.
You'll have to set the culture and language information for the page.
Importing the System.Globalization is not enough, you have to use it.

There are some globalization examples at:
http://msdn.microsoft.com/library/e...ization.asp?frame=true#cpsmpcultureinfosample

http://samples.gotdotnet.com/quickstart/aspplus/

http://samples.gotdotnet.com/quickstart/aspplus/doc/cultureencoding.aspx

http://samples.gotdotnet.com/quickstart/aspplus/doc/localizingapps.aspx

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage
 
Thanks Mark for your comments. A response is below:

Mark Fitzpatrick said:
I don't know if this is part of it, but if you look at the actual code for
the page there are at least three complete document headers including
Click to expand...
tags. You can only have one and it must be at the beginning. Also, your page
has lots of extra closing tags for the document (</body></html>). This could
also be causing problems as the browser may not be able to figure out what
part of the page can be Japanese.
Click to expand...

I didn't realise this. It is due to the include page within the aspx page. I
use FP include page webbot for the htm pages and <!-- #Include
virtual="IncludePage.htm" --> for the aspx. It looks like the aspx page is
including everything, even <body> and <html> tags. I have tried leaving out
For ASPX, it's not just a matter of importing the globalization namespaces.
You'll have to set the culture and language information for the page.
Importing the System.Globalization is not enough, you have to use it.

There are some globalization examples at:
http://msdn.microsoft.com/library/e...ization.asp?frame=true#cpsmpcultureinfosample

http://samples.gotdotnet.com/quickstart/aspplus/

http://samples.gotdotnet.com/quickstart/aspplus/doc/cultureencoding.aspx

http://samples.gotdotnet.com/quickstart/aspplus/doc/localizingapps.aspx
Click to expand...

Thanks for the hints and links. I will check them out and pass them onto my
aspx guy.

Dennis
 
what kind of aspx app is it? is it an app like the ibuyspy, or asp-nuke?
I'm only asking because i've recently become interested in the asp.net apps
again ;-)
 
Not sure what you mean Chris, but the web site where aspx is being used is
only a basic database retrieval site and is getting us some practice in
..net. I only use FP2K as I have very limited programming experience. My
colleague, who does programming for me raves about Microsoft's Web Matrix
(which is a free app), which he uses for coding and uses DreamWeaver to
modify pages. He says DreamWeaver 2004 works well with WebMatrix as it
doesn't try and change things too much. I am hoping that FP2003 will handle
asp.net pages well (or at least know to how to open them) and save me from
learning how to use a new program. I have never heard of ibuyspy, or
asp-nuke.
 
FrontPage 2003 is excellent for ASP.Net. It has the same type of wizards for
doing ASP.Net database connectivity as it has had for ASP. The Editor is
very friendly to ASP.Net, and has a number of tools that facilitate working
with ASP.Net. However, Web Matrix and Visual Studio.Net are the serious
development environments to use for ASP.Net. I use FrontPage to do the HTML
Page Template code, and then paste it into an ASPX page in Visual Studio to
code it.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
http://www.takempis.com
Big Things are made up of
Lots of Little Things.
 
and then back to fp for publishing/ management or do you do that from
visualstudio?
 
Thanks guys, then that's what I'll do. Get FP2003, design the pages in it,
use Web Matrix for coding (or learn how to) then finetune and publish
through FP.
 
Well, actually, in my case, we do it from Visual SourceSafe. It could be
done via Visual Studio or FrontPage. It can even be done by simply
transferring files in one way or another, as ASP.Net assemblies don't need
to be registered on the server, just in the /bin folder of the web app.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
http://www.takempis.com
Big Things are made up of
Lots of Little Things.
 
I see. Thanks for the info. I'm sort of gnawing on the idea of trying
again to delve into .net. I has a fairly unsuccessful experiment with the
ibuyspy portal (now rainbow portal, I think).
I think I'll start by deploying and trying to come to an understanding of a
pre-existing application. I'm leaning towards:
http://www.aurigma.com/Products/MediaGallery/
unless someone knows something I don't ;-)
 
Back
Top