I lose with this method the possibility to reopen all the previous SVG files in the revision of my 20 Git repo with my shiny Inkscape 0.92.
Estimated 40GB of file transfert necessary. ).Ĭommit all of them all again and push them to remote over 20 Github repo (after full proofreading in local), render them to JPG hi-res, JPG low-res, singlepage, very long, even if I can script something for it. And with over 40 languages, 20 episodes, I can’t check if a line is missing or if a line is broken in language I can’t read ( eg. I need to check anyway if the files are broken or not after the batch, a visual proofreading is necessary. But this type of solution cannot work: the problem is a bit more complex than "launch a single mass conversion, high five myself and party time with unicorns" : Downgrading my local install to 0.91, blacklisting 0.92 SVG files on the renderfarm and advising all 40 translators to not update to 0.92 is a short-term fix and not a pleasant one.Īs David Revoy is a well known artist and promoter of Open Source Applications for Artists. This version will hit all the GNU/Linux distros, Windows and Mac users will download this new version from the official website and problems with SVG files will hit Pepper&Carrot. So, first, let accept it: 0.92 is a released version. I hate when I have to admit that using open-source is actually a production handicap in this type of scenario. I don't want to loose all the previous revisions of SVG file on Pepper&Carrot too! And what if I do it then Inkscape tells me I have to do it again for the future Inkscape 0.93? This type of development decision, relying on 'userland must fix it themselves' must stop. I can't spend the end of month to convert over 10000 files manually one by one and push them to Git.
0 kommentar(er)
