algorithmicalgorithmscross-referencing
\usepackage{algorithm}
\usepackage{algorithmic}
\begin{algorithm}[tb]
\caption{Algorithm}
\label{alg}
\begin{algorithmic}[1]
\STATE blalblabla \label{cond1}
\STATE blablabla \label{cond2}
\STATE return to step \ref{cond2}.
\end{algorithmic}
\end{algorithm}
As you see it gives "return to step 1" (instead of 2)
The IEEEtran's documentation suggests:
B. Algorithms
IEEE publications use the
figureenvironment to containalgorithmsthat are not to be a part of the main text flow. Peter Williams’ and Rogerio Brito’salgorithmic.stypackage [24] or Szász János’algorithmicx.stypackage [25] (the latter is designed to be more customizable than the former) may be of help in producing algorithm-like structures (although authors are of course free to use whatever LaTeX commands they are most comfortable with in this regard). However, do not use the floatingalgorithmenvironment ofalgorithm.sty(also by Williams and Brito) oralgorithm2e.sty(by Christophe Fiorio) as the only floating structures IEEE uses arefigures andtables. Furthermore, IEEEtran will not be in control of the (non-IEEE) caption style produced by thealgorithm.styoralgorithm2e.styfloat environments.
So, as suggested, do not use the algorithm floating environment; you can wrap your algorithm inside a figure (or figure*) environment (if a caption is required and the captions are to be IEEEtran compliant) and use the algorithmicx package ; something like this:
\documentclass{IEEEtran}
\usepackage{algpseudocode}
\begin{document}
\begin{figure}
\begin{algorithmic}[1]
\Procedure{Euclid}{$a,b$}\Comment{The g.c.d. of a and b}
\State $r\gets a\bmod b$
\While{$r\not=0$}\Comment{We have the answer if r is 0}
\State $a\gets b$
\State $b\gets r$
\State $r\gets a\bmod b$
\EndWhile\label{euclidendwhile}
\State \textbf{return} $b$\Comment{The gcd is b}
\EndProcedure
\end{algorithmic}
\caption{Euclid's algorithm}\label{euclid}
\end{figure}
\end{document}
If no caption is required, then simply don't use the figure environment.
The algorithms bundle provides the user with the flexibility to change things to suit their needs, albeit somewhat manually. To that end, I suggest creating a language-specific environment to manage the languages you're using, say frenchalgorithm and englishalgorithm:
\documentclass{article}
\usepackage{algorithm,algorithmic,lipsum}
\usepackage[T1]{fontenc}
\usepackage[french,english]{babel}
\newenvironment{englishalgorithm}[1][]
{\begin{algorithm}[#1]
\selectlanguage{english}%
\floatname{algorithm}{Algorithm}%
\renewcommand{\algorithmicif}{\textbf{if}}%
\renewcommand{\algorithmicthen}{\textbf{then}}%
\renewcommand{\algorithmicend}{\textbf{end}}%
% Set other language requirements
}
{\end{algorithm}}
\newenvironment{frenchalgorithm}[1][]
{\begin{algorithm}[#1]
\selectlanguage{french}%
\floatname{algorithm}{Algorithme}%
\renewcommand{\algorithmicif}{\textbf{si}}%
\renewcommand{\algorithmicthen}{\textbf{alors}}%
\renewcommand{\algorithmicend}{\textbf{fin}}%
% Set other language requirements
}
{\end{algorithm}}
\begin{document}
\lipsum[1]
\begin{englishalgorithm}[H]
\caption{An algorithm}
\begin{algorithmic}[1]
\STATE This is a statement
\IF{abc}
\STATE This is another statement
\ENDIF
\end{algorithmic}
\end{englishalgorithm}
\begin{frenchalgorithm}[H]
\caption{Another algorithm}
\begin{algorithmic}[1]
\STATE This is a statement
\IF{abc}
\STATE This is another statement
\ENDIF
\end{algorithmic}
\end{frenchalgorithm}
\lipsum[2]
\end{document}
You'd have to define each of the translated keywords manually. The same would go if you were using the algorithmicx package.
More about the above changes is briefly discussed in sections 3.14.3 Customization and 4.4 Customization of the algorithms documentation.
I don't speak French...
Best Answer
If you use a label and a ref, you need to compile your document twice. Otherwise an error may occur.
Which gives when compilied twice: