On Ma, 2008-07-14 at 09:09 +0200, Julen wrote: > Hi everyone, > > Following with my SoC tasks, time for search enhancements has arrived. > Last Friday Friedel, Clytie and me discussed briefly some ideas on IRC > and I want to expand the discussion here so we can define the right > way to go.
Great to hear of all the progress! > There are already some RFEs on this topic[1] [2] [3], claiming these > improvements: > - searching for specific fields (source, target, notes, locations) > - case-sensitive searches > - regex. support > - listing all the search results in a single page > - choosing the hierarchical point to search in > - recent searches > - search and replace > > As you can see there are a bunch of things to improve, but for now we > should prioritize the most important things to do. > I think searching for specific fields is a good starting point, which > could lead to major improvements in the future. I think we need to realise that our rules for prioritisation is influenced by at least the usefulness _and_ the amount of work to implement an improvement. Doing specific fields should be fairly easy, and I guess that is part of why I support this as a starting point. > > We should take into account the limitations we have using pogrep > and/or indexing, eg, pogrep supports regex whereas indexing can't > perform this kind of searches. In case indexing is enabled on the > server and an operation can't be done with the indexing engine, we > should fall back to pogrep. > I've created a wiki page[4] for the purpose, so feel free to > add/remove/edit any information you see necessary. Lars, you're > probably the person who better knows this stuff so your help and > comments would be very welcome. > > Looking forward to your comments, Instead of just falling back to pogrep, we could use the results from the indexing and filter through the results to implement the same effect. In fact, we might be able to build a fake translation store with all the search results, and then use pofilter to search through that. It should still be faster than using pofilter directly on all the files - which can be very slow in large projects. I'll try to add some extra notes to the wiki page. Friedel ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
