Re: Multilingual site best practices
Hello,
I have read something today about multi lingual database. There is a
project hosted there:
http://code.google.com/p/django-utils/wiki/TranslationService
that seems to do what you are looking for.
I have never used it myself.
I hope that will help you
On Aug 10, 9:52 pm, Francis <[EMAIL PROTECTED]> wrote:
> 1. You should use a quick description and then write the full text in
> the po file.
>
> 2. You are better of using english in the {%trans%} bloc because
> gettext don't support UTF-8 or character outside the limited ascii.
>
> no clue for 3.
>
> Francis
>
> On Aug 10, 11:42 am, Vincent Foley <[EMAIL PROTECTED]> wrote:
>
> > Hello,
>
> > I work for a company who develops web sites and web applications for
> > clients in Quebec. People in Quebec mainly speak french, but there
> > are english speaking people too. Most sites we make eventually want
> > to have a french and english version with french being the "main"
> > version.
>
> > I would like to know if anyone could share best practices for
> > multilingual sites. I also have some questions:
>
> > 1. In the {% trans %} and {% blocktrans %} tags, should I include the
> > full text, or just a quick description and enter the full text in
> > the .po files?
>
> > 2. As I said, french is the main language in Quebec, so if I write a
> > site in french and am later asked to translate it, will the accented
> > characters cause a problem if they're used in the msgid of the .po
> > files?
>
> > 3. It seems the server always has to be restarted after the .po files
> > have been compiled. Is that so? If I don't have root access to the
> > server to restart Apache, is there a way I can have the new
> > definitions appear on the site?
>
> > Thanks for the input,
>
> > Vincent.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: Multilingual site best practices
1. You should use a quick description and then write the full text in
the po file.
2. You are better of using english in the {%trans%} bloc because
gettext don't support UTF-8 or character outside the limited ascii.
no clue for 3.
Francis
On Aug 10, 11:42 am, Vincent Foley <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I work for a company who develops web sites and web applications for
> clients in Quebec. People in Quebec mainly speak french, but there
> are english speaking people too. Most sites we make eventually want
> to have a french and english version with french being the "main"
> version.
>
> I would like to know if anyone could share best practices for
> multilingual sites. I also have some questions:
>
> 1. In the {% trans %} and {% blocktrans %} tags, should I include the
> full text, or just a quick description and enter the full text in
> the .po files?
>
> 2. As I said, french is the main language in Quebec, so if I write a
> site in french and am later asked to translate it, will the accented
> characters cause a problem if they're used in the msgid of the .po
> files?
>
> 3. It seems the server always has to be restarted after the .po files
> have been compiled. Is that so? If I don't have root access to the
> server to restart Apache, is there a way I can have the new
> definitions appear on the site?
>
> Thanks for the input,
>
> Vincent.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: Multilingual site best practices
There's django-multilingual for that.
On Aug 10, 1:05 pm, Grupo Django <[EMAIL PROTECTED]> wrote:
> Vincent Foley ha escrito:
>
>
>
> > Hello,
>
> > I work for a company who develops web sites and web applications for
> > clients in Quebec. People in Quebec mainly speak french, but there
> > are english speaking people too. Most sites we make eventually want
> > to have a french and english version with french being the "main"
> > version.
>
> > I would like to know if anyone could share best practices for
> > multilingual sites. I also have some questions:
>
> > 1. In the {% trans %} and {% blocktrans %} tags, should I include the
> > full text, or just a quick description and enter the full text in
> > the .po files?
>
> > 2. As I said, french is the main language in Quebec, so if I write a
> > site in french and am later asked to translate it, will the accented
> > characters cause a problem if they're used in the msgid of the .po
> > files?
>
> > 3. It seems the server always has to be restarted after the .po files
> > have been compiled. Is that so? If I don't have root access to the
> > server to restart Apache, is there a way I can have the new
> > definitions appear on the site?
>
> > Thanks for the input,
>
> > Vincent.
>
> I'd like to extend this questions.
> 4. Best practice to use a multilingual database. i.e. News in English
> and French from an app. I need it for a project. I'll write some docs
> about it when I get it to work, if I get it ;-) IMHO, multilingual in
> the interface but monolingual in database, is not very useful.
> Thanks,
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Re: Multilingual site best practices
Vincent Foley ha escrito:
> Hello,
>
> I work for a company who develops web sites and web applications for
> clients in Quebec. People in Quebec mainly speak french, but there
> are english speaking people too. Most sites we make eventually want
> to have a french and english version with french being the "main"
> version.
>
> I would like to know if anyone could share best practices for
> multilingual sites. I also have some questions:
>
> 1. In the {% trans %} and {% blocktrans %} tags, should I include the
> full text, or just a quick description and enter the full text in
> the .po files?
>
> 2. As I said, french is the main language in Quebec, so if I write a
> site in french and am later asked to translate it, will the accented
> characters cause a problem if they're used in the msgid of the .po
> files?
>
> 3. It seems the server always has to be restarted after the .po files
> have been compiled. Is that so? If I don't have root access to the
> server to restart Apache, is there a way I can have the new
> definitions appear on the site?
>
> Thanks for the input,
>
> Vincent.
I'd like to extend this questions.
4. Best practice to use a multilingual database. i.e. News in English
and French from an app. I need it for a project. I'll write some docs
about it when I get it to work, if I get it ;-) IMHO, multilingual in
the interface but monolingual in database, is not very useful.
Thanks,
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
Multilingual site best practices
Hello,
I work for a company who develops web sites and web applications for
clients in Quebec. People in Quebec mainly speak french, but there
are english speaking people too. Most sites we make eventually want
to have a french and english version with french being the "main"
version.
I would like to know if anyone could share best practices for
multilingual sites. I also have some questions:
1. In the {% trans %} and {% blocktrans %} tags, should I include the
full text, or just a quick description and enter the full text in
the .po files?
2. As I said, french is the main language in Quebec, so if I write a
site in french and am later asked to translate it, will the accented
characters cause a problem if they're used in the msgid of the .po
files?
3. It seems the server always has to be restarted after the .po files
have been compiled. Is that so? If I don't have root access to the
server to restart Apache, is there a way I can have the new
definitions appear on the site?
Thanks for the input,
Vincent.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---
