Bindestrich

[info-1587]

Hallo

Ich habe folgendes Problem.

Immer wenn ich in einem Textrahmen einen Bindestrich eingeben will,  
wird ausgezoomt und den Bindestrich kriege ich nicht in den Text.

Kennt jemand das Problem?

Vielen Dank im Voraus.

mabu


_______________________________________________
scribus mailing list
scribus@...
http://lists.scribus.info/mailman/listinfo/scribus

[a.l.e]

hallo mabu

> Immer wenn ich in einem Textrahmen einen Bindestrich eingeben will,  
> wird ausgezoomt und den Bindestrich kriege ich nicht in den Text.

ach, verbunde mit mod-tasten (alt, ctrl, strg) wirkt den bindestrich tatsächlich als kürzel für's zoomen... aber allein... ???

welche:

- scribus version?
- welches systemm (distribution? os x? win?)?

ciao
a.l.e

_______________________________________________
scribus mailing list
scribus@...
http://lists.scribus.info/mailman/listinfo/scribus

[Ralf-Diether Ebel]

Hallo mabu,
der Fehler ist im bugtracker bekannt. Du kannt nur unter
Datei-Allgemeine Einstellungen - Tastenkürzel das Kürzel für den
bedingten Bindestrich neu definieren, und zwar habe ich (CTRL) Shift "_"
genommen. Hängt mit unser deutschen Tastatur zusammen, da es
standardmässig mit Ctrl-Shift "-" belegt ist, und das ergibt bei
deutschem Layout Ctrl-"_".

a.l.e schrieb:

> hallo mabu
>
>> Immer wenn ich in einem Textrahmen einen Bindestrich eingeben will,  
>> wird ausgezoomt und den Bindestrich kriege ich nicht in den Text.
>
> ach, verbunde mit mod-tasten (alt, ctrl, strg) wirkt den bindestrich tatsächlich als kürzel für's zoomen... aber allein... ???
>
> welche:
>
> - scribus version?
> - welches systemm (distribution? os x? win?)?
>
> ciao
> a.l.e
>
> _______________________________________________
> scribus mailing list
> scribus@...
> http://lists.scribus.info/mailman/listinfo/scribus
>

_______________________________________________
scribus mailing list
scribus@...
http://lists.scribus.info/mailman/listinfo/scribus

[Calum Polwart-6]

I work on a small newsletter project.  While I understand how workflow
should be getting others to play nicely is difficult so there seems to
be a relatively large amount if editing done (spelling, typos, grammar
occasionally rewording to fit something into space)after I've added to
the scribus layout.

I'm increasingly thinking it would be better to share the document in an
editable format with the editor.  But as we are 350miles apart to work
in real-time this would need to be - either:

- A 'Shared Drive' on a Virtual Private Network
- A SubVersioning System

Share Drive has several disadvantages.  Only one person can edit the
file at once being one of the main ones.  If I leave the file open and
go out for 8 hours (as I tend to!) its locked for the whole time.  It'd
need a VPN and while I could set that up rest assured the Editor would
have issues!  File names may be problematic - I work on linux - he works
on Windows.  VPN may be quite slow.  By the time the document is
finished it usually creates a 60Mb PDF - so that'd be bandwidth hungry
and I suspect slow.

SVN on the other-hand MAY allow dual user edits - after all the file is
an XML file - so basically plain text?  There are windows GUI front ends
 for SVN - all he'd basically need to do would be click "update/commit".
 SVN would use a local file so should be quicker to work with in terms
of edits and bandwidth would only by the sla file and any other
added/edited files not every file every time.  My biggest concern (apart
from the XML not actually being "mergable" would be file names?)

Looking for anyone who actually does this or something to achieve the
same result to chip in and tell me what they think?


Calum

_______________________________________________
scribus mailing list
scribus@...
http://lists.scribus.info/mailman/listinfo/scribus

[Calum Polwart-2]

I work on a small newsletter project.  While I understand how workflow
should be getting others to play nicely is difficult so there seems to
be a relatively large amount if editing done (spelling, typos, grammar
occasionally rewording to fit something into space)after I've added to
the scribus layout.

I'm increasingly thinking it would be better to share the document in an
editable format with the editor.  But as we are 350miles apart to work
in real-time this would need to be - either:

- A 'Shared Drive' on a Virtual Private Network
- A SubVersioning System

Share Drive has several disadvantages.  Only one person can edit the
file at once being one of the main ones.  If I leave the file open and
go out for 8 hours (as I tend to!) its locked for the whole time.  It'd
need a VPN and while I could set that up rest assured the Editor would
have issues!  File names may be problematic - I work on linux - he works
on Windows.  VPN may be quite slow.  By the time the document is
finished it usually creates a 60Mb PDF - so that'd be bandwidth hungry
and I suspect slow.

SVN on the other-hand MAY allow dual user edits - after all the file is
an XML file - so basically plain text?  There are windows GUI front ends
 for SVN - all he'd basically need to do would be click "update/commit".
 SVN would use a local file so should be quicker to work with in terms
of edits and bandwidth would only by the sla file and any other
added/edited files not every file every time.  My biggest concern (apart
from the XML not actually being "mergable" would be file names?)

Looking for anyone who actually does this or something to achieve the
same result to chip in and tell me what they think?


Calum


_______________________________________________
scribus mailing list
scribus@...
http://lists.scribus.info/mailman/listinfo/scribus

[Gregory Pittman]

Calum Polwart wrote:

> I work on a small newsletter project.  While I understand how workflow
> should be getting others to play nicely is difficult so there seems to
> be a relatively large amount if editing done (spelling, typos, grammar
> occasionally rewording to fit something into space)after I've added to
> the scribus layout.
>
> I'm increasingly thinking it would be better to share the document in an
> editable format with the editor.  But as we are 350miles apart to work
> in real-time this would need to be - either:
>
> - A 'Shared Drive' on a Virtual Private Network
> - A SubVersioning System
>
> Share Drive has several disadvantages.  Only one person can edit the
> file at once being one of the main ones.  If I leave the file open and
> go out for 8 hours (as I tend to!) its locked for the whole time.  It'd
> need a VPN and while I could set that up rest assured the Editor would
> have issues!  File names may be problematic - I work on linux - he works
> on Windows.  VPN may be quite slow.  By the time the document is
> finished it usually creates a 60Mb PDF - so that'd be bandwidth hungry
> and I suspect slow.
>
> SVN on the other-hand MAY allow dual user edits - after all the file is
> an XML file - so basically plain text?  There are windows GUI front ends
>  for SVN - all he'd basically need to do would be click "update/commit".
>  SVN would use a local file so should be quicker to work with in terms
> of edits and bandwidth would only by the sla file and any other
> added/edited files not every file every time.  My biggest concern (apart
> from the XML not actually being "mergable" would be file names?)
>
> Looking for anyone who actually does this or something to achieve the
> same result to chip in and tell me what they think?
>  

I wonder if svn might be overkill for this. One thing to consider is
which part(s) you want to allow someone else to edit. If they are mainly
editing text, keep the text separate for that purpose.
If I were in charge of layout, I don't think I'd want others fiddling
with my layout -- make suggestions for edits, sure, but let one person
be responsible for the layout.

Greg

_______________________________________________
scribus mailing list
scribus@...
http://lists.scribus.info/mailman/listinfo/scribus

[Calum Polwart-6]

Gregory Pittman wrote:
> Calum Polwart wrote:

>> SVN on the other-hand MAY allow dual user edits - after all the file is
>> an XML file - so basically plain text?  There are windows GUI front ends
>>  for SVN - all he'd basically need to do would be click "update/commit".
>>  SVN would use a local file so should be quicker to work with in terms
>> of edits and bandwidth would only by the sla file and any other
>> added/edited files not every file every time.  My biggest concern (apart
>> from the XML not actually being "mergable" would be file names?)
>>
>> Looking for anyone who actually does this or something to achieve the
>> same result to chip in and tell me what they think?
>>  
> I wonder if svn might be overkill for this.

That was certainly my original feeling...

 One thing to consider is
> which part(s) you want to allow someone else to edit.

It would mostly be text yes.

 If they are mainly
> editing text, keep the text separate for that purpose.

Maybe I'm missing something fundamental in how I use scribus (quite
possible).  I get word documents (much as I'd like to change the world -
I have to realistic - contributions come from a small community of
people some of whom will be using library machines etc and have no power
to use OOo and ALL of whom would think I've lost the plot if I asked
them to use OOo instead.)  I then tend to just do a straight cut n paste
from OOo into Scribus.  perhaps I should  save as a writer file and
import but since I'd still have to apply the styles in OOo I don't see
the advantage.  I haven't ever figured out a way to allow a "linked"
text file - like you have with a picture.  If I have a picture and I
open it in gimp, & edit it then the changes come into scribus.  I
haven't found a way to do something like that with text... ...am I
missing something obvious?

There is text that I add that isn't provided in *.doc format - mostly
headings, captions on photos etc...  I'd expect them to be editable
too... but they don't have a separate file?

When (proper) tables come I'd like the ability for them to be edited too
- again there doesn't seem likely to be an "linked file" method unless
I'm completely being stupid!


> If I were in charge of layout, I don't think I'd want others fiddling
> with my layout -- make suggestions for edits, sure, but let one person
> be responsible for the layout.

I agree to some extent... but I doubt he'd intentionally change much
layout.  There may be the accidental change issue.  One advantage of SVN
would be the option to roll back - although it'd likely be a bulk load
of changes so that might not be quite so simple, and the XML is not
quite as pretty code to edit as a PHP file.  Of course RIGHT CLICK: LOCK
is a powerful tool and based on the competence of the average windows
user should be sufficient to prevent accidental damage!


>
> Greg
>
> _______________________________________________
> scribus mailing list
> scribus@...
> http://lists.scribus.info/mailman/listinfo/scribus


_______________________________________________
scribus mailing list
scribus@...
http://lists.scribus.info/mailman/listinfo/scribus

[Calum Polwart-2]

Gregory Pittman wrote:
> Calum Polwart wrote:

>> SVN on the other-hand MAY allow dual user edits - after all the file is
>> an XML file - so basically plain text?  There are windows GUI front ends
>>  for SVN - all he'd basically need to do would be click "update/commit".
>>  SVN would use a local file so should be quicker to work with in terms
>> of edits and bandwidth would only by the sla file and any other
>> added/edited files not every file every time.  My biggest concern (apart
>> from the XML not actually being "mergable" would be file names?)
>>
>> Looking for anyone who actually does this or something to achieve the
>> same result to chip in and tell me what they think?
>>  
> I wonder if svn might be overkill for this.

That was certainly my original feeling...

 One thing to consider is
> which part(s) you want to allow someone else to edit.

It would mostly be text yes.

 If they are mainly
> editing text, keep the text separate for that purpose.

Maybe I'm missing something fundamental in how I use scribus (quite
possible).  I get word documents (much as I'd like to change the world -
I have to realistic - contributions come from a small community of
people some of whom will be using library machines etc and have no power
to use OOo and ALL of whom would think I've lost the plot if I asked
them to use OOo instead.)  I then tend to just do a straight cut n paste
from OOo into Scribus.  perhaps I should  save as a writer file and
import but since I'd still have to apply the styles in OOo I don't see
the advantage.  I haven't ever figured out a way to allow a "linked"
text file - like you have with a picture.  If I have a picture and I
open it in gimp, & edit it then the changes come into scribus.  I
haven't found a way to do something like that with text... ...am I
missing something obvious?

There is text that I add that isn't provided in *.doc format - mostly
headings, captions on photos etc...  I'd expect them to be editable
too... but they don't have a separate file?

When (proper) tables come I'd like the ability for them to be edited too
- again there doesn't seem likely to be an "linked file" method unless
I'm completely being stupid!


> If I were in charge of layout, I don't think I'd want others fiddling
> with my layout -- make suggestions for edits, sure, but let one person
> be responsible for the layout.

I agree to some extent... but I doubt he'd intentionally change much
layout.  There may be the accidental change issue.  One advantage of SVN
would be the option to roll back - although it'd likely be a bulk load
of changes so that might not be quite so simple, and the XML is not
quite as pretty code to edit as a PHP file.  Of course RIGHT CLICK: LOCK
is a powerful tool and based on the competence of the average windows
user should be sufficient to prevent accidental damage!


>
> Greg
>
> _______________________________________________
> scribus mailing list
> scribus@...
> http://lists.scribus.info/mailman/listinfo/scribus



_______________________________________________
scribus mailing list
scribus@...
http://lists.scribus.info/mailman/listinfo/scribus

[a.l.e]

hi
> I haven't ever figured out a way to allow a "linked"
> text file - like you have with a picture.  If I have a picture and I
> open it in gimp, & edit it then the changes come into scribus.  I
> haven't found a way to do something like that with text... ...am I
> missing something obvious?
>  
imho, the biggest difference lay ins the fact that with scribus you
tipically don't edit the picture, you just include it in your layout:
so, the changes you do in the gimp won't affect the way scribus manages
the picture.

on the other side, you want to change and -- this is the biggest problem
-- format text in scribus *and* oo.writer. the second one won't
understand some of the formattings coming from scribus and the changes
done in the first will scramble fine settings done at the layout stage.

where i can agree with you is: it would be nice to have a tool which
fully retains scribus' formattings and just lets you change the text and
apply styles (a scribus plugin for oo.writer may be the best solution...
but i fear that it can't be implemented...).

though, if i understood it correctly, you can expect in the (not so
near) future some progress in the way scribus handles distributed editing!

ciao
a.l.e

_______________________________________________
scribus mailing list
scribus@...
http://lists.scribus.info/mailman/listinfo/scribus

[Calum Polwart-2]

a.l.e wrote:

> hi
>> I haven't ever figured out a way to allow a "linked"
>> text file - like you have with a picture.  If I have a picture and I
>> open it in gimp, & edit it then the changes come into scribus.  I
>> haven't found a way to do something like that with text... ...am I
>> missing something obvious?
>>  
> imho, the biggest difference lay ins the fact that with scribus you
> tipically don't edit the picture, you just include it in your layout:
> so, the changes you do in the gimp won't affect the way scribus manages
> the picture.
>
> on the other side, you want to change and -- this is the biggest problem
> -- format text in scribus *and* oo.writer. the second one won't
> understand some of the formattings coming from scribus and the changes
> done in the first will scramble fine settings done at the layout stage.
>

Oh yeh - I followed the issue - just wasn't sure if there was a way
round it - and I guess the response is "Not yet"

> where i can agree with you is: it would be nice to have a tool which
> fully retains scribus' formattings and just lets you change the text and
> apply styles (a scribus plugin for oo.writer may be the best solution...
> but i fear that it can't be implemented...).
>

While a OO.o plugin might be good - I think we'd still hit problems with
the hard and fast MS Word users.  If as someone else suggested you could
just install story editor alone and edit with that it wouldn't seem to
extreme a request to ask MS Word users to install a little programme and
 make tweaks to their files, which could then be imported back in.

> though, if i understood it correctly, you can expect in the (not so
> near) future some progress in the way scribus handles distributed editing!
>
> ciao
> a.l.e
>
> _______________________________________________
> scribus mailing list
> scribus@...
> http://lists.scribus.info/mailman/listinfo/scribus

_______________________________________________
scribus mailing list
scribus@...
http://lists.scribus.info/mailman/listinfo/scribus

[Calum Polwart-6]

Calum Polwart wrote:

> Gregory Pittman wrote:
>> Calum Polwart wrote:
>
>>> SVN on the other-hand MAY allow dual user edits - after all the file is
>>> an XML file - so basically plain text?  There are windows GUI front ends
>>>  for SVN - all he'd basically need to do would be click "update/commit".
>>>  SVN would use a local file so should be quicker to work with in terms
>>> of edits and bandwidth would only by the sla file and any other
>>> added/edited files not every file every time.  My biggest concern (apart
>>> from the XML not actually being "mergable" would be file names?)
>>>
>>> Looking for anyone who actually does this or something to achieve the
>>> same result to chip in and tell me what they think?
>>>  
>> I wonder if svn might be overkill for this.
>

Do I take it as the conversation moved to editing text files out side of
scribus - no-one

(a) Thinks using SVN is a good idea
(b) Has tried using SVN to comment if it screws up the files really badly!

Calum

_______________________________________________
scribus mailing list
scribus@...
http://lists.scribus.info/mailman/listinfo/scribus

[Gregory Pittman]

Calum Polwart wrote:

> Calum Polwart wrote:
>  
>> Gregory Pittman wrote:
>>    
>>> Calum Polwart wrote:
>>>      
>>>> SVN on the other-hand MAY allow dual user edits - after all the file is
>>>> an XML file - so basically plain text?  There are windows GUI front ends
>>>>  for SVN - all he'd basically need to do would be click "update/commit".
>>>>  SVN would use a local file so should be quicker to work with in terms
>>>> of edits and bandwidth would only by the sla file and any other
>>>> added/edited files not every file every time.  My biggest concern (apart
>>>> from the XML not actually being "mergable" would be file names?)
>>>>
>>>> Looking for anyone who actually does this or something to achieve the
>>>> same result to chip in and tell me what they think?
>>>>  
>>>>        
>>> I wonder if svn might be overkill for this.
>>>      
>
> Do I take it as the conversation moved to editing text files out side of
> scribus - no-one
>
> (a) Thinks using SVN is a good idea
> (b) Has tried using SVN to comment if it screws up the files really badly!
>  

One thing you have to think about is the way that Scribus handles text
(as compared with graphics). Text is internalized, graphics only ever
just have a pointer to an external file.
The current way to communicate with Scribus about what you might have
done to a file (text-wise) is via the .sla file. Therefore, what is
needed, and I think will eventually be feasible, is to be able to parse
the .sla file, extract the text and its markup, modify it, then reinsert
or re-create the .sla file so that Scribus can reload the file.
An advantage of this, like SVN, is that can be made to be nondestructive
of the original file, or at least preserve it as a backup.

I'm  of course not one of the devs, but it would seem that interacting
with Scribus internally is a very complex project, whereas interacting
via the .sla file is a more easily attainable goal.

Now a bit more to your point, Calum, there has been someone on the list
(IIRC) that was using some kind of networking in the context of Scribus,
but not SVN.

Greg

_______________________________________________
scribus mailing list
scribus@...
http://lists.scribus.info/mailman/listinfo/scribus