Problem with the filename case of help strings

View: New views
6 Messages — Rating Filter:   Alert me  

Problem with the filename case of help strings

by Jaiver Enciso :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi All,

I'm trying to tag (adding the translator's information, md5, and so on)
some language files for the Spanish translation of the help strings,
however, the problem arises when I use the command:

$ octlang tag "function"

where "function" is the filename of the function that has been
translated. Since there are files named with capital letters (e.g.
OCTAVE_HOME, O_ASYNC, O_CREAT, etc.), octlang complains about it and
doesn't allow to tag the given files.

On the other hand, when one tries to update the document base
(a.k.a.Updating base http://octave.sourceforge.net/translation.html),
capitalized filenames (one for each letter of the alphabet) are created
out of the initial of the help files. As you might suspect, this
produces a conflict with svn since the version system isn't able to
manage filenames with uppercase.

So I wonder, is there any one else aware of this issue? if so, could any
of you guys provide me insights to get rid of it?

P.S.: The Spanish package is about 400 files big and it would be
wonderful if it is listed with the other Octave packages :).


Best regards,
--
Ing. Javier Enciso                Email: encisomo@...
CSE Master Student                Tel.:  +49 (0)174-213-9631
Technische Universität München    WWW:   http://home.in.tum.de/~encisomo


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

signature.asc (204 bytes) Download Attachment

Re: Problem with the filename case of help strings

by Søren Hauberg :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

søn, 30 08 2009 kl. 00:43 +0200, skrev Javier Enciso:
> So I wonder, is there any one else aware of this issue? if so, could any
> of you guys provide me insights to get rid of it?

I must confess that I don't know the first thing about the translation
system, so I can't be of much help :-(

Could you possibly describe the problem in some more detail? From what I
understand, the problem is that you end up creating a file called 'xxx'
and another one called 'XXX', which then creates problems on file
systems that treats upper and lower case letters identically. If so,
then why can't these two files simply be placed in two different
directories?

> P.S.: The Spanish package is about 400 files big and it would be
> wonderful if it is listed with the other Octave packages :).

The reason why it currently isn't listed, is that the package didn't
build why I made the last release. At the moment I don't have the time
to make a new release, so unless somebody else steps up, this will have
to wait a while :-(

Søren


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Problem with the filename case of help strings

by Jaiver Enciso :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Søren Hauberg schrieb:

> søn, 30 08 2009 kl. 00:43 +0200, skrev Javier Enciso:
>  
>> So I wonder, is there any one else aware of this issue? if so, could any
>> of you guys provide me insights to get rid of it?
>>    
>
> I must confess that I don't know the first thing about the translation
> system, so I can't be of much help :-(
>
> Could you possibly describe the problem in some more detail? From what I
> understand, the problem is that you end up creating a file called 'xxx'
> and another one called 'XXX', which then creates problems on file
> systems that treats upper and lower case letters identically. If so,
> then why can't these two files simply be placed in two different
> directories?
>  
Hi Søren,

I went though the logic of the scripts and have found some
inconsistencies within the file called admin/split_docstrings. I already
fixed them and committed the changes.

Btw, the issues were:
1. The filename was created out of the first letter of the command name,
and
2. The for loop didn't take into account the last command name in the
DOCSTRINGS files.

>  
>> P.S.: The Spanish package is about 400 files big and it would be
>> wonderful if it is listed with the other Octave packages :).
>>    
>
> The reason why it currently isn't listed, is that the package didn't
> build why I made the last release. At the moment I don't have the time
> to make a new release, so unless somebody else steps up, this will have
> to wait a while :-(
>  
OK, good to know.

Javier Enciso
> Søren
>
>  


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Problem with the filename case of help strings

by Søren Hauberg :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

lør, 05 09 2009 kl. 15:44 +0200, skrev Jaiver Enciso:
> I went though the logic of the scripts and have found some
> inconsistencies within the file called admin/split_docstrings. I already
> fixed them and committed the changes.
>
> Btw, the issues were:
> 1. The filename was created out of the first letter of the command name,
> and
> 2. The for loop didn't take into account the last command name in the
> DOCSTRINGS files.

Does that mean the issue is fixed?

Søren


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

Re: Problem with the filename case of help strings

by Jaiver Enciso :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Sat, 2009-09-05 at 06:52 -0700, Søren Hauberg wrote:

> lør, 05 09 2009 kl. 15:44 +0200, skrev Jaiver Enciso:
> > I went though the logic of the scripts and have found some
> > inconsistencies within the file called admin/split_docstrings. I already
> > fixed them and committed the changes.
> >
> > Btw, the issues were:
> > 1. The filename was created out of the first letter of the command name,
> > and
> > 2. The for loop didn't take into account the last command name in the
> > DOCSTRINGS files.
>
> Does that mean the issue is fixed?
Yes, It does. Although a new question emerges...

Consider, for example, the definition of the 'warranty' help string
given by the octave-3.2.2/src/DOCSTRINGS file, say,
warranty
@c toplev.cc
-*- texinfo -*-
@deftypefn {Built-in Function} {} warranty ()
Describe the conditions for copying and distributing Octave.
@end deftypefn

out of this definition, and after execute the admin/split_docstrings
script, a new file called 'warranty' will be created, replacing the old
one, at octave-forge/language/base/help/octave/ with the following
content:
@c toplev.cc
-*- texinfo -*-
@deftypefn {Built-in Function} {} warranty ()
Describe the conditions for copying and distributing Octave.
@end deftypefn

So far, the files located at octave-forge/language/base/help/octave/
start omit the line "@c toplev.cc", instead they start with "-*- texinfo
-*-", so the question is, is that behavior intended? in other other
words, should the content of the files located at
octave-forge/language/base/help/octave/ start with

-*- texinfo -*-

or something like:

@c toplev.cc

which is actually the information one can get from the
octave-3.2.2/src/DOCSTRINGS file and vary for each command?




>
> Søren
>

Best regards,
--
Ing. Javier Enciso                Email: encisomo@...
CSE Master Student                Tel.:  +49 (0)174-213-9631
Technische Universität München    WWW:   http://home.in.tum.de/~encisomo


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev

signature.asc (204 bytes) Download Attachment

Re: Problem with the filename case of help strings

by Søren Hauberg :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

lør, 05 09 2009 kl. 16:36 +0200, skrev Javier Enciso:

> Yes, It does. Although a new question emerges...
>
> Consider, for example, the definition of the 'warranty' help string
> given by the octave-3.2.2/src/DOCSTRINGS file, say,
> warranty
> @c toplev.cc
> -*- texinfo -*-
> @deftypefn {Built-in Function} {} warranty ()
> Describe the conditions for copying and distributing Octave.
> @end deftypefn
>
> out of this definition, and after execute the admin/split_docstrings
> script, a new file called 'warranty' will be created, replacing the old
> one, at octave-forge/language/base/help/octave/ with the following
> content:
> @c toplev.cc
> -*- texinfo -*-
> @deftypefn {Built-in Function} {} warranty ()
> Describe the conditions for copying and distributing Octave.
> @end deftypefn
>
> So far, the files located at octave-forge/language/base/help/octave/
> start omit the line "@c toplev.cc", instead they start with "-*- texinfo
> -*-", so the question is, is that behavior intended?

Sorry, but I don't know :-(

Does anybody else know? Otherwise, I'm afraid you'll have to investigate
this one yourself :-(

Søren


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Octave-dev mailing list
Octave-dev@...
https://lists.sourceforge.net/lists/listinfo/octave-dev