![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
According to a friend of mine that has used InDesign for some personal
projects, InDesign can export and import XML. That could mean that you
only have to create a template and then insert the documentation by
automatic search and replace. (I use the same technique to build simple
websites.)
Apparently InDesign even has scripting facilities, she has not used them
herself. She is not a programmer, but a child of the WYSIWYG point and
click generation. All in all it sounds to me as something that matches
your interests and abilities. Perhaps she can even help you a bit. She
has met people that use complex programs to do simple tasks before (i.e.
we have worked together for some time).
--
Everytime the IT department forbids something that a researcher deems
necessary for her work there will be another hole in the firewall.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 18/06/2014 08:40 PM, andrel wrote:
> According to a friend of mine that has used InDesign for some personal
> projects, InDesign can export and import XML. That could mean that you
> only have to create a template and then insert the documentation by
> automatic search and replace. (I use the same technique to build simple
> websites.)
> Apparently InDesign even has scripting facilities, she has not used them
> herself. She is not a programmer, but a child of the WYSIWYG point and
> click generation. All in all it sounds to me as something that matches
> your interests and abilities. Perhaps she can even help you a bit. She
> has met people that use complex programs to do simple tasks before (i.e.
> we have worked together for some time).
OK. Well that all sounds like something worth looking into.
(I overheard the guy who's working on the documentation the other day.
We was explaining - as if this is a really complex and novel idea - how
he's managed to configure InDesign in such a way that it *automatically*
updates the table of contents and the index when you change something.
As if this is a really sophisticated idea, rather than - you know -
something that EVERY half-decent document production system should be
able to do out-of-the-box...)
It sounds like with some suitable tinkering, we could probably get quite
a nice workflow with this thing.
I wonder if there's any official documentation for it online. I'll take
a look...
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>
> I wonder if there's any official documentation for it online. I'll take
> a look...
https://helpx.adobe.com/ca/indesign.html
(You'll need to replace the "ca" bit of the URL...)
- Go to adobe.com
- Click on menu
- Click on the inDesign icon
- Click Learn & support
--
/*Francois Labreque*/#local a=x+y;#local b=x+a;#local c=a+b;#macro P(F//
/* flabreque */L)polygon{5,F,F+z,L+z,L,F pigment{rgb 9}}#end union
/* @ */{P(0,a)P(a,b)P(b,c)P(2*a,2*b)P(2*b,b+c)P(b+c,<2,3>)
/* gmail.com */}camera{orthographic location<6,1.25,-6>look_at a }
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Orchid Win7 v1 <voi### [at] dev null> wrote:
> On 18/06/2014 08:40 PM, andrel wrote:
> > According to a friend of mine that has used InDesign for some personal
> > projects, InDesign can export and import XML. That could mean that you
> > only have to create a template and then insert the documentation by
> > automatic search and replace. (I use the same technique to build simple
> > websites.)
> > Apparently InDesign even has scripting facilities, she has not used them
> > herself. She is not a programmer, but a child of the WYSIWYG point and
> > click generation. All in all it sounds to me as something that matches
> > your interests and abilities. Perhaps she can even help you a bit. She
> > has met people that use complex programs to do simple tasks before (i.e.
> > we have worked together for some time).
>
> OK. Well that all sounds like something worth looking into.
>
> (I overheard the guy who's working on the documentation the other day.
> We was explaining - as if this is a really complex and novel idea - how
> he's managed to configure InDesign in such a way that it *automatically*
> updates the table of contents and the index when you change something.
> As if this is a really sophisticated idea, rather than - you know -
> something that EVERY half-decent document production system should be
> able to do out-of-the-box...)
>
> It sounds like with some suitable tinkering, we could probably get quite
> a nice workflow with this thing.
>
> I wonder if there's any official documentation for it online. I'll take
> a look...
Good idea. I have had to work with indesign files given by clients and I managed
to work with it. I wouldn't compare the learning curve to Blender at all,
InDesign is a lot easier.
Alternatively afaik SVG supports feathered dropshadows and rounded boxes. I
think SVG could be the future of design because it seems to support just about
everything needed for print and web.
-Nekar Xenos-
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Le 19/06/2014 07:43, Nekar Xenos a écrit :
> Alternatively afaik SVG supports feathered dropshadows and rounded boxes. I
> think SVG could be the future of design because it seems to support just about
> everything needed for print and web.
svg has even draft about multipage... which, with the ability to use CSS
at top of svg file, might or might not be a good thing.
In formating of the page, there is already the World vs North-America
(A4 vs US letter). Either you designed your template to only use the
common area, dropping the margin (width 210 vs 216 mm, height 297 vs 279
mm, so 6 mm & 18 mm of white..), or you didn't and the change of paper
becomes "interesting" (truncated text, or repaginated with references
becoming wrong...)
A document is more than a collection of pages.
And remember: your documents will be migrated to the new company logo
and charts when the bigger corporation buy your company... or resell
it... or change its visual identity, or want to explore a new market.
Better keep a strict separation between formatting and content. (your
diagrams & pictures might show the company logo, but it should not be
copied inside every of them, it should be part of the formatting data
that can be referenced by them). The company name as well as the product
name are also not part of the content.
--
Just because nobody complains does not mean all parachutes are perfect.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Le 2014-06-19 02:27, Le_Forgeron a écrit :
> Le 19/06/2014 07:43, Nekar Xenos a écrit :
>
>> Alternatively afaik SVG supports feathered dropshadows and rounded boxes. I
>> think SVG could be the future of design because it seems to support just about
>> everything needed for print and web.
>
>
> svg has even draft about multipage... which, with the ability to use CSS
> at top of svg file, might or might not be a good thing.
>
> In formating of the page, there is already the World vs North-America
> (A4 vs US letter). Either you designed your template to only use the
> common area, dropping the margin (width 210 vs 216 mm, height 297 vs 279
> mm, so 6 mm & 18 mm of white..), or you didn't and the change of paper
> becomes "interesting" (truncated text, or repaginated with references
> becoming wrong...)
>
> A document is more than a collection of pages.
>
> And remember: your documents will be migrated to the new company logo
> and charts when the bigger corporation buy your company... or resell
> it... or change its visual identity, or want to explore a new market.
>
> Better keep a strict separation between formatting and content. (your
> diagrams & pictures might show the company logo, but it should not be
> copied inside every of them, it should be part of the formatting data
> that can be referenced by them). The company name as well as the product
> name are also not part of the content.
>
>
This.
I happen to work with commercial software packages that were bought,
renamed, and merged multiple times... It makes life interesting when
looking for upgrade logs. I imagine documentation writers must be
having a field day.
--
/*Francois Labreque*/#local a=x+y;#local b=x+a;#local c=a+b;#macro P(F//
/* flabreque */L)polygon{5,F,F+z,L+z,L,F pigment{rgb 9}}#end union
/* @ */{P(0,a)P(a,b)P(b,c)P(2*a,2*b)P(2*b,b+c)P(b+c,<2,3>)
/* gmail.com */}camera{orthographic location<6,1.25,-6>look_at a }
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 19-6-2014 8:27, Le_Forgeron wrote:
> Le 19/06/2014 07:43, Nekar Xenos a écrit :
>
>> Alternatively afaik SVG supports feathered dropshadows and rounded boxes. I
>> think SVG could be the future of design because it seems to support just about
>> everything needed for print and web.
>
>
> svg has even draft about multipage... which, with the ability to use CSS
> at top of svg file, might or might not be a good thing.
>
> In formating of the page, there is already the World vs North-America
> (A4 vs US letter). Either you designed your template to only use the
> common area, dropping the margin (width 210 vs 216 mm, height 297 vs 279
> mm, so 6 mm & 18 mm of white..), or you didn't and the change of paper
> becomes "interesting" (truncated text, or repaginated with references
> becoming wrong...)
Huh, I though current paper sizes were IPad, IPad mini, IPhone,
1600x1200,1280x1024,..., and whatever the android phones/tablets use.
--
Everytime the IT department forbids something that a researcher deems
necessary for her work there will be another hole in the firewall.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On Thu, 19 Jun 2014 01:43:15 -0400, Nekar Xenos wrote:
> I wouldn't compare the learning curve to Blender
> at all, InDesign is a lot easier.
The idea in the comparison (on my part) was not to say that they're
equally difficult, but that the UI seems to get in the way (at least with
FrameMaker, I've no direct experience with InDesign) until you understand
the workflow that it's designed for. I've used a number of Adobe
products over the years, and have found that to be the case.
IOW, it's not about "this is more difficult than that" but that it is
important to learn the tool, and there is a learning curve before one
becomes familiar enough to be very productive.
Jim
--
"I learned long ago, never to wrestle with a pig. You get dirty, and
besides, the pig likes it." - George Bernard Shaw
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 19/06/2014 4:20 PM, andrel wrote:
>
> Huh, I though current paper sizes were IPad, IPad mini, IPhone,
> 1600x1200,1280x1024,..., and whatever the android phones/tablets use.
>
So cynical for one so young. ;-)
--
Regards
Stephen
I solemnly promise to kick the next angle, I see.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Jim Henderson <nos### [at] nospam com> wrote:
> On Thu, 19
> IOW, it's not about "this is more difficult than that" but that it is
> important to learn the tool, and there is a learning curve before one
> becomes familiar enough to be very productive.
>
> Jim
>
True. It did take some time to figure things out.
The documentation and Google helped a lot
-Nekar Xenos-
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |