Filtering - New feature request

[GoogleCodeExporter]

It would be great to have the possibility to filter translations by their
location.
For example: 
- have html templates separately from views and models
- all translations within one file (some html template)

Now we have to search each text string to translate one page consisting of
dozen strings. It would be ideal to have all them on page for translation.

Original issue reported on code.google.com by pakhomov...@yandex.ru on 21 Oct 2009 at 3:07

[GoogleCodeExporter]

Alex, Rosetta will look in the location path of each string (i.e. the content 
of the Occurrences column), so 
searching for e.g. 'views.py' will return all strings defined in a view.

Does this cover your feature request?

Original comment by mbonetti on 21 Oct 2009 at 3:14

[GoogleCodeExporter]

Not exactly.
I don't know how to realize it but here is my case.

I have a dynamic page. It includes a dozen of text strings. All they are 
scattered
randomly through rosetta. So we need to find each one by one.
Usually it's the case with html template.

So the administrator should know which template to search. Usually he doesn't. 
The
only thing he knows is the url of the page he wants to edit and translate.

Ideally I imagine the process like this:
- we copy the url of the page we want to translate
- we paste it in rosetta and press the button "search all texts for this page"
- some reverse hidden function tries to resolve the url and define the template 
that
was used for this page to render.
- as result we have all texts that belong to this page on one page to translate 
them
at the same time

Original comment by pakhomov...@yandex.ru on 21 Oct 2009 at 4:01