Today's localisation sprint started with a presentation from Piotr on how multilingual installations works in CiviCRM.
Multilingual is when you want to have not only a localised interface, but many co-existing languages. So for example the labels of custom fields may need to be in English or Spanish if the organisation has a bilingual website. In general, most labels can be translated using multilingual, but not the data itself. The main except to this is the contact name, so that it can be entered in multiple alphabets.
Blogues
Restez à l'affut des dernières nouvelles de CiviCRM avec les billets de blogue de développeurs et d'utilisateurs de partout dans le monde.
26 avril 2010
par mbriney sujet CiviCase, Architecture, CiviCon, CiviCRM, TeamsThe following notes were gathered from the CiviCon session on what the community would like to see in CiviCRM 4.0:
* Goals * No new features * Framework switch * Not as major a rewrite as it looks * Don't want to change many of the private APIs * Want to switch away from pear * Test unit coverage * Better API hooks * What users would like to see * Continuous Integration * Hudson - as you submit code runs through suite of unit tests to see what's broken * Better decoupling * Drupal Forms API
26 avril 2010
par michaelmcandrew sujet DocumentationIt's 5 to midnight and we're just wrapping up. Mr Kurund says that I can't go to bed until I've written this post, so...
Participating in the second book sprint is just as fascinating as it was the first time around, but the dynamic is definitely different. Having a book in place already makes a big difference - there's no panicking that we'll end up with the sections half finished, and it is easier to cover components when a lot of the design decisions have already been made. Having already written sections on the components is especially helpful when covering new components.
25 avril 2010
par scyrma sujet CiviCRM, Internationalization and Localization, SprintsWell, it's been done, we chose the translation platform: Transifex. We're fully aware that we did not actually choose a platform that fully supports the ideal situation, but such a platform does not exists. This is more the choice of a promising back-end which we hope we can eventually develop into the ideal situation.
The interesting part in the discussion was finding a balance between the technical and functional interests.
25 avril 2010
par michal sujet CiviCRM, Internationalization and Localization, SprintsThat's right, you probably noticed there are two sprints going on here in Tahoe. You can read the report from the book sprint in Jack blog post, now it's time you found out what's the second sprint about.
24 avril 2010
par jackaponte sujet DocumentationIt's 11pm in beautiful Truckee, CA, and the CiviCRM Book Sprint crew of twelve dedicated souls is still hard at work after a 10am start. We've come from across the US and around the globe to help update and improve the existing book, making it more useful for CiviCRM users, developers, implementers, and administrators.
24 avril 2010
par michal sujet CiviCon, CiviCRMThis Thursday, the first ever CiviCon took place. After five years of constant development of the CiviCRM project, we felt it was definitely time to have an in-person gathering of CiviCRM community members, talk about past, plan the future and enjoy being together. It was really a great day.
21 avril 2010
par lobo sujet CiviCRM, DrupalWe had another super awesome day at DrupalCon SF 2010 today. Was great to watch and hear Cricket from Jane Goodall Institude proclaim: "I love CiviCRM!" to the audience :) To keep the momentum going, we've scheduled two BoF sessions for today. Please check the BoF notice board for the rooms.
20 avril 2010
par AllenShaw sujet DrupalOriginally posted at TwoMiceAndAStrawberry.com.
I recently had to modify CiviCRM to support a specific use case for a client. In this project I needed to allow the user to enter anything in the Individual Prefix field, rather than choosing from a list of options. The client in this case was very sensitive about presenting the individual's honorific precisely as the individual wants, so that "Dr.," "Rev. Dr.," and "Most Rt. Rev. Dr." should all be possible, along with anything else the user might want to enter.
