Unfortunately I do not know enough to be even slightly dangerous so I will use the “2PC route”.This is a quick guide to help people troubleshoot their XML during the creation processįirst install Notepad++, it is a free editor with syntax highlighting, which by default recognize many programming languages. My suspicion is there is a setting somewhere in the program which can be used to switch the text format from line to paragraph. So I will do my editing on that PC and then copy the file into the required program via a USB stick. XML files stored on a USB stick on another Win10 PC I have copied the file to the desktop and dragged it into the Notepad++ window - it opens in the usual neat format. I think I have found a way round the problem. I have done nothing to the file, simply copied it from inside the program and dragged it to the NotePad++ window. I am afraid I cannot go back to Win 7 since all my PC’s now run Win 10. I tried using Word Wrap but that breaks the line to the size of the window, it does break it into nice neat paragraphs. In win 7 the file has the usual neat and easily readable XML format but now in Win10 as I said before the text is one long line. I have downloaded a program which contains. The only completely safe way to add white space where it does not matter would be to use a processor that actually knows the XML’s schema to do the Thank you for your reply.
… is entirely legitimate XML, and differs from this bit: How and where is the XML generated? Is it possible that logic has changed? I recall some processors having options on the save of the XML to determine how compact the output should be.Ī quick and dirty way to line break an XML file is to replace all instances of >\r\nIn the word decided, the middle syllable is stressed. My suspicion is that the file just does not have the white space in it to formatting it as you would like. If you take you xml, bunched up on Windows 10, to a Windows 7 machine, does it display more to your liking? I would be surprised if that’s true. I’m sorry this response will provide no quick answer.įirstly, though, I wonder why the migration from Windows 7 to Windows 10 has produced this change? That sounds odd to me.
0 kommentar(er)
