Both Drupal and Views have real performance limitations they try to overcome by caching (saving) the results of an operation for reuse. This can make testing painful by showing you the results of a previous test, not the current test. There are a few things to switch off when developing new views or changing something that is input to a view.
Look in Views advanced settings,
admin/structure/views/settings/advanced, and switch off the cache. I have never had a problem with the cache when developing by myself. Some people report problems when several developers are working on related or similar views. If you change your view but the results do not change, try switching off every cache in views and in Drupal.
Translation of text should not cause a problem because most people develop code and build content in the same language. Some problems occur when editors encode special characters in one characterset then the translation code tries to use a different characterset. switch off translation to see what happens.
If switching off translation does solve the problem, you need to look at your editors and sources of data to ensure everything is in the same characterset.