Jump to content


Not possible to use Russian letters at "Russian" Iron?

Cyrillic text

  • Please log in to reply
4 replies to this topic

#1 Pete Swede

Pete Swede

    Russian Bike Nut

  • Members
  • PipPipPip
  • 1,001 posts
  • Joined:27-April 11
  • Gender:Male
  • Location:Sweden
  • Interests:Woman, motorbikes, history and dogs...

Posted 19 March 2014 - 04:29 PM

I'm trying to find pictures of the first M72 batteries for a 3D project and was happy to find the Russian name of the factory that made "ЗМТ-7"    1Posted Image   ...was hoping to get some info from a Russian speaking member...

Feels like a waste of time to use Illustrator or Photoshop to first make pictures out of Cyrillic text before you can use them here...

Posted Image  
becomes: "Саратовский завод свинцовых аккумуляторов"

Not so cool... Posted Image

http://www.russianir...pic=15290&st=60

#2 digitalebola

digitalebola

    Russian Bike Nut

  • Admin
  • PipPipPip
  • 814 posts
  • Joined:04-March 07
  • Gender:Male
  • Location:Stone Mountain, GA

Posted 20 March 2014 - 07:25 AM

Unfortunately it is a limitation of the software the board runs on. It is possible to add it but it is not as simple as flipping a switch. There is down time involved and there is a risk of hosing the database in the process. At least that was the case a year or so ago when I looked into it.

I will check again with some of the updates that have come out though.

John

#3 Pete Swede

Pete Swede

    Russian Bike Nut

  • Members
  • PipPipPip
  • 1,001 posts
  • Joined:27-April 11
  • Gender:Male
  • Location:Sweden
  • Interests:Woman, motorbikes, history and dogs...

Posted 20 March 2014 - 09:23 AM

http://community.inv...xt#entry2064862

Quote

BTW it took me some time to find it - in IPB 3.0.x and newer you can just add this to the global_config.php
$INFO['sql_charset'] = 'utf8';


Quote

The only way to solve encodings problem totally is to set utf-8 absolutely everywhere: as the MySQL default encoding, as the database, each table and each field encoding, in MySQL collation, in PHP sources and in HTML pages.

Someone is speaking windows-1251...

Test to copy this to you reply window...   Сарато   then reply and go in and edit, you will now see Cyrillic text in your reply window... So the reply function speaks utf-8 until you post it, the receiver speaks windows-1251...

So for me it seams that the problem is windows-1251-based IPB 2 to UTF-8-based IPB 3... Was this forum upgraded from IPB 2 to IPB 3?...

//P

#4 digitalebola

digitalebola

    Russian Bike Nut

  • Admin
  • PipPipPip
  • 814 posts
  • Joined:04-March 07
  • Gender:Male
  • Location:Stone Mountain, GA

Posted 20 March 2014 - 01:00 PM

We are currently on 3.3.4.  One of the issues is transcoding the database. I do like the article you found - It is much more helpful than the support I got from IP Board.

I am not saying no - I am just letting everyone know it is not a switch flip like some other features.  I will review again this week.

When I do make the change it will probably coincide with a few other maintenance issues to save multiple down times.

John

#5 Pete Swede

Pete Swede

    Russian Bike Nut

  • Members
  • PipPipPip
  • 1,001 posts
  • Joined:27-April 11
  • Gender:Male
  • Location:Sweden
  • Interests:Woman, motorbikes, history and dogs...

Posted 20 March 2014 - 03:23 PM

Quote

It is much more helpful than the support I got from IP Board.

LOL... Yes, IPB:s support are not famous for being very supportive...




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users