I think the following tests will be performed at least.
* file/uri operations(non-ASCII)
* create new file
* open(view)
* edit & save
* display the file name in a list view
* contentes rendering
* rendering the contents that contains non-ASCII characters.
Actually I have not unittested that yet. It was regression tested by "make check". and I tested it for the Japanese characters handling using web browser manually.
I propose to create(or add) Japanese version of existing tests. What do you think?
(maybe it is ugly for non japanese speakers if I add Japanese version to existing tests.)
And, I think it should be tested by Latin characters. I just tested it for Japanese characters.
Hello,
I'm sorry my delay.
Thank you for your review.
Ideally all operations should be tested.
I think the following tests will be performed at least. non-ASCII)
* file/uri operations(
* create new file
* open(view)
* edit & save
* display the file name in a list view
* contentes rendering
* rendering the contents that contains non-ASCII characters.
Actually I have not unittested that yet. It was regression tested by "make check". and I tested it for the Japanese characters handling using web browser manually.
I propose to create(or add) Japanese version of existing tests. What do you think?
(maybe it is ugly for non japanese speakers if I add Japanese version to existing tests.)
And, I think it should be tested by Latin characters. I just tested it for Japanese characters.
Hideaki