We do not generate it at main level, like we want to, we generate at a
lower level today.
if you look in the .po files, you will see the filereferences are inserted
as comments, and there are no rules saying that an editor shall keep the
comments in exact the same place. If just one comments moved
On 11/6/12 12:23 PM, jan iversen wrote:
> On 6 November 2012 11:58, Dwayne Bailey wrote:
>
>> On 6 November 2012 10:25, jan iversen wrote:
>>
>>> I prefer .xlif because it is easier to handle, and I do not need to store
>>> information (like module/source file) in comments.
>>>
>>
>> You still n
Hi
soon is real soon, I have already had a mail conversation with juergen, and
I understand that Dwayne first of all has a new release, and secondly is
interested in some of the ideas I had.
Jan.
On 14 November 2012 13:38, Andrea Pescetti wrote:
> On 06/11/2012 jan iversen wrote:
>
>> However
On 06/11/2012 jan iversen wrote:
However the issue is still open, and I think andrea/juergen will have a
talk with you on that subject, and a couple of pootle server details during
this week.
This indeed happened. I believe Juergen and Dwayne will soon (for a
reasonable definition of "soon"!)
I am not a deep makefile specialist, but the last project we worked on, had
lines similar to what I wrote, and the process was just started once for
all files on the line.
in our case I would say:
dMake genLang
And that should cause dmake to start "genLang -m -t src1.hrc src2.xcd "
I w
On 11/6/12 5:59 PM, jan iversen wrote:
@andre:
I just saw one line in your mail, that I forgot to respond toyou look
for the interesting part of the code, the file tree scanner.
There are no tree scanning with the new concept, it is done by the makefile.
Each makefile (or build.lst) is ext
@andre:
I just saw one line in your mail, that I forgot to respond toyou look
for the interesting part of the code, the file tree scanner.
There are no tree scanning with the new concept, it is done by the makefile.
Each makefile (or build.lst) is extended with something like:
genLang: src1
HI
Thanks for your input, it is not too harsh, I prefer straight comments than
something I have to read several times to understand.
I will not disturb your session, but I have put some reasons/answers below.
rgds
Jan I.
On 6 November 2012 14:38, Andre Fischer wrote:
> On 11/4/12 1:55 PM, jan
On 11/4/12 1:55 PM, jan iversen wrote:
Hi.
I have finished the control part of the new localization tool, and
before I walk further down the line (writing/converting all the
translations parts) I would like to have checked if the code is ok in
terms of standard, readability and expectations (
On 6 November 2012 11:58, Dwayne Bailey wrote:
> On 6 November 2012 10:25, jan iversen wrote:
>
> > I prefer .xlif because it is easier to handle, and I do not need to store
> > information (like module/source file) in comments.
> >
>
> You still need to store some reference right?
>
Yes, we in
On 6 November 2012 10:25, jan iversen wrote:
> I prefer .xlif because it is easier to handle, and I do not need to store
> information (like module/source file) in comments.
>
You still need to store some reference right?
I think preference in some way should be decided by what people are doing
I have made a description of a new workflow, where this code is only part
of it. I do not know it you have seen otherwise here is a link:
http://wiki.openoffice.org/wiki/Localization_AOO/new_proposal
Jan.
On 6 November 2012 10:54, Dwayne Bailey wrote:
> On 4 November 2012 12:55, jan iversen w
I prefer .xlif because it is easier to handle, and I do not need to store
information (like module/source file) in comments.
However the issue is still open, and I think andrea/juergen will have a
talk with you on that subject, and a couple of pootle server details during
this week.
thanks for co
On 4 November 2012 12:55, jan iversen wrote:
> Hi.
>
> I have finished the control part of the new localization tool, and before
> I walk further down the line (writing/converting all the translations
> parts) I would like to have checked if the code is ok in terms of standard,
> readability and
14 matches
Mail list logo
