 Hello everyone, my name is Gaval Kerman, I work for the Hungarian Miss Corporation, and I would like to talk about our results next year, so since last conference, and the title of my talk is basically just an emphasis of approach to this program of introducing the office into the Hungarian Public Center. So, Ajeda, I will take a little look back to my last year's talk, but the problems I faced in the last year are still there, but these are just better now. So, these are the problems this year, and that's for the next year also. So, to summarize, our company still, and the Ministry of Interior, still supports improving the OX and I support the office, because it's believed to be a big deficit for moving today from Microsoft Office software. So, last year, I presented our results for assessing the user needs, which has happened in 2017, so we asked them what features do they use, and these are the program areas that we have known back then to be probably used, and probably cause serious interoperability issues. So, this is the result set of the assessment model, and this helped us by realizing the work that we have started in 2018. So, as you can see, changebacking needs quite on margin, and also jobs are very, very popular feature that everyone uses. But everyone but quite a huge portion of our users, and these are the results for the assessment features. Most users, of course, need to chat, and all that stuff, especially the protection features are also program. And, of course, basic functionality, that was just a generative task, because we thought it's another set of features that are not very likely that people don't use them. So, basically, these are the other program areas that a lot of people use, more than 70% have ticked each of these boxes on the assessment, and for 1,500 repris, this is quite a bit of a user piece. So, last year, we have done a lot of systematic testing, which was finished this year, and in these areas, this chart shows the segmentation of problems that we have found. So, these are only the program areas that have more than 10 robots on our list, and we can see that most of the problems is the blue one, which means interoperability here. So, what that means, that our functionality is in some areas quite a bit buggy, and especially this is something that we think would be useful, but that's really a minority in most of the cases. So, if we can tackle the interoperability issues, we will be quite in a good position. So, of course, our assessment of bugs is not necessarily complete, because existing bugs might mask other problems. For example, karg is unable to write activists for properties at all. So, once that is, once that one bug is fixed, we may discover that there are a lot of activists, properties that are not being handled properly, but we don't see them yet. So, we kind of expect that there is a lot more hiding under these, but probably not that many. Last year, I talked about us improving user experience of the office, and these are areas that have much improved since then, and by user experience, I meant the experience that users have when they open the documents they wrote on last day before searching to develop this, or that they get from other people who have not yet finished. So, most basic of these things is part of the formatting. There are still minor problems with borders, but not even much apart from that, that we know of. So, at least paragraph one goes to and roundtips pretty well. Then charts have huge input. There is some, still some has been interoperability issues, and I think what I should learn about my audience will talk about that in one and a half hour in this room. So, please stay after that. I think today we can say that most of the problems that are in the three basic job types are really big problems that are not simply interoperability issues, but problems that have functionality or that have functionality type of issues. Another topic is change that king. Last one event has worked on that part of this year, and now we can correctly do a lot of text based change that king. So, like simple edition king or cut and paste, cut, paragraph formatting styles, bytes and numbering, and these are partly written, accepted, rejected, even when you see the text format and when you see the document, these go to also probably. So, better visualize our progress, better to go in chart. I colonized the OX and I chart created bugs that were fixed by an esteem. So, about here is the cross-out part, and the AIO ones are the ones that were fixed by Varsh, not counting duplicates and one-two spots. And similar noise, but those are actual fixes. Another variable is the token exchange that king. AIO highlight marks the ones that were fixed by Laszkov. And there is some pretty good progress. And what is still left is the change that king of the non-texted objects, which is not really supported by God, but not like that in the first place. So, you need to add support for that first in the text editor engine. But we have more. So, AIO number of 13 who has started to work on fixing the durability of high values, because that's kind of how simple Laszkov is being developed. And so, that's how those catalogs look. Mostly those are overfixed, and yellow marks are also the ones that were fixed by all team. So, the person who did this could not come, but didn't do this kind of development and change really all some of these problems. So, there are some more, these are some smaller areas, like what has she done that day. You might have seen it in the first slides, that a lot of people do and that existing OSMR charts in Word documents. I'm not sure why this is the best thing, but they do. And, for example, like in 6.1, it looked very good. It was all the way misdesized after our sale. But finally, it's not a huge feature but now, at least, it works in library thanks to Laszkov's name. So, the user has gone from completely unrivaled to pretty much the unrivaled. So, high learnings, and they have... Namely, one could think that it's a pretty common thing, and there are no real problems with that. Like, how can one make mistakes when writing, I think, in total. There were some, and now it's quite a bit of an improved area. There are some issues that need to be tackled like Excel has cell-level hyperlinks where cork has tax-level hyperlinks. So, cork can have multiple different hyperlinks on multiple parts of the text, and this cannot be very representative in Excel aspects. But apart from that, it's not really serious. Azov njenvarj has been improved a little bit because in 6.3, I think, write and all can be destroyed, njenvarj širec that have been put into a write-down document, or even a word went, so we can round in those problems. A little bit of thanks to other people who are also working on interoperability issues. This is just to highlight people who have worked on the same topic, because without help from others, other people would not be successful, and we are hoping that without help others kind of success will do. So, many thanks for Mikosvar for BTR, thanks for your work, and for Smartup. I would like to thank you for your time, sorry. Just in those 4.x very basic practice. Paragraph, header, filter, table, and what not work, and the regular handshuff don't get worshiped with the work, there is still a lot to do on that area, but at least someone has started amazing work, and more and more microphones for your table works. Thank you. Cerskrot for table of content work, table of contents have been a disaster area for not having one in 6.3 acting, and Tamar Zolavi has the amazing feature called unfold table. People have worked quite a bit using folding tables without even understanding or knowing about it, but at least we can now save them from our little bit of MLSMF, so that someone sends them in document with such a person. And also, form control side, I use a lot of places, and usually it's only one person who makes that form, but then 100 or 1000 must use that form to get that task done. So that's amazing. So, thanks for the future, Tamar Zolavi has plans to expand the team, and with more human resources it will be possible to not only continue working on these areas that are already in progress, but to start working on other important areas to, like, fixing one, but numbering tables in better condition, or, I think, in the in-car page settings in multiple software, header, router, in writer, and maybe more, I'm not sure yet, what will be finished after this year, but there is a lot of work still to be done. So, now for the opportunity, but we can do everything all alone. And other companies or tropical industrial organizations are here by invited to join us, and they contribute in these areas. These are currently not a scope for us, as of now, but it would be nice to program the other floating tables, more objects for change that in, like table, contents, more table, but images. It would be nice to have probably working object positioning, like images, charts, and tables, as well. And also Miara, which is an experience, when you consider Miara, which is at least quite a bit difficult to understand actual end users or identification, what would be done there. Also for Kark, it would be nice to have tables, ties, more table, writer, fixes, and how to create an environment. I don't know how many of you have heard that Excel can feel that things by the color of the cells, but apparently, it's a pretty popular feature in all user cases, maybe other user cases, but that feature too. It would be nice to have a little bit of more type of component charts. Maybe we can fix that, I'm not sure, but, yeah, another problem area is the main style of user experience. Namely, because there is a lot of already existing feature requests about that, and I think even with the recent we were in last years some of old, it would be really nice to consolidate that poplist even more. So if we would implement everything, that would be our mess, so that would be quite difficult to have. So more, more programs, so that should change that in this somewhat user, in our user base and share it to our book anything, just building on top of it and people can just edit commonly as far as that is on our file share or share point of something like that. Of course, door and machine and smart art is still need out of a lot, and the PBDX interoperability in general is still lacking and it's not really in scope for us as of yeah, really in macros but I think I should not say anything more about that. Ok, so that was for for a big picture of the activities of the news. Thank you for your attention and questions please if there is any.