[texworks] We've reached r700+; please test

Paul A Norman paul.a.norman at gmail.com
Sat Dec 4 08:09:10 CET 2010


Looking good, just to clarify please, a few quick questions.

In   http://www.google.com/codesearch/p?hl=en#TCAOwTxChU8/trunk/src/TWScriptAPI.cpp&q=writeFile%20package:http://texworks%5C.googlecode%5C.com

line 257

int TWScriptAPI::writeFile(const QString& filename, const QString&
content) const

1. Ok, so const QString& filename is a fully qualified path?

Through Qt internals, does the path default to anything if no path is given?

Stefan, you mentioned that const QString& content is going to write as UTF-8

  umBytes = fout.write(content.toUtf8());

2. If  QString& content is only ascii will that as expected only
render as Ascii in that utf-8 doesn't kick in unil after ascii 127(?)
- is that right? Ascii to 128 will still be saved as a single octet?
Qt doesn't do anything unexpected here?

3. And the int returned on success/failure, is there some hint as to
cause of failure available?

Looks at moment like just   SystemAccess_Failed    or
SystemAccess_OK  -  is that right?

For text files returnFileContents() will be really really helpful :)


On 3 December 2010 12:47, Paul A Norman <paul.a.norman at gmail.com> wrote:
>> @script authors: Any testing experience with the new writeFile and/or
>> disabling plugins, yet?
> Not by me, for one, yet Stefan, hoping to have a day on it soon, in
> the middle of moving hosting servers so no time for other things yet.
> Paul
> On 3 December 2010 09:07, Stefan Löffler <st.loeffler at gmail.com> wrote:
>> Hi,
>> we've reached the magic 700th revision - yippie ;).
>> At the same time, this is another call for testing. I know, you'll
>> probably say you know that already, but in reality this should give you
>> a brief overview over what has changed (and should therefore be looked
>> out for).
>>  * (un)indent, (un)comment. There have been several issues regarding
>> which lines get indented in a (multiline) selection. These should
>> hopefully be resolved, but this doesn't mean I didn't break anything
>> related I didn't notice.
>> (http://code.google.com/p/texworks/issues/detail?id=442)
>>  * previewer tool code has changed. Everything should work more
>> smoothly, now. Ctrl+Click = synctex, Shift/Alt+Click = zoom, normal
>> click = follow link or use magnifier. The mouse cursor should be updated
>> appropriately as well. Tell me if something feels weird (also in cases
>> where you change your mind in the middle, use several modifiers at once,
>> ...) (http://code.google.com/p/texworks/issues/detail?id=440)
>>  * the latex error parsing script has been updated. It should give a
>> nicely formated output now, and the links should work now for multi-part
>> documents as well. It won't help to use a new build for this, you need
>> to replace the script yourself. It's available from
>> http://code.google.com/p/texworks/source/browse/trunk/res/resfiles/scripts/Hooks/latexErrors.js
>> - please put it in your <resources>/scripts/Hooks folder and type away
>> (preferably errors ;)).
>> @script authors: Any testing experience with the new writeFile and/or
>> disabling plugins, yet?
>> Thanks,
>> Stefan

More information about the texworks mailing list