--
Ticket URL: <http://transifex.org/ticket/348>
Transifex <http://transifex.org/>
Integrated translation platform
* cc: tch@… (removed)
* cc: tch, raven (added)
--
Ticket URL: <http://transifex.org/ticket/348#comment:1>
* milestone: => When the time has come
Comment:
This falls under a "translation memory" type of functionality. This is
definitely in our roadmap, but definitely not for a couple of months.
Updating milestone accordingly.
--
Ticket URL: <http://transifex.org/ticket/348#comment:2>
Comment(by Raven):
Search would be superb, but I don't think global "search and replace" is a
good idea, especially in highly contextual languages, like Polish.
--
Ticket URL: <http://transifex.org/ticket/348#comment:3>
Comment(by tch):
Only in one of the cases I presented is the context really that much
relevant. Also, implementing global "search and replace" doesn't mean that
anybody would start using it recklessly and screw things up.
It might be a good idea, to display the list of strings to be replaced
with a hint of the context (say 1 or 2 preceding and following lines).
--
Ticket URL: <http://transifex.org/ticket/348#comment:4>
* ready_for_review: => 0
Comment:
Doing search&replace would be very valuable, but it might need a few
restrictions:
* only replace for a given language
* only replace within a project
I'm not sure there is a real use case for doing search & replace across
multiple projects.
--
Ticket URL: <http://transifex.org/ticket/348#comment:5>
* status: new => closed
* resolution: => wontfix
Comment:
Hi,
Lotte has already received work on improved searching (see
http://blog.transifex.com/2012/03/tips-on-how-to-filter-entries-in-
lotte/).
The "search & replace functionality will not be implemented for the
foreseeable future, since it is something quite dangerous thing to do.
By the way, trac is also shutting down. You can use
https://github.com/transifex/transifex/issues/ for any new issues or to
report back on this one.
Thanks,
Apostolis
--
Ticket URL: <http://transifex.org/ticket/348#comment:6>