Jump to content

language files BUGs


Guest qsd

Recommended Posts

Here is example

<?php

$lang = array (

//2.2

'gbl_more_search'                => "More Search Options",
'gbl_auto_close'                => "(Message will auto close in 2 seconds)",
'gbl_my_friends'                => "My Friends",
'gbl_sitemsg_header'            => 'Site Message',
'gbl_gd_reload'                 => 'Click to generate a new image',
'mygallery'                        => "My Albums",
//2.1.4 - for IDM when released
'idm_header'                    => "Downloads",



Here is what to look at:

'gbl_sitemsg_header' => 'Site Message',

'Site Message' should be "Site Message" ... for all, right? There are errors like this on many language files, I'm fixing this while I translate to Bulgarian but i think this is kind of bugs in them.. ?

Link to comment
Share on other sites

/**
* JS Language File: English
*/

var message_pop_up_lang =
{
    // DEFAULT
    'error'               : 'An Error Occurred',
    'no_permission'       : 'You do not have permission for that action',
    'cannot_cont'       : 'Cannot continue with this request',
    'settings_updated' : 'Settings Updated',
    
    // Custom errors:
    'pp_date_error'     : 'Date must be a legal valid date',
    'pp_friend_exist'   : 'That member does not appear to exist',
    'pp_friend_already' : 'You already have that member as your friend',
    'pp_friend_removed' : 'Friend(s) Removed',
    
    // Friend added:
    'pp_friend_added'     : 'Your friend(s) have been added to your list!',
    'pp_friend_added_mod' : 'Your friend must approve your request',
    'pp_friend_approved'  : 'Friend request approved',
    
    // Comments update
    'pp_comments_updated'  : 'Comments updated',
    'pp_comment_added_mod' : "Comment must be approved before it's shown",
    
    // POLL MODULE
    'already_voted' : 'You have already voted',
    
    // ARTICLES MODULE
    'rating_updated' : 'Your rating has been updated',
    'rating_added'   : 'Your rating has been added',
    'rating_already' : 'You have rated this article already'
};

/**



' or " here?!?!

I'll submit to BUGs as well... but let me know because i'm translating..

Link to comment
Share on other sites

its not directly a bug, but strings in single quotings can be faster to process for the interpreter than strings in double quotes.

escape sequences and interpreted stuff have to be in double quotes. when using single quotes, the php interpreter will not search for such things.

so u can use single quotes to make your scripts faster, but i don

Link to comment
Share on other sites

its not directly a bug, but strings in single quotings can be faster to process for the interpreter than strings in double quotes.



escape sequences and interpreted stuff have to be in double quotes. when using single quotes, the php interpreter will not search for such things.



so u can use single quotes to make your scripts faster, but i don

Link to comment
Share on other sites

To be fair, since this is now virtually feature complete, there's no harm to starting translation now. After all, all it means is that he'll have less work to do later when the final is released :)



Right! ;)



its not directly a bug, but strings in single quotings can be faster to process for the interpreter than strings in double quotes.



escape sequences and interpreted stuff have to be in double quotes. when using single quotes, the php interpreter will not search for such things.



so u can use single quotes to make your scripts faster, but i don

Link to comment
Share on other sites

  • 4 weeks later...

I started upgrading the Spanish Pack to 2.2... too many changes from no quotes to single quotes... then the problem going from $lang['topic_text'] to 'topic_text'... yes, I know they work the same way, but it would be kind of nice if you guys stick to a specific format so we don't have to be going back and forth... :)

Link to comment
Share on other sites

then the problem going from $lang['topic_text']to 'topic_text'... yes, I know they work the same way, but it would be kind of nice if you guys stick to a specific format so we don't have to be going back and forth



All language files should be in the second format. How are you ending up, or seeing, $lang['some_key'] format?

If you use the language API file, or edit languages from the ACP, they should always be in the second format in 2.2. :huh:
Link to comment
Share on other sites

Some files were left like that in the 2.1 release... two to be exact (no biggie)... but they're all in the same format now.


Now, for some (not all) of the entries in some files there were no quotes and now all of them seem to have single quotes, for instance...


We went from (2.1)

reg_success                    =>    "Registration Successful",

To (2.2)

'reg_success'                    =>    "Registration Successful",




Is that something that was "fixed" for this release or were my files corrupted somehow?

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...