Mantis Issue Tracking for Scribus
· Hosting provided by Anduin.net / Øverby Consulting ·

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0009848ScribusStylespublic11-Mar-17 11:3014-Jul-03 21:41
Reportercezaryece 
Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusnewResolutionopen 
PlatformallOSOS Version
Product Version1.4.0svn 
Target Version1.5.1Fixed in Version 
Summary0009848: [PATCH] add controll for Hyphenation Mode property of Pragraph Style
DescriptionSomeone add HyphenationMode property for paragraph`s style, but it was not used in any place.
In my patch I have add:
- control for this property in Style Manager
- hyphenator`s work depends on paragraph HyphenationMode property
- applying Paragraph Style with other hyphenation mode than AutomaticHyphenation call dehyphenation routine
TagsNo tags attached.
Attached Filespatch file icon HyphenationModeinParStyle.patch [^] (15,471 bytes) 11-Mar-17 11:30 [Show Content]
? file icon typographiccolour.ui [^] (14,039 bytes) 11-Oct-27 15:26
? file icon hyphenationstyle.ui [^] (8,210 bytes) 11-Nov-17 19:51
? file icon typographiccolourV2.ui [^] (13,974 bytes) 11-Nov-21 03:24
patch file icon hyph_control.patch [^] (43,111 bytes) 12-Jan-09 15:37 [Show Content]
patch file icon hyph_control2.patch [^] (48,803 bytes) 12-Jan-10 10:27 [Show Content]

- Relationships
child of 0001279feedbacklouisdesjardins Adequation of settings in Paragraph styles/Properties palette/Text editor 

-  Notes
(0025827)
cezaryece (developer)
11-Mar-17 11:48

I dont know how to gently solve problem of changing this property for existing styles and text using it. Now there is no control or check if any text is using that style and need be hyphenated or dehyphenated.

It may be done in few ways
- action in menu for rehyphenating all text in doc
- action called on applying style`s changes
- any automatic action - only user manual hyphenation/dehyphenation (like now)

What is better?
(0025833)
cezaryece (developer)
11-Mar-17 15:56

Longer I am thinking about it, I am starting to prefer menu entry for script/routine for re-hyphenation, and like in Short Words dialogue box, there should be setting for doing it for frame, page or whole document.
(0025866)
cbradney (administrator)
11-Mar-21 08:03

In its current form, this patch is too intrusive and would quite likely damage existing documents. Hyphenation via styles should only be available for new docs if the user activates the feature.
(0026012)
cezaryece (developer)
11-Apr-06 10:26

IMHO user should be informed that styles has no information about hyphenation mode and that there is possibility to set it to enable/disable hyphenation for desire styles.
But while opening these old docs as default value of hyphenation mode in style should be set hyphenation setting for document.

What you think?
(0027117)
louisdesjardins (developer)
11-Oct-27 15:24

I am not able to see the patch and to see Scribus work with it but in any event I have worked on a UI file that could be of help maybe.

The idea is quite simple: users can create as many “Typographic colour” sets as they wish to accomplish the desired typographic colour. Scribus would ship with a few predefined sets. The idea is to save those sets that could be seen as substyles, usable in a paragraph style.

Since one image is worth a thousand word, I provide here the .ui file. Get back to me if further details are needed.
(0027138)
avox (administrator)
11-Oct-31 21:41

Hi Louis!

Two questions:
- what's group tracking? Not character spacing, is it?
- "No hyphen on last word of pages" - shouldn't that be "of frames" ? If you have several text frames on a page you need extra rules to determine the "last word".

Comments:
- when we have mixin-styles that could be just part of a paragraph style
- what about widows/orphans settings?
- we'll probably have a "maximum word spacing" setting in the future, too
- do we need a separate hyphenation language that is different from the spell-checking language?
- We should use "word spacing" instead of "word tracking"
(0027139)
cezaryece (developer)
11-Oct-31 22:44
edited on: 11-Oct-31 22:48

"do we need a separate hyphenation language that is different from the spell-checking language?"
No if we can set language for whole style, which will affect hyphenation and spell-checker (what about short-words and quotes chars?).
For me language should be applicable locally on demand for selected text from PP. BTW all char and paragraph styles settings should be applicable locally for selected text without creating new style.

But all that discus is only near report topic... What about commit this patch just as is? For old documents (there is no direct settings about hyphenation) default value from document hyphenation setting should be set.

(0027140)
cbradney (administrator)
11-Oct-31 22:53

Cezary, its obvious from the mailing list that there are people using 1.5.0 for normal work. There must be a way to tell Scribus to keep current hyphenation and not use Paragraph style based hyphenation.

Also, have you considered the opening of 1.3.x/1.4.x created documents and the effect that this patch would have on them. Remember, people like John Culleton create in 1.4.0svn and export with 1.5.0 for the PDF export options.
(0027141)
louisdesjardins (developer)
11-Nov-01 00:05

I just saw my answers disappear with an error from the server… I will not re-write tonight but will later on. Andreas, please stay tuned!
(0027142)
cezaryece (developer)
11-Nov-01 00:56

@cbradney: do you expect some problems with 1.5.0 with porting that patch to it? I can prepare two patches if it helps.
As I wrote before - if while opening there is not direct set of hyphenation property for style then should be used default setting for document for each style. Simply and efficiency.
In fact I have some fixes in my local Scribus used for production where I am testing my patches, so I must provide new patch (specially fix how to get not hyphenated paragraphs - not by avoid hyphenation in hyphenator but enabling or disabling hyphenation while formatting lines - seems it works much better and is easier while changing hyphenation setting for style).
But there must be agreement for that feature at start.
(0027215)
louisdesjardins (developer)
11-Nov-16 21:54

Hi Andreas!

Here is a bit more info about the Typographic Colour feature.

I had already wrote that in a discussion earlier this summer and I realize you were not in the loop. So I repost this email here where it will be much more helpful to pursue the discussion! I am not forgetting to get back with answers to your specific questions. For now here is the email that was sent along with the .ui file that is now available here on the bugtracker.

Hello everyone,

Some further thoughts I would like to share in the form of a new dialog I created using Qt-design for Scribus.

"Typographic Colour" is constantly coming to the surface from time to time so I thought of getting into this further. Some links below.

It's a long time shot since I believe we should have some way to simplify the work and get more consistent results with type. So here is what I suggest.

First, we need a new menu in Edit > Typographic Colour

This will bring up the dialog attached here.

Filling this dialog and hitting ok will add a new "Typographic Color Set" in the top window of the dialog.

By default, Scribus will ship with 4 basic settings that can of course be edited at will by the users: No hyphenation | Tight Justification | Medium Justification | Loose Justification. Or users can add to this short list they own Set. For the sake of the explanation, let's say we have those 4 basic settings. They constitute 4 options that will then appear in the Property Palette as Typographic Color. Users can select one of them from a new pull-down menu that will either be added to the PP or — my preference so far — be replacing the actual tabs for Optical Margins and for Advanced Settings (except the 3 fields that are more Type Effects than anything else in my view but this is highly debatable! and that we can move elsewhere in the PP [we will have more room with my suggestion]).

Last minute thought! We could even propose 6 settings with the application since the settings for word tracking and glyph extension works so well we could then have the following 6 basic settings which, when chosen by the users, would ensure top quality typography.

Without Hyphenation
Tight Justification No Hyphen | Medium Justification No Hyphen | Loose Justification No Hyphen

With Hyphenation
Tight Justification With Hyphen | Medium Justification With Hyphen | Loose Justification With Hyphen

Basically, we want to help the user by putting in his/her hand a powerful tool that will help achieve outstanding Typographic Color for body text with a single command in the PP while leaving all the room to create more Sets, as the work demands it.

Once the user is happy with the result, all the type settings, including this Typographic Color can be synthetised into a single Paragraph Style Sheet. The Typographic Color pull down menu will also appear in the Create Paragraph Style dialog in replacement of all the separate settings that is currently crowding this dialog.

Now, we may not want this in a new submenu of the Edit menu. I also gave this some thoughts. Since we're using the Prefs to deal with such lists (I am thinking of the list of custom document sizes), the other place where this could fit would obviously be in the Prefs. The behaviour would be the same. The list created there would appear in both the PP and in the Paragraph Style Dialog. We could apply it as any other settings — like a color or a pattern or make it part of a Paragraph Style Sheet. Easy.

So, this dialog I am proposing now is a first draft. It can be turned into a Prefs window that would include the 3 main settings that affect the Typographic Color: Optical Margins, Tracking and Glyph Extension... and Hyphenation.

You will note that I have removed 2 options for Optical Margins as I assume it has no effect when there are no hanging punctuation or hyphens on one side. So, unless I miss something, I see no reason to have the Right Only, Left Only and Both Sides distinction. It doesn't matter! The settings in my view is either ON or OFF and applies to both sides since only one side will be affected anyway, depending on the language being a Left-Right or a Right-Left language. Let me know if what I assume is wrong.

You will also note that I have added a couple more settings for Hyphenation. These are missing since the beginning. I have also removed the dinosaurs which are the 2 options Suggestions of Hyphenation and Hyphenate when Typing. They make simply no sense and we warn users not to use those settings so we better take them away.

Let me know what you think!

Louis


http://en.wikipedia.org/wiki/Typography#Color [^]
http://fr.wikipedia.org/wiki/Gris_typographique [^]
http://de.wikipedia.org/wiki/Grauwert [^]
(0027220)
Mike (reporter)
11-Nov-17 11:32

This topic is related to 0008805.

Implementation of this feature would resolve 0008243.

I have some remarks to this solution:

1) There is no need for six default settings of Typographics Colour. One style is sufficient. Other styles can be created by user when would be needed.

2) New dialog in Edit > Typographic Colour is nearly perfect and implementation the stylying into PP and Styles as well. What is really nonsense is removing optical margins. Margins and the rest of the features in Advanced Settings should be kept the same way as now.

So remove "Use optical margins" from UI proposition and keep Optical Margins and the rest of the Advanced Settings. PP should be redesigned because it contains a lot of blank space.

3) After the implementation, Extras > Hyphenate Text, Dehyphenate Text could be removed.
(0027223)
louisdesjardins (developer)
11-Nov-17 16:50

Hi Mike,

1. The reason for 6 defaults settings is to make people at ease and make them *use* the feature. If someone finds this is too much or too little, the only thing needed then is to edit that list. A job might require that there is no hyphens at all and there is still the need to have uniformity in typographic colour. The other variable of importance once you have isolated the font, font size and linespacing is the width of composition. Hence those 3 settings for each of Hyphenated or Not hyphenated text.

2) I think that Optical Margins are part of the settings that help accomplish professional typographic colour. Again, this is something people might just not use because they don’t know what it's for. Also, why I took away the right or left options is only because my understanding of the feature makes me believe that if there is nothing to hang on one of the sides, selecting rigth or left will make no difference and can in fact lead to errors. Hence the choice of simplifying and letting only On or Off by the mean of a single checkbox. I would keep it there in the new dialog however I have no strong opinion on keeping it in the PP as a distinct settings but one has to consider that if we're going to use this settings, it’s more than probable that it’s going to be *along with* the variables that affect the quality of typography? Why would someone use Optical Margins without dealing with the other variables at the same time?

3) Right.
(0027225)
Mike (reporter)
11-Nov-17 19:50

Hi louisdesjardins.

I was thinking about implementation of this missing feature once again. Is really necessary to create Typographics Colour dialog? Other solution:

- repair Word Traking, Min. and Norm. in Style manager (not related to this feature)
- add "Hyphenation" + list with styles to the character style dialog bellow Language
- create Edit > Hyphenation Styles or implement GUI directly into Style manager (better) - Hyphenation Style would be bellow the Character Style item.
- other options would remain unchanged
(0027232)
louisdesjardins (developer)
11-Nov-18 19:18

Hi Mike,

The purpose of that dialog is to make more accessible and more usable a whole set of features more easily than having to reset them for every paragraph style needed. Create a style and grab the typographic colour that fits the needs according to easy-to-understand naming. Plus, this approach makes it easy to be consistent from document to document. As I see that, in the paragraph style dialog you would only be shown the list from which to pick the desired typographic colour. So, one pulldown menu instead of the whole thing, still you can easily access the settings for fine-tuning, through that new dialog. It's pretty convenient in my view.
(0027244)
Mike (reporter)
11-Nov-20 20:34
edited on: 11-Nov-20 20:52

Two questions at the beginning: Will this patch somehow resolve the situation when image is at the bottom of page and text flows around the image, but frame doesn't end? ...something like "No Hyphen on Last Word of Column". And second question: What is Group Tracking?

There are some bugs in your UI:
- Delete button is missing.
- No Hyphen on Last Word of Pages > Frame

For me, the proposed solution is less accessible than creating only Hyphenation Styles. Optical Margins, Language, Word Tracking, Glyph Extension I would prefer to have separately - directly in Paragraph/Character Styles.

Example one: For bilingual document you must doubled the number of Typographic Colour and Styles too. When you would have only Hyphenation Styles, there would be the same number of Hyphenation Styles as for document written only in one language => language should be property of Character Style.

Example two: You have a simple book. Headlines: no hyphenation + some settings of glyph extension and word tracking, opt. margins; Normal text: hyphenation + settings2; Footnotes: hyphenation + settings3; Image caption: no hyphenation + settings4. So you have 4 Typographic Clour Styles. If you use Hyphenation Styles, only 2 are necessary - hyphenation, no hyphenation. Other properties is possible to inherit via Styles.

I think, more users should say how they are working with Scribus.

(0027246)
louisdesjardins (developer)
11-Nov-21 03:23
edited on: 11-Nov-22 04:37

Sorry for the confusion about Group Tracking. I took the field that already exists in the "Advanced Settings" subtab of the Text tab in the PP. The new mockup doesn’t have the icon itself which should replace the plain text I put in the mockup but it is the exact same thing. It's arguable whether we need that in that new dialog or not but for the moment, I prefer to leave it there. It can be removed in a breeze without affecting the dialog.

In answer to Andreas' questions:
1. That was the now late Group Tracking. Thanks for being patient! :-)
2. I have fixed the Last Word of Frames. Nice call! Thanks!

In answer to Mike's comments:
I completely understand that you would prefer to have those settings in a distinct dialog and your example of a bilingual (or more) document is nice but in my view, considering just how much languages are different, make or not extensive use of capital letters or longer or shorter words, not mentioning the diacritics signs and the typographic spaces, that for each language there would have to be nonetheless a need for a new Typographic Colour set.

Those settings are somewhat bound together.

For headlines is see no real interest for Typographic Colour. Remember it is meant for body text. It can be of course used for everything else but will prove its efficiency when Typographic Color is at stake.

(0027247)
louisdesjardins (developer)
11-Nov-21 03:32
edited on: 11-Nov-21 03:37

Looking at your proposal for Hyphenation Style I think that we must keep in mind the final result. Typographic Colour is the real challenge here. Not hyphenation. Hyphenation is one variable in the whole process and isolating it in a specific dialog will, in my view, not help more to accomplish what needs to be done. People might just forget that it exists just like they do now. Or they will not use the Advanced Settings. All this is of no real help, is it?

What we need here is a holistic approach!

(0027250)
louisdesjardins (developer)
11-Nov-21 15:02

Hi Andreas,
You wrote a few comments a couple weeks ago and I reproduce them only to facilitate the follow up!

Comments:
Andreas - when we have mixin-styles that could be just part of a paragraph style
Louis - Right, this is what I envision too.

Andreas - what about widows/orphans settings?
Louis - Still possible but not part of this dialog

Andreas - we'll probably have a "maximum word spacing" setting in the future, too
Louis - This would be wonderful. Maybe I should add it to the dialog? This is clearly part of the Typographic Colour. More below.

Andreas - do we need a separate hyphenation language that is different from the spell-checking language?
Louis - I think these go together and if not it would be exceptional, no?

Andreas - We should use "word spacing" instead of "word tracking"
Louis - In my understanding, "word tracking" refers to letterspacing within each word and the envisioned "word spacing" refers to the space between words. You might just want that: keep a distance between words (this will of course have more effect on non-justified text) while tightening the tracking. The one example that comes readily to mind is when you set type for kids learning to read. Schoolboards ask for an increased spacing between words. Being able to set that space would be more than nice.
(0027445)
cbradney (administrator)
12-Jan-03 21:29

Where are we up to now with this request? Is there consensus on the issues and does the current version of the patch cover them? Has it been properly tested and does it apply and work on 1.4.1svn ?
(0027449)
cezaryece (developer)
12-Jan-04 10:43

No, that patch is outdated. Working on text layout routine I have found nicer way for controlling hyphenation from paragraph styles setting during text formatting routine. Now I am working hard on foot/endnotes feature for 1.5, but I try to take a break and prepare new patch for hyphenation control.

I don`t know about consensus. I would like to provide simply way for controlling hyphenation for paragraphs for headers (most common case). Luis idea is maybe good, but it is enhancement for all typography settings and control - should be requested separatelly, not instead my proposal.
(0027450)
Mike (reporter)
12-Jan-04 14:50

I agree with cezaryece. This request should solve only the patch. Additional features should be requested in separated bug.

I think there is no consensus. Solution as Louis proposed is not so effective for me so I proposed other solution of the missing feature.
(0027452)
cbradney (administrator)
12-Jan-04 19:33

Ok, understood..

However, we need to be clear on the direction for 1.4.0 - stable, well tested fixes will be accepted. Features will be considered only if thoroughly tested and not wide reaching. I'd suggest a patch for a fix for 1.4.1.svn and a patch for a feature set for 1.5.0.svn. Please also note we need to get 1.5.0.svn stabilised, so patches there need to be tested and proven, and 90-100% complete (assuming a reality exists where the remaining % can be completed quickly).
(0027467)
louisdesjardins (developer)
12-Jan-05 22:19

Acting on hyphenation only, within a style, might seem interesting but it is not the way to go in my view. It's like considering the motor without the transmission, or vice versa.

Only so it's clear, I am really not talking for myself alone here and not trying as well to solve a case of a unique individual but in fact learning from over 25 years of experience with dtp, text formatting, magazines and books making, all text intensive work, including multilingual documents. Hyphenations are one part of the equation here.
(0027471)
StefanM (reporter)
12-Jan-06 09:34

Hi Louis, please consider a separate feature request for typo. color. Thanks
(0027475)
louisdesjardins (developer)
12-Jan-06 20:26

Hi Stefan,

I don't understand how a separate feature request would help this discussion.

I think I'm clearly on target.

I am not reinventing the wheel. Aside from a very few options that are still not available in both the Advanced Settings for Text (in the PP) and the Hyphenation dialog, I suggest we make them work together in a logical way.

Adobe InDesign and QuarkXPress are working just the same as I suggest. The only real novelty here is the way to name the option which I think is better named by the final result than by naming each mechanism by its name. So I go for Typographic Colour that translates very well into other languages as it is a typographic reality designers are facing in their everyday work.
(0027477)
cbradney (administrator)
12-Jan-06 22:28

Typographic colour, however probably means absolutely nothing to a beginner.. but I don't mind if some docs are written about it if it is added.

Still.. this bug relates to certain hyphenation issues, and not about additional ideas necessarily. Hijacking bugs causes them to never get fixed or for a fix to take too longer.

a) Do we want this fixed as described via the bug description? (If no->close the bug)
b) Is this patch complete and does this patch do what it is intended?
c) Does it break anything else ? (which implies the answer to b is no)

As long as we have a) yes b) yes and c) no , then lets get this patch into SVN and close this bug.

If you want to add another RFE for further enhancements to attain this Typographic Colour stuff, then please go ahead.
(0027495)
louisdesjardins (developer)
12-Jan-09 03:01

1. I will write the doc if someone is to take the challenge of gathering those settings together and make them a new set of substyles named "Typographic Colour". I ask for NO novelties, just a gathering of the already available settings. BTW I think that I will not have a big effort to write much because all the typographic color stuff is well covered in Wikipedia! :-)

2. I fully agree that "Hijacking bugs causes them to never get fixed or for a fix to take too longer." For this very reason, I think that bug 0009848 should be closed.

Answers are as follow:
a) no
b) because of a) = no, it's irrelevant
c) because of a) = no, it's irrelevant


We should instead put energy on bug 0000417
http://bugs.scribus.net/view.php?id=417 [^]
which is a need and once solved will make more appealing the new RFE for Typographic Colour (for which I will create a separate bug as asked).
(0027496)
louisdesjardins (developer)
12-Jan-09 03:18

New bug
http://bugs.scribus.net/view.php?id=10502 [^]
created
(0027499)
cezaryece (developer)
12-Jan-09 15:45

Too fast again... please delete my last patch I have upload. Must add some code to properly opening files where HyphenationMode property was not set in styles.
(0027502)
cezaryece (developer)
12-Jan-10 10:26

OK, new patch bring compatibility with previous created files and set Hyphenation Mode for paragraph styles to doc default. Fortunately someone else done saving of Hyphenation Mode for paragraphs style in SLA file.
I have change initial value for HyphenationMode property to -1 (HyphModeNotSet). If such value is found while checking paragraphs by ScribusDoc::redefineStyles then it is set to manual or automatic accordingly to doc prefs.
Checking of HyphenationMode property for current paragraph style is added to hypenation controll conditions in PageItem_TextFrame::layout().

TODO:
- read hyphenation setting for styles created while importing from ODT/DOC
- add local control for hyphenation for selected paragraphs to PP
(0027504)
louisdesjardins (developer)
12-Jan-10 14:35

About "- add local control for hyphenation for selected paragraphs to PP " do you mean adding to PP what is in Extra at present time or adding to PP the hyphenation settings that are in the Prefs at present time?
(0027505)
cezaryece (developer)
12-Jan-10 15:25
edited on: 12-Jan-10 15:30

I mean in PP should be possibility to set "local" hyphenation mode for selected paragraphs which will override setting from style`s definition, so user can quickly enable/disable hyphenation not changing paragraph style (like other changes for paragraph properties done in PP - PP does it local, not changing style definition).
Personally I want to see all paragraph`s properties changeable "localy" by PP - we still have missing Drop Caps control and paragraphs margins (gaps before and after and left/right margins) control in PP. But I am waiting for new PP to see what will done there.

(0027509)
louisdesjardins (developer)
12-Jan-10 22:47

http://bugs.scribus.net/view.php?id=1279 [^]
(0028136)
cbradney (administrator)
12-Jun-14 23:20

Cezary.. where are you up to with the TODOs here? Can you please provide a diff to current trunk for the existing work.. (and only the existing change for this work, no other patches)
(0029702)
cezaryece (developer)
13-Jan-14 11:13

Patch for current trunk is in 0011370.

- Issue History
Date Modified Username Field Change
11-Mar-17 11:30 cezaryece New Issue
11-Mar-17 11:30 cezaryece File Added: HyphenationModeinParStyle.patch
11-Mar-17 11:48 cezaryece Note Added: 0025827
11-Mar-17 15:56 cezaryece Note Added: 0025833
11-Mar-21 08:03 cbradney Note Added: 0025866
11-Apr-06 10:26 cezaryece Note Added: 0026012
11-Apr-16 11:25 cbradney Target Version => 1.4.1
11-Oct-27 15:24 louisdesjardins Note Added: 0027117
11-Oct-27 15:26 louisdesjardins File Added: typographiccolour.ui
11-Oct-31 21:41 avox Note Added: 0027138
11-Oct-31 22:44 cezaryece Note Added: 0027139
11-Oct-31 22:48 cezaryece Note Edited: 0027139 View Revisions
11-Oct-31 22:53 cbradney Note Added: 0027140
11-Nov-01 00:05 louisdesjardins Note Added: 0027141
11-Nov-01 00:56 cezaryece Note Added: 0027142
11-Nov-16 21:54 louisdesjardins Note Added: 0027215
11-Nov-17 11:32 Mike Note Added: 0027220
11-Nov-17 16:50 louisdesjardins Note Added: 0027223
11-Nov-17 19:50 Mike Note Added: 0027225
11-Nov-17 19:51 Mike File Added: hyphenationstyle.ui
11-Nov-18 19:18 louisdesjardins Note Added: 0027232
11-Nov-20 20:34 Mike Note Added: 0027244
11-Nov-20 20:51 Mike Note Edited: 0027244 View Revisions
11-Nov-20 20:52 Mike Note Edited: 0027244 View Revisions
11-Nov-21 03:23 louisdesjardins Note Added: 0027246
11-Nov-21 03:24 louisdesjardins File Added: typographiccolourV2.ui
11-Nov-21 03:32 louisdesjardins Note Added: 0027247
11-Nov-21 03:33 louisdesjardins Note Edited: 0027246 View Revisions
11-Nov-21 03:37 louisdesjardins Note Edited: 0027247 View Revisions
11-Nov-21 15:02 louisdesjardins Note Added: 0027250
11-Nov-22 04:37 louisdesjardins Note Edited: 0027246 View Revisions
12-Jan-03 21:29 cbradney Note Added: 0027445
12-Jan-04 10:43 cezaryece Note Added: 0027449
12-Jan-04 14:50 Mike Note Added: 0027450
12-Jan-04 19:33 cbradney Note Added: 0027452
12-Jan-05 22:19 louisdesjardins Note Added: 0027467
12-Jan-06 09:34 StefanM Note Added: 0027471
12-Jan-06 20:26 louisdesjardins Note Added: 0027475
12-Jan-06 22:28 cbradney Note Added: 0027477
12-Jan-09 03:01 louisdesjardins Note Added: 0027495
12-Jan-09 03:18 louisdesjardins Note Added: 0027496
12-Jan-09 15:37 cezaryece File Added: hyph_control.patch
12-Jan-09 15:45 cezaryece Note Added: 0027499
12-Jan-10 10:26 cezaryece Note Added: 0027502
12-Jan-10 10:27 cezaryece File Added: hyph_control2.patch
12-Jan-10 14:35 louisdesjardins Note Added: 0027504
12-Jan-10 15:25 cezaryece Note Added: 0027505
12-Jan-10 15:30 cezaryece Note Edited: 0027505 View Revisions
12-Jan-10 22:47 louisdesjardins Note Added: 0027509
12-Jan-10 22:48 louisdesjardins Relationship added child of 0001279
12-Apr-29 23:12 cbradney Target Version 1.4.1 => 1.4.2
12-Jun-14 23:20 cbradney Note Added: 0028136
12-Oct-03 15:18 ale Summary [NEW FEATURE] add controll for Hyphenation Mode property of Pragraph Style => [PATCH] add controll for Hyphenation Mode property of Pragraph Style
13-Jan-13 22:32 cbradney Target Version 1.4.2 => 1.4.3
13-Jan-14 11:13 cezaryece Note Added: 0029702
13-Jul-04 22:24 cbradney Target Version 1.4.3 => 1.5.0
14-Jul-03 21:41 Kunda Target Version 1.5.0 => 1.5.1



Copyright © 2000 - 2014 MantisBT Team
Powered by Mantis Bugtracker