You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now Pootle allows to configure the wordcount function to use. There are two available functions: Pootle one and TTK one. Ideally both functions should be:
Merged together and
Placed in TTK (or in a separate package from Pootle and TTK)
Also Pootle should allow to set the wordcount function to use per project (like we do now for quality checks) instead of using a global setting.
The text was updated successfully, but these errors were encountered:
This is to allow maximum configurability in a scenario where a single Pootle server has several projects for several customers (where each customer only sees its projects) and each customer wants to use their wordcount settings. So instead of using the notion of customer idea we think it is easier to set it by project.
Of course it's up to you if you want to share one Pootle instance between customers, but I bet if this this what you end up with, you will need to do many tweaks here and there to support multiple customers, and this might not be the optimal route. Virtual servers are very cheap now, so I'd suggest just using private instances of Pootle for each customer and not spending time on complicating the core codebase. Just my $0.02.
Right now Pootle allows to configure the wordcount function to use. There are two available functions: Pootle one and TTK one. Ideally both functions should be:
Also Pootle should allow to set the wordcount function to use per project (like we do now for quality checks) instead of using a global setting.
The text was updated successfully, but these errors were encountered: