Projects tagged ‘multilingual’ and ‘python’

XBMC media center is a free cross-platform media-player jukebox and entertainment hub. XBMC is open source (GPL) software available for Linux, Mac OS X, Microsoft Windows operating-system, and the ... [More] Xbox game-console. XBMC can play a very complete spectrum of of multimedia formats, and featuring playlist, audio visualizations, slideshow, and weather forecast functions, together with a multitude of third-party plugins. [Less]

XBMC is a multimedia player/jukebox for the Xbox from Microsoft. It can be used to play or view most common video, audio, and picture formats such as MPEG-1/2/4, DivX, XviD, MP3, AAC, JPG, and GIF ... [More] directly from a CD or DVD in the Xbox DVD-ROM drive or from the Xbox hard drive. XBMC can also stream files over a local network or from the Internet. Playlist and slideshow functions, a weather forecast, and many audio visualizations are also included. [Less]

A library providing support for multilingual content in Django models. Features: - simple model syntax - nice admin integration - adding a language requires only a change to project settings ... [More] - language-independent data ordering and filtering via the usual ORM API [Less]

A tree based django CMS applicationThis Django CMS enable you to create and administrate hierarchical pages in a simple and powerful way. DemoThis admin interface is no up to date, but could give ... [More] you an idea of what the software is doing: admin : http://pagesdemo.piquadrat.ch/admin/ frontend : http://pagesdemo.piquadrat.ch/pages/ See the Screenshots Key featuresAutomatic creation of localized placeholders (content area) in admin by adding placeholders tags into page templates. Django admin application integration. Multilingual support. Various Rich Text Editors are directly available. Page can be moved in the tree in a visual way. The tree can be expanded/collapsed. A cookie remember your preferences. Possibility to specify a different page URL for each language. The frontend example provide a basic "edit in place" feature. Directory-like page hierarchy (page can have the same name if they are not in the same directory) Every page can have multiple alias URLs. It's especially useful to migrate websites. Possibility to integrate 3th party apps Optional featuresHere is the list of features you can enable/disable: Revisions. Support for future publication start/end date. Inherited page permissions. Grant all rights to a user. Grant rights on a page only. Grant rights on a page hierarchy. Inherited templates. Page redirection to another page. Page tagging. User input sanitizer (to avoid XSS). Sites framework Dependencies & CompatibilityDjango 1.1, Django 1.0 with older release (1.0.5) Python 2.3. django-mptt django-tagging (if PAGE_TAGGING = True) html5lib (if PAGE_SANITIZE_USER_INPUT = True) django-tinymce (if PAGE_TINYMCE = True) jQuery. Compatible with MySQL, PostgreSQL, SQLite3, some issues are known with Oracle Help and documentationFAQ Install in existing project Check the rest of the Wiki Or post something into the Google Group Test itTo test this CMS checkout the code with subversion : svn checkout http://django-page-cms.googlecode.com/svn/trunk/ django-page-cms And then, run the development server : cd example/ manage.py syncdb manage.py runserverTo run the test suite: python setup.py testIf you have the special page permission system enabled and you are not admin, you must create a PagePermission object with all rights assigned to your user. After that you will be able to create pages. Handling imagesDjango page CMS can use these other projects: http://code.google.com/p/django-page-cms-image-placeholder/ http://code.google.com/p/django-filebrowser/ TranslationsThis application is available in english, german, french, spanish, danish and russian. Site made with Django Page CMShttp://www.osff.no/ Other Django CMSDjango CMS comparaison [Less]

TOW (Trac On Windows) project is for providing Trac(http://trac.edgewall.org/) packages on Windows with easy. Trac is not easy to install on Windows.

The SELF Platform will have two main functions. It will be simultaneously a knowledge base and a collaborative production facility: On the one hand, it will provide information, educational and ... [More] training materials that can be presented in different languages and forms: from course texts, presentations, e-learning programmes and platforms to tutor software, e-books, instructional and educational videos and manuals. On the other hand, it will offer a platform for the evaluation, adaptation, creation and translation of these materials. The production process of such materials will be based on the organisational model of Wikipedia. This software project is akin to what Wikimedia is to Wikipedia. The users of this software can be any educational or training institute that intends to run an online distributed collaborative authoring and learning service. Project website: http://www.selfproject.eu/ Other Software Required: The platform is based on Python, Zope, and GNOWSYS (the latter is a GNU Project), and does not have any non-free software dependencies. Other Comments: The first development release can be downloaded from http://gnowledge.org/selfApp.tgz [Less]

Provides support for multilingual fields. The goal of this project is to Keep It Simple (Stupid!) ( http://en.wikipedia.org/wiki/Keep_it_simple_stupid ) so there is only 33lines of code (excluding ... [More] the comments). Example: models.py from django.db import models from multiling import MultilingualModel class Language(models.Model): code = models.CharField(max_length=5) name = models.CharField(max_length=16) class BookTranslation(models.Model): language = models.ForeignKey("Language") title = models.CharField(max_length=32) description = models.TextField() model = models.ForeignKey("Book") class Book(MultilingualModel): ISBN = models.IntegerField() class Meta: translation = BookTranslation multilingual = ['title', 'description']>>> lang_en = Language(code="en", name="English") >>> lang_en.save() >>> lang_pl = Language(code="pl", name="Polish") >>> book = Book(ISBN="1234567890") >>> book.save() >>> book_en = BookTranslation() >>> book_en.title = "Django for Dummies" >>> book_en.description = "Django described in simple words." >>> book_en.model = book >>> book_en.save() >>> book_pl = BookTranslation() >>> book_pl.title = "Django dla Idiotow" >>> book_pl.description = "Django opisane w prostych slowach" >>> book_pl.model = book >>> book_pl.save() >>> >>> # now here comes the magic >>> book.title_en u'Django for Dummies' >>> book.description_pl u'Django opisane w prostych slowach'To have it interated with Django Admin nicely, try this: admin.py from django.contrib import admin import models class BookTranslationInline(admin.StackedInline): model = models.BookTranslation extra = 1 min_num = 1 class BookAdmin(admin.ModelAdmin): list_display = ["ISBN"] inlines = [BookTranslationInline] admin.site.register(models.Book, BookAdmin) [Less]

The modeltranslation application can be used to translate dynamic content of existing models to an arbitrary number of languages without having to change the original model classes. It uses a ... [More] registration approach (comparable to Django’s admin app) to be able to add translations to existing or new projects and is fully integrated into the Django admin backend. Please read the InstallationAndUsage page. Changelogv0.1Date: 2009-02-22 Initial release packaged from revision 19 [Less]

Simple blog application for Djangodjango-lazyblog is a simple blog application for lazy Django developers bored to build again and again a blog engine. Beware: it still is in development. Do not use ... [More] it in a production environment. Dependencies and compatibilityDjango 1.0 Python 2.4 Django MPTT Wikib Markup Syntax python-markdown2 InstallationFirst, get the source: svn checkout http://django-lazyblog.googlecode.com/svn/trunk/ django-lazyblogCopy django_lazyblog folder anywhere in your PYTHONPATH. Add the application django_lazyblog in your settings.py. [Less]

Experimental pluggable model i18n solution for djangoWARNING: This project is just an experiment, take a look at the code if you are curious but keep in mind this is not a working solution. What ... [More] does "pluggable" model i18n means?The developer should be able, for example, to install this app on an existing project, and be able to add i18n support to models without modifying their definitions and have good defaults in views and templates (model field access and ORM queries). The basic idea is that the developer for each multilingual model in an app defines and register a translation options object (ModelTranslation objects) in the translation.py file (think in the admin.py files idea). Then a dynamic translation model is created for each registered model to store the translations which can be acceded thanks to some extensions on the original model. This makes possible come cool stuff, like add model i18n on 3rd party apps without touching them or write an app and then, when you are comfortable with your models, make them multilingual. Code exampleDefinitionThis is how you define what is multilingual content. Suppose you have this model: from django.db import models class Item(models.Model): slug = models.SlugField() title = models.CharField(max_length=50) description = models.CharField(max_length=150)You create a translation.py file on the app dir and define there your translation options for the model and register them like this: import translations class ItemTranslation(translations.ModelTranslation): fields = ('description', 'title') translations.register(Item, ItemTranslation)You can define other options there, such as 'db_table' for example. When a translation is registred a new model is dynamically created for you, this would be the translation model definition for this example: class ItemTranslation(models.Model): _language = models.CharField(db_index=True) _model = models.ForeignKey(Item, related_name='translations') title = models.CharField(max_length=50) description = models.CharField(max_length=150)An important detail here is that this model just store the data translations, in the original model we are storing the values for the "default language" (sites default or defined for a model in ModelTranslation option). So if you have a model that already has data on it that data (no matter what language is it in) it will still be used. It's also a performance feature since you will save a join if you are requesting data in the default language. [Less]