 time. So my name is Potash Limab and I work with Olapuram and my course will be about how to do some more case studies. I will discuss only one big case study and a small example from the past year. So probably you all know what Olapuram is. Olapuram is an open source company. Olapuram is a subsidiary of Olapuram who do consultancy around the number of these main developers of Olapuram online. But from all point of view, the most important thing that we are dedicated to enterprise is the product called Olapuram Office and we provide the university support for Olapuram Office. So let's define the terms of what we mean by university support. For my point of view, level 1 support is some basic support for troubleshooting. For example, the inter-count range and to the left has to speak on the table or something like that. So very basic level 2 support towards the poor inter-level. Some configuration, some registry hacking or I don't know. The problem can be solved. So these tasks are usually outsourced to our partners or to our customers who can give us the interest in the native language and usually we don't date those support requests. Of course there are exceptions. But the most important thing that we are doing is the level 3 support and the resolution of the issue requires change in the source code level. And it also requires if you change the source code of course we have to create a building. We cannot wait for six months to appear in the upstream development. So we create a building before this program tamper fits me and they provide the user in the case that I need. So usually the university support should I cycle that depending on the service level agreement that we have with the customer. We confirm the problem and the very at the problem usually happens during the day, business day, I would say. And then we start to fix the issue by today which may take a few days or sometimes it depends on the complexity of the problem and then we provide an ATF payment. So we of course push at least our team to get it immediately to master branch development usually and it will appear in the next level of the strength plan. But if you take time solving it will take up to six months. On the other hand, all of our offices which we are using on a monthly basis up to four months for users, all of this can get fixed that doesn't need for a particular customer. So the case today is about the south-eastern health and social care trust which internally called Vastar Hospital because it's shorter. So the whole picture there's Vastar Hospital. It's an organization in Northern Ireland in the UK and they started a big migration project two years ago and they started to migrate to or product which was called all of our office at the time but now it's called all of our office. So they had a license agreement with Microsoft or Microsoft software this week but somehow Microsoft office was not part of this contract and then they licensed it, they had to renew it at a quite high price which was 145 pounds per year per user. So the primary goal was the cost saving and that's why they accepted our proposal or solution. So we not only provided them licenses for all of our office but also furthering support package which included the matrixes and still price was much, much lower than it would be with the Microsoft office which of course had been without leveraging code support. So S.Torbara is a precutable company in the United Kingdom and we have had the most under of certified developers in the community and we have experience in the diversity support and so on. It reused the release of the migration. So first of all we presented them the standard migration protocol, so the strategy that the document foundation recommends which means that we asked them to install Polaborab office on all the workstations, do not segment the users as like users, normal managers can run with Polaborab office but we suggested to use Polaborab office already with Microsoft office from the first day and of course we also recommended to use the open document format. Unfortunately, the state is advised and they are able to create proprietary migration formats and OSL because they said that it would have been impossible for them to exchange documents with other trusts and organizations who would use ODF. So this of course, as you can expect, caused some problems in the migration but here we are near some of their problems. About three years later we brought a case study about this migration process which is a very requested Polaborab website where we described the technical problems that we ran during this migration process and basically it was a size story. It was after two years of the pilot, this sound system has essentially just created a long report about the project and basically what they wrote that migration is possible at least is the person of the staff can migrate to Polaborab office and the existing issues are minor and can be solved. During the pilot they reported around 130 missions and out of them 108 have been resolved. So I would like to show you a few examples of their problems that we have solved during the course of this project. Starting with the easier, simpler ones and the online kind of show you some, which I felt for outside the technical areas of the single one thing, but rather for the future development. So the first one is the some check boxes, you know you can enter check boxes several days into the document and it was a problem to import and export them but there was a problem with the option to import some of the oversight back in the day about these things. And it's funny how users use the check boxes in different times. So if I saw the form there was at least three types of check boxes, they use small controls, small text controls or even they use a special character which doesn't exist in the form and then we get an empty object. So I had a bugger port which just made me and the way that these developers changed this to and another thing instead of the empty box, so Jack was there. Then we had some problems with the ActiveX form code to us, so we could import them but they were alive in the sense that we imported the EMF metaply in German instead of the picture control. It was an export program, it was not similarly handled in the US and write the documents, but in the end it was not the world of those problems. So now we can export the default text to us. Another example when the user just couldn't resize the table, that actually goes to the margin. It was a clearly defect that could be missed easily. Another interesting example and in the audio team document which was not from Microsoft Office but from the surface of there which is some depredated OSNL signals which was the OZI guy from Microsoft Office, of course, but we had to implement this in the office to show the before and after specials show that we were finally able to import this variation from ourselves. Tables, so when we got an email when the subject is a table issue, we are very sad because I think these problems happen very frequently. The most annoying problem is that the writer, we don't have the concept of a floating table. By word it's quite common. A floating table means that the table floats around the page and the text can run on it, but unfortunately when you click on a table in word and move the mouse or you write on Excel, the table becomes a floating table. So if we are using some heuristic now on the whole, whether it's a real floating table or it's a normal table, which should be very important. So the problem is that floating tables are usually imported in right sections, but those sections cannot span to multiple pages. So we have to use heuristics before we import floating tables to cover up. We have a problem with the built-in time sheets, which is quite important, and ways to get paid at the end of the course, so that the time sheets saved by the OZI were not consumed by the visual basic macro, because the format was incorrect. So we have to use the BFF oscillator from Microsoft, which identified quite a few products in our library that export code. We solved all of these. Another interesting family problem is that third-party companies produce more than no extra data, which is not a bad answer, basically. However, third can point in this, and the users don't care about the senders, they just care about the end result. So we have to implement Microsoft's third behavior and accept invoiced OXML files. So this one is a floating table program before and after the specials pretty much show the result of this workpiece, so you see in the end that we have a table that's made. The managing we have to implement is a little bit of a confusion on their side, so it's a user experience problem. They didn't understand what was going on and asked us to change these message codes that comes out when you want to merge the cells in time. This is clearly the effect found in those of the fashion. Another interesting thing that some users like, they use the documents instead of them. So they put documents into the documents, and those documents appear on the iPhone, so they just prove him files of the word document and embed documents into the documents. In the video here, it's not clear, but I think it offers many, many combinations. You can have, for example, a file in a doc, and you can embed XLS, XLSX, OX in this document. You can have the same with OX, and the video here is smaller in these cases. So we unified this video here, somewhat similarly, but I'm sort of confused what it's doing. These problems, the second problem is in mics, XLS, so it's still not fully released, but they did a lot of work about the invocators, both the documents and the standard compines point of view. So one of the big advantages to have support from a company is that it is possible to find out or suggest the ways where the project will develop. So it's often asked, question, there is the roadmap, but it's on the roadmap about the plan. Actually we implement features, but it's a slack. And if somebody wants to influence on the roadmap, then we do consultancy work, and we are happy to develop features. So for example, the previous dimension, the time sheet, at all get another feature that the empty lines had to be deleted. On the other hand, they were protected, but there was a protection that was not being overwritten in the office. The problem was that XLS is a more kind of protection model, which we imported and exported correctly, but we didn't have the options on the user interface. So this example shows where we added those options. So again, the time sheet filled in in the office, they also wanted to disable some components of the office. For example, they didn't want the base UI, they didn't want the PDF import. And I think in the beginning, they didn't want to mount the intro, but in the final version, they had installed it. And this feature is just about what people create. It means Microsoft install the console files, which are the inside. So when they install the product, they have these options grayed out, and the user interface starts to use applications. Another big topic in development task was the integration with SharePoint. So unfortunately, replacing Microsoft software doesn't only mean replacing office, but more brands that cannot replace, but they need to implement it. So one of these examples was SharePoint, and exporting SharePoint list to God was solved within the course of this application model project. The other favorite feature request was the watermarks. They marked watermarks somehow, and it looked like an easy feature, and we had a recursive feature already. But in the end, it became a nightmare for us, because it turned out that the correct internal availability with Microsoft Office in terms of watermarks and it came to really a lot of time. But by now, I think that the feature is all big, and it's been working perfectly for all five, four months. And it's really compatible with Microsoft Office. So in this hospital, there are users who use the auto text having probably conditions, just typing some radiation, and it was a trend to do this medical text. I don't know exactly, however, we had this sort of problem before, the auto text from the OS format. It was already the binary format before it was present in the office. Other big area, we developed a lot of things, such as the Merge. So Merge, Merge really needs a database, a range of assets and stuff is there, and it's plenty of options, storing data, but in fact, it was possible to use tables, simple tables to use as a data source, but this feature wasn't presently right. Somehow, the users applied this feature and created a new internet for them. The other problem with Merge is that, as I mentioned, they don't use the running format, they use the ranks of running formats, and there are quite a few problems in these formats in terms of Merge. So for example, the management of things, Merge is working as such to run the running formats. It was something else before, it was something extremely of a lice, that was granted to us from the database. It was a featuring word, and they expected the same behavior. But we had a converse, we eventually got to the interface level and the compatibility level that we had to do. Incidentally, these parts were reported to Orban's in-law many years ago, but obviously, nobody fixed them because they weren't easy to use. It was important to have the big customer who actually sponsored. This microfeature, highlight-close customization, is also asked by the hospital because they said that if these highlight-close, they want to customize it, then all right, the customers can have problems in making the distinction between those colors. So this was in the running, it was not a very big work, but it's a nice feature, as I mentioned. And these formats found it interesting to mention that these might as well document how often people take models with the right interests, and they often ask how would the VBA... You have just a couple of minutes. All right. And how would the VBA be in support of the office as it is here? It's pretty good with the VBA somewhat, but who can guarantee that you can run and be a model of the models from Microsoft of these files. So it would be a huge task to implement everything, and it's not easy to do so. What I thought was that you get a macro from a customer that has to be run, and they implement every single piece that comes from each of us. They implement the format number for the function or the option button from the community with the existing button from us. He even met with the world-raising models, which is 20 years old, and I hate technology, but I need that to understand this world-raising models. I'd like to mention, for me, as well, Thor, which is the association yesterday, this is why I just showed you this useful translating from visual-based applications to phone number of these, which this way the phone number of these can be used as a drop-in replacement for Microsoft of these in some cases. It's very useful because sometimes visual-based applications are crucial for mobilization of the source-loving types of systems, and it's not possible to replace it. They are higher-up because I don't have much time left before they also release the proxy detection on Windows, which is an important form of getting the crash reports, and I just assume that the mother seems to have done what I don't have time to talk about them, but the slides will be uploaded. So, with a final word, thank you, Payesh, of course, because all one hand, everything we do is very important, we take back to the world of making and the users who use the office for free, but we should mention that what we do is funded by our customers, and I would like to thank them to the fund for work and which helps making this better for everyone, especially the staff, the staff here, the social staff, and the NG, and the other customers that won't ever see, who won't support, so that was my presentation, very much. I think I used more time than I had, so if you have any questions, you can find me later in the world. That's those questions, so thank you very much again.