PEAK XOOPS - Re: backend.php & EMLH in englishin japanese

Re: backend.php & EMLH

List posts in the topic

normal Re: backend.php & EMLH

msg# 1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.1.2.1.1
depth:
20
Previous post - Next post | Parent - Children.1 | Posted on 2005/4/18 9:31
domifara  Private 1st Class   Posts: 19
I'm sorry ..incomprehensive...


When the character is cut short, the same problem is brought up.

The problem when the character for RSS is cut short is two.


1.When you cut the language tag character short
Because the language tag for EMLH becomes a character string not shut, the language
tag cannot be correctly processed.

When you cut the character short
After editing the language tag, the one like Xoops Multlang HACk seems to keep necessary ..cutting the character short.. previously.
sorry this is
Multlang HACk was not necessary.
etc.
				'description' => xoops_utf8_encode(htmlspecialchars(xoops_substr(easiestml($story->hometext()) , 0 ,125), ENT_QUOTES))

call easiestml function

2.Backend.php has only one Cashe.
It doesn't change because backend.php has only one Cashu though and the language tag are previously processed.

I think
improve this
・In backend.php, the character is not cut short.

or

・Is Cashu turned off
$tpl->xoops_setCaching(2); 
to
$tpl->xoops_setCaching(0);

or

・I think that it remodels backend.php to Cashe of each language.

Votes:0 Average:0.00

Posts tree

  Advanced search


Login
Username or e-mail:

Password:

Remember Me

Lost Password?

Register now!