DragonPrime - LoGD Resource Community
Welcome Guest
  • Good morning, Guest.
    Please log in, or register.
  • July 31, 2010, 03:49:48 AM
Home Forums News Links Downloads Login Register Advanced Search
* * *
DragonPrime Menu
Login
 
 
Resource Pages
IRC Channels
Search

Pages: [1]   Go Down
  Print  
Author Topic: Translation question  (Read 1419 times)
0 Members and 1 Guest are viewing this topic.
MOW
Guest
« on: February 24, 2005, 11:50:11 AM »

hi have a question,

i would like to change the mainpage into german.
but i find no way to come to the mainpage when i login.
and into the grotto at untranslated texts is alway write "There are no untranslated texts in the database! Congratulations!!!"
the main language is german.
i use prerelease 14.

MOW
Logged
Sichae
iMod God
SVN Users
Mod God
*
Offline Offline

Posts: 3458


If ya didn't get it by now... you're hopeless...


View Profile WWW
« Reply #1 on: February 24, 2005, 05:12:59 PM »

I believe for the main page, you need to manually translate the code.

Since there is no internal way to get to the outside, in order to translate.

Perhaps something new in the next PR?
Logged

If you didn't understand anything in the above post, don't try to attempt anything suggested.

XChrisX
Global Moderator
Mod God
*****
Offline Offline

Posts: 4652

Be aware of the squirrel!


View Profile WWW
« Reply #2 on: February 25, 2005, 04:52:27 AM »

the untranslated part also checks the home.php, create.php and so on...

but it has to be activated... Then the untranslated table should contain some texts for you to translate... Wink
Logged

Running for more than three years now:
MOW
Guest
« Reply #3 on: February 25, 2005, 07:28:18 AM »

how can i activate the untranslatet table?

/Edit: my settings are:
Permanently collect untranslated texts (overrides the next settings!)    YES
Are we currently collecting untranslated texts?    1
Maximum number of players    

but it shares no untranslated texts

Huh

MOW
« Last Edit: February 25, 2005, 07:37:13 AM by MOW » Logged
KhanTervel
Guest
« Reply #4 on: February 25, 2005, 11:23:06 PM »

Hi,

I suppose there is a bug in the table creation as untranslated table is created as InnoDB but has to be MyISAM (because of the delayed insert statement). So just change the table type of "untranslated" to MyISAM and it should start collecting texts.

Regards,
« Last Edit: February 25, 2005, 11:24:52 PM by KhanTervel » Logged
Kendaer
Global Moderator
Mod God
*****
Offline Offline

Posts: 1806


Once a dragon, always a dragon


View Profile WWW
« Reply #5 on: February 25, 2005, 11:32:36 PM »

Khan, it is only on version of mySQL prior to 4.0.14 which require it to be MyISAM instead of InnoDB.

The code looks at 'requiremyISAM' flag in the table descriptor and will create it as myISAM if you are using a version of mysql less tan 4.0.14, otherwise, it can (and should) be InnoDB.

Logged

Ex co-developer of LotGD
KhanTervel
Guest
« Reply #6 on: February 25, 2005, 11:45:08 PM »

you sure? I am using 4.1.9 and it was the same situation.

... now i checked mysql documentation and you can see http://dev.mysql.com/doc/mysql/en/insert-delayed.html

"INSERT DELAYED works only with MyISAM and ISAM tables"
Logged
Kendaer
Global Moderator
Mod God
*****
Offline Offline

Posts: 1806


Once a dragon, always a dragon


View Profile WWW
« Reply #7 on: February 26, 2005, 12:14:39 PM »

Ahh.. I see.
Eric changed it to use insert delayed.

*grouse*

My change initially had been because InnoDB in versions prior to 4.0.19 didn't allow you to index on a text field, which is what we needed to do.

I hadn't realized that eric made  change which caused a different dependancy on myISAM.

I'll fix this in the installer.

Logged

Ex co-developer of LotGD
Kendaer
Global Moderator
Mod God
*****
Offline Offline

Posts: 1806


Once a dragon, always a dragon


View Profile WWW
« Reply #8 on: February 26, 2005, 12:26:38 PM »

After talking with Eric, instead of forcing that table to be MyISAM we are removing the 'delayed' keyword there.

This does mean that the gathering of untranslated texts could be more intensive on a system, but there is a higher cost to having table types be of multiple types in the memory required by MySQL to manage the multiple types of tables.

Thanks for pointing this out.
Logged

Ex co-developer of LotGD
Pages: [1]   Go Up
  Print  
 
Jump to:  


*
DragonPrime Notices
Welcome to DragonPrime - The LoGD Resource Community!

Support Us
No funds raised yet this year
Your help is greatly appreciated!
Who's Online
26 Guests, 1 User
spector
DragonPrime LoGD
Recent Topics
Home Forums News Links Downloads Login Register Advanced Search