#290 Problem language calendar

0.8.1
closed-fixed
nabber00
None
5
2013-06-20
2012-10-19
Pepito
No

I'm using 0.8.1 sphpblog .. My language is Spanish and so I have it set.
My problem is that I schedule our months and days in English. Also the date of entry.
Examples: 'october' for 'octubre', 'Sun' for 'Lum', 'Thursday, 18 de October de 2012,' for 'viernes, 19 de octubre de 2012'.
I see a user forum're like Russians.
Solucinar could help the problem.
Thank you.
Pepito

Discussion

  • nabber00

    nabber00 - 2012-10-19

    Let me see if I have this right, your version is set to the Spanish language. But you see some things like the time in English. When set to Russian you don't have this problem?

    There are known issues with the Spanish language in particular, I need someone with Spanish language expertise to fix it. See bug ID: 3072128.

     
  • nabber00

    nabber00 - 2012-10-19
    • labels: 626485 -->
    • assigned_to: nobody --> nabber00
    • milestone: 2845182 --> 0.8.1
    • status: open --> pending-duplicate
     
  • Pepito

    Pepito - 2012-10-22
    • status: pending-duplicate --> open-duplicate
     
  • nabber00

    nabber00 - 2012-10-22
    • status: open-duplicate --> open-accepted
     
  • nabber00

    nabber00 - 2012-10-22

    I see. It looks like the problem is the calendar, we are using PHP to generate the date/time information. I'm using setlocale() in the language file but that doesn't seem to work for some reason.

     
  • Comment has been marked as spam. 
    Undo

    You can see all pending comments posted by this user  here

    Anonymous - 2013-04-16

    I had the same problem with the german translation. This happens because languages/sb_lang.php doesn't call sb_language( $page ); anymore (it's commented out) and thus the locale isn't set.

    Localized dates probably don't work in any language.

     
    Last edit: Anonymous 2014-10-29
  • nabber00

    nabber00 - 2013-06-20
    • status: open-accepted --> closed-fixed
     
  • nabber00

    nabber00 - 2013-06-20

    Thanks for the tip! I was able to fix this in svn r248.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks